►
From YouTube: SIG Cloud Provider 2022-08-17
A
A
A
D
A
C
A
C
D
B
A
A
D
A
B
A
Okay,
cool,
okay:
I
think
those
are
the
only
two
issues
sitting
in
triage
for
this
one
I'll,
also
I'll
leave
it
out
of
triage
just
so
that
we
take
a
look
at
it
in
two
weeks
and
follow
back
up
and
cool
yeah.
Let's
go
through
what's
up
project
updates.
If
everybody
wants
to
take
a
few
seconds,
if
you
have
an
update,
just
add
it
to
the
list.
B
B
B
Those
very
helpful
issues
that
were
just
like
basically
go
fix
your
tests,
people
and
I
wanted
to
say
that
we
have
been
paying
attention
to
that
and
in
provider
azure
we
went
and
got
all,
but
one
of
our
failing
tests
are
currently
fixed,
so
yeah.
If
you
click
on
that
link
and
search
for
azure,
there
is
only
one
that
is
currently
failing.
A
B
Awesome,
I'm
just
just
a
reminder
to
all
of
us
to
pay
attention
to
these
family
tests
issues
that
nick
had
opened
for
us
because
it
is
yeah
for
azure.
If
you,
if
you
search
for
azure,
you
will
find
there
is
one
right
now
yep,
but
I
think
that
we
can
all,
I
think,
it'll
be
impossible
for
all
of
us
to
have
zero
failing
tests
forever.
But
I
bet
we
can
all
follow
what
nick
asked
us
to
do
and
open
those
go
pursue
some
of
your
failing
tests
and
I
bet
it'll
be
possible.
B
C
B
Yeah,
I
just
put
a
couple
since
we
were
agenda
light,
but
obviously
we
don't
have
to
spend
a
ton
of
time
on
them,
but
there
was
one
that
our
team
did
go
through
and
put
a
couple
of
updates
on
this
particular.
If
you
look
at
that
particular
one,
that
is
one
of
those
it's
been
open
absolutely
forever
and
we're
trying
to
get
it
through,
and
I
wanted
to
see
if,
because
we,
if
you
jump
down
to
the
bottom,
we
did
just
get
some
suggest.
B
You
had
made
some
suggestions
very
helpfully,
which
I
appreciate
and
we
did
get
a
couple
of
those
in,
and
I
was
wondering
if
those
you
know
the
comments
or
the
the
changes
that
were
made
like
helped.
You
had
a
few.
You
know
questions
back
to
you.
Basically,
I
just
wanted
to
make
sure
we
keep
this
one
moving.
A
A
Yeah
this
one
I
mean,
is
a
little
hard
for
me
to
review
because
I'm
not
super
familiar
with
the
rev
controller,
but
it
just
seemed
like
there
was
a
configuration
setting
that
was
going
into
the
per
route
struct
and
didn't
quite
seem
like
the
right
place.
So
I
was
kind
of
just
asking
if,
if
it's
possible
to
put
that
in
the
like
yeah
the
rock
controller
structure
or
something
else,
that's
kind
of
more
global
or
just
a.
I
wonder.
B
E
I
took
a
cursory
look.
I
know
bridget
actually
pinged
me,
I
think
two
weeks
ago,
and
I
promised
that
last
that
two
weeks
ago
that
week
was
bad
and
I'd,
look
at
it
at
the
next
week
and
yeah.
I
think
I
needed
a
reminder
and
I
apologize.
I
will
try
to
get
it
to
it
later
this
week.
I've
actually
got
it
written
on
a
post-it
note
now
and
on
my
laptop.
B
A
B
B
B
B
B
A
B
A
B
E
E
So
there
had
been,
there
had
been
a
person
who
had
been
requesting
the
ability
to
run
extra
cloud
provider
specific
logic
in
the
ccm
without
having
to
worry
about
doing.
You
know
basically
have
a
controller
that
kicked
in
after
so
the
cloud
like
the
cloud
life
cycle
controller,
and
so
one
of
the
suggestions
outstanding
that
I
had
made
had
been
pos
had
been
on
top
of
some
work.
E
That
nick
was
doing
where
nick
was
basically,
you
know,
setting
whether
using
the
cloud
provider
equals
external
to
indicate
whether
or
not
to
add
the
cloud
tank
which
overloads
it
a
little
bit.
And
so
one
of
my
counter
suggestions
had
been
given
that
there
was
another
customer
who
wanted
to
be
able
to
run
extra
controllers.
E
E
A
E
A
D
E
E
D
A
Yeah
yeah,
I
think
we
should.
I
have
a
feeling
it
will
turn.
I
mean
if
it's
like
a
really
short
cup.
I
I
wouldn't
be
surprised
if
it
ended
up
being
one
just
because
it's
like
a
api
change
kind
of
thing,
but
but
this
is
the
this
is
the
pr
that
walter
was
referring
to
I'm
basically
just
changing
sort
of
deprecating
the
cloud
provider
flag,
changing
it
to
a
boolean
configuration
where
it's
just
external
or
not
external
and
external,
directly
means
apply
the
taint.
A
E
D
E
So
I
I
so
maybe
it
does
so
my
thought
would
be
that
if
you
had
that,
what
we're
saying
is,
if
you
have
cloud
provider
external
it'll,
add
the
x
until
cloud
provider
goes
away,
it'll,
add
the
uninitialized
taint
and
that,
but
we
add
verbiage
to
that,
almost
like
what
nick
has
here
that
says,
you
know
going
forward,
there's
a
cloud
node
taint
and
you
would
be
expected
for
most
of
us,
google,
azure,
etc.
You'd
be
expected
to
say
cloud.
Node
taint
equals
uninitialized
for
cops
and
other
ones.
E
D
I
feel
like
that
will
need
a
cup
because,
like
right
now,
the
expectation
is
that
if
I
set
cloud
provider
external,
I
get
the
uninitialized
team
and
I
would
expect
that
in
the
future,
when,
if
the
cloud
provider
flag
goes
away
and
everything
has
to
be
external
cloud
providers,
then
shouldn't
the
kubelet
like
always
come
up
with
that
up
like
having
to
switch
to
apply
it
myself
is
going
to
be
a
big
change.
I
think,
for
a
lot
of
there's.