►
From YouTube: Kubernetes SIG Cluster Lifecycle - Cluster API AWS
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
B
A
A
B
I
want
to
talk
about
like
if
we
like,
if
we're
targeting
this
for
the
Alpha.
What
do
we
want
to
expose?
It
seems
that
we
don't
want
to
expose
Covidien
configs
upstream,
yet
so
I
was
were
thinking.
We
might
want
to
expose
more
configuration
now
for
get
up
this
provider
maybe
contributor
later
upstream.
If
there
is
enough
consensus,
it
would
be
like
just
an
optional
package
that,
like
other
providers,
can
use
to
later
on,
but
what
configuration
that
we
want
exposed
to
the
user?
That's
the
main
question.
I
have.
A
Yeah,
so
there's
a
trade-off
really
because
there's
already
some
configuration
that's
already
exposed
through
the
cluster
object,
specifically
the
pod
ciders
and
the
server-side
earths.
That
presents
a
challenge.
If
we
just
expose
the
cube,
ATM
config
wholesale,
which
is
the
easiest
option
to
expose,
can
fake
because
then
we
don't
have
to
kind
of
marshal
between
different
configured
checks,
so
you
know:
do
we
want
to
sit
there
and
just
expose
the
cube,
ATM
config
and
then
somehow
merge
those
options
that
can
be
said
externally
somehow
or
how
do
we
want
to
handle
that?
B
B
But
that
means
we
will
have
to
like
kind
of
render
that
end
and
then
yes,
we
could
go
in
and
merge.
I
don't
know
if
there
is
that
any
patches
like
a
library
that
we
can
use
for
that,
or
that
we
will
have
to
write
our
own
I'm,
more
leaning
to
always
the
first
one,
which
is
the
simplest
one
for
now
and
see
the
use
cases
later.
A
A
Because
then
you
know,
even
once
we
break
cube
ATM
out.
We,
we
don't
necessarily
want
to
be
tied
to
a
specific
version
of
cube
ATM
and
that's
part
of
the
reason
why
we
were
pushing
for
for
beta
for
the
cube
ATM
configured
so
that
it
would
be
a
stable
version
across
multiple
releases
of
kubernetes
in
qadian.
But.
C
Because
what
some
people
do
too,
is
they
literally
the
format
and
just
import
that
or
just
create
their
own
duplicate
version
of
types
with
just
the
struct
so
that
we
can
serialize
properly?
And
that
is
a
easy
way
to
get
around
this
and
that's
what
other
people
have
done
with
V
1
beta,
1
you're,
pretty
much
safe,
so
famous.
C
B
D
Sorry
I
was
just
saying:
why
can't
we
just
vendor
or
cake
/
it
yeah,
because.
C
B
C
B
B
A
You
know
I
think
we
probably
need
to
touch
base
again
with
the
field
folks
and
other
kind
of
venues,
oriented
people
and
and
get
prioritization
on
which
which
items
are
most
important
to
them
again,
and
we
can
bring
that
up
again.
The
next
time
we
have
kind
of
a
demo
yep
okay,
this
week.
Actually,
oh,
it.