►
Description
KEP 1771 - Cloud Provider versioning scheme
Docs accuracy with Node Controller
Plans to test Cloud Provider feature gates
A
Welcome
to
the
2021
thursday
november
4th
sig
cloud
provider,
cloud
provider
extraction
working
group
meeting:
this
meeting
is
part
of
syd
cloud
provider,
kubernetes
and
cncf,
and
our
our
various
rules
and
policies
are
to
be
kind,
inclusive
and
respectful
of
others.
So
yeah,
please
do
that
all
right.
A
A
I
think
the
pertinent
part
is
that
the
major
and
minor
version
numbers
of
the
cloud
provider
should
be
tracking
the
kubernetes
version
they
intend
to
support.
Part
of
this
is
intended
to
make
it
easy
for
a
customer
to
understand
what
level
of
conformance
they're
getting
right.
So
if
you
say
that
you're,
if
you
say
that
you
are
conformant
approved
at
kubernetes
116,
then
we'd
like
your
version
to
be
say,
116,
to
match
the
kubernetes
to
116,
which
would
then
match
the
116
conformance
plan.
B
Yeah,
so
we've
been
doing
some
reviews
on
our
end
as
we
prepare
for
an
internal
security
review
of
some
of
our
stuff,
and
we
were
going
through
the
upstream
documentation
again
and
there's
this
line
in
the
cloud
controller
docs
that
says
you
know
the
node
controller
is
responsible
for
creating
node
objects.
When
new
servers
are
created
in
your
cloud
infrastructure
that
did
not
seem
accurate
to
us.
I
believe
that
would
be.
A
How
do
I
there?
We
go
sorry
about
that.
Generally,
whatever
your
deployment
system
is
or
possibly
your
your
node,
auto
scaler
is
to
create
the
actual
node
object,
and
only
once
it's
created,
then
the
cloud
node
controller
is
going
to
kick
in
to
actually
for
lack
of
a
better
term
populate
the
node,
but
it
isn't
actually
create
the
node,
because
it's
to
create
the
node,
it
would
have
to
be
polling
the
cloud
provider
and
as
far
as
and
we
we,
that
is
not
something
that
we
do.
B
B
Yeah
so
this
was,
you
know:
we've
been
doing
a
lot
of
tests
recently,
integrating
the
gcp
cloud
provider
into
our
releases
as
well,
and
this
you
know
so
mikhail
fidocin
who's
been
opening.
Some
of
these
bugs
he's
just
been
coming
across
a
few
bugs
as
he
goes
through
this,
and
I
just
wanted
to
kind
of
raise
the
issue
here,
just
to
get
a
little
more
attention.
B
A
A
A
A
The
cube
up
script
sets
the
cloud
provider
facts
which
will
cause
things
like
the
cubelet
and
the
cube
api
server
to
bomb
out
immediately
based
on
those
feature
gates,
so
it
would
be,
and
then
we
once
we
get
that
going.
We
should
then
get
a
list
of
all
of
the
tests
that
are
going
to
break
and
we
will
hopefully
then
have
a
list
of
work
to
be
done
before
we
can
move
those
feature
gates
to
beta
or,
if
we'll
find
something
else
wrong
and
have
to
yet
another
step
to
do.