►
From YouTube: Kubernetes - AWS Provider - Meeting 20211029
Description
Recording of the AWS Provider subproject meeting held on 20211029
Issue Triage: https://github.com/kubernetes/cloud-provider-aws/pull/272, https://github.com/kubernetes/cloud-provider-aws/issues/282, https://github.com/kubernetes/cloud-provider-aws/issues/281
B
Hello,
everybody.
This
is
the
bi-weekly
aws
cloud
provider
meeting.
I
am
your
moderator
facilitator
for
today.
Just
in
santa
barbara,
I
work
at
google
a
reminder.
This
meeting
is
being
recorded
and
we
put
on
the
internet
and
therefore,
please
be
mindful
of
our
code
of
conduct,
which
boils
down
to
being
a
good
person.
We
have
a
couple
of
items
on
the
agenda.
Please
do
feel
free
to
add
your
name
and
any
other
items.
B
A
B
B
B
B
B
B
C
C
C
C
D
C
C
B
B
B
B
So
we're
talking
here
about
issue
282,
where,
when
a
user
is
using
an
ecr
docker
registry
as
a
mirror
for,
for
example,
docker
hub
they
can,
they
can
configure
that
in
container
d,
however,
container
d
by
default
won't
pass
any
past
the
credentials
to
the
to
the
registry
and
ecr
with
all
will
say.
No.
Thus,
I
think
the
request
here
was
to
allow
ecr
to
pass
it
to
docker
hub
or
some
other,
like
list
of
registries,
that
the
user
could
provide.
B
B
D
B
D
A
B
B
B
I
think
if
there
was
a,
I
think
we
should
ask
chaos
puppy.
If
container
d
could
do
the
ecr
authentication-
which
I
imagine
is
a
solved
problem
somehow
then,
would
that
solve
their
problem
and
then
we
wouldn't
have
to
change
like
it
would
only
be
the
node
credentials.
So
if
they're,
if
they're,
somehow
doing
anything
more
advanced
than
that,
then
we
need
to
rethink,
but.
B
B
B
D
D
Right
eventually,
so
it's
in
the
path
of
like
going
to
nlp
route
and
for
nlp.
We
have
load
balancer
controller
for
now,
where
we
do
support
it,
so
we
at
least
provide
some
solution
to
the
users.
Of
course,
we
have
to
like
have
a
good
story
for
the
cloud
provider
as
well
like
the
ccm
eventually.
So
that's
the
next
step
that
we
need
to
work
on.
B
Looking
at
the
cli
commands,
it
looks
like
it's
sort
of
additive,
and
if
we,
if
it's
not
in,
if
it's
not
supported
by
the
controller,
it
looks
like
it's
something
that
the
user,
for
example,
could
run
the
cli
commands
on
after
the
load
answer
was
created,
and
I
think
that
ties
nicely
into
jay.
Your
work
on
the
operators
like
is
this:
what
is
the
status
of
the
operators?
Is
this
something
we
can
configure
with
the
operators.
A
D
D
D
C
D
D
B
B
B
Doesn't
look
like
when
we've
set
that
we
ever
clear
it,
which
is
also
a
little
so
like?
Presumably
it's
not
a
terrible
thing
to
do
if
a
while,
while
the
volume
is
taking
a
long
time
to
go
onto
a
node,
if
we,
you
know
after
five
minutes,
say,
hey
stop
putting
more
pods
on
here,
but
then
once
it
attaches,
we
should
probably
say
keep
going.