►
From YouTube: Kubernetes Community Meeting 20190926
Description
The Kubernetes community meeting is intended to provide a holistic overview of community activities, critical release information, and governance updates. It also provides a forum for discussion of project-level concerns that might need a wider audience than a single special interest group (SIG).
See this page for more information! https://github.com/kubernetes/community/blob/master/events/community-meeting.md
Like what you see here? Continue the conversation on https://discuss.kubernetes.io
A
Hi
everybody
welcome
to
the
September
26
2019
kubernetes
community
meeting.
This
is
as
always
being
live
stream
to
YouTube
and
we
will
also
have
a
recording
up
on
YouTube.
So
I
just
want
to
remind
folks
to
adhere
to
our
code
of
conduct.
If
we
could
get
a
note-taker
that
would
be
fantastic.
We
are
using
a
Google
Doc
to
collaboratively
track
the
agenda
notes.
It
looks
like
Lachlan
Evanson
has
volunteered.
Thank
you.
A
I
am
Tim
pepper,
I
work
for
VMware
as
a
source
software
engineer
and
also
am
active
in
the
community
as
a
chair
and
sig
release
and
as
I
volunteer,
and
that
everything
in
this
meeting
is
being
presented
similarly
by
community
volunteers.
So
if
there's
anything
that
you
would
like
to
see
here
or
participate
in
step
up
and
volunteer,
we
are
always
in
need
of
new
people.
So
in
our
normal
agenda
we
start
out
typically
with
a
demo.
B
A
C
Right
so
hello,
I'm,
Brenna,
miles
I
work
at
VMware
and,
most
importantly,
today,
I'm
nuts,
about
this
tool.
I
have
called
octant
and
why
I
share
my
desktop
here?
Let
me
tell
you
what
octant
is
octant
is
a
tool
that
we
created
to
help
answer
the
question:
what's
going
wrong
with
my
stuff
in
kubernetes
and
when
I
say
stuff
in
Kluber,
Nettie's
I
mean
literally
whatever.
C
The
whole
point
is
that
kubernetes
is
purposefully
complex.
It
needs
to
be
complexed
because
it
handles
so
many
different
situations,
so,
but
that
complexity
is
also
a
little
daunting
to
users
who
either
one
have
better
things
to
do
like
program,
their
apps
or
two
are
beginning
and
just
don't
know
where
to
start
so
normally
I
mean
I
can
literally
talk
for
hours
about
octant,
but
today,
to
show
you
something
that
I
find
pretty
interesting
about
octant
and
handling
use
cases.
That
might
actually
happen
to
you.
So
before
we
get
started.
C
C
As
we
do
in
show
business,
we
just
do
it
all
live,
so
here
we
go
so
I
have
a
website
and
we're
in
the
business
of
presenting
HTTP
bin,
and
we
have
HTTP
bin
as
a
service.
If
there
is
such
a
thing
and
a
little
sidebar
and
the
reason
I
like
this
website,
if
you
do
any
kind
of
web
development
and
you
need
to
test
HTTP
stuff
out
HP
pen-
is
it's
pretty
great
for
that
it
does
like
all
the
standard
things
get
post
put.
Delete
can
do
often
things
like
that.
B
C
It's
5:00
p.m.
and
as
Phi
p.m.
people
like
to
deploy
stuff
on
Fridays
I,
don't
know
why,
but
that's
just
when
they
want
to
do
it.
So
we'll
pretend
that
we
have
a
super
fancy
deployment
chain
and
release
chain
and
we'll
pretend
that
we're
not
looking
at
what
I'm
doing
here
so
I'm
redeploying
my
website
and
I'm
going
home
and
because
what
could
happen
all
my
tests
passed,
so
things
should
be
right,
so
we
go
so
look
at
the
website
and
quickly
we
realize
the
site
is
down
now.
This
is
a
little
bit
daunting.
C
Even
if
you
understand
kubernetes,
there
could
be
so
many
things
wrong
here.
So
as
a
as
a
advanced
user
of
kubernetes,
what
could
you
do
here?
Well,
you
can
well,
let's
just
get
all
we're.
Gonna
use
queue,
control
and
get
everything
in
here.
Well,
I
see
some
pod
I
see
a
service
I
see
a
deployment,
it
all
doesn't
even
show
ingress
is
so
I,
don't
know
how
useful
that
is
to
everyone.
But
let's
get
this
ingress
to
well.
We
have
an
ingress
here.
So
where
do
I
start
to
get
these
things
figured
out?
C
Well,
I
want
a
short
circuit
all
that,
with
with
another
tool
and
reason
we
developed
Occident
was
to
actually
help
solve
these
problems
and
do
other
things.
So,
let's
fire
up,
octant
and
and
see
what
we
have
going
on
here.
So
octant
is
a
web-based
tool
that
runs
locally.
That
can
talk
to
your
cluster
and
it
uses
your
credentials
now.
You're
gonna,
say
Brian.
Why?
Why
doesn't
it
run
in
the
cluster?
C
Well,
there
is
a
whole
suite
of
issues
we
can
get
rid
of,
namely
security
issues
by
just
using
one
set
of
credentials
inside
one
set
of
credentials
that
you
provide
and
running
it
local.
So
we're
not.
We
don't
worry
about
cluster
resources
and
we
don't
worry
about
security
in
this
case.
So
this
is
octant
right
now,
octant
is
a
is
a
web
view.
C
Ultimately,
I
think
we're
going
to
bundle
its
I'm
syan
application
kind
of
like
what
github
did
with
their
tools
or
even
what
the
its
code
did
with
their
editor,
because
I
just
think
that'll
be
a
better
experience.
But
how
can
we
use
octant
to
figure
out
what's
wrong?
So
when
you
first
go
to
octant,
you
get
a
list
of
your
other
name
space
that
you're
currently
in,
and
you
can
see
all
these
things
since
time
is,
is
a
interesting
thing
here.
C
It
will
not
go
through
all
of
them,
but
I
want
to
show
you
a
new
feature
that
we're
going
to
release
in
our
next
version
of
octant
I,
guess
that
would
be,
and
probably
about
three
and
a
half
to
four
weeks
that
will
actually
allow
you
to
see
an
application
and
see
all
the
components
of
it.
So
octant
has
this
concept
of
applications,
and
we
see
there's
an
application
called
HTTP
bin
right
here,
and
the
astute
people
around
are
probably
saying
well
hold
on.
C
So
if
you
see
right
now,
these
ones,
starting
with
a
kubernetes
site
name,
let
me
show
you
those
actually
inside
of
octave,
so
you'll
notice
that
we've
labeled
every
single
component
that
belongs
to
our
application
with
these
labels.
So
in
this
case,
I
have
three
labels
here,
let's
say
demo,
and
then
it
should
be
Ben
and
b1
and
I've
labeled
everything,
and
because
I've
done
that
often
can
use
that
convention
to
actually
group
things
together.
C
Let's
look
at
this
red
one
first,
so
inside
of
octave
we
can,
since
we
know
how
ingress
is
work,
we
can
make
guesses
about
how
an
ingress
should
function.
So
in
this
case,
what
we
have
here
is
that
this
HT
bin
thing
ingress
has
a
bad
configuration.
It
has
a
a
back-end
which
first
were
service.
It
doesn't
exist.
So
this
is
the
first
example
of
using
octant
to
determine
how
things
are
working,
and
this
is
we
do
we
don't
have
editors
for
every
single
object
yet,
but
we're
building
those.
C
So
what
I'll
do
is
I'll
just
use
jib
control
edit
to
fix
this
thing.
So
if
I
go
down
here,
I
can
see
that
the
in
the
role
the
back
end
actually
is
pointing
to
the
wrong
thing
and
in
real
time
I
won't
even
switch
the
editor.
Yet
what
you're
going
to
see
is
now
the
ingress
goes
back
to
green,
because
it's
configured
correctly
it
can
find
a
service.
So
now,
let's
look
at
this
service.
C
This
service
is
telling
us
that
there's
no
endpoints
for
service
to
route
traffic
to
pods
it
has
to
have
endpoints
and
it
doesn't
have
endpoints.
They
can't
route
traffic
and
once
so,
what's
what's
going
on
here.
So
if
we
look
at
this
thing,
there's
not
this
thing
is
actually
this
service
is
not
configured
incorrectly
at
all.
C
So,
actually
it's
fine,
but
what
we
do
know-
and
this
is
something
that
I
want
achtung
to
be
able
to
tell
people-
is
that
services
route,
2
pods
and
they
use
a
selector
and
will
notice
that
the
selector
is
its
most
likely
wrong.
And
but
we
do
have
a
selector
editor
in
here
and
what
I'm
going
to
do
is
just
change
a
selector
to
match
my
application,
so
I
can
match
the
demo
HB,
Ben,
v1
and
then
I'm
just
going
to
edit
it
from
inside
the
application.
C
C
Well,
it
should
have
been
working.
Maybe
there's
a
problem
somewhere
else.
So
octant
is
showing
us
this,
but
octane
can
also
do
something
else
here.
So
let
me
the
pulley
another
version
of
my
website,
and
this
is
saying
that
we
just
it's
now
during
the
week
again
and
we've
wrapped
their
website.
You
didn't
see
it
but
really
quickly.
What
Achtung
can
do
is
you
can
track
all
your
replica
sets?
It
can
attract
a
track,
a
deployment
in
real
time
so
because
we
can
track
a
deployment
in
real
time.
C
So
now,
if
I
go
back
to
my
website
here,
we
can
see
that
I
deployed
a
new
version
and
the
new
deployed
version
is
we
just
move
a
ship
and
to
Engine
X?
So
this
is
the
literally
the
nickel
tour
of
octant.
You
can
download
it
at
at
github.com,
so
I
actually
am
where
slash
octant.
We
had
binaries
for
Mac,
Windows
and
Linux.
We
have
we're
trying
to
get
people
into
the
community
more.
We
do
have
some
port.
C
We
have
some
issues
that
are
some
good
first
issues
we're
in
the
github
are
we're
in
the
kubernetes
slack
under
often
please
come
in
there.
I
am
my
team.
We're
we're
there
to
answer
questions
and
try
to
make
a
tool
that
everyone
likes
and
I
want
to
end
this
with
one
final
thing:
I
tweeted
this
last
week,
I,
don't
think
people
are
understanding.
C
What
I
was
saying
is
that
kubernetes
needs
the
benefit
from
a
relevant
and
and
really
what
I
meant
there
and
I'll
talk
about
this
more
in
a
different
forum
is
that
convention
over
configuration
is
powerful.
We
need
to
figure
out
what
that
looks
like
in
the
kubernetes
land.
So
we
could
make
tools
that
are
still
flexible
but
are
still
powerful,
because
what
happens
in
a
lot
of
cases
is
that
we're
creating
tools
that
are
powerful,
but
they
have
no
basis
they're,
pretty
abstract,
which
means
they're
not
flexible
to
our
environments.
C
C
C
All
right,
so
there
are
no
question
so
one
thing
that
I
I
will
want
to
I,
say
wow.
If
you
want
to
psych
any
questions
and
I
ought
to
say
this.
Real
quick
visualizations
are
hard,
and
so
one
thing
that
we
are
focusing
on-
and
hopefully
we
can
get
this
in
our
next
release
is
we
do
have
a
new
version
of
the
visualization
that
you
saw.
C
It
showed
there
because
I
want
to
make
sure
that
we
can
put
in
as
much
information
as
clear
as
possible,
because
it's
pretty
difficult
to
show
these
things,
but
I
want
to
show
it
in
a
plain
thing
that
if
someone
can
sit
down
with
this
tool,
not
really
understand
all
the
pieces
of
how
everything
works,
but
they
can
still
feel
empowered
to
fix
problems
as
they
come
about.
So
that's
octant
and
we're
actively
working
on
it.
A
B
Good
morning,
everyone
again,
my
name
is
Guinevere
I
go
by
Glenn
or
Guinevere.
I'm
super
excited
to
lead
the
last
release
of
this
year
and
currently
we're
gonna
make
one.
We
are
very,
very
busy,
selecting
team,
lead,
shadows
and
also
looking
over
enhancements
cleaning
up
the
milestone
thanks
to
Bob
for
that
work,
and
if
you
have
any
questions
for
me,
please
ping
me
on
slag.
Let
me
know
get
in
touch.
The
real
big
thing
for
117
currently
is
only
I
want
everyone
to.
Please
please
be
aware
of
deadlines.
B
B
A
So
patch
releases
I
also
volunteer
on
the
patch
release
team.
So
there's
a
link
there
to
the
schedule.
We've
fallen
into
a
cadence
of
basically
mid
month,
releases
on
all
of
the
patch
branches,
with
the
exception
of
our
dot.
One
release
is
typically
two
weeks
out
instead
of
four
weeks
out,
so
that
is
coming
up
here
soon.
Cherry
pick
deadline
for
that
is
tomorrow
for
one
16.1
and
a
release
target
of
next
week
and
two
weeks
after
that,
subsequent
releases
of
everything
and,
of
course
those
are
always
subject
to
change.
A
D
D
Could
type
flush
owners
where
and
your
github
panel
and
that
will
tell
you,
give
you
a
quick
little
search
of
what
owners
files
you
happen
to
be
in,
and
this
is
kind
of
you
know
kind
of
important.
What
just
we
have
a
whole
slew
of
owners
sprawl,
so
sort
of
getting
an
idea
of
where
you
might
be
an
owner
will
give
you
an
idea
of
you
know
where
some
of
the
stuff
is
coming
in
and
if
you
just
do
a
little
audit
one
take
too
long,
but
it
will
just
help
the
experience
for
everyone.
A
D
A
F
Good
yep
perfect,
so
my
name
is
ma
che
I'm,
one
of
the
leads
for
the
sake
CLI
and
a
quick
information
on
what
we've
been
working
and
116
release,
time
frame
and
what
we
are
planning
to
work
on
and
the
next
release
as
well.
So
the
majority
of
the
efforts
that
we
we
are
focusing
on
over
the
past
and
the
current
release
is
getting
cube,
CTO
out
of
the
main
communities
repository,
as
you
probably
notice,
majority
of
you
that
are
working
with
kubernetes
repo.
F
F
So
as
not
as
it
is
not
a
surprise.
We
are
continuing
with
the
effort
because
there
are
still
three
main
commands
that
are
left
in
the
main
repo
which
are
causing
us
a
lot
of
problems.
First
of
them
is
the
Get
Command,
and
the
reason
that
the
get
command
was
not
moved
is
that
the
work
required
to
move
get
I
would
estimate
about
half
of
the
work
that
is
needed
to
move
the
entire
cube.
F
Cpl
house
of
the
work
is
just
yet
itself,
so
we
moved
a
lot
of
the
bits
and
pieces
already
to
the
staging
repo,
but
there
is
still
quite
a
lot
to
be
done
and
Shawn
is
doing
an
awesome
work
currently
finishing
the
gate
command,
mostly,
that
is
related
with
how
we
are
printing
their
resources.
When
you
are
invoking
get
get
pause,
for
example,
the
other
offender
I
would
call
it
that
way
where
we
are
still
struggling
is
the
author,
icon
style,
and
the
reason
for
that
is.
F
That
is
another
example
where
we
still
rely
on
the
internal
utilities
from
the
main
community
repository,
and
we
are
in
contact
with
the
sick
off
to
try
to
extract
a
library
that
we
can
share
between
kubernetes
repo
and
the
keep
CTO
and
the
third
offender,
where
we
took
a
slightly
different
approach,
is
a
cube
CTL
convert.
If
you've
ever
tried
working
with
with
give
CTO
convert,
it
is
basically
a
command
that
allows
you
to
convert
from
one
to
another.
F
If
your
resource
coexists
and
multiple
versions
like,
for
example,
deployments
they
used
to
exist
in
extension,
v
1
beta
1,
which
is
disabled
by
default
these
days,
but
you
still
might
have
some
yellow
files
reusing.
The
extensions.
Do
you
want
beta
1
using
the
cube
CTO
converter
can
convert
that
file
to
a
apps
v1,
which
is
the
default
API
version
for
deployment.
The
problem
with
cube
CTL
convert
is
that
it
greatly
relies
on
the
internal
API.
F
We
are
still
under
discussions
trying
to
figure
out
the
best
place,
I'm,
guessing
that
the
final
destination
will
rely
on
where
the
internal
API
exists,
but
don't
be
surprised
if
in
117
you
type
keep
CTO
convert
and
you
will
be
prompted
with
a
gentle
message
that
cubes
you
do
convert
is
not
part
of
cube
CTO
anymore.
Then
you
need
to
get
a
separate
binary
that
will
provide
that
functionality.
F
Other
topics
that
we
are
looking
at
for
one
seven
things
are
around
experimental
commands
to
work
with
commands.
Currently
the
only
way
to
to
work
with
events.
Currently,
the
only
way
to
work
with
events
is
to
get
comment
or
describe
the
get
command
for
events
is
quite
cumbersome
because
it
throws
at
you
a
bunch
of
events
and
doesn't
allow
you
to
filter
or
sort
them
in
any
reasonable
way,
whereas
in
describe
you
get
the
description
of
the
resource
and
events
related
to
that
one.
F
Okay,
my
screen
off.
Ok,
the
sub
projects
that
we
own.
There
are
two
of
them
that
are
worthy
of
mentioning
customize,
which
allows
you
to
customize
Road
templates
and
apply
additional
modifications
about
a
couple
months
back.
We
released
version
3
of
it
recently
where
these
specifically
version
3.2,
which
extended
the
amount
of
possible
patches,
including
the
inland
inline
patch
for
customize,
and
we
improved
the
resource
matching.
If
you
haven't
played
with
customize
check
it
out,
it's
pretty
cool
it.
F
It
definitely
allows
to
have
much
more
control
over
they'll
most
and
you
didn't
have
to
modify
the
default
Aeons
that
you
have
on
your
on
your
disk.
The
other
project
that
just
it's
0.3,
release
specifically
0.01
in
the
past
two
weeks
is
crew.
Who
is
a
plug-in
manager
for
keeps
you
field
plugins?
It
is
a
plugin
by
itself,
but
what's
most
importantly,
it
allows
you
to
search
through
the
curator
index
that
that
currently
holds
about
50
plugins
and
we're
hoping
to
expand
the
index
even
even
more.
F
F
A
A
E
E
A
B
A
E
E
E
E
From
the
OPA
team,
so
we
are
running
it
like
a
POC
project
for
the
policy
from
our
application.
If
you
are
digging
into
like
math,
please
take
a
look
at
the
project.
This
will
be
the
most
mathematical
thing
you
will
ever
encounter
with
kubernetes.
Okay,
so,
and
we
also
try
to
better
align
with
since
f6
security
to
contribute.
E
E
A
A
H
So
I'm,
like
talking
and
I'm
one
of
the
chairs
of
working
group
component
standard
I'm,
happy
to
be
at
the
meeting
today.
So
thanks
for
having
us
so
today
we're
going
to
talk
a
little
bit
about
our
working
group
and
kind
of
what
we
do.
We
have
some
updates
from
last
cycle,
some
information
about
some
work,
that's
in
progress
and
some
like,
hopefully
exciting
things
about
the
future
and
why
people
should
come
join
us.
H
So,
first
off
our
working
group
is
designed
to
help
develop
a
standard
foundation
for
core
purées
components
to
build
on
top
of
so
you
can
think
of
it
as
kind
of
like
some
standard
in
libraries
and
frameworks
that
consolidate
a
lot
of
the
code
that
has
been
independently
implemented
for
the
same
features
across
a
lot
of
our
components.
So
examples
would
be
code
for
dealing
with
config
logging,
different
sort
of
status
and
points
on
components.
H
Different
integration
points,
not
that
sort
of
thing,
so
working
group
component,
standard
kind
of
grew
out
of
this
kept
for
creating
the
component
base
repo,
and
it's
designed
to
put
all
these
different
efforts
that
people
were
already
working
on
on
these
different
things
in
one
place,
give
it
a
forum
for
discussion
and
hopefully
get
some
work
done.
So
we
think
this
is
important
kind
of
a
this
is
sustainability
and
maintainability
of
the
project
and
affects
most
of
us
and
most
important
have
many
areas
that
can
have
some
improvement.
H
What
we
did
last
cycle
so,
first
off,
we
had
a
few
leadership
changes.
The
word
was
started
around
Q
Khan
last
year
in
December,
with
myself,
Stephanie
Lansky,
Red,
Hat
and
Lucas
Lucas
this
summer
stepped
down
from
his
chair
position
and
he's
been
replaced
by
stealthy
boxes.
Our
newest
chair
he's
been
really
great,
really
involved
in
the
working
group.
H
So
that's
been
great.
We
had
a
contributor
onboarding
session
in
July,
so
welcome
and
thank
you
to
all
the
new
contributors
who
came
to
bet
that's
recorded
and
it's
on
YouTube
and
our
playlist
I
wish.
We
have
a
link
to
it
here
in
the
presentation
so
for
people
who
are
interested,
that's
also
a
great
way
to
kind
of
check
out
the
working
group.
So
we
and
you
know
we're
relatively
small
working
group
right
now,
but
trying
to
grow
so
we
managed
to
ship
a
few
things.
Last
cycle
stealthy
box
had
some
small
refactoring.
H
We
managed
to
get
scripts
serializer
support
into
codec
factories.
So
what
that
means
is
now
components
that
read
in
config
files
can
reject
files
that
have
unrecognized
keys
in
the
config.
So
previously
we
were
just
using
the
basic
API
machinery
where
you,
if
you
made
a
typo
in
a
field
name,
they
filled
with
just
getting
the
word.
For
example,
you
would
get
in
there
bad.
So
now
we
have
the
ability
to
give
back
those
airs
and
we
have
some
people
who
are
working
on
actually
implementing
that
support
components
themselves.
H
We
also
have
the
legacy
flag
library
that
I
wrote,
which
is
kind
of
a
thin
wrapper
around
PFLAG.
That
is
supposed
to
help
with
some
of
them
were
challenging
tasks.
When
people
migrated
to
component
config
configurations,
especially
around
maintaining
backwards
compatibility
during
the
deprecation
timeline
of
like
the
flights
that
you're
migrating
to,
so
we
also
have
a
bunch
of
work-in-progress,
notably,
we
have
a
lot
of
work
by
new
contributors
who
are
being
mentored
in
working
group.
H
H
We
also
have
a
number
of
kind
of
important
caps
that
in
flight
few,
around
graduating
various
components,
component,
config
api's
to
data-
we
have
some
ideas
around
how
to
handle
fields
and
optional
parameters
and
component
config
some
discussions
around
whether
we
should
just
totally
get
rid
of
command
line
flags
or
provide
at
least
some
way
to
do
some
way
overrides
for
debugging
or
simple
config
cases
in
component,
configure
it
now
and
so
now.
This
is
the
most
important
slide
of
this
presentation.
H
This
is
about
the
future
and
kind
of
where
we
need
help.
So
today,
a
lot
of
our
projects
have
been
focused
on
config,
because
that
was
one
of
those
to
report
founding
things
that
working
group,
but
we're
actually
scopes
to
do
more
than
just
config
again.
This
is
for
developing
a
sort
of
standard
foundation
for
core
components
to
build
on
topics.
H
So
if
you
see
opportunities
where
the
same
features
implemented
in
a
lot
of
different
places,
but
you
think
it
should
have
a
common
implementation-
a
common
foundation
are
working
with,
is
the
place
to
come
and
propose
that
and
work
on
it,
and
we
are,
you
know
again.
We
actively
mentoring
new
contributors
and
we're
happy
to
have
new
people.
We
just
sent
out
an
email.
H
Some
of
you
might
have
seen
earlier
this
week,
requesting
new
people
and
we've
gotten
a
ton
of
interest,
so
in
our
weekly
meeting
next
week,
we'll
be
running
a
small
intro
session
kind
of
to
the
working
group
and
how
to
get
served
on
some
of
our
ongoing
projects.
So
for
people
who
are
interested,
you
know
please
reach
out
to
us
on
slack
on
our
mailing
list.
So
again
how
you
can
get
started
come
to
our
meeting
next
week,
we'll
have
an
intro
session.
H
You
can
find
open
issues
in
our
project
board
or
with
our
WG
component
standard
label
on
github.
Our
selection
is
hash
tag,
WG
component
standard,
so
reach
out
to
us.
There
I
think
I
actually
reach
out
to
us
there
I'm
on
the
mailing
list.
We
can
mentor
you
if
you
want
to
work
on
projects,
we're
mentoring,
people
right
now,
it's
a
great
way
to
get
started.
H
So
here's
some
basic
information
myself
stealthy
boxing
is
defined.
The
chairs
we've
got
the
home
page
link
their
selection
on
mailing
list.
Also,
a
link
to
all
of
our
meetings
recorded
on
YouTube.
That's
our
playlist.
You
can
also
find
the
onboarding
session
we
ran
over
the
summer
there
thanks
so
much.
A
All
right,
thank
you
again.
I
really
appreciate
folks
coming
and
sharing
this
the
between
the
the
weekly
meeting
and
the
recordings
of
these
and
getting
each
of
the
cigs
and
now
working
groups
also
coming
by
quarterly.
We
really
hope
that
this
community
meeting
becomes
sort
of
the
the
one-stop
shop
spend
the
maximum
hour
a
week,
keeping
up
a
pulse
of
the
overall
project.
What
is
going
on
alright?
Moving
on
to
our
next
topic
area,
we
have
announcements,
election
status
for
the
steering
committee
George
or
Bob
Dylan.
Would
you
like
to
speak
to
that.
G
G
302
of
you
out
of
the
850,
have
voted
yea
if
you're
in
the
voters,
MD
and
I
put
the
link
in
the
notes
there,
if
you're
in
that
file-
and
you
have
not
received
a
ballot-
please
let
us
know
at
election
at
kubernetes
I/o
and
all
these
have
been
published
on
the
kubernetes
dev
mailing
list.
If
you're
not
in
that
file,
then
you've
missed
all
the
deadlines.
Some
time
to
snag
you
next
time
and
that's
it.
A
A
A
Not
seeing
any
alright
so
shoutouts
for
the
week,
we
have
a
channel
and
slack
called
shout
outs,
and
it's
just
a
place
to
show
appreciation
and
give
thanks
and
celebrate
the
work
of
your
peers
in
our
huge
community,
and
it
was
a
very
active
channel
this
week,
which
is
kind
of
natural.
We
just
finished
the
one
that
16
releases.
A
We
talked
about
a
little
bit
earlier,
and
people
are
kind
of
doing
a
pause
in
between
release
cycles
and
kind
of
thinking
about
where
their
teammates
have
been
great
teammates
and
expressing
that
in
the
channel,
so
to
kind
of
go
through
them.
Lachlan
Evanson,
who
is
our
note-taker
today,
but
it
was
also
our
outgoing
release
team
lead
for
1.16.
He
gives
a
big
thanks
to
Gwen
singer.
A
It
looks
like
Geoff
and
Nico
for
being
fantastic
leads
also
in
the
kubernetes
1.16
release
cycle.
Also,
things
from
Lachlan
to
liggett,
see
blacker
and
dims
for
their
tireless
work
during
the
1/16
release.
These
three
in
particular
are
stellar
community
members
who
are
just
on
top
of
all
sorts
of
things
and
they're
sort
of
members
of
the
release
team
at
large.
A
Making
things
happen
and
and
really
getting
things
done
in
the
last
moments
of
the
release,
more
sacredly,
shout
outs
from
stephen
augustus
and
a
link
to
a
tweet
that
he
gave
out
they're
just
really
feeling
some
pride
for
the
release.
Team
and
cig
release
appreciates
all
the
volunteers
there
and
what
all
they
do
to
get
you
to
release
out
Jason
Day
Tiberius
has
a
shout
out
to
a
large
list
of
people
from
the
cluster
API
team
who
came
together.
A
Josh
burkas
huge
shout
out
to
Tim
Hakan
for
coming
up
with
tons
of
ideas
for
contributor
summit
sessions.
The
contributor
summit
is
coming
up
the
day
before
the
official
program
of
Q
con
starts
and
the
schedule
I
think
is
just
about
to
get
released
and
people
have
been
submitting
topics
and
Tim
Hawkins
submitted
quite
a
few
great
suggestions
there.
A
That
josh
is
really
appreciative
of
as
the
organizer
of
or
one
of
the
organizers
of
the
content
for
the
summit
and
Tim
Hawken
thanks
Josh
and
everybody
else
who
were
involved
in
volunteering
on
that,
because
it
is
a
large
volunteer
event
and
finally
Vince
pregnant.
Oh
I,
shout
out
to
Cecil
for
putting
a
huge
amount
of
work
towards
publishing
cap
Z,
the
cluster
api
asher
for
v1
alpha
2.