►
From YouTube: Kubernetes sig-aws 20181005
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello:
everyone:
it
is
Friday,
October,
5th,
2018
or
October
2018.
This
is
CA
WS.
We
have
a
fairly
light
agenda,
but
if
you
do
want
to
put
anything
on
it,
please
do
so
so
we
can
be
sure
to
get
to
it.
I
am
your
host
Justin
Santa
Barbara
from
Google
and
I.
Think
first,
up
on
our
agenda,
I
see
you're
still
typing
in
there,
but
do
you
want
to
do
you
want
to
have
the
floor
for
a
bit?
Yes,.
B
I
will
thanks
Justin,
hey
all
if
you
guys
have
heard
me
say
the
same
thing
in
other
sig
meetings:
I
apologize
for
repeating
myself,
that
I'm
I
I'm,
the
113
release
lead
for
Cuban
at
ease.
I'm.
Just
do
me
and
Kendrick.
We
are
doing
rounds
different
six.
This
weekend
next
may
need
to
introduce
ourselves
and
also
to
highlight
of
the
113
time
frame.
You
would
have
already
seen
emails
in
both
the
Cuban
80
step
channels
and
also
in
PRS.
We
have
a
super
short
release
this
time.
It's
about
ten
weeks
and
code.
B
B
Again,
a
Kendrick
sent
an
email
out
yesterday
saying
that
we
are
planning
this
to
be
more
like
a
stability
release
and
the
encouragement
is
to
focus
working
on
things
that
are
much
easier
to
land.
It
could
be
bug
fixes,
just
fixes
all
features
that
have
that
have
differed
from
previous
milestones
that
you
think
you
can
wrap
up
in
the
short
time
frame.
B
So
I
just
wanted
to
highlight
that
as
you
stop
thinking
about
your
enhancements
load
for
this
release,
the
official
enhancements
collection,
we
are
calling
features
enhancements
right
now
and
hence,
when
can
be
any
feature,
work
or
a
bug
fix.
So
the
official
collections
date
will
start
on
Monday
the
coming
Monday
October
8th.
So
the
request
is
to
open
issues
in
the
Kuban
at
ease,
features
people
for
anything
that
you
are
planning
to
work
on
this
dis
release
we
want
one
of
the
guidance
from
CPM
is
to
back
every
enhancement
with
a
cap.
B
So
if
you
could
open
an
issue
in
the
features
repo
and
then
fill
out,
the
template
there,
which
tells
us
the
confidence
of
each
feature,
the
test
coverage
talks
and
and
when
you're
likely
to
you
know
wrangle
all
this
in
my
code
freeze.
So
that
will
give
us
a
good
sense
of
where
each
feature
stand.
So
that's
all
I
wanted
to
say.
If
you
don't
have
any
other
questions,
then
yeah
there
are
a
couple
specific
features
that
I
wanted
to
discuss,
but
I
can
take
questions
before
that.
Okay,.
C
So
I
have
an
update
ash
for
you.
We've
been
obviously
chatting
offline
about
this,
and
I've
mentioned
this
to
Justin
as
well.
So
we're
probably
gonna
do
this
for
the
first
time
from
AWS,
so
AWS
el,
the
ingress
controller
will
go
for
an
alpha
release.
At
this
point,
we
will
try
to
add
all
the
testing
integration,
but
we've
had
some
offline
discussions
yesterday
about
how
we
could
do
that
properly,
and
so
we've
done
the
unit
testing
and
the
integration
testing
needs
some
more
work.
C
That's
why
we
will
punch
the
beta
for
next
release,
one
not
one
for
all
so
I
had
committed
to
you
verbally
that
the
CSI
driver,
which
Chang
is
working
on
with
the
Red
Hat
engineers
that
will
go
into
alpha
1.13.
We
feel
pretty
confident
about
that.
We
have
also
worked
with
Mike
root
here,
who
is
sitting
in
the
room
and
he's
basically
working
on
the
out
of
tree.
Ccm
implementation
and
justin
is
reviewing
all
our
PRS
going
out,
so
that
will
also
hit
alpha
in
1.13
right
now.
C
C
Also,
I
wanted
to
talk
about
the
4:23.
Yes,
well,
the
issue
that
you
had
highlighted
and
I
think
testing
in
general,
I'm,
an
honest
person
and
I'll
say,
is
in
general,
it's
a
mess
for
AWS,
which
we
want
to
change
going
forward,
so
I'm
a
bit
nervous
to
commit
to
beta.
But
what
we
want
to
do
is
I've
taken
a
couple
of
bugs
that
we
can
fix
and
maybe
I
will
use
some
help
from
Mike
root
and
yang
who's,
working
on
the
L
being
wrest
control
on
my
team
to
see.
C
B
Cycle
thanks
a
lot,
and
thanks
for
being
on
top
of
this
I
know
we
you
we've
had
all
fine
chats
and
thanks
a
lot.
Yeah
I
completely
agree
that
test
having
good
stable
tests
and
showing
that
it's
definitely
a
need
for
beta
and
happy
that
sig
has
made
that
conscious
choice
to
move
it
to
140
great
and
looks
like
you
guys
are
always
already
ahead
of
the
alpha
features.
So
look
for
the
caps
and
fall
out
there.
Cool
and.
C
A
Mean
I
think
it's
it's
great
to
see.
I
I
will
but
idea
it's
great
to
see
everyone
like
doing
all
this
work.
I
think
it's
wonderful
and
I
think
it's
ambitious,
but
I
think
that's
ok,
yeah
I
think
I
did
have.
There
was
one
thing
in
the
agenda
which
I
thought
was
interesting,
I
used
which,
as
you
said
since
it's
out
of
a
tree
where
we
need
release,
notes
mention
yes,.
B
A
That's
yeah,
that's
more
like
a
question
for
a
sig
release
right
because
I
don't
know
what
we're
gonna
do
as
we're
moving
more
more
out
of
tree.
What
we're
gonna
do
about
release
notes
it's
like.
Otherwise,
if
it
isn't
in
the
release
notes,
then
the
release
notes,
aren't
you
know
for
the
project,
but
yeah.
B
I'm
gonna
keep
this
to
sit
p.m.
a
little
bit
because
I
know
Stefan
and
folks
are
working
around
the
process
and
how?
How
do
we
seamlessly
move
out
of
tree
while,
while
we
do
this
and
if
they
are
really
good
mentions
that
need
to
go
out
in
general,
then
how
do
we?
How
do
we
wrangle
those
yeah?
My
question
here
was:
do
you
if
you,
if
you
guys
need
that
this
needs
to
be
mentioned?
Would
you
be
able
to
put
that
in
the
cat
and
then
I'll
follow
up
with
Stefan
to
see?
B
A
C
I
just
wanted
a
review
on
the
Charter.
The
review
was
done
by
Joe
Beda
Brandon,
Phillips,
Justin
and
Chris
I
did
make
some
changes.
So
couple
of
things,
I
added
was.
C
Organization
who
are
the
chairs?
What
is
the
election
process
for
the
chairs?
Who
are
the
members
and
who
are
the
maintainer
zin
owners,
so
Justin?
You
might
want
to
check
that
section
one
more
time.
This
was
an
ask
from
Chris
and
I
used.
Our
friend
Andrew
Kim's
help
from
cloud
to
cloud
provider
to
copy
some
of
the
content,
but
other
than
that
I've
followed
the
format
of
sake
of
all
the
charters
as
defined
in
the
governance,
and
so,
if
you
all,
could
take
a
look
and
give
a
final.
C
A
That's
wonderful!
Thank
you
so
much
for
doing
that.
Ish!
Yes,
it
is
important.
I,
don't
think,
there's
anything
controversial
in
there.
But,
yes,
it
is
important
for
everyone
to
make
sure
that
they
are
on
board
with
what's
in
there.
So
if
you
have
time
to
be
great
to
have
a
look
and
thank
you
so
much
miss
you
for
like
it
is
long
overdue
and
thank
you
for
actually
doing
that.
A
We
have
a
question:
not
if
there's
nothing
else
then
XD
on
the
agenda
is.
There
is
a
question
about
the
cops
111
alpha,
so
this
is
coming
soon.
I
think
this
is.
We
all
want
to
turn
this
and
keep
like
the
separation
between
cops
office,
hours
and
cigarettes,
but
hopefully
coming
soon
I
think
we
I
think
we
had
we
rebased
a
bunch
of
code
on
the
latest
kubernetes.
We
fix
some
issues.
A
C
Have
one
question
in
Justin,
so
one
of
the
problems
at
least
we
are
having
is
people
tend
to
raise
their
issues
and
problems
in
ckw
s
more
than
making
an
official
issue
against
kubernetes,
/
Cuba
and
IDs
and
labeling
it
as
a
kws?
C
A
A
Yeah
I,
don't
I
I,
don't
I
I
think
we
should
try
to
encourage
people
to
use
issues
if
we're
gonna
I
mean
I,
think
that's
what
we're
doing
so
far
github
issues
and
appropriate
use
of
tagging,
and
we
can
try
to
build
more
tooling.
On
top
of
that,
but
I,
don't
I,
don't
know
if
I
think
the
I
think
the
idea
of
pointing
users
to
eight
different
repo
is
going
to
be
tricky
and
I.
C
C
C
Guess
my
point:
is
people
just
ask
a
lot
of
questions
in
sigue
WS
and
they
never
open
an
issue
and
by
security,
as
what
I
mean
is
the
slack
channel,
and
if
everyone
could
encourage
people
to
create
issues,
then
we
have
a
better
written
track
of
it.
And
then
we
can
design
features,
look
at
things
and
make
calculated
decisions
on
the
future
roadmap.
Yeah.
A
A
You
say
you
want
to
do
X
and
you're
trying
to
X
admitting
a
problem,
but
in
fact
you
want
to
do
Y
and
you
see
someone
to
say
hold
on
just
don't
look
about
go
read
about
ingress
like
the
classic
example.
I
guess
would
be.
How
do
I
have
more
than
50
load
balancers
right
and
the
answer
is
probably
how
do
you
know
about
ingress?
A
Because
you
don't,
then
you
don't
have
to
buy
for
DL
these
yeah,
but
there
I
mean
there
are
people
for
whom
they
do
want
to
run
more
than
50
lb
is
genuinely,
but
most
of
the
people
actually
wants
to
learn
about
ingress,
yeah,
and
that
can
be
as
simple
like
slack
so
I,
don't
know,
I
think
they're
agree
with
you
that
win
something
progresses
beyond
a
certain
level
of
technical
complex.
Then
we
should
redirect
from
slacks
to
an
issue,
but
I
think
the
slack
is
great
for
hey.
Do
you
know
about
ingress
type
thing?
C
F
F
F
A
Thanks
and
I
do
think
it
is
unlikely
that
we
will
ever
reach
a
situation
where
users
that
are
finding
issues
like
know
the
correct
component
that
is
not
working
and
are
able
to
file
it
in
the
correct
repo,
so
I
think
we'll
always
have
to
deal
with
this.
So
I
think
if
in
doubt
like
filing
in
the
central
repo
and
if
it
becomes
a
problem,
we
can
always
move
it.