►
From YouTube: Kubernetes Office Hours 20200617 (West Coast Edition)
Description
Office Hours is a live stream where we answer live questions about Kubernetes from users on the YouTube channel. Office hours are a regularly scheduled meeting where people can bring topics to discuss with the greater community. They are great for answering questions, getting feedback on how you’re using Kubernetes, or to just passively learn by following along.
For more info: https://github.com/kubernetes/community/blob/master/events/office-hours.md
A
Hello,
everybody.
This
is
a
community
meeting
june
kubernetes
community
meeting
and
this
will
be
live
streamed
and
posted
publicly
on
youtube.
So
please
be
mindful
that,
whatever
you
say
is
being
recorded.
We
have
a
code
of
conduct,
so
please
be
excellent
to
each
other.
My
name
is
Laurie
Apple
I'm,
coming
to
you
from
Berlin
Germany
I'm,
representing
SIG's,
contra
bugs
and
release.
A
A
Can
someone
put
you
in
and
take
notes,
okay,
I
guess
I
will
do
that.
So
we
should
go
to
our
release.
A
So
shall
we
move
on
to
our
release?
Updates
we've
got
for
the
least
development
cycle,
Taylor
Dolezal
our
release
lead
hello,
Taylor,
hey.
B
Everybody
how's
it
going
hope
that
you're
having
a
fantastic
Thursday
so
I
definitely
have
an
update
for
you
one.
Let
you
know
that,
as
of
yesterday,
we
have
a
couple
bug-fix
releases
that
came
out
118
for
117,
seven
and
one
sixteen
eleven.
There
is
a
known
issue
with
118
for
and
I
believe
the
team
was
looking
at
that
next
up
list,
we've
got
terrific
deadline,
which
is
going
to
be
July,
10th
and
release
target
on
that
one.
This
one
visualizes
it's
August
through
December
2020.
B
We
have
all
of
those
releases
planned
and
documented
in
the
meeting
notes
and
we
did
have
some
scheduled
shifts
just
as
an
update.
So
you
have
not
seen
that.
Please
take
a
look
at
that.
I'll
be
sure
to
link
to
that
in
the
meeting
notes
as
well
other
than
that
I've
got
nothing
hope
y'all
again
have
a
fantastic
Thursday
and
I'll
talk
to
you
later.
C
Cool,
can
everybody
hear
me
I
hope?
Yes,
all
right
sure
Oh
can't
share
my
screen
yet
says:
host
disabled
Debbie
screeching.
Try
now
alright,
wonderful!
It
looks
like
it
works,
alright,
so
triage
party.
So
let
me
talk
a
little
bit
about
triage
party,
real
quick,
so
my
name
is
Tom
Stromberg
I'm,
one
of
the
many
containers
and
mini
cube,
gets
a
lot
of
incoming
issues.
Lots
of
it's
for
a
lot
of
people,
it's
their
first
experience
in
kubernetes,
not
everybody
is
super
technically
adept
and
a
lot
of
people
are
and
kubernetes
just
complicated.
C
Frankly,
so
we
have
to
help
a
lot
of
people
and
we
felt
like
we
were
really
dropping
the
ball
last
year.
So
we
ended
up
with
this
idea
of
somebody
who
is
on
triage
duty
and
we
would
rotate
between
the
maintainer
--zz
every
week
to
kind
of
go
through
the
issues,
and
we
had
this
long.
Complicated
document
to
actually
say
like
here
are
the
queries
that
we
run
and
it
was
time-consuming
and
I
felt
like
we
were
going
nowhere.
C
So
I
did
like
what
any
good
engineer
does
and
tried
to
automate
myself
out
of
a
job.
So
I
created
triage
party,
so
I'm
going
to
show
you
the
version
for
the
instance
for
me
cube
right
now,
so
you
can
follow
along
by
doing
tinyurl.com,
slash,
you're,
gonna,
keep
party
and
hopefully
it'll
load
quickly,
but
so
this
is
instance
hosted
by
cloud
run
and
what
we
can
see
we
go
visit
the
daily.
C
So
this
one
isn't
that
amazing,
it
Sun
prioritized
issues
older
than
five
days.
But
what
is
interesting
is
that
every
rule
that
we
have
has
a
clear
resolution
path
to
make
sure
to
get
this
box
empty,
and
this
page
should
be
empty
at
least
once
a
day
and
will
give
somebody
a
really
nice
message
when
this
page
is
actually
empty.
C
C
We
are
also
able
to
do
things
like
with
the
state
tracking
needs
information,
but
has
an
update,
so
these
have
been
labeled
as
needs.
It
triage
needs
information,
but
what
you
can
see
here
from
this
receive
tag
is
that
the
author
of
the
issue
has
actually
come
back
to
us
with
more
information
and
we
need
to
go
ahead
and
and
see
what
they
have
to
say,
for
instance,
so
you
can
see
here
they
have
they've,
provided
some
more
information.
C
So
now
I
can
go
ahead
and
say
this
is
no
longer
a
needs
information
kind
of
issue.
So
so
we
also
have
a
weekly
triage,
and
this
is
where
we
get
to
show
off
one
of
the
other
unique
features
which
is
so
for
our
weekly
triage.
We
host
a
zoom
meeting
that
anyone
in
the
community
can
participate
in,
and
so
you
can
see.
We've
got
55
items
listed
here
for
covering
in
our
weekly
triage,
which
sounds
like
a
long
boring
meeting,
but
we
are
able
to
paralyze
the
effort
using
multiplayer
mode.
C
So
if
there
are
six
people
in
the
meeting,
then
we
can
assign
player
numbers
based
on
who's
there
and
it's
what's
the
work
up
among
it'll
it'll
split
the
work
among
our
six
ways
based
on
the
github
IDs,
so
this
has
turned
out
to
be
one
of
the
the
best
features
and
where
a
triage
party
actually
got
its
name,
so
we've
got
some
other
things.
One
of
the
new
features
that
we
just
released
in
the
most
recent
beta
is
a
Kanban
dashboard,
and
so
any
of
these
pages
can
be
shown
as
a
Kanban
dashboard.
C
It
doesn't
necessarily
make
sense
for
all,
but
a
good
case
where
it
does
make
sense.
Is
this
milestone
view
which
shows
us
a
left-to-right
progression
of
here
is
where
each
issue
is
in
in
terms
of
state?
Is
it
has
anyone
starting
to
worked
on
it
as
a
as
progress
started?
Is
there
PR?
Does
the
PR
need
review?
C
Is
it
review
but
needs
emerge,
or
is
it
done
so
one
of
the
fun
things
that
we're
able
to
do
because
we've
automated
all
of
this
is
we
are
able
to
make
completion
etas
for
a
milestone,
because,
as
software
engineers,
we
also
suck
at
time
estimation.
So
this
is
kind
of
an
attempt
to
hint
to
the
person
running
the
milestone
that
hey
this
milestones
gonna
be
late
unless
you
start
reducing
the
number
of
issues
on
it.
So
the
rows
here
are
all
just
different
queries.
C
Sorry,
the
columns
are
different
queries
and
the
rows
are
swim
lanes
for
Sinese.
You
can
see
here's
the
available
work
that
nobody
has
picked
off
and
if
you
prefer
a
item
view,
this
shows
the
same
exact
issues,
but
in
kind
of
the
more
classic
format,
so
it
doesn't
have
to
be
just
done
for
milestones.
There's
also,
this
page
important
where
we
can
click
which
is
these
are
things
marked
as
priority
important
senior
urgent
and
we
can
click
on
the
Kanban
dashboard
view
of
this.
C
If
you
like
as
well,
so
any
page
can
be
a
Kanban
page.
We
also
show
some
basic
stats
here
for
like
right
now.
There's
a
1.4
day,
average
wait
for
users
to
hear
back
from
us,
and
we
have.
This
is
much
better
than
when
we
started
triage
party.
It
was
40
days
on
average
at
that
point,
so
so
I'm
going
to
show
you
how
to
start
your
own
triage
party.
You
can
I'll
start
it
two
different
ways.
C
This
is
a
kubernetes
meeting,
so
I
will
do
one
of
them
as
a
kubernetes
cluster
using
really
cute
locally.
So
this
one's
going
to
take
a
little
bit
because
there's
no
cash
state,
since
it's
a
brand
new
cluster
and
then
one
I'm
gonna
run
locally
for
the
kubernetes
community
and
that's
what
you
come
up
pretty
quickly.
So
so,
let's
look
at
the
kubernetes
community.
We
go
so
you
can
point
trash
party
at
any
github
repository.
C
C
C
You
set
your
repositories,
you
can
have
multiple
repositories
to
query
across.
You
can
rely
on
the
normal
member
relationships
on
github
or
you
through
code,
your
own.
This
is
central
or
others
file.
So
for
each
page
we,
a
page,
is
just
a
collection
of
rules,
so,
for
instance,
if
we
want
to
see
this
rule
further
down,
it's
basically
just
a
set
of
filters
filtering
for
anything
that
doesn't
have
the
priority
label
doesn't
have
a
triage,
partridge
ladle
and
was
created
over
five
days
ago.
C
The
Kanban
rules
look
a
little
bit
more
complicated
because
they
have
to
figure
out,
like
has
the
assignee
open
to
PR,
if
so
put
it
here.
So
let's
look
at
the
there's.
A
more
simplistic
version,
of
course,
doesn't
all
have
to
be
complicated.
This
is
a
pretty
minimal
version
and
if
we
load
the
version,
that's
running
in
our
crew
branded
cluster
locally.
Here
you
can
see
the
minimalistic
version
loaded,
so
we
do
have
a
fair
bit
of
documentation
out
on
how
to
get
how
to
get
started
and
how
to
deploy
this.