►
From YouTube: Kubernetes - AWS Provider - Meeting 20220819
Description
Recording of the AWS Provider subproject meeting held on 20220819
Agenda - https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqySkXwJnrGJP9OGyP2_P14/
A
B
A
C
A
D
Yeah,
nothing
particularly
specific
this
week
of
general
interest,
though,
is
this
run
c
regression
around
executive
tty,
which
we
are
grappling
with
for
124.
I
will
try
to
find
a
link
and
paste
it
into
the
notes
for
anyone
that
is
interested
or
may
have
a
solution
other
than
asking
run
c
nicely
to
do
a
new
release.
I
think
they're,
aware
of
it
so.
A
E
E
E
C
C
A
A
A
C
A
C
A
D
Oh
sorry,
the
one
concern
I
have
is
it
sounds
like
this
was
a
specific
problem
with
nodes
and
that
this
tag
resource
is
called
from
a
bunch
of
places
and
the
one
thing
I
think
we
would
want
to
be
careful
of
is,
for
example,
if
there
was
an
async
or
eventually
consistent
api.
Like
you
know,
iam
sometimes
doesn't
show
things
right
away
or
did
at
least
used
to
not
show
things
right
away.
D
We
would
probably
lose
the
ability
to
retry,
maybe
so
the
the
alternative
way
to
do
this
would
be
for
the
specific
case
when
we're
calling
tag,
resources
or
untech
resources
to
check
for
a
check
for
this
particular
error
on
the
call
site.
But
I
do
kind
of
agree
that
I
think
this
is
probably
pretty
a
pretty
good
idea
like.
I
think
this
tagging
is
pretty
much
best
effort
anyway,
but
it's
worth
checking
where
it
is
cold.
A
C
A
B
C
A
I
have
a
question
for
justin
earlier,
like
john
from
chaos.
Team
was
talking
about
like
how
we
want
to
include
the
load
balancer
controller
with
chaops
as
a
add-on,
and
he
also
brought
about
like
disabling
the
cloud
provider,
the
load
balancer
code
in
the
ccm.
So
that
is
something
that
I
or
we
want
to
look
into
as
well.
A
D
Yeah,
I
mean
you're,
I
think
I
think,
nick
you've,
you
integrated
the
cloud
provider
aws
in
the
past,
so
you
probably
have
the
most
like
direct
experience
of
of
someone
like
adding
something
there
you'd
be
very
welcome
to
that
would
be
wonderful.
We
also
are
working
on
more
what
we
call
sort
of
additional
objects
or
external
objects.
D
So
the
idea
that
if
the
load
balancer
controller
had
had
a
something
like
component
config,
you
could
sort
of
configure
it
that
way
without
having
to
necessarily
integrate
it
as
tightly
into
the
k-ops
api
or
into
the
one
day
or
as
tightly
into
the
k-ups
code.
We
aren't
totally
there
yet
and
that's
still
future
flagged,
so
we're
sort
of
in
between
the
two
worlds.
Okay,
but
you
know,
if
you'd
be
welcome
to
do
either
one
and
I'm
happy
to
sort
of
give.
D
D
It's
sort
of
like
scheduler,
moved
to
it
fairly.
We
had
a.
We
had
an
issue
in
k,
ups,
where
scheduler,
basically
deprecated
a
function,
functionality
from
flags
and
you
had
to
start
using
the
scheduler
config,
yaml
or
file,
and
that
was
unfortunate
because
we
didn't
we
didn't
transition
in
time
for
some
people.
But
yes,
it's
it's.
Basically
a
gamma
configuration
file
instead
of
flex.
A
A
D
A
C
On
that
note,
do
we
want
to
pack
it
like,
I
feel
like
we
want
most
cases,
users
to
install
ccm
and
the
load
bouncer
controller
together.
So,
like
you
know,
cops
is
one
situation.
Do
we
also
want
to,
like
I
don't
know,
somehow,
have
a
packaged
installation
method
for
for
users
who
are
not
using
eks
and
not
using
cops.
A
So
we'll
provide
the
options,
that's
the
best
thing.
We
can
hope
right,
because
different
distributions
have
their
own.
Our
packaging
have
their
own
rules
and
requirements
will
will
enable
them,
but
will
not
go
and
more
define,
like
all
the
possible
packages
out
there.
Maybe
the
popular
ones.
Chaos
cks
like
these
are
the
ones
that
that
are
more
popular,
we'll
do
something
there
for
other
users,
we'll
let
it
up
to
the
maintainers
to
pick
it
up.
At
least
we
will
have
the
option
so
we'll
say:
okay,
this
is
the
one.
C
Yeah,
I'm
thinking
of
users
who
come
to,
I
don't
know,
maybe
they're
you
know
they
have
some
way
of
setting
a
cluster.
They
come
to
the
ccm
repository
and
they
install
it
somehow
right
now,
there's
not
a
lot
of
information
about
the
load,
balancer
controller
from
that
direction,
so
maybe
even
even
as
just
like
documentation,
we
just
add
good
documentation
on
lbc.