►
From YouTube: Kubernetes SIG Release Meeting 20210921
Description
For more info, see https://git.k8s.io/community/sig-release
A
Hello,
everyone
welcome
to
the
I
had
to
check
the
date.
It's
tuesday
september
21st
bi-weekly
sig
release
meeting.
My
name
is
jeremy
and
I
will
be
the
host
today.
I
am
going
to
drop
the
agenda
into
the
chat
if
you
could
go
ahead
and
add
yourself
to
the
attendees
for
today.
That
would
be
awesome.
If
you
have
any
topics,
you'd
like
to
add
to
the
agenda,
feel
free
to
add
them
as
well.
A
We
have
a
few
things
that
we'll
go
through,
but
we
normally
like
to
kick
these
meetings
off
first
by
reminding
everyone
that
this
is
the
kubernetes
sig
meeting
and
therefore
we
are
covered
by
the
kubernetes
code
of
conduct,
which
can
essentially
be
boiled
down
to.
Please
be
excellent
to
one
another,
and
I'm
gonna
make
sure
that
I
have
given
ray
co-host
just
in
case.
We
need
a
backup
and
with
that
we'll
go
ahead
and
first
open
it
up
to
anybody
to
introduce
themselves
if
you're
new
to
sig
release.
B
Hey
hi,
I'm
baruch
from
india,
I'm
going
to
this
community
like
I'm,
exploring
all
things
joining
meetings
I
started
yesterday.
Awesome
welcome
it's
nice.
D
I
can
introduce
myself
my
name's
chun
hi
everyone
I
work
at
apple.
I
applied
to
be
a
shadow
release
lead
in
august,
but
unfortunately
I
wasn't
selected
but
based
on
an
email
that
I
got
from
jeremy
recommendations
to
participate
more
often
in
sig
meetings.
So
here
I
am
I'm
going
to
try
to
contribute
as
much
as
I
can
and
learning
lots
about.
Kubernetes
awesome
welcome
glad
to
have
you.
E
Anyone
else
yeah
I'll
go
next
hi.
My
name
is
machi,
I'm
a
sick,
apps
and
sex
cli
lead.
I
think
I
I
wasn't
joining
sick
release
before
I'm
not
sure.
Maybe
I
have
in
the
past
either
way
I
work
with
red
hat
and,
like
I
mentioned,
I
work
in
the
area
of
cli
and
controllers.
E
E
Yeah
actually
eddie
tricked
me
because
I
see
he's
out
and
he
asked
me
whether
I'll
be
able
to
join.
I
was
like
yeah
I'll
try
to
squeeze
that
in
between
meetings
and
I'm
like
joining
in
parallel
another
meeting.
So
if
I
don't
respond,
that's
probably
because
I
my
brain
is
halfway
through
the
other
one.
Oh
no
worries
we
can
always
bump
that
to
the
next
meeting
as
well.
If
you're
back
now,
we
can
kick
it
off
this
time.
Okay,.
F
Themselves,
hi:
I
can
go
next
sure,
so
my
name.
F
And
I
work
at
ibm,
india
and
recently
I've
started
making
very
small
contributions
to
kubernetes,
mainly
in
scheduling
and
d
scheduler
code.
Oh
yeah,
it's
great
to
be
here,
oh
yeah!
This
is
the
first
time
I'm
joining
this.
Thank
you.
A
Joining
us,
it's
great
to
see
so
many
new
folks
joining
us
today,
all
right
looking
through
the
list,
I'm
pretty
sure
everybody
else
has
been
here
before,
but
we'll
pause
for
one
second,
just
in
case
and
if
not,
we
will
move
on
to
sub
project
updates
and
I
don't
see
adolfo
on
the
line.
But
I
do
see
our
brand
new
release
manager.
A
Congratulations.
Veronica.
Do
you
think
you
could
give
us
an
update
on
the
release
engineering
sub
project.
A
Yeah
no
worries
we
will
do
asynchronous
updates
there
if
there's
anything
that
needs
to
be
covered
and
we'll
drop
them
in
say
release,
so
everybody
can
be
informed
next
up
ray.
Do
you
want
to
take
the
release
team
update
and
I
can
take
notes
while
you're
talking.
G
Yeah
we're
currently
in
week
five
of
the
release
cycle,
we're
kind
of
in
the
quiet
period,
because
we
have
kubecon
coming
around
the
corner
as
well.
So
we
have
a
total
57
enhancements
tracked
and
that's
including
two
exceptions
for
for
a
few
csi
entry,
they're
going
out
of
tree
and
those
acceptors
were
approved,
so
total
of
is
57.
Enhancements
tracked
just
started
to
do
a
call
for
future
bugs
as
well
that
went
out
last
friday
and
also
states
this.
G
The
stated
release
was
all
sent
out
to
the
community
last
friday
as
well.
So
next
milestones,
we
actually
don't
have
any
milestones
for
the
rest
of
september
and
october
so
because
we
do
have
coupon
so,
but
that
also
puts
us
in
place
where
we
have
many
milestones
around
the
around
many
holidays
and
so
we're
just
trying
to
get
a
leg
up
on
that
work.
So,
like
the
docs
team
started
to
paying
enhanced
owners
to
start
their
doc
placeholder
prs
fairly,
even
though
that
deadline
is
until
november
18th.
G
But
we
just
want
to
get
that
word
out
early,
so
so
from
now
until
for
the
month
of
october,
around
coupon
we're
just
trying
to
make
sure
we
have
enhancements
owners
aware
of
the
deadlines
they're
approaching
around
the
holidays,
so
they
could
start
work
early
like
future,
bugs
like
docs,
etc.
A
All
right,
thanks
for
that
update
and
thanks
for
all
the
great
work
so
far
on
the
release,
it's
been
great
to
see
things
going
pretty
smoothly
so
far.
A
Okay,
that
will
take
us
to
our
first
agenda
item
I'll
just
delete
this
one
placeholder
and
that
would
be
releasing
and
versioning
cube,
ctl
independently,
and
I
think
that's
eddie
and
mache.
If
you
yeah.
E
So
the
short
idea
is,
we've
had
staging
for
so
long
and
q
pedal
is
one
of
the
the
projects
top
projects
of
the
entire
cube
ecosystem.
That
is
interested
in
actually
doing
the
one
step
further
and
we
want
to
be
part
of
a
separate
repo.
We
are
already
syncing
the
code
and
everything
else.
E
The
last
bit
that
is
still
left
is
figuring
out
how
we
can
drill
these
cube
cuddle
outside
of
cube
repo
okay.
For
starters,
I
would
probably
go
because
the
end
goal
is.
We
would
like
to
be
able
to
release
cube
cuddle
faster
than
than
cube.
I
don't
know
the
cadence
is
something
to
to
figure
out
in
the
long
term,
but
I
would
probably
start
with
let's
align
them
together
and
only
afterwards
we
can
figure
out
how
to
change
or
shorten
that
time,
but
for
starters,
to
make
it
simpler.
E
The
question
is
how
hard
it
is
to
release
cube
cuddle
from
a
separate
repo,
not
from
the
main
kubernetes
repo,
because
you
would
basically
have
to
release
all
all
the
artifacts,
but
under
a
different
repo.
I'm
not
sure
if
the
release
team
has
been
doing
something
like
that.
In
the
past,
if
you
have
that's
cool,
if
not,
I
guess
we
that's.
Why
I'm
here
to
figure
it
out
the
initial
steps
required
to
do
this.
A
I
don't
think
that
we
have
been
doing
anything
outside
of
kk
in
terms
of
the
core,
artifacts
taylor
and
veronica.
Can
maybe
correct
me
if
they're
aware
of
any
efforts,
we've
done
there
so
far,
but
I
don't
think
we
have
so.
This
is
probably
an
area
that
we
need
to
collaborate
on
with
you
to
make
it
out
of.
E
Reality
I
mean
there
are
several
options,
because
currently
we
are
public,
really
releasing
all
the
artifacts
with
all
the
tags
in
the
release
page
under
kk,
so
I'm
guessing
for
some
period
of
time.
We
would
be
releasing
both
of
them
in
both
repos,
but
we
would
still
link
the
cubecaro
artifacts
into
the
main
kk
repo,
just
for
the
sake
of
everyone
else,
looking
for
those
artifacts
and
then
eventually
we
could
cut
backward
and
have
them
separate
and
then
even
go
all
the
way
further
to
release
on
a
different
entirely
different
cadence.
E
But
that's
good
for
that.
But
that's
I
guess
it's
a
very
forward
thinking.
I
would
start
simple
by
just
having
the
separate.
G
So,
just
just
thinking
high
level
would
this:
would
this
process
start
out
as
a
cap
to
as
like
an
alpha
to
give
a
warning
to
the
community?
That's
like
that
cube
cuddle
will
be
released
outside
of
kk
and
I'm
not
sure
what
the
proper
process
of
this
I've
seen
this
in
some
entry
out
of
cheap
applications.
But
that's
that's.
My
train
of
thought
is
like
moving
keep
cuddle
in
tree
and
clean.
G
It's
on
repo,
so
having
one
way
is
to
have
a
first
have
a
cup
so
that
it's
it's
communicated
to
the
community.
Alpha
stage
would
be
just
just
that
warning
that
cute
pedal
will
be
will
be
released
outside
of
kk.
G
E
Already
have
a
cap
from
the
past,
where
we
covered
not
sure
how
far
the
process,
but
it
definitely
covered
the
part
of
moving
all
the
code
to
cuddle
related
to
staging.
I
can
probably
look
it
up
in
a
bit
and
I'm
positive
that
it
didn't
mention
the
fact
that
we
will
be
moving
this
over
to
a
separate
repo,
but
it
didn't
go
too
much
into
details.
So
probably
a
worthy
point
would
be
to
just
update
this
or
create
a
follow-up
cap
to
describe
the
process.
E
I'm
curious
from
just
the
technical
side
of
things,
thus
releasing
this
in
a
separate
repo
is
that
much
of
a
problem
or
the
the
current
scripts
are
easily
modifiable
to
to
go
through
a
separate
repo
as
well.
A
I
don't
think
he
is
just
ping
him
directly
on
slack.
This
is
probably
one
that
will
need
to
follow
up
offline
and
get
back
to
you.
A
E
Probably
we'll
have
to
open
one.
This
is
the
one
that
we
use
in
the
past
for
for
the
process
and
since
the
link
doesn't
work
to
the
cap,
I'm
just
digging
up
the
current
state
of
the
cap.
There's
no
link
to
the
cap
that
we
previously
created.
E
Yeah,
it
mostly
covers
the
the
move
to
staging
from
what
I'm
quickly
glancing
over.
A
E
Okay,
I'll
sync,
with
eddie
about
creating
the
enhancement
issue
and
start
sketching
the
cap
for
this
one
as
well.
Okay
in
parallel,
and
you
can
figure
out
the
the
details
from
the
technical
side
of
things
and
we
will
deal
with
the
the
paperwork
in
parallel
cool.
A
All
right,
we
will
follow
up
offline
and
see
what
the
next
steps
for
this
are
and
make
them
available
for
everyone
thanks.
A
Okay,
next
up
james,
had
put
a
topic
on
here
around
release
team
selection,
improvements
for
future
releases.
James,
do
you
want
to
start
us
off
there.
H
Sure
so
what
I'm
looking
to
do
here
is
really
start
a
conversation
ahead
of
the
next
release,
so
124
in
january.
I
don't
suspect
that
anyone's
going
to
make
any
decisions
now,
but
this
is
where
I
wanted
to
start.
So.
One
thing
that
I
and
others
have
spoken
to
have
noticed
over
the
past
few
releases
is,
I
feel,
we're
somewhat
outgrowing
the
existing
mentoring
shadowing
shadowing
selection
process
and
I
think
it's
very
much
a
victim
of
its
own
success.
H
If
you
look
at
its
last
the
last
release
in
123
jeremy
you'll
notice,
I
think
it's
like
185
applicants
for
shadow
positions
and
we
have
like
25
30.
I
think
possible
spots
for
foreshadows,
which
is
you
know,
hugely
oversubscribed,
and
I
think
that,
given
that
this
is
a
situation
we
are
in,
we
could
be.
We
could
handle
this
process
better,
both
from
the
perspective
of
the
release
team
itself
and
picking
better,
not
not
necessarily
better
candidates.
That's
not
really
what
I
mean.
H
What
I
mean
is
providing
more
consistency
in
terms
of
allowing
people
to
come
back
more
easily
and
also
make
it
possibly
easier
for
people
to
to
apply
and
understand
how
that
process
works.
I
I
had
a
couple
of
ideas.
I
think
others
I've
spoken
to
have
as
well
max.
I
think
it
was
you
who
wrote
a
diagram
of
one
of
them.
There
was
there's
kind
of
a
few
floating
around.
A
Yeah,
I
think
it's
worth
revisiting
this
and
determining
what
improvements
we
can
make.
It
definitely
was
challenging.
I
think,
for
all
of
the
leads
this
time
to
pick
shadows,
because
there
were
so
many
options
and
then
it's
also
it's
difficult
for
folks
that
apply
maybe
multiple
times
and
just
don't
get
through
because
of
the
sheer
volume
of
folks
that
are
applying.
I
think
we
also
addressed
discussed
this.
We
didn't
addre
like
come
up
with
a
solution,
but
we
discussed
it
in
the
really
one
of
the
release.
A
A
I
don't
have
any
really
good
suggestions
on
what
it
should
look
like
at
this
point.
I
think
it
is
going
to
continue
to
grow.
I
think,
unless
we
we
tell
people
not
to
apply
it'll
it'll
continue
to
just
be
a
very
high
volume
of
applicants
for
a
very
low
number
of
positions.
A
I
think
that
one
concern
I
have
just
as
a
as
a
lead
is
that
we
don't
necessarily
get
the
long-term
secession
planning
out
of
it
that
we
might
have
in
the
past,
and
I
think
that
there's
a
lot
of
reasons
for
that-
probably
covid
people
being
burned
out
and
just
the
world.
But
we
looked
at
like
the
123
release
team.
A
A
better
way
of
of
backfilling,
like
you,
said,
going
back
to
focus
in
the
past.
If
we
got
karen
two
to
come
back
and
do
comms
this
time.
Who
was
a
previous
lead,
but
I
think
that
it
wasn't
clear
like
what
the
order
was.
A
What
what
way
we
should
have
gone
about
finding
folks-
and
I
think,
maybe
as
part
of
this,
we
should
identify
better,
better
reach
back
policies
or
just
a
a
way
to
make
it
easier
for
folks
that
maybe
don't
have
the
network
so
that
you
know
nabaroon
as
the
enhancement
or
the
ea
next
time
or
array
as
the
ea
for
125,
or
something
figuring
out
like
which
people
I
should
talk
to
from
releases
of
two
years
ago
or
one
year
ago.
Whatever
that
might
be.
I
We're
going
to
need
some
kubernetes
history
books
here
after
a
while
to
know
who
we
need
to
reach
out
to
I.
I
agree.
I
think
that
there's
definitely
some
merit
in
with
with
some
of
the
they
are
rejection
letters,
but
they
give
opportunities
for
people
to
jump
off
into
different
projects
or
within
different
capacities
as
well,
and
when,
whenever
we've
sent
those
out,
I
think
I've
seen
an
overwhelming
response
where
they're
like,
oh
my
gosh.
I
I
know
this
is
a
rejection
letter,
but
this
is
the
best
one
I've
ever
gotten,
because
it
gives
them
a
jumping
off
point
for
other
things.
They
could
potentially
do
within
the
project.
So
we
we
might
be
able
to
reach
out
to
some
other
sig
leads
or
sub
projects
and
say:
hey
are
you
looking
for?
Someone
is
and
then
kind
of
give
people
those
options
too.
If
they
don't
get
accepted
to
the
the
release
team.
I
I
know
that
some
people
just
want
to
help
and
they
don't
know
the
best
place
to
start,
and
that's
just
the
most
visible
one
is.
Is
the
release
team
so
definitely
definitely
agree
with
you
and
definitely
want
to
get
there
before
we
hit?
You
know:
5
000
applicants.
Maybe
next
next
release
cycle.
J
You
know
I
mean
it's
a
good
problem
that
we
had
this
cycle
and
it's
been
growing
with
the
amount
of
applicants,
but
we
also
I
mean,
if
there's
some
aspirational
goals.
Aside
from
this,
we
do
see
some
problems
and
maybe
sig
contrabex
can
play
a
partners
because
we
had
to
put
the
call
out
for
sick
docks,
like
the
bench
got
really
thin
to
where
then,
all
of
a
sudden
everything
was
falling
on
jim
angel,
I've
seen
other
groups
start
to
kind
of
fold.
Some
of
them
are
smaller.
Cigs,
so
is.
J
Is
there
a
way
that
you
know
we
can
channel
some
of
this
energy?
That's
coming
directly
into
the
the
release
team
into
some
of
these
areas.
Like
I
know,
taylor
you're,
right,
like
the
the
letter
we
have
is,
is
good.
It
gives
direction,
but
you
know
some
some
people
like
myself,
where
I
think
it's
you
know
we
sometimes
even
need
more
than
breadcrumbs
and
we
need
help
to
kind
of
be
shepherded
into
a
program
like
how
do
we
you
know?
J
Could
we
shepherd
them
into
all
these
other
areas
if
they
can't
fit
into
the
team
so
that
we
just
instead
of
just
casting
off
a
hundred
and
something
we
actually
find
a
way
to
be
like
okay,
you
didn't
make
it,
but
here's
directly
where
you
could
go
like
we
could
definitely
use
help
here.
I
don't
know
if
that's
it
easy,
but
I
think
if
there's
a
goal,
you
know
we
should
definitely
be
looking
at
back
filling
and
then
you
know
I
know
we
don't.
J
I
don't
know
if
there's
any
metrics
that
have
been
collected
previously
about
you
know,
retention
and
how
things
are
going,
but
you
know
I've
always
think
it's
good.
When
we
can
kind
of
capture
some
of
this,
you
know,
but
it
just.
It
definitely
feels
like
we
get
a
lot
in
on
this
release
team,
but
then
it
just
doesn't
really
extend
into
the
broader
ecosystem
and
as
this
project
matures,
we
know
how
the
life
cycle
of
these
projects
kind
of
go.
J
I
I
think
that
there's
there
is
there
is
that
issue
with
people
kind
of
on
boarding
and
as
well
as
as
the
project
goes
on,
you
know
things
come
up.
I
You
know
like
was
kind
of
spoken
about
whether
it
be
burnout
or
just
something
personal
that
happens
or
anything
like
that
to
have
seen,
people
on
different
releases
have
to
bow
out
typically
within
the
shadow
capacity
or
just
a
misunderstanding
of
you
know
the
the
time
commitment
that
that
took
making
kind
of
promotion
promotion
with
regards
to
the
next
lead
for
the
next
release
being
difficult.
I
You
know,
and
sometimes
we
have
had
to
fall
back
to
you
know,
let's
take
a
look
at
people
who
have
served
in
this
capacity
before
and
tried
to
source
that.
So
I
definitely
I
agree
with
you.
I
think
the
problem's
twofold
too
and
ways
that
we
can
kind
of
help
with
this
circulation
for
for
lack
of
a
better
word
within
the
community
would
be
would
be
fantastic,
definitely
like
to
help
them
on
that
front.
C
As
always,
I
think
that
one
of
the
reasons
why
taylor's
situation
is
the
lack
of
processes
or
the
lack
of
robust
documentation
like
it's,
I
can
totally
see
new
people
coming
in
and
yeah
aside
from
the
time
commitments
and
all
those
things
that
were
already
mentioned,
it's
hard
to
just
start
working
in
an
I
don't
know,
I'm
trying
to
be
empathetic
to
someone
new
just
coming
into
this
massive
amounts
of
information
in
systems,
and
I
know
that
in
all
areas
of
stick
release,
we
could
do
dogs
a
little
bit
better.
C
I
think
we
we're
we
have
been
doing
a
great
job
recently,
but
in
the
past
I
have
seen
that
people
from
the
shadow
program
struggle
unless
someone
really
tells
them
explicitly
what
to
do,
because
there
are
no
well,
there
are
some,
but
there
there
aren't
enough
manuals
or
processes
documented
etc.
C
So
I
don't
know.
Probably
one
of
the
things
that
we
could
talk
about
later
is
to
sort
of
do
an
iterative
process
of
like
the
same
people
who
come
as
newcomers
or
in
the
shadow
program
could
leave
a
little
bit
of
documentation
in
a
better
state
for
the
people.
In
the
future,
you
know,
like
document
their
own
process,
on
how
they
learn
things
and
how
to
look
for
things
etc.
C
I
I
absolutely
agree:
we
had
some
feedback
on
that
front,
two
from
a
couple
shadows
where
they
said
you
know
that
they
kind
of
got
the
oh,
thank
goodness
you're,
here
experience
and
kind
of
the
documentation
linked
and
shown
to
them,
but
they
said
it
was
kind
of
hard
to
ingest
and
so
maybe
even
different
formats.
I
You
know,
instead
of
markdown
making
it
just
to
look
like
google
slides
or
something
like
that,
a
little
bit
more
easy
for
them
to
kind
of
ingest
or
to
understand
or
have
visibility
on,
but
I
definitely
agree
with
you
there.
It's
it's
it's
difficult
to
see
that
and
we
may
even
well
have
the
documentation,
for
we
do
a
lot
of
the
time.
Finding
that
or
just
kind
of
making
sense
of
that
is
is
something
that's
difficult.
G
Okay,
I
do
like
the
idea
that
taylor
brought
up
having
the
documentation
easy
to
ingest
format,
going
through
all
the
documents,
all
the
role
handbooks.
I
know
a
lot.
Some
handbooks
are
better
than
others,
so
they're
not
on
the
same
level
and
the
ones
are
better
than
others.
It
might
be
too
detailed
for
folks
who
are
new
to
the
project
to
actually
youtube
to
comprehend
and
digress.
So,
like
I
do
like
that
idea,
I
might
start
on
that,
since
there's
some
a
little
bit
of
quiet
time
for
me,
so.
A
Yeah,
so
it
sounds
like
there's
a
couple
of
parallel
issues:
one
is
just
the
selection
process
and
what
that
looks
like
one
is
the
onboarding
experience
slash
just.
I
guess
the
overall
experience,
the
level
of
documentation,
that's
available,
the
training
that's
available
and
we
could
probably
work
on
those
things
in
parallel.
A
I
think
that
it
would
be
worth
starting
a
github
discussion
issue,
so
we
can
start
hashing
this
out
a
little
bit
more
and
then
make
some
concrete
action
items
to
take
away
james.
Do
you
want
to
start
one
for
the
onboarding
process
or
not
the
sorry,
the
selection
process
and
just
the
structure,
maybe
and
then
I'll,
take
a
I'll,
take
an
action,
okay,
cool
and
then
for
the
second
one,
really
the
like
the
documentation,
slash,
training,
slash
other
stuff.
A
I
can
take
that
and
work
with
ray
and
we'll
start
with
a
discussion
and
veronica,
and
we
can
just
start
a
discussion
there.
Does
that
sound
good.
A
H
A
Think
that
it's
worth
having
these
things
as
just
get
you
know
using
github
as
a
place
to
store
all
of
the
the
info,
so
that
we
can
make
sure
that.
A
It
added
a
suggested
action
item
and
is
that
your
james
mccoy?
It's
funny,
I
know
a
person
named
jim.
I
think
it's
probably
picking
someone
from
sorry
total
attention
super
distracting.
A
Okay,
so
those
two
things
we'll
start
with
and
try
to
pull
some
some
concrete
issues.
We
can
add
to
the
the
board
and
maybe
open
some
of
this
up
to
to
work
for
shadows
later
on
any
other
comments
or
questions
about
that.
A
All
right,
the
last
one
on
the
agenda
and
probably
the
last
thing
we'll
get
to
go
through
because
we're
almost
out
of
time
got
like
14
minutes
left
is
taylor.
Do
you
want
to
talk
us
through
the
zoom
splain
youtube
integration.
I
Yes,
so
I
got
the
very
fun
task
of
solving
a
mystery.
Now
it
wasn't
like
clue
there
weren't
any
murder,
weapons
or
rooms
that
these
things
were
solved
and
well,
not
technically
meeting
rooms.
Maybe-
and
we
had
an
issue
where
we
would
record
these
cloud
meetings
and
they
weren't
getting
uploaded
to
youtube-
sounds
pretty
straightforward
right.
Well,
it
wasn't
what
was
happening
was
the
we
have
a
plug-in
that
pushes
these
videos
to
youtube
and
that
integration
is
called
splain.
S-P-L-A-I-N-Dot
io
is
the
website.
I
If
you
want
to
check
it
out
not
too
much
to
read
there,
what
was
happening
was
we
had
our
integration
set
up,
just
fine,
all
our
ids
and
and
linkages
were
okay.
What
had
changed
was
when
we
did
the
shift
over
to
the
g
suite
list
of
products
and
changed
our
email
address.
That's
what
broke
things
on
the
spleen
side
worked
a
lot
with
spleen
support
to
try
to
figure
this
out.
You
know
it
looks
fine
looks
like
it
looks
fine.
Then
we
found
that
out.
I
It
was
really
just
basically
removing
the
integration
and
bringing
it
back
in
now.
We
can
verify
that
everything
works.
So
I
believe
this
might
be
one
of
the
first
meetings
where
we
have
it
pushed
to
youtube.
The
only
caveat
that
exists
is
that
just
so
that
we
have
the
time
to
go
through
things.
You
know,
if
say
something
were
to
get
zoom
bombed,
or
you
know
just
the
the
recording
needs
to
be
edited
in
any
way.
This
does
push
it
up
to
youtube.
It
leaves
us
private
and
it
doesn't
associate
it
with
a
playlist.
I
So
I
can
help
out
with
that,
because
I've
got
access
to
zoom
into
youtube
if
I
don't
respond
or
from
vacation
on
vacation
at
youtube,
admins
or
at
zuma.
Bins
would
be
able
to
help
out
with
this,
but
I
can
go
and
set
those
after
meetings
to
public
and
then
put
that
on
the
right
playlist,
so
that
people
can
reference
it
after
those
calls
complete
on
youtube
but
yeah.
That
was
it.
It
was
a
fun
mystery
glad
we
got
it
solved
and
everything
is
working
out.
A
So
to
add
things
to
the
playlist.
Is
that
any?
Is
that
something
anybody
can
do
or
no
because
they're
marked
as
private,
so
we
won't
have
the
links
to
them.
I
I
think
I
there
is
the
ability
to,
I
think,
youtube
added
the
ability
to
delegate.
So
if
anyone
does
want
that
ability
to
do
that,
I
think
we
can
share
out
a
link
for
people
to
go
ahead
and
add
those
things
in,
but
I
think
it
is
a
one-off
type
of
permission
currently.
Otherwise
it's
just
it
used
to
just
be
admins,
and
then
they
have
like
a
shareable
link
that
you
can
use
to
kind
of
administrate
that
so
happy
to
help
out
on
that
front
anyway,
possible.
A
Okay,
this
sounds
good.
Thank
you
for,
for
fixing
that
I
was
trying
to
do
these
manually
and
it
was
such
a
pain
to
do
that.
I
I
I
I
Multiple
sigs
did
see
this
we'll
get
it
even.
There
are
even
some
times
where
you
can
have
it
set
up
just
fine
and
the
web
hook.
Integration
with
splain
will
fail.
They
do
have
some
scale
and
and
load
issues
over
explain.
So
I
think
at
some
point
in
time.
It'd
benefit
us
just
writing
our
own
tool
for
the
community,
but
yeah.
It's
just
a
matter
of
time.
I
think,
and
people's
ability
to
help
it
on
that.
A
Okay,
cool.
Thank
you.
Next
up,
we'll
spend
just
a
few
minutes
kind
of
walking
through
the
board
and
see
if
there's
anything
that
needs
to
be
triaged
immediately.
So
let
me
share
my
screen.
A
A
19
days
ago
I
said
it
was
in
my
queue
for
tomorrow.
So
I'll
definitely
put
it
in
my
queue
for
today.
A
All
right,
all
right!
Next
up,
we
have
in
progress
yeah
anybody
on
the
line
that
can
speak
to
any
of
these
start
at
the
bottom.
Tucker
lead
off
boarding
for
dan,
I
think,
is
mostly
done
I'll
ping
steven
offline
for
that
one
release
team
lead
access
for
ray
james,
the
rest
of
the
steps.
A
A
Yeah,
okay,
so
we
will
hopefully
close
that
one
out
with
two
reviews
that
are
open,
pull
kubernetes
ede
gce
is
nearing
its
timeout.
A
A
Does
anybody
want
to
volunteer
to
to
follow
up
on
this
one.
C
C
So
this
could
be
part
of
that
effort,
but
yeah
definitely
not
blocking
or
anything
like
that.
A
Okay,
so
to
do
in
123,
move
kube
adm
out
of
kubernetes
kubernetes.
I
think
this
is
similar
to
what
sig
release
was
talking
or
sorry
still.
I
was
talking
about
they've
moved
code
out,
but
I
think
the
critical
piece
of
that
is
building
some
of
this
and
I
think
nabaroon
was
going
to
look
into
some
of
that.
A
Yeah
there
we
go
so
I
will
ping
mabaroon
about
this.
A
All
right
anything
that
anyone
would
like
to
to
bubble
up
on
here
that
they're
aware
of.
A
Okay
with
that
we'll
end
the
meeting
just
a
few
minutes
early,
then
we'll
open
it
up
just
again
for
any
questions
that
people
may
have
or
any
last
minute
items
they'd
like
to
bring
up,
but
otherwise
we
can
end
a
few
minutes
early
and
everybody
can
have
a
few
minutes
back
before
they
have
to
jump
to
another
meeting
or
or
end
their
day.
A
little
bit
early.
A
All
right:
well,
I
hope
everybody
has
a
great
morning
afternoon
evening,
whatever
it
may
be
and
hope
everyone
stays
safe
and
have
a
great
week
if
you
have
any
other
questions
or
anything
comes
up.
Please
reach
out
to
us
on
the
sig
release,
slack
channel
or
the
mailing
list.
All
right.
Thanks
have
a
great
one.