►
From YouTube: Kubernetes Community Meeting 20200319
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
Kubernetes
community
can
be
a
great
place
for
you
to
participate.
If
you
like,
what
you
see,
there's
always
room
for
you
to
be
a
contributor
in
different
ways.
Contributor
experience
is
here
to
be
that
jump
off
point
for
you.
So
please
join
us
in
our
slack
or
any
of
our
regular
meetings
and
we
will
get
you
oriented
and
on-boarded
to
a
special
interest
group
and
get
you
rolling.
But
with
that
we'll
just
jump
right
into
the
fray
here,
Jorge
is
going
to
give
us
an
update
on
the
current
release
or
hey.
Are
you
there.
A
D
C
So,
starting
with
a
steering
committee
update,
this
is
the
first
update
after
the
last
election.
So
we've
got
some
new
members
now
right
now,
it's
Christoph
direct
terms,
myself
Parris,
Aaron
and
Tim
on
the
steering
committee.
Please
feel
free
to
reach
out
to
us.
These
are
stuck
and
github
handles
and
you
can
also
find
more
info
in
the
kubernetes,
slash
steering
people
so
I'm,
going
to
cut
right
to
the
trails
and
talk
about
something
that
we've
been
working
on
since
the
past
month
and
something
that's
going
to
affect
the
community
as
a
whole.
C
So
we
are
planning
on
setting
up
a
program
called
community
health
check
or
a
roll
call
similar
to
what
Apache
does
so
six
sigelei,
so
sick
chairs
will
fill
out
a
questionnaire
about
the
health
of
their
sick
and
the
steering
committee
will
review
their
answers.
If
the
steering
committee
has
more
questions
or
we
feel
that
there
is
merit
and
discussing
certain
aspects,
we
will
invite
the
sick
chairs
to
the
sig
chair,
TL
monthly
meeting,
to
discuss
more
about
it
and
yeah.
So
tourists
are
more
about
how
this
would
look
like.
C
C
So
if
you
are
a
Sayyed
or
chair
sick
charity
al
you
can
attend
that.
I
want
to
make
sure
that
this
discussion
happens
in
that
meeting,
so
that
other
leads
can
pitch
in
and
six
can
take
inspiration
from
each
other
as
well,
and
we
certainly
don't
want
any
more
meetings.
I
pretty
sure-
and
we
are
also
setting
up
a
person
guide
for
the
steering
committee
meeting.
C
So
for
those,
if
you
don't
know,
we
have
a
public
monthly
steering
committee
meeting
and
we
really
felt
that
having
a
bosom
guidance
script
would
help
in
making
sure,
like
the
agenda
is
published
to
the
mailing
list
before
the
meetings
and
notes
are
published
after
the
meetings
and
all
staring
members
have
adequate
context
and
come
prepared
so
that
we
don't
spend
too
much
time
discussing
or
debating
in
the
meeting
itself,
which
I
know
has
happened
in
the
past.
So
we
want
to
make
sure
that
meetings
are
much
more
efficient
and
effective
for
everyone.
C
Next
up,
we
are
planning
of
cleaning
up
some
of
the
inactive
Reapers
and
the
main
kubernetes
github
are,
if
you've
already
seen
some.
If
you
are,
if
you're
already
on
the
mailing
list
of
some
sects,
you
might
have
seen
that
we
are
also
cleaning
up
Reapers
in
the
kubernetes
incubator
or
github
part,
so
we're
moving
them
to
cover
86
or
we
feel
like
there
aren't
enough
people
contributing
to
it
or
it's
not
needed
anymore.
We
are
moving
them
to
come
in
it,
we're
just
archiving
them
and
moving
them
to
the
kubernetes
retired
org.
C
C
C
The
other
thing
that
we've
been
working
on-
and
this
is
a
really
sort
of
a
tough
problem
to
solve,
is
like
say,
you're
an
approver
for
some
part
of
the
code
base,
and
you
want
help
with
the
task,
like
that's
a
little
bit
of
a
bigger
task
like
say
migrating,
the
part
of
the
code
base
that
would
take
certain
weeks
or
even
months.
So
you
want
to
make
sure
that
you
don't
get
drive-by
contributions
for
such
tasks
and
contribute
a
stick
around
when
they
are
when
they
show
up.
C
So
we
are
looking
at
crafting
policies
to
define
policies
and
tools
to
help
with
this,
we
have
used
the
rule
board
on
discussed
at
kubernetes
that
I
are
in
the
past
and
while
we
did
get
some
folks
from
there,
it's
proven
to
be
a
little
harder
to
get
traction
on
it.
So
we
are
going
to
draft
a
policy
or
to
community
members
domini
and
matthias
helped
draft
googledoc
draft
a
policy
for
it.
It's
still
in
review,
but
and
we're
still
discussing
more
ideas.
C
If
you
have
ideas
around
this,
please
feel
free
to
pitch
in
on
issue
issue
number
141
on
the
steering
this
has
being
in
discussion
for
quite
some
time
now
that
we
are
planning
up
on
setting
up
a
travel
support
program
for
active
contributors,
who
one
responsible
can't
be
sponsored
by
their
employers
to
travel
to
coupons.
So
we
targeting
this
for
Amsterdam
whenever
that
might
be
and
will
provide
updates
as
soon
as
we
get
more
information
and
discuss
more
with
CN
CF.
C
Finally,
we
also
have
issue
templates
in
the
community,
slash
steering
repo
to
make
sure,
like
the
community,
can
Triple
S
problem
statements
or
propose
whatever
ideas
they
have
in
a
much
more
efficient
manner.
So
you
can
use
this
and
you
can
also
reach
out
to
us,
and
the
public
slap
channel
feel
free
to
like
jump
in
any
thoughts
you
might
have
regarding
anything
in
there
we
have
a
mailing
list
steering
and
kubernetes
data,
which
is
public
and
then
finally
discuss
something.
C
Okay,
we
have
steering
private
at
community
style,
we
have
meetings
that
are
public
and
anyone
can
join
on
first
Mondays
of
each
month
at
11
a.m.
Pacific
time.
If
there
is
something
that
you
would
like
to
discuss
in
the
meeting,
especially
if
something
that
requires
woods
or
decision-making,
please
send
an
email
to
the
mailing
list
beforehand,
so
that
everyone
has
adequate
context
and
everyone
comes
prepared
to
the
meeting.
C
Finally,
you
can
also
file
an
issue
in
the
community
is
steering
people
and
I
also
just
want
to
say
that
all
of
us
are
super
friendly
is
if
there's
something
that's
like
bothering
you
no
matter
how
tiny
that
might
be
feel
free
to
DMSO.
If
you
just
want
to
bounce
thoughts
of
someone,
and
we
can
try
and
see
how
we
can
figure
out
problems
together
and
yeah,
that's
all
I
have
Thank.
A
You
Nikita,
thank
you
so
much
for
that
update.
It's
really
great
to
see
the
progress
happening
in
the
steering
committee
and
great
calls
to
action
for
all
of
us.
If
we
want
to
get
more
involved,
you
are
very
friendly.
I
can
attest
to
that
as
a
newbie
to
go
back
a
step
or
rayar.
Can
you
give
us
a
brief
update
on
release
management.
B
Yes,
absolutely
so
hi
everyone
I'm
the
release,
lead
for
kubernetes
118
and
right
now
we
are
in
week
11
of
the
kubernetes
really
of
the
Korean
coronaries
release
cycle.
This
is
hopefully
the
last
full
the
last
full
week
for
this
cycle
in
the
pack
in
the
past.
In
the
past
couple
weeks,
there's
been
a
there's
been
a
lot
of
work,
some
of
the
most
notable
updates.
A
we
have
is
a
new
kubernetes.
Patch
versions
have
been
made
available,
so
115
11,
168
117
for
are
out
in
the
wild.
B
If
so,
it
is
time
to
a
it
is
time
to
upgrade
indirectly
regarding
kubernetes
118.
We
are
now
in
the
interior
of
Kota,
so
they
must.
The
master
branch
and
kubernetes
kubernetes
is
wide
open.
A
contributors
can
now
merge
their
fears
and
everything
that
caused
him.
From
now
on,
it's
gonna
be
slated
to
cover.
Ladies
acorn.
It
is
119
if
anyone
has
any
patch
or
PR
than
you
think
should
go
into
one
18.0.
If
you
are
a
please
feel
free
to
a
proposed.
A
cherry
pick
of
your
PR.
B
Now,
the
current
the
current
deadline
for
that
they,
the
deadline
that
we
are
proposing
for
118
0,
is
next
Tuesday,
March
20.
If
everyday.
If
everything
goes
well
and
hopefully
a
not
a
nothing
breaks
between
now
and
then
a
the
world
will
have
a
new
governess
version
of
a
out
and
about
that
everyone
that
everyone
can
use
and
other
a
big
announced
order.
Big
announcement
that
we
have
is
take
away.
They
released
him
at
the
end
of
a
at
the
end
of
each
cycle.
We
have
a
retrospective
where
we
go
back
a
work.
B
We
go
back
and
revisit
things.
I
have
that
we
believe
have
done
have
been
done
very
well
things
that
we
could
do
better
in
the
future.
The
retrospective
for
118
is
scheduled
for
April,
April
or
moderator
is
going
to
be
Jeffy.
Thank
you,
Bob,
very,
very
much,
and
possibly
if
we
need
a
second
part
for
the
retrospective,
which
has
been
the
case
in
the
past.
That
will
be
scheduled
for
April
6
during
the
sinc
release
weekly
meeting
and
those
are
all
the
updates
that
I
have
from
the
release
team.
Thank
you
very
much.
Okay,.
A
E
Hello,
everyone.
Can
you
hear
me?
Yes,
okay,
can
you
see
my
screen
great
okay,
hello,
everyone,
I
am
Alana.
Hashman
I
am
the
I
guess
one
of
the
newly
crowned
chairs
of
sig
instrumentation,
so
I'm
going
to
jump
right
to
our
update.
We
recently
in
the
past
couple
of
weeks
have
had
a
shift
in
our
sig
leadership.
So
the
first
thing
that
I
will
announce
is
our
new
cichlids
hi
I'm,
one
of
them
peter,
is
becoming
an
emeritus
lead.
Frederick
is
shifting
from
his
chair
role
to
becoming
a
tech.
E
Lead,
I
am
becoming
a
chair
as
well
as
Han
Kang,
also
becoming
a
chair
and
David
Asheville
was
elected
today
as
our
second
tech
lead.
So
if
you
have
any
questions
about
sig
leadership,
these
are
now
folks
to
contact
and
I
will
have
a
summary
of
them
at
the
end
of
the
slides
as
well.
For
those
who
are
not
familiar
with
sig
instrumentation,
what
do
we
do?
E
Well,
we
are
responsible
for
all
the
instrumentation
across
the
kubernetes
project,
so
we
are
a
horizontal
sea
and
frequently
it's
kind
of
easy
to
imagine
this
as
us
covering
the
three
pillars
of
observability,
and
that
is
what
I
will
split
our
updates
into
so
metrics
time.
Series
data,
that's
emitted
by
various
components
of
the
project
logging,
which
is
text-based
data
emitted
from
various
components
and
traces
which
allow
us
to
trace
requests
from
the
beginning
of
their
life
through
the
end
so
I'm.
E
So
on
the
metric
side,
we
have
a
metric
stability
framework
that
was
accepted
a
few
releases
ago
and
as
of
the
118
release,
it
is
now
in
beta.
We
have
migrated
the
culet
resource
metrics
to
use
this
metric
stability
framework
and
hence
the
metrics
endpoint
has
moved
from
an
alpha
endpoint
to
a
non
alpha
endpoint,
which
is
kind
of
exciting
for
DQ
bullets.
E
On
the
logging
side,
we
have
a
structured
logging
cap,
which
was
just
accepted
this
quarter
and
was
just
moved
in
the
past
couple
of
weeks
to
implementable.
So
we
are
targeting
alpha
for
the
119
release,
and
contributors
are
wanted
to
help
out
with
that
effort.
If
folks
are
interested
structured
logs,
as
opposed
to
just
you
know,
regular
boring
old
text
logs
are
typically
emitted
in
a
format
like
JSON
with
key
values
which
make
them
easier
to
parse
and
easier
to
process.
E
On
the
tracing
side,
our
distributed
tracing
cap
was
just
merged
again
in
the
past
quarter
and
as
a
result,
sig
API
machinery
has
gone
ahead
and
added
context
to
client
go
functions
to
help
implement.
Some
of
this
there
is
more
to
go.
The
cap
is
not
yet
in
the
implementable
State,
it
is
currently
provisional,
but
that
is
hopefully
we're
targeting
implementable
suit.
E
Lily
tells
me
very
emphatically
that
new
contributors
are
wanted
so
more
info
on
that
later
in
the
slides'
metric
server
status,
one
of
our
other
sub
projects,
so
recently,
metrics
server
has
been
working
on
improved
documentation
and
installation
instructions
to
make
it
easier
for
folks
to
install
and
use
recently
our
there
was
an
effort
for
triaging
the
backlog,
and
so
a
bunch
of
issues
have
been
identified
for
new
contributors
to
make
that
easier
for
folks
to
contribute
to
the
project.
There
are
two
upcoming
releases.
E
Oh
three,
seven
has
significant
improvements
for
the
release
pipeline
and
oh
for
ode
next
to
major
rewrite
addressing
production.
Readiness
issues
that
have
been
raised
here
is
a
list
of
relevant
caps.
I
mean
you
can't
click
on
my
screen,
but
all
of
the
links
are
available
in
the
slides,
which
are
the
meeting
notes.
So
if
you
want
to
take
a
look
at
in
particular
structure,
logging
cap
and
the
distributed
tracing
cap,
those
are
the
links
and
how
can
you
contribute
cube?
State
metrics
is
seeking
new
contributors.
E
I
guess:
I
didn't
really
introduce
cube
state
metrics,
a
quick
summary
of
that
project.
It's
effectively
like
a
Prometheus
adapter
for
your
cluster
state,
so
it
can
emit
various
information
like
pod,
statuses
and
things
like
that
in
Prometheus
format,
so
you
can
consume
them
in
your
Prometheus
or
other
vendor
products.
So,
if
you'd
like
to
help
out
with
that,
you
should
contact
Lily,
her
github
handle
is
Lily
C
and
the
metric
server,
which
provides
a
summary
format
of
metrics
for
horizontal
pod,
auto
scalars,
and
things
like
that.
E
They
are
also
seeking
new
contributors
and
structure
blogging.
Also
seeking
new
contributors
for
both
metrics
server
and
structure
logging.
Please
contact
Merritt
who's
github
handle
is
sera
theas.
Where
can
you
find
us?
I
am
one
of
the
chairs
Hana
also
another
one
of
the
chairs
tech
leads
are
frederick
and
david
actual.
You
can
find
us
on
slack.
That
is
probably
the
best
place
to
find
us
in
our
slack.
There
is
a
link
to
our
meeting
notes,
as
well
as
our
mailing
list
and
google
group.
E
If
you
subscribe
to
that,
you
will
get
the
automatic
invite
to
our
meetings.
I
don't
want
to
try
to
tell
you
the
time
for
the
meetings,
because
daylight
savings
time
has
messed
everything
up.
They
are
bi-weekly
on
Thursdays.
Our
next
one
is
in
ten
minutes,
as
you
can
hear
from
my
reminder,
but
I
will
probably
not
drop
so
I
can
attend
the
rest
of
the
community
call.
So
if
you
have
any
questions
best
place
to
reach
out
is
on
flack
and
I
hope
to
see
you.
There
perfect.
A
A
We
kind
of
release
containing
the
new
CRD
version
of
service
catalog,
which
is
your
DBS
rather
than
the
eyesore
implementation,
and
pretty
much
other
than
that.
We've
only
been
in
maintenance,
but
we've
been
fixing
bugs
that's
pretty
much
it.
We
don't
really
have
anything
any
new,
pressing
features
or
future
sets
on
the
docket.
A
Given
that
participation,
the
signals
to
down
turned
after
several
companies
left
the
project
we've
been
trying
to
source
new
new
people
to
be
interested
in
contributing
and
we've
got.
A
couple
leads
are
working
on
that,
but
not
anything
they're
prepared
to
announce
this
time.
So
no
problem,
hey
Jonathan.
Can
you
give
maybe
like
a
boilerplate
pitch
for
what
service
standard
covers?
A
So,
for
those
who
don't
know,
service
catalog
is
an
implementation
of
the
open
service
broker
API,
which
is
an
open
standard
for
allowing
cloud
platforms
like
kubernetes,
but
in
a
very
generic
sense
to
provision
and
manage
cloud
resources
again,
a
very
generic
sense
without
having
to
know
the
specifics.
So
say
you
want
my
sequel
databases
to
be
a
type
that's
available
for
provisioning
on
your
kubernetes
cluster.
A
A
So
that's
kind
of
what
we're
trying
to
figure
out
is
how
how
does
Service
Catalog
fit
into
that,
because
now
that
we've
acted
as
being
CR
debased
it
I
guess
he
is
an
operator
depending
on
the
technical
definition
of
what
an
operator
is
I
mean
was
written
manually.
It
wasn't
produced
using
cube
builder
or
operator
SDK,
but
I
mean
it's
the
definition
I
guess
so.
A
We've
been
we've
been
in
talks
with
a
lot
of
the
operator
SDK
and
the
cube
builder
folks
about
what
exactly
the
future
is
going
to
look
like,
because
a
lot
of
the
the
operators
people
are
writing
have
problems
that
Service,
Catalog
sort
of
solves
Weather,
Service
Catalog
is
going
to
be
the
solution
of
those
or
people
are
going
to
invite
something
else.
That's
that's
up
for
discussion,
ok,
cool!
So
if
you
like
a
little
ambiguity
and
some
cloud
service
providers
and
kubernetes,
you
might
just
happen
sig.
Thank
you.
Jonathan
anything
else.
A
D
So
next
are
presenting,
so
my
name
is
Sully
I'm
one
of
the
co-chairs
for
six
storage.
So
first
up
I
want
to
talk
about
some
of
the
governance
updates
that
cig
Storage
has
gone
through
recently
I.
Some
of
you
are
aware.
Our
co-chair
Brad
childs
passed
away
late
last
year,
and
so
we
put
together
a
little
memorial
for
him
feel
free
to
take
a
look
at
that.
D
I'll
share
the
slides
in
the
agenda,
so
we
were
looking
to
fill
his
seat
and
in
doing
so,
what
we
decided
to
do
was
follow
the
model
of
other
SIG's
and
adopt
not
just
two
chairs,
but
two
tech
leads
as
well
and
for
the
chairs
I'm
going
to
be
continuing
as
a
chair
and
Shang
Yang
has
stepped
up
to
take
the
other
chair
and
tech.
Liens
Michelle
who
and
Yan
suffer
neck
are
going
to
be.
Our
tech
leads
they've,
both
been
working
and
six
storage
for
a
very
long
time.
D
If
any
of
you
have
interacted
with
six
storage,
I'm
sure
you're
familiar
with
their
work.
So
join
me
in
congratulating
them
when
you
get
a
chance,
so
highlights
from
the
1.17
release
which
went
out
late
last
year.
There
were
three
big
features,
one
with
CSI
topology.
This
is
a
feature
to
allow
CSI
drivers
to
surface
to
kubernetes
what
the
internal
to
what
their
internal
topology
looks
like.
D
What
this
means
is
that
some
volumes
may
not
be
equally
accessible
to
all
notes
within
a
cluster,
and
we
now
have
a
mechanism
by
which
a
storage
system
can
surface
that
information
up
to
kubernetes,
so
that
kubernetes
can
make
intelligent
scheduling
decisions
using
that
and
so
that
functionality
is
now
moved
to
GA.
The
second
big
feature
was
volumes
snapshots.
This
is
a
something
that
we
had
in
alpha
for
a
long
time.
It
allows
a
kubernetes
user
to
use
just
the
kubernetes
api
to
trigger
a
snapshot
on
a
volume.
D
Rather
than
going
around
kubernetes
and
interacting
directly
with
the
storage
system,
we
moved
that
functionality
to
beta
in
1.17.
This
was
a
significant
rewrite
and
breaks
a
lot
of
the
api
between
alpha
and
beta.
So
if
you
were
using
the
alpha,
please
take
a
look
at
this
and
figure
out
what
the
differences
are
as
we
move
to
GA
we're
anticipating
much
for
your
API
changes.
D
We
have
a
legacy
way
of
doing
it,
which
is
entry,
volume,
plugins,
we're
kind
of
putting
all
new
features
into
CSI,
but
we
want
to
provide
a
seamless
migration
story
for
entry
volume
plugins
to
CSI
and
the
core
functionality
to
enable
that
seamless
migration
has
moved
to
beta
last
quarter
and
now
all
the
different
cloud
providers
who
had
entry,
Balian
plugins,
are
working
on
on
on
writing
adapters
to
plug
into
that
to
enable
enable
that
seamless
transition
that
includes
GCE,
eight
of
u.s.
sure
and
vSphere.
D
Talking
about
this
release,
that's
going
out
in
the
next
couple
of
weeks.
The
big
features
that
six
stories
delivered
here
are
raw
block
volumes.
This
allows
for
a
volume
to
be
surfaced
up
in
a
container
as
a
block
device
instead
of
a
mounted
file
system.
The
benefit
of
this
is
there
are
some
databases,
for
example,
or
software-defined
storage
systems
that
prefer
to
interact
directly
with
a
raw
block
device
rather
than
through
a
file
system
for
performance
reasons.
They
can
do
that
now.
Volume.
Cloning
was
another
feature
that
we
moved
to
GA.
D
This
allows
you
to
use
the
kubernetes
api
to
create
a
a
duplicate
of
a
volume
that
you
have
and
this
functionality
moved
to
GA
and
as
it'll
work
as
long
as
your
underlying
CSI
driver
supports
it,
and
then
the
third
feature
that
we
moved
to
GA
was
the
CSI
driver
kubernetes
api
object.
This
is
for
CSI
driver
authors,
it's
a
mechanism
by
which
your
driver
can
customize
how
kubernetes
interacts
with
it.
For
example,
if
you
don't
need
a
volume
attached,
you
can
instruct
kubernetes
to
skip
attach
for
your
driver.
D
It
also
makes
it
a
little
bit
easier
for
users
to
discover
what
drivers
are
installed
by
doing
a
cute
cuddle,
get
a
CSI
driver's
call
and
then
finally,
we
introduced
a
couple
of
features
in
alpha
in
1.18.
The
big
one
is
Windows
CSI
support,
so
CSI
is
the
mechanism
that
we
are
using
for
extending
kubernetes
storage.
D
This
becomes
a
huge
problem.
If
you
have
a
ton
of
files
and
directories
and
your
volume
and
so
we're
introducing
a
new
flag
that
allows
you
to
be
allows
kubernetes
to
be
a
little
bit
smarter
when
it's
doing
this,
it'll
only
go
through
and
change
ownership
if
the
route
ownerships
do
not
match
so
it'll,
do
it
the
first
time
and
then
every
subsequent
time
will
be
a
lot
faster.
If
you
are
interested
in
any
of
this,
please
join
us
in
our
bi-weekly
meetings.
D
The
next
meeting
is
going
to
be
next
Thursday
on
the
26th
at
9:00
a.m.
Pacific
time.
We're
gonna
be
doing
a
wrap-up
of
the
1.18
release,
getting
a
final
status,
update
of
what
made
it
into
the
release
and
what
did
not,
and
then
the
subsequent
meeting
we're
going
to
be
doing
a
planning
session
for
what's
going
to
go
into
the
1.19
release,
those
meetings
tend
to
be
the
most
crucial
because
it's
where
we
plan
what
the
cig
is
gonna
work
on
who
gets
to
work
on
what?
D
So,
if
you're
interested
in
participating
at
all
those
would
be
the
meetings
to
attend.
We
have
a
couple
of
mechanisms,
forums
that
you
can
communicate
with
us.
One
is
the
slack
channel
there's
a
number
of
people
that
are
answering
questions
on
that
feel
free
to
to
go
there
and
ask
any
questions
you
might
have,
and
then
you
have
a
mailing
list
as
well.
That's.
A
A
Moving
right
along,
maybe
she'll,
be
able
to
join
later
we're
rolling
right
into
announcements
being
really
efficient
on
time.
So
quick
recap
of
things.
The
last
update
on
coop
comm
is
that
it
has
been
delayed.
As
we
know
it's
targeting
right
now,
July
August
timeframe,
there
will
be
some
in-person
contributor
summit
there.
That's
the
last
update
from
the
team,
but
there
will
be
more
virtual
meetings
in
the
meantime
so
keep
reaching
out
to
peers.
A
If
you
need
to
connect
in
the
short
term
long
term
there
something
will
come
together
once
you
know,
there's
some
more
certainty
there,
but
be
especially
appreciative
for
anyone
who
runs
events
in
the
tech
world
right
now.
They
are
going
through
quite
a
lot
and
they
do
incredible
work
so
that
we
can
have
a
seemingly
seamless
time
so
feeling
sending
a
lot
of
love
out
to
everybody
there.
Thank
you
for
what
you
do
if
you're
listening
next
up
the
next
host
for
this
next
meeting
for
April
will
be
Taylor.
A
Taylor
is
an
SRE
at
Disney
he's
listed
himself
as
a
book
fan
and
I
did
a
little
internet,
stalking
and
found
out
he's
reading
a
great
book
that
maybe
you
can
give
us
a
book
review
up
next
month.
Why
are
you
yelling
the
art
of
productive
disagreement?
Taylor,
please,
you
know
give
that
shout
out
next
month.
That's
definitely
why
I'm
gonna
show
up
amongst
the
kubernetes
things
and
he's
also
the
released
lead
for
1.19,
so
very
excited
to
have
him.
A
There
are
some
additional
updates
coming
in
so
regarding
KU
con
thanks,
Thank
You
Saul,
our
ecosystem,
teka
of
events,
organizers,
who
are
dealing
with
very
complicated
logistics
right
now,
absolutely
to
bring
us
towards
the
end
of
this
meeting.
We've
got
shout
outs
listed.
There
are
a
ton,
but
we've
shifted
to
a
month-over-month
in
this
meeting.
A
So
there's
a
ton
of
shout
outs
to
people,
but
for
those
that
are
familiar
with
it,
there's
a
shout
outs
channel
in
our
slack
community
be
sure
to
highlight
people
that
have
been
kind
to
you
that
have
helped
you
with
things
or
just
stuff.
You
appreciate
about
being
a
member
of
this
community
and
when
this
is
sent
out
after
take
some
time
to
go
through
and
see
specifically
what
was
helpful,
it's
really
inspiring
to
see
you
know
new
participants
and
longtime
participants
appreciating
each
other
with
that.
A
A
All
right
all
quiet
on
the
western
front
here
so
we'll
take
some
time
to
update
the
agenda
and
then
send
that
out
to
both
this
course
and
the
kubernetes
dead
mailing
list.
Thank
you
all
for
being
participants
really
appreciate
having
you
here.
I
hope
you
all
have
a
wonderful
time
at
home,
send
more
pictures
in
in
on
Twitter
and
in
slack,
and
we
will
see
you
next
month
or
at
your
local
cig
Meetup.
Thank
you
thanks.
Everybody
bye
all
happy
Thursday.