►
From YouTube: SIG Cloud Provider 2023-09-27
Description
Meeting agenda: https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/edit#bookmark=id.1h3q0nfeyssb
A
All
right
welcome.
Everyone
today
is
Wednesday
September,
27
2023,
and
this
is
the
Sig
cloud
provider.
Meeting
Sig
cloud
provider
is
a
sub-project
of
kubernetes
sigs
and
as
such,
we
follow
their
meeting
guidance
which
basically
boils
down
to.
Please
treat
everyone
as
you
would
expect
to
be
treated
and
explicitly
so,
please
be
kind
to
each
other
and
also
please
raise
your
hand
if
you'd
like
to
be
called
on
and
I
will
call
on
you
so
yeah
with
that.
D
D
My
PR
is
mostly
extension
on
top
of
an
exchanges
to
rested
of
a
book
as
a
validating
web
configuration
and
the
episode
that
way
like
now.
With
this
like,
we
should
be
able
to
use
the
I
mean
the
cloud.
Progress
should
be
able
to
use
the
framework
to
automatically
just
write
the
webwork
logic
and
get
the
auto
registration
terms.
A
A
A
A
D
A
Formatting
here,
okay,
so
you
know
I've
been
doing
a
lot
of
work.
Looking
at
this
looking
at
updating
the
cap
and
we
need
to
answer
a
few
of
the
Readiness
questions
and
then
a
couple
questions
have
come
up
on
review
that
I
wanted
to
bring
here
to
the
Sig
to
see
what
people
thought
so
I'll
just
I'll
start
with
these
questions
on
review,
because
they're
here
and
then
I'm
going
to
switch
to
another
terminal.
So
we
can
look
at
the
other
questions.
A
So
Mo
Khan
had
a
few
things
that
he
brought
up
here
and
some
of
these
I'm
still
working
on.
But
you
know
we
got
down
to
a
discussion
where
I
think
you
know.
Moa
has
kind
of
two
questions
here.
One
is
about
doing
like
the
forward
migration
and
then
the
backward
migration
you
know
do
we
have
any
tests
that
show
that
this,
wouldn't
that
this
wouldn't
break
anything
by
going
forward
and
backward
like
that
and
I
think
you
know
part
of
what
he's
this
comment.
A
That
I'm
highlighting
here
is
where
we
kind
of
got
into
this
discussion,
and
you
know
I
thought
that
he
was
talking
about
the
code
in
the
KCM,
but
I
think
what
MO
is
asking
is
like.
When
we
do
the
migration
to
the
external
Cloud
providers,
do
we
have
any
tests
that
are
showing
the
migration
to
them
and
then
the
migration
back,
that
nothing
is
getting
broken
in
these
fields
and
I?
Don't
think
we
do
have
any
tests
like
that
and
I'm
not
sure
what
we
should.
A
You
know
how
we
should
respond
to
that
and
then
the
other
question
he
asked
me
as
well
was
kind
of
getting
into
like
are
we
you
know?
Have
we
done
anything
to
confirm
that
the
new
code
is
not
creating
more
load
than
the
old
code
and
I'm
a
little
bit
I'm
a
little
bit
confused
by
this
one,
because,
like
I
mean
was
where
we
started,
was
the
the
old
code
became
the
new
code?
But
then
those
projects
have
become
kind
of
external
projects
managed
separately
by
each
of
the
providers.
A
So
it
feels
a
little
bit.
You
know
kind
of
out
of
scope
for
me,
and
you
know
where
did
I
talk
about
this?
You
know
like
it
feels
a
little
bit
out
of
scope
for
me.
You
know
his
original
question
was
you
know,
whatever's
been
taken
to
make
sure
the
new
code
doesn't
create
a
bunch
of
extra
load
that
the
old
code
didn't
and
since
we're
moving
to
external
CCMS
at
this
point,
doesn't
that
become
like
a
purview
of
those
CCMS
like?
A
A
B
C
Well,
what
we
can
say,
though,
is
that
all
of
the
controllers,
like
the
core
controllers,
like
they're,
actually
the
exact
same
implementation
that
we
have
in
tree
like
the
controllers
themselves
and
the
calls
they
make
to
the
API
server
are
all
the
same.
And
the
main
difference
really
is
the
change
in
the
actual
like
provider
implementation.
C
So
if
you
call
like
one
of
the
methods
and
the
interfaces,
it's
possible
that,
like
the
external
implementation,
may
do
like
extra
calls
compared
to
the
entry
implementation,
but
like
you're,
saying,
like
that's
kind
of
implementation,
details
per
provider,
so
I
don't
know
if
that
helps.
Just
saying
like
we're
not
actually
like
the
actual
core
controllers
are
actually
the
same.
We're
just
moving
the
controller
logic
from
one
component
to
another
right.
C
C
C
The
other
point
also,
we
could
just
say
like
hey,
like
we
actually
have
a
lot
of
providers
like
using
already
using
this
in
production,
and
it's
quite
vetted
like
in
based
on
like
real
clusters
and
and
users.
But
it's
not
necessarily
like
a
strong
data
point.
It's
more
anecdotal,
but
in
the
past,
like
that's,
been
a
fine
justification
as
well.
So
yeah.
A
D
Yeah,
like
we
had
done
like
I,
mean
this
credibility.
Testing
like
as
part
of
the
not
I
mean
not
just
for
this,
but
we
do
this
as
part
of
every
release
so
that
we
so
as
part
of
the
novel
process
we
had
done
it
even
been
going
to
the
external
protosses.
So
yeah
we
didn't
so.
This
has
been
tested
scale
from
AWS
set.
A
Okay,
this
is
good
and
thank
you
Andrew
and
Kirsten,
like
I'll,
try
to
form
some
of
this
into
a
response.
I'm
guessing
I'm
thinking,
Moe's,
probably
going
to
get
back
to
me
today.
So
I'll
just
keep
the
conversation
going,
but
if,
if
either
of
you
could
take
a
review
on
this
and
maybe
add
your
thoughts
into
this
discussion
chain
like
that,
would
that
would
really
be
helpful.
D
A
A
You
know
this
is
where
this
is
where
I
was
kind
of
having
a
little
bit
of
trouble
because,
like
you
know,
Moe
was
saying,
like
you
know,
say:
a
field
in
a
resource
was
always
set
to
five
with
the
Legacy
code,
and
then
it
gets
sent
to
six
by
the
new
code
on
a
downgrade.
The
resource
would
still
exist,
but
now
the
old
code
would
see
a
six
instead
of
a
five.
You
know,
which
you
may
not
understand
now
kind
of
my
response
here.
A
You
know
I
tried
to
restate
the
problem
because
I
wasn't
quite
understanding
it,
but
I
said,
like
you
know
the
former
entry
controllers.
You
know
that
became
the
external
CCMS
I,
don't
think
they're
actually
making
modifications
to
the
node
or
service
objects
in
a
way.
That
would
do
that,
but
I
don't
think
we
have
a
test
that
demonstrates
that
does
any.
Is
there
any
like
data?
We
could
back
this
up
with
or
I
mean
I
I
had
kind
of
assumed
that
everything
was
just
working.
A
The
same
we'd
already
migrated
like
the
labels
and
everything
like
all
that
work
had
been
done
before
things
got
switched,
but
I
don't
know
if
it's
possible
that
a
CCM
could
modify.
You
know
like
a
node
or
service
object
in
a
way
that
would
create
this
incompatibility
and
I'm,
not
sure
how
we
demonstrate
this.
C
A
He
didn't
have
a
concrete
field
here.
That's
why
I
was
trying
to
turn
it
into
a
concrete
example,
because
I'm
not
I'm
I'm,
not
sure
that
I'm
not
sure
how
much
context
MO
is
bringing
into
this
like
I,
I
thought
I.
Think
maybe
he's
looking
at
this
like,
like
yeah,
we're
upgrading
some
component
that
has
a
an
API
crd
associated
with
it
that
they're
tightly
coupled
or
something.
But
it's
not
really
the
case
here.
As
far
as
I
understand.
C
We're
just
importing
over
like
the
same
controllers,
between
components
and
the
the
logic
I
mean
the
backing
implementation
might
change
what
specific
values
that
the
cloud
provider
would
return
to.
Those
controllers
which
could
change
certain
field,
values,
I,
guess
right,
but
I,
don't
see.
It's
not
I,
can't
think
of
anything
that
would
be
considered
like
incompatible
or
breaking
or
like
unusual,
because
it's
it's
for
the.
A
C
A
That
wouldn't
be
aware
that,
like
that's
all
kind
of
coded
into
the
core
framework,
but
it's
possible
that
someone
could
create
a
CCM
that
didn't
you
know,
that's
the
only
thing
I
could
think
of.
But
again
this
puts
the
onus
back
on
like
okay,
we're
part
of
the
activity.
We're
doing
here
is
migrating
these
CCMS
to
external
repos.
That
will
be
managed
by
different
project
teams,
like
these
components
are
no
longer
being
shipped
as
part
of
kubernetes,
so
the
user
has
some
responsibility
to
find
an
external
CCM,
and
then
the
question
is
like
okay.
A
C
A
C
I
guess
like
I
guess
he
does
have
a
good
point,
though,
that
maybe
we
should
oh
it's
possible
that
Jared
might
have
added
a
test
for
this
already.
Actually,
we
just
have
to
dig
it
up,
but
a
test
that
does
some
like
run
some
basic
edoe
tests
like
while
it's
entry
and
then
migrates
to
this,
like
the
CCM
leader,
election
migration
logic
to
auditory
right.
C
A
Currently,
you
know
we
only
deep
deeply
test
the
cloud
controllers
on
GCE
right
and
with
a
subset
of
of
those
tests
running
on
AWS
and
a
subset
of
those
tests
running
on
Azure
and
as
far
as
I
know,
like
openstack
and
vsphere
used
to
be
part
of
the
entry
and
I,
don't
think
those
were
ever
tested
using
the
core
tests,
so
I
mean
we
had
code
in
there
before
that
was
never
tested
and
I
totally
I
love,
adding
more
tests
and
stuff
like
that.
But
it's
starting
to
get
to
the
point
where
it's
like.
A
Okay,
there
is
no
default
cloud
provider,
that's
packaged
with
kubernetes,
so
a
choice
first
has
to
be
made
that
you're
going
to
run
an
external
CCM
and
then
now
you
have
to
run
this
upgrade
downgrade
test
and
it's
I
think
that's
just
pushing
our
testing
kind
of
Beyond
where
we've
been
in
the
past.
So,
like
I'm,
not
saying
it's
a
bad
idea
to
do
that
kind
of
testing,
but
it
is
a
big
effort.
A
Yeah
like
we.
We
do
this
kind
of
testing
on
openshift
internally,
a
red
hat,
but
we
have
all
sorts
of
operators
that
we've
put
in
place
to,
like.
You
know
to
manage
the
external
to
internal
CCM
like
Transit
and
whatnot
and
like
I,
don't
I,
don't
think
we
have
anything
equivalent
in
kubernetes,
so
someone's
gonna
have
to
write
that
test
and
manually
write
all
these
like
transactions
to
like
upgrade
the
cluster
then
downgrade
the
cluster.
You
know
that's.
B
B
C
A
A
C
A
So
I
I
appreciate
this
conversation.
Deeply
and
I
will
try
to
express
these
points
in
the
pr
I
have
a
feeling
that
I
have
a
feeling
that
I'm
not
expressing
myself
in
a
way
that
is
coming
across
very
well
to
Mo,
though,
because
I'm
I'm,
failing
to
make
some
of
these
points
so
again,
like
any
help,
would
be
greatly
appreciated.
C
A
C
A
B
A
A
Like
you
know,
how
can
a
rollout
fail?
Can
it
impact
running
work,
I
mean
I,
guess
I
at
some
level
like
I,
can
try
to
go
through
and
answer
some
of
these,
but
like
other
ones
like
the
specific
metrics
to
inform
a
rollback
like
I
could
use
some
help.
Answering
some
of
these
I
don't
know
if
we
want
to
try
to
go
through
these
here
in
this
meeting,
I'd
be
happy
to
if,
if
folks
are
up
for
it,.
A
C
A
A
A
A
C
A
C
A
C
D
C
C
A
C
A
B
A
C
C
B
C
A
A
C
B
B
A
A
B
A
A
C
A
A
C
A
B
C
Is
not
necessarily
to
have
answers
to
all
these
questions
like
or
like
a
good
answer
to
all
these
questions,
but
my
understanding
is
that
it's
just
to
ensure
that
we've
kind
of
asked
ourselves
some
questions
and
thought
about
it.
So
I
think
what's
important.
Is
that,
like
whatever
we
put
in
here,
it's
kind
of
just
proving
that
we've
kind
of
like
done
the
exercise
of
thinking
through
some
of
these.
C
So
so,
for
for
this,
one
I
would
say
like
what
steps
should
be
taken
like
the
obvious
ones,
are
like.
Okay,
well
check
the
system
logs
like
what's
what's
the
issue
right,
if
it's
authentication
issue
like
make
sure
your
R
back
is
correct.
If
it's
a
quota
issue
with
your
cloud
provider,
apis
like
ensure
you
have
like
ensure
you
increase
your
quota,
make
sure
you
have
enough
quota
if
it's.
A
C
C
A
Cool
I
think
that's
good
and
thank
thank
you
so
much
Andrew
I'm,
just
going
to
scroll
I,
think
that's
it
now.
So
I
will
update
this
again.
You
know
one
of
the
things
I'm.
One
of
the
things
I'm
concerned
about
here.
Is
that,
like
we're,
you
know
next
Friday
is
the
is
the
freeze
date
for
this
and
I'm
hopeful.