►
From YouTube: Kubernetes Community Meeting 20190530
Description
We have PUBLIC and RECORDED weekly meeting every Thursday at 10am PT
See: https://github.com/kubernetes/community/blob/master/events/community-meeting.md for more details.
A
Hello:
everyone
welcome
to
this
Thursday
May
30th
edition
of
kubernetes
community.
We
clean
weekly-
this
is
our
usual
show.
My
name
is
Paris.
We
will
have
a
actual
condensed
post
cube
con
EU
celebration.
Today
we
do
have
to
say
updates.
We
have
release,
we
have
a
few
announcements
and
then
we'll
be
on
the
road,
so
I
estimated
30
minutes
that
everybody
will
get
their
time
back
cool
all
right
first
up
today
is
the
release
section
with
Claire.
We
actually
don't
have
a
demo,
but
also
a
quick
shout
out
to
get
some
more
demos.
A
B
So
the
release
is
now
in
week.
8
of
our
cycle
today,
end
of
day
Pacific,
so
6
p.m.
Pacific
time
is
going
to
be
our
code
freeze
for
1:15,
so
anyone
that
has
any
open
items
they
are
trying
to
get
into
the
1:15
release.
Today
is
the
day
to
get
your
code
complete
and
then
tomorrow
is
our
docks
PR
milestone.
So
if
you
have
an
enhancement
going
into
1:15
tomorrow
is
the
deadline
to
have
a
PR
open?
B
It
doesn't
need
to
be
finished,
it
doesn't
need
to
be
merged,
but
the
PR
does
need
to
exist
for
the
docks
team
to
know
to
track
it
and
I.
Think
yesterday,
during
our
burn
down
our
docks,
lead
Barney
did
mention
that
they've
only
got
of
the
43
enhancements
being
tracked
about
28
responding,
whether
or
not
they
need
dock.
So,
if
you've
got
anything
that
is
on
the
115
train,
make
sure
to
get
those
docks.
Pr
is
open
if
needed,
so
yeah
tracking
443
enhancements.
B
B
In
addition
to
that,
starting
with
burn
down
we're
now
going
into
colors
that
each
of
our
different
leads
will
be
given.
I
gave
the
color
red
after
Monday's
called
given
our
CI
signal.
Team
is
feeling
slightly
red
since
there
are
still
jobs,
failing
on
master
blocking
and
we've
got
eleven
jobs
failing
on
master
informing
our
CI
signal
team
believes
the
cause
for
most
of
those.
Eleven
failures
is
due
to
a
new
core
DNS
version
and
they've
got
CID
cluster
lifecycle.
B
Looking
at
that
failure
to
try
and
resolve
it
and
then
for
the
one
failing
job
on
master
blocking
a
cig.
Network
has
an
open
PR
that
they're
hoping
to
merge,
which
should
resolve
that
failure.
And
then,
since
our
meeting
yesterday,
I
checked
tusk
red
this
morning
and
we
have
two
new
failures
for
vSphere
conformance
tests.
So
I
will
follow
up
with
CI
signal
to
see
if
they're
checking
in
with
the
vSphere
sig
to
check
on
those
conformance
tests,
and
then
some
upcoming
milestones,
we're
gonna
start
daily
burn
downs
next
week.
B
If
anyone
is
interested
in
attending
it
should
be
through
the
usual
zoom,
and
then
our
Doc's
deadline
for
PR
is
ready
to
review.
That
basically
means
our
Doc's
PR
should
be
merged
at
that
point,
so
the
docs
team
can
review
them
and
start
getting.
Our
Doc's
ready
is
June
4th
and
then
we're
going
to
have
the
beta
to
cut
on
June
5th.
B
I
know
that
we've
seen
some
Chad
burr
in
socks
on
email
threads
around
some
pain
points
with
the
with
the
release.
If
anyone
has
any
feedback
that
they'd
like
to
share,
we
do
have
a
115
retro
doc
that
I'd
love
to
see
stuff
get
added
to
there,
so
we
can
discuss
it
during
the
retro
and
then
give
feedback
to
the
next
leads
for
the
1/16
and
then
later
really
cycles.
So
if
you
have
feedback
on
the
release,
please
put
it
in
the
retro,
doc
and
I
believe
that
is
our
release.
Update
for
the
week.
C
A
I
did
have
a
really
quick
contributor
tip
of
the
week.
A
lot
of
our
SIG's
are
starting
to
do
how-to
videos.
What
this
means
is
they're
doing
like
how
to
do
triage,
how
to
do
code
reviews
things
along
those
and
things
along
those
lines
if
you've
been
looking
to
contribute
to
other
SIG's
and
other
ways,
for
example,
if
you're
looking
to
contribute
to
API
machinery
as
a
reviewer
but
feel
like
it's
always
just
been
too
complex,
documentation
too
complex.
A
These
are
great
sessions,
for
you
join
the
sig
of
interests,
mailing
lists
because
things
like
that
are
going
out
and
calendar
invites,
for
instance,
API
machinery
is
doing
a
live,
bug
scrub
this
Friday.
They
do
them
every
week
now,
so
you
can
see
what
they
look
for
and
how
they
triage
issues,
and
things
like
that,
so
you
can
jump
in
and
help
them
out
so
sig
updates.
D
Hey
everybody,
so
hopefully
it
should
be
pretty
quick.
Today,
in
the
past
couple
weeks,
the
months
for
six
Service
Catalog
we've
had
a
lot
of
exciting
stuff
going
on
most,
notably,
we
will
cut
zero
to
zero.
So
that's
still
a
beta
release
was
catalogue,
but
it's
the
GA
of
namespaced
resources,
so
that
was
big
feature
release
for
us
that
went
out
shortly
before
cou
con.
D
Now,
that's
out
we're
looking
forward
to
what
we're
gonna
do
in
the
immediate
future
and
the
biggest
thing,
probably
in
that
realm
is
CR
DS,
so
Service
Catalog
it's
kind
of
an
old
project.
It
started
before
CDs
existed,
so
they
weren't
really
available
for
us
to
use
but
they're
pretty
much
a
perfect
fit
for
what
we're
trying
to
accomplish.
We
want
to
transition
them
and
get
rid
of
our
API
server.
So
that's!
D
What's
on
that's
the
main
topic
for
our
next
milestone:
zero,
three
zero
we're
working
on
a
couple
things
and
sort
of
that,
notably
we're
gonna,
move
our
repositories
over
to
kubernetes
AIG's,
so
we're
still
incriminated
incubator,
which
is
kind
of
deprecated.
At
this
point,
so
we
want
to
move
over
to
the
new
place
and
then
also
in
support
of
that
there's
a
whole
bunch
of
reorganization
as
teams
and
such
in
the
github
organizations
and
all
that
has
to
add
them.
D
Also
in
support
of
that
to
maintain
backwards
compatibility,
we
have
to
continue
supporting
api
server
version
for
nine
months
past
the
release
of
c
IDs.
So
in
order
to
both
those
simultaneously
we're
gonna
have
to
revamp
our
entire
CI
pipeline
and
all
that.
So
that's
that's
thing.
Number
two
that
has
to
happen
thing
number
three
is
we're
gonna
rewrite
our
Doc's
substantially
I,
don't
know
if
I'd
say
completely,
but
that's
that's
the
other
big
thing
we're
trying
to
get
done.
This
releases
rewrite
our
Doc's.
D
D
D
Right,
this
is
sort
of
a
sub-project
update,
so
as
part
of
moving
the
repositories,
there
are
a
couple
external
repositories
that
service
catalog
depends
on
for
various
reasons
like
a
client
lived.
That
was
previously
it's
owned,
I
think
under
one
of
the
previous
contributors,
personal
accounts,
so
we're
gonna
be
taking
ownership
of
luzon
moving
those
into
kubernetes
SIG's,
that's
just
more
organizational
stuff
that
has
to
get
moved
around
we're
also
taking
ownership
of
a
service
broker.
So
this
isn't
necessarily
strictly
related
to
Service
Catalog.
D
But
a
previous
contributor
to
Service
Catalog
elements
like
wrote,
a
nifty
little
service
broker
called
mini
broker,
which
just
pushes
helm
charts
for,
like
my
single
databases
and
stuff,
but
it's
a
lot
more
feature
complete
because
it
like
actually
does
stuff.
We
want
to
use
it
in
our
Docs
and
all
of
our
use
cases
and
stuff
in
the
previous
or
the
dummy
broker
we
were
using.
We
got
in
touch
with
her
and
she's
interested
in
contributing
it.
So
probably
gonna
take
ownership
of
that
as
well
and
move
it
into
community
SIG's.
D
D
A
Cool
thanks
and
then
who's
on
the
line
for
IBM
cloud
I
see
sad
I've
sought
ever
you
running
the
show
today.
E
I
just
joined
yeah
I
was
I
had
another
presentation.
Okay,.
E
Yep
all
is
good
on
my
own
perfect
Cinda,
hello,
everyone.
My
name
is
Sudhir
Saul
I'm,
one
of
the
sig
late
for
a
CGI
being
cloud.
We
also
call
it
m
and
enrich
artists
colloids
and
they
both
I,
think
they
are
on
the
call
as
well
so
we'll
be
pointing
updates
for
the
for
the
past
quarter.
One
of
the
thing
most
exciting
thing
happened
with
this
Seger
lady
was
the
new
sub
project
we
have
created.
This
was
the
first
project
for
the
seabed
and
CG
as
well.
It's
called
cumulus
cluster
API
for
the
IBM
cloud.
E
You
probably
all
are
familiar
with
cumulus
cluster
API
project
right.
That's
the
main
project
was
created
to
to
create
declarative
cue,
minstrel
ApS
for
managing
the
Cuban
is
cluster.
So
this
the
cluster
API
provided
IBM
cloud
project
is
an
implementation
of
the
from
the
IBM
cloud
provider.
Side
and
other
browsers
also
have
their
own
implementation.
You
can
find
this
project
and
you
know
other
produce
project
call
and
on
the
key
to
humanity's
slashings.
E
The
other
thing,
which
was
a
work
which
was
a
work
in
progress,
is
still
work
in
progress
we
mentioned
in
our
last
update.
Was
you
know,
working
on
IBM
cloud
for
the
interface
sub-project,
so
we
already
have
at
IBM
the
IBM
cloud
provider
internally.
There
is
a
PDF
of
its
internal
to
IBM
right
now
and
that's
the
the
IBM
cloud
humanities
Service,
IPS
team
uses.
We
already
have
obtained
intern
approval
to
open
source
cloud
portal
code
and
we
are
targeting
beta
release
for
the
q.
E
E
Buddhist
hyperlink
and
the
charts
are,
the
link
is
provided
in
the
agenda
as
well,
so
you
can
access
it,
but
it
was
a
good
session.
We
pretty
much
use.
You
know
70
mates
65
to
70
minutes,
so
that
was
more
than
what
I
thought
but
seems
like
combining
them
to
was
a
good
idea.
There's
a
good
interactions,
good
questions
and
nobody
took
a
break
in
between.
So
that
was
good.
E
We
also
had
CGI
being
plowed
face
to
face
meeting
as
part
of
the
contributors
summit.
So
thanks
to
Paris-
and
you
know
George
and
other
folks-
for
for
that
time,
you
know
as
part
of
the
contributors,
some
it's
all
I,
think
along
with
us,
ten
or
twelve
other
six
also
participated
for
the
face
to
face
meeting.
E
Luckily,
our
time
was
in
the
morning
and
the
club
for
a
time
for
face
to
face
meeting
was
in
the
afternoon
so
I
had
a
you
know:
III
was
there
as
part
of
the
sea
cloud
for
discussions
as
well
a
very
good
time.
We
talked
about
like
almost
two
hours,
talking
about
updates
on
Club,
for
weather
itself
and
from
our
seek
and
reps
from
others
sake
from
Google,
VMware
or
OpenStack
and
other
six.
We
also
participated
in
sig,
meet-and-greet,
I,
I,
love
that
in
30
minutes
or
one
over
time
we
had
missed
three
new
folks.
E
E
Besides
that
we
have
our
bi-weekly
meetings
regularly
unless
we
have
to
cancel
it
for
any
reasons
like
cube,
corn
or
some
other
conflicting
events,
and
all
the
videos
are
linked
or
added
here
for
the
YouTube
plans
for
upcoming
cycles.
So,
as
I
mentioned,
we
have
our
first
sub
project
created.
It's
been
like
3
to
4
weeks
now,
so
we
will
be
focusing
on
growing
the
project
with
new
contributor
base
right.
You
would
like
folks
to
contribute.
So,
if
you're
interested,
please
take
a
look
at
the
project.
It's
just
it's
like
newly
created
projects.
E
The
code
base
is
not
so
big.
It's
easy
to
understand.
What's
out
there
right
some
of
good
thing
too,
to
start,
isn't
no
new
contributor
to
contribute
to
the
project
and
if
you're
any
questions
on
the
project
guide,
you
can
reach
out
to
myself
or
any
other
sig
leads
we'll
be
focusing
on
having
our
IBM
cloud
provider
interface.
E
You
know
out
on
external
ketta,
the
interface
was
primarily
on
dye
on
the
cumulus
controller,
Control
Manager
architecture,
but
we
are
working
on
Maundy
to
cloud
control,
measure
architecture,
so
that
work
is
in
progress.
We
also
bring
some
of
the
refactoring.
You
know
considering
we'll
have
it
out
on
externally
and
then
the
I
casing
is
also
working
on
some
of
the
changes
they
need
for
internal
build
process
once
we
have
it
open
source.
E
There
is
a
link
here
for
the
issue
related
to
care
for
for
this
out
of
free
IBM
cloud
provider
or
repo,
and
we
also
you
know,
continue
participating
with
the
sig
cloud
provider
to
consolidate
all
the
cloud
for
the
six
under
one
umbrella
and
that
will
be
the
sig
Club
for
other
projects.
Other
SIG's,
the
cloud
46,
our
moon
has
a
sub
project,
so
we
will
be
continue.
E
Working
on
on
on
that
discussions-
and
you
know,
as
it
happens,
I
think
based
on
my
discussion
with
with
the
cloud
folder
in
sig
sig
leads
and
to
in
other
states
and
other
folks
at
in
Barcelona
the
face
to
face
meeting
thing.
We
are
shooting
sometime
in
July.
You
know
approximately
to
have
this
happen.
E
A
A
First,
shout
out,
I
know
Josh
can't
be
with
us
right
now,
but
Josh
Marcus
is
planning
the
Shanghai
contributor
summit
and
Josh
and
pooja
are
both
looking
for
current
contributors
to
help
out
on
site,
as
well
as
with
content.
If
you
are
a
current
contributor
or
listening
right
now-
and
you
are
going
to
Shanghai,
please
reach
out
to
Josh
or
pooja
and
slack
their
info
is
in
the
in
the
doc
as
well.
They
really
need
your
help.
Thanks,
y'all
also
meet
our
contributors
is
next
Wednesday.
We
are
doing
we're
sticking
with
the
7:30
a.m.
A
Pacific
time
slot.
We
get
hundreds
of
folks
that
watch
that
slot
and
we
are
gonna,
cancel
the
1
p.m.
Pacific
and
look
for
a
new
time
that
new
time
will
most
likely
be
in
the
evening
Pacific
to
shake
things
up
a
little
bit,
and
this
is
again
mentoring
on
demand.
We
have
up
stream
upstream
folks,
although
up
two
approvers
on
a
line
asking
and
answering
questions
from
a
wide
array
of
topics,
whether
it's
self
care.
How
do
I
get
this
full
request
merged?
A
You
can
ask
anything
and
everything
in
the
meet
our
contributor
slack
channel,
also
watch
past
episodes
in
the
agenda
pull
stuff
and
then
shout
out.
We've
got
a
ton
of
shoutouts
this
week.
A
lot
lots
to
do
with
cubic
on
last
week's
Omega.
Thanks
just
a
blanket
statement
to
everybody
that
put
on
cube
con
and
everybody
that
came
out
to
cube
con.
It
was
an
awesome
time
and
I'm
sure
everyone
would
agree.
A
Honeys
wanted
to
shout
out
Tim
pepper
for
consistently
being
a
great
context,
giver,
helper,
recruiter,
describer
and
mentor.
How
important
thank
you
Tim
sue
me
for
publishing
our
packages,
especially
on
not
so
convenient
occasions
and
Catherine
berry
for
jumping
in
figuring
it
out
and
fixing
our
test
grid
or
test
grid
config
or
something
else
still
not
sure
what
the
exact
problem
was
issue
Ben
wants
to
shout
out
a
og
Olaf
and
PJ
PB
and
J,
and
anyone
I
miss
for
hoping
answers.
A
A
We
had
over
200
people
there
pair
programming,
getting
hands
on
kubernetes
cluster
support,
venting
about
all
types
of
kubernetes
challenges
and
making
camaraderie
and
community
amongst
us,
and
it
was
wonderful,
thank
you
all
so
much
for
being
a
fantastic
community
and
to
do
all
the
mentoring
session
participants
as
well.
We
did
pod
style
mentoring,
yes,
pun
intended,
and
it
was
super
fun.
Thank
you
to
everybody
for
being
amazing
leaders
in
this
awesome
community.
Without
you,
it
would
not
be
here
alright
and
that
ends
our
show
today.