►
Description
Discussed one remaining admission cloud controller in the K8s api server, specifically the storage labelling controller. This is the reason for having a webhook in ccm. We need the controller to be ported into the two CCMs, GCP and AWS.
https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit#bookmark=id.fyaubkkgkf3t
A
Think
adding
more
information
to
the
cap
about
like
what
components
are
affected.
What
the
upgrade
path
looks
like,
and
also
some
information
about,
testing
I
think
as
well,
but
with
that
I
kind
of
opened
the
floor
up,
I,
don't
know
Walter
Andrew
Victor.
If
you
have
any
topics
you
want
to
bring
up
about
that.
B
I
mean
I,
think
it's
a
great
topic
and
I
hate
to
throw
throw
you
under
the
bus.
There
help
me
go
one
of
the
AIS
around
this
that
we
had
from
last
time
was
to
reach
out
to
Ben
the
Elder
about
trying
to
work
out
how
to
run
the
tests
with
the
cloud
provider.
Disabled
build
flag,
having
been
turned
on
and
I
think
you
had
jumped
on
that
particular
grenade.
So
I
figured
I'd
start
with
asking
if
you'd
had
a
chance
to
reach
out
to
Ben
and
if
you'd
found
anything
out.
A
I
have
not
reached
out
to
Ben
I.
Did
you
know?
I
I
responded
on
that
thread
to
dims
about
what
I
thought
were
the
kind
of
the
minimum
viable
tests
that
we
needed
to
run
in
order
to
you
know
to
accomplish
the
goals
and
I
think
dims
kind
of
ran
with
that
I
will
reach
out
to
both
dims
and
Ben
in
the
next
week
or
two
just
to
kind
of
ask
them
about
this.
A
I'll
just
note
I'm
going
to
be
on
PTO
next
week,
so
it
might
take
me
more
than
a
week
to
get
in
touch
with
them,
but
I
think
where
we're
stalled
at
now.
Is
you
know,
dims
tried
to
advance
the
enhancement
to
the
next
stage
and
we
got
a
little
bit
of
pushback
there
I
think
from
wojtek
about
you
know
not
having
some
information
there
that
we
should
have
since
we're
graduating
it
from
alpha
to
Beta,
State
and
so
I
I
wasn't
sure
like
how
we
wanted
to
collect
that
information
like
I.
A
Have
you
know,
I
have
some
maybe
incomplete
ideas
about
what
needs
to
go
there,
but
I
might
need
some
assistance
in
terms
of,
like
you
know,
filling
out
about
the
individual
components
and
and
the
upgrade
scenarios
for
them
and
whatnot,
but
I
think
testing
wise.
It
sounded.
I
I
had
the
impression
that
divs
had
kind
of
gone
forward
with
that
and
tried
some
of
it
off.
C
C
I
think
this
is
just
a
result
of
like
we.
We
started
that
cap
like
a
long
time
ago
and
it's
the
cap.
Template
has
changed
significantly
over
time
and
like
what
we
have
in
the
tent.
What
we
have
in
the
cap
is
just
like
completely
out
of
sync
with,
like
all
the
questions
that
are
in
there
now,
and
we
just
we
just
have
to
backfill
it
and
update
to
do
that.
C
B
C
B
B
A
C
C
B
Yeah
so
I
mean
I,
think
I
think
the
big
thing
is,
let's
make
sure
Jordan
doesn't
have
any
concerns
and
then
let's
and
let's
what
what
was
the
I
just
saw
whole.
Oh,
no!
That's
on
the
this
one.
Okay,
that's
fine
yeah,
so
I
think
the
big
thing
is:
let's
get:
let's
engage
with
Antonio.
Let's
get
this
rebase.
Let's
make
sure
that
Jordan's
concerns
have
been
met
and
then
let's
get
it
merged.
B
This
may
also
be
over,
like
in
the
cloud
provider,
gcp
repo,
one
of
the
weird
things
we've
had
a
couple
problems
with
is,
as
we
saw
and
they've
got
with
the
API
machinery
and
the
cape,
the
the
API
Machinery
proxy
server.
Repo
is
sometimes
you
know.
Sometimes
you
know
a
thread
can
happen
in
what
amounts
to
the
wrong
repo
and
it
it's
just
not
visible
to
the
people
right.
People.
A
A
C
B
C
Yeah
last
time,
last
time
I
spoke
with
Nick.
So
around
the
same
time
we
both
sip
down
as
chairs.
He
was
transitioning
into
a
new
team
within
eks.
That's
like
focused
on
like
off
off
stuff,
basically,
and
he
did
mention
that
there'll
be
more
like
focus
on
on,
like
ETS,
going
like
less
focus
on,
like
Cloud
providers
say
hence
like
stepping
down
from
the
role
and
whatnot
so,
and
it
might
be
good
to
just
touch
base
with
him
and
just
clarify
explanation.
C
A
B
Possibly
I
mean
the
other.
My
other
thought
is
I
mean.
Ideally,
we
should
have
Cloud
Reps
for
every
cloud
here,
but
I
will
say
that
I
think
that
Amazon
is
a
very
large
Cloud
to
not
have
a
rep
for
so
I
I
will
leave
it
at.
It
would
make
a
lot
of
sense
to
me
to
try
and
get
a
rep
engaged
from
Amazon
and
help
them
do
that
work,
but
it
would
really
be
nice
for
them
to
see
them.
B
B
B
C
C
I
think
it's
I,
don't
think
we
need
like
everyone
at
this
meeting,
because
the
kind
of
the
point
of
this
meeting
was
more
to
be
like
tactical,
like
kind
of
like
addressing
the
like
the
gnarly
technical
problems,
to
unblock
the
work
and
I,
don't
like
I,
don't
think
we
need,
like
the
whole
sick
attending
this
meeting,
so
I'm,
okay,
like
if
folks,
don't
like.
If,
if
it's
too
many
meetings,.
B
I
I
agree
with
that.
As
a
general
thing,
my
thoughts
are
I
think
there
may
be
value
in
having
Microsoft
here
and
the
specific
example
that
comes
to
mind
is
that
I
think
we
are
getting
to
the
point
we
we
just
discussed
the
the
the
last
known
good
issue,
but
all
of
that
is
about
trying
to
set
up
testing
that
a
cloud
provider
remains
valid
between
the
Dare
repo
and
the
main
KK
repo
and
I.
Think
that's
something
that
would
be
very
valuable
to
get
Microsoft
to.
B
C
B
C
A
A
You
know,
especially
with
kind
of
like
you
know
like
what
we're
talking
about
in
terms
of
Nick
and
finding
a
new
AWS
contact
and
then,
like
you
know,
if
we
do
have
technical
issues
that
come
up
like
you
know,
having
to
wait
a
week
between
meetings
or
something
that
can
be
kind
of
a
pain,
sometimes
so
I
think
it's
worth
bringing
up
just
to
say,
hey!
Look!