►
From YouTube: Kubernetes Release Team Meeting for 20220118 (1.27)
Description
Kubernetes Release Team Meeting for 20220118 (1.27)
A
A
A
Just
so,
we
can
have
a
record
of
everyone
that
was
here,
and
this
meeting
I
think
is
probably
going
to
run
a
little
bit
longer
than
our
typical
release
meeting,
because
we're
going
to
be
doing
a
lot
of
introductions
to
meet
all
of
the
Shadows
that
are
joining
us
here.
So
normally
these
these
tend
to
go
pretty
quick,
but
I
think
we'll
we'll
run
a
little
longer
this
time,
so
I'll
I'll
just
kick
off
with
an
introduction.
A
I'm
I'm,
Xander
I
am
the
1.27
release,
lead
and
professionally
I
work
at
Microsoft
as
an
open
source
product
manager.
I've
I've
been
with
the
release
team
since
version
1.20
so
yeah.
Certainly,
if
any
questions
come
up
through
the
process,
I'm
I'm
always
happy
to
answer
things
like
and
and
I'm
I
try
to
be
as
available
as
possible
on
slacks.
B
Occasionally-
and
this
is
I've
been
on
the
release
team
for
since
as
the
enhancement
Shadow
for
125
and
126,
and
now
I'm
the
lead
yeah.
Thank
you.
Grace
I've
worked
with
Grayson
enhancements,
yeah
she's
LED
it
too.
So
last
week
we
had
a
couple
of
the
Shadows
introduced
themselves.
I
think
artharva
is
on
the
column,
wasn't
able
to
introduce
himself.
So
do
you
want
to
say
hi
yeah.
C
B
A
D
Don't
think
I
had
a
chance
to
introduce
myself.
Her
name
is
my
name
is
Drew
Hagen
I
am
a
full
stack
software
engineer
at
a
student
information
system,
company
and
I've
started
to
grow
an
interest
in
devops
and
Cloud
native
Technologies,
so
I'm
really
excited
for
this
opportunity
and
I'll
be
shadowing
on
CI
signal.
D
A
A
E
Good
morning,
everybody,
my
name
is
Katz.
For
my
actual
day,
job
I
work
at
Dell
as
a
lead,
developer,
Advocate,
but
I
have
been
on
the
release
team.
Since
one
two
two
officially,
though,
because
of
the
one
two
one
dockership
drama
I
was
involved
there
at
the
end
too,
but
I've
been
around
for
a
while.
I
was
on
comms
for
a
minute
I've
LED
comms-
and
this
is
my
second
round
as
a
release-
lead
Shadow,
which
is
a
a
super
fun
role.
It
turns
out,
but.
F
A
G
G
H
H
J
J
I
So
hi
everyone,
my
name,
is
Heba
I
work
for
Microsoft
and
AKs
team.
As
a
software
engineer,
I've
been
involved
in
in
the
release
seg
since
1.18
as
a
enhancement
of
Shadow
and
and
then
bacteria
Shadow
bacteria,
so
I've
been
involved
for
a
while.
Now
it's
it's
amazing
place
to
to
you
know
like
to
get
involved
and
to
know
everyone
yeah
and
happy
happy
to
be
here
with
everyone.
Thank
you.
A
B
L
I
hide
some
audio
issues
because
I
dropped
for
a
minute:
hey
everyone.
My
name
is
Priyanka
sagu
I
work
for
Souza
I
work
in
the
Linux
operating
system
team.
As
a
kubernetes
integration
engineer,
I
have
been
part
of
the
release
team
since
1.23
release
cycle
as
part
of
the
enhancements
team
and
during
the
last
cycle,
I
was
a
release,
lead
Shadow
and
yeah
happy
to
be
back
to
the
release
team
again.
A
Thank
you,
so
all
new
Shadows
here,
the
the
lead
Shadows.
You
know
this
whole
group
has
been
around
for
a
while.
So
they're
definitely
here
to
be
a
resource
for
you.
If
you
have
any
questions
or
anything
throughout
the
process
like
feel
free
to
reach
out
to
like
I
said
myself
or
or
any
of
the
lead
shadows
as
well
so
from
here
we
did
enhancements
and
actually
Mark.
If
you
want
to
just
update
on
the
yellow
status,
I
would
would
love
to
hear
that
yeah.
B
I
wasn't
sure
if
it's
yellow
or
green,
because
it's
still
early
in
the
release,
but
some
updates
that
we're
still
working
on
getting
a
pet
to
use
in
the
Pro
jobs
to
update
the
enhancements
board.
There's
a
link
to
a
quote-unquote
final
slack
thread
because
there's
been
a
whole
bunch
of
different
discussions
on
this
and
have
this
been
a
big
help
with
that
I
have
a
GitHub
action
running
and
a
personal
GitHub
repo
to
update
it.
B
B
We
have
some
onboarding
meetings
scheduled
for
today
with
all
of
the
shadows
and
I've
been
working
on
PRS
to
get
everybody
into
all
of
the
appropriate
groups.
The
org
membership
PRS
are
done
and
I
think
all
of
the
group
ones
I
just
need
to
rebase
so
get
that
cleaned
up.
Hopefully
this
week
too,
so
far,
there's
been
34
enhancements
added
to
the
the
board,
but
we
haven't
gone
through
and
started
sorting
them
and
figuring
out
what
stage
they're
in
yet
so
we'll
provide
those
updates.
Next
week.
A
M
Hi
everybody,
if
for
high,
especially
it's
holiday
Shadows,
my
name
is
Laura.
I
am
the
lead
for
CI
signal
for
this
release.
Previously
I've
been
a
shadow
on
CI
signal
and
the
enhancement
sub
team
in
Prior
releases.
My
day,
job
I
work
at
Google
on
gke
as
a
software
engineer
and
yeah
pretty
excited
to
have
a
good
127
with
all
of
you.
M
M
N
O
Yes
sure,
hello,
everyone
myself,
I,
am
a
student
yet
pursuing
my
bachelor's
in
Computer,
Engineering
and
a
final
year
student
and
also
working
at
redhead,
as
in
software
quality
engineering
intern
and
apart
from
that,
I
have
played
a
role
in
release
team
as
a
docs
shadow
in
one
two
three
and
one
to
four
and
as
a
CI
signal,
Shadow
and
1.26,
and
again
here
and
looking
forward.
Thank
you.
M
A
Q
S
R
I
hope
it's
it's
better
now,
so
as
for
the
backgrounds
for
the
status
of
the
team,
I'm
waiting
for
one
member
to
join
the
kubernetes
organization,
and
then
we
can
start
with
thinkable
to
the
right
groups,
and
then
we
can
start
managing
issues.
So
we
have
started
with
onboarding
by
you
know
doing
all
the
necessary
accents
at
first
and
we
will
have
a
team
meeting
soon
to
onboard
the
new
Shadows
I
believe
the
new
Shadows
are
all
but
one
here
in
the
call,
so
Carlos
pathway
and
soumya.
T
Yeah
I
I'll
go
next
hi
I,
hope,
I'm
audible,
because
this
has
not
worked
with
me
before
good
yeah,
okay
hi,
so
my
name
is
parthi
I.
This
is
my
second
time
scheduling
for
the
release
team.
The
first
time
was
in
1.24
when
I
worked
with
Mickey
and
cat,
so
hey
I
was
with
I.
Was
the
com
Shadow
then,
and
this
time
I'm
with
bugs
team,
so
I'm
happy
about
it
and
on
my
day,
job
I
work
as
a
software
engineer
at
Red
Hat
working
on
developer
Tools
around
openshift.
F
Hi
everybody
I'm
samya
I'm
part
of
bug,
clear
shadow,
my
day,
job
I
work
as
a
QA
manager
in
sunsar,
Rancho
based
out
of
California
super
excited
to
be
here.
This
is
my
first
time
here
we
have
worked
a
lot
with
kubernetes
and
I
can't
believe
I've
not
applied
before
so
super
excited
to
be
on
the
team.
Thank
you.
R
And
and
for
me,
because
I
I
skipped
that
part
my
daily
job
I'm,
a
software
engineer
at
Financial,
working
on
the
micro
case,
distribution
and
I've,
been
on
the
release
team.
Since
126
I
was
a
shadow
for
the
bacteria's
team
and
I'm
happy
to
lead
it
for
this
silo
and
as
a
final
update,
so
some
of
the
enhancements
I'm
waiting
to
see
how
we
will
proceed
with
the
personal
access
token
for
the
prior
job
to
configure
the
two
automatically
update
the
bacterials
board.
R
Q
So
we
are
currently
in
the
process
of
onboarding.
Our
final
shout
out
to
the
Kate's
org
I'll
update
all
the
team
membership
when
the
org
membership
updates
are
complete.
On
my
end,
I
also
need
to
create
the
1.27
docs
Branch,
when
both
team
membership
and
org
memberships
are
complete
and
finally,
I'm
scheduling
our
shadow
onboarding
meeting
for
next
week.
U
H
Hey
everyone,
my
name
is
harshita
I'm,
an
engineering
student
and
I
have
been
in
the
ready
cycle
since
20.25
I
have
shadowed
for
book
triage
and
then
for
comms
and
I
am
completely
for
the
cycle.
The
initial
the
status
of
comps
is
green,
as
this
is
initial
stage
of
the
cycle
and
I
see
two
of
my
Shadows
on
hold.
So
please
go
ahead
and
introduce
yourself.
V
M
J
Hi
everyone,
my
name,
is
Sasha
I'm
admitted
job
I
work
at
Cisco,
I've
been
with
release
Team
for
two
cycles
in
sequence,
from
126
127.
Before
that
I
worked
with
Navarro
on
118
and
to
an
extent
on
119
as
well.
So
as
for
the
updates,
though
we
have
done
on
Shadow
onboarding
work,
we
have
had
a
discussion.
J
We
went
through
some
of
the
examples
we
we
also
did
a
quick
demo
how
to
set
up
the
tooling
and
then
get
the
release,
notes,
generated
and
there's
a
couple
of
full
difference
that
I
have
opened
in
terms
of
getting
the
contacts
added
to
the
right
owner.
Alias
is
endless
and
there's
a
bullet
test
that
I
think
got
approved
by
Sasha
in
terms
of
updating
it
into
the
city
release
under
the
contact
list.
J
W
Hi
there
I
can
go
first.
My
name
is
Ana
Margarita
Medina
for
my
professional
job,
I'm,
a
Staff
developer,
Advocate
over
light,
stop
and
I'm
very
excited
to
be
in
this
part
of
the
release
team.
Once
again
last
release
I
was
part
of
release,
notes
as
well
and
in
1.25
I
was
on
comms
under
cat.
So
it's
always
been
really
fun
to
see
how
everything
comes
together
and
continue
growing.
The
kubernetes
space.
X
J
A
No
no
pressure
to
to
speak
if,
if
you're
not
feeling
up
to
it
either
we
can
always-
and
you
know,
feel
free
to
introduce
yourself
at
any
time
in
the
future.
If
you'd
like
a
lot
of
this
could
be
my
problems
but
yeah.
Let's,
let's
move
on
to
release
Branch
management.
Cc.
Are
you
you
on
the
call?
Yes.
K
Hi
hi
everyone-
this
is
Stacey
Juan
in
the
current
release,
I'll
be
acting
as
the
release
branch
manager
and
just
a
quick
introduction.
I've
been
with
release
team
starting
back
to
release
1.22
and
I
was
the
equivalent
to
1.25
release
lead
as
well
professionally
I'm,
currently
working
on
Google.
As
a
software
engineer
and
I
look
forward
to
working
with
all
of
you
regarding
this
release,
Branch
management
updates.
K
A
K
Y
Hello,
my
name
is
James
lavrock
I'm,
the
Artemis
advisor
for
this
release
of
kubernetes
professionally
I'm,
a
Staff
Solutions
engineer
at
jetstack,
which
is
a
uk-based
kubernetes
consultancy,
most
famous
for
cert
manager.
If
you've
seen
that
on
the
release
team,
this
is
my
eighth
release
team.
The
first
one
I
was
in
was
118
and
I'm.
Also
a
former
release
lead
back
on
124,
so
I've
been
around
for
a
while.
At
this
point
my
job
is
to
look
after
all
of
the
Shadows.
Y
That's
my
role
on
that
note,
Shadow
selection
is
is
complete.
All
Shadows
should
now
be
informed
of
a
status
one
way
or
the
other,
and
thank
you
to
everyone
who
applied.
We
had
an
awful
lot
of
applications
and
I'll
talk
about
the
numbers
in
a
minute.
So,
even
if
you
were
not
successful,
thank
you.
So
much
for
applying
it
really
is
really
is
very,
very
useful
to
us
I'm
working
with
the
leads
to
handle
all
membership,
which
is
mostly
done
at
this
point
and
a
few
other
onboarding
tasks.
Y
Y
This
will
be
a
a
session
that
Shadows
can
can
join
where
I
can
explain
and
answer
questions
about
the
release
Sim
in
general
release
process,
the
kubernetes
org
et
cetera,
Etc,
that
sort
of
thing
it
is
optional
but
but
recommended
you
should
all
be
going
through
orientation
specific
to
your
role,
with
your
role,
lead
as
well.
I've,
of
course,
do
feel
free
to
ask
your
lead
any
general
questions
as
well.
Y
I'm
also
going
to
go
work
with
Leo
to
who
is
a
the
form.
The
last
release
lead
and
has
done
a
lot
of
work
around
standardizing
how
we
collect
Shadow
information
from
the
survey
and
we're
going
to
try
to
generate
some
stats,
and
the
idea
is
that
I
will.
For
the
first
time
ever,
we
will
produce
statistics
from
those
Shadows
that
opted
into
statistics.
In
the
shadow
survey
about
the
kind
of
applicants
we
get
using
the
at
their
ancestor
questions,
or
you
know
fully
anonymized
we're
talking
to
cortrex
about
it.
Y
A
A
So
what
that'll
do
is
add
all
of
the
Shadows
to
the
correct
Google
Groups,
which
will
give
you
access
to
edit
this
document
and
get
the
calendar
invites
and
such
you
will
need
a
Google
account
with
the
email
address
that
you
applied
to
be
a
shadow
with
and
you'll
need
to
be
signed
in
with
that
Google
account
on
Google
Docs
to
be
able
to
edit
this
Doc
and
such
so
I
know.
If,
if
you
see
things
where
it's
like,
rather
than
letting
you
edit
it
pops
up.
A
As
like
a
comment
like
a
change
suggestion,
you
might
need
to
sign
in
with
the
Google
account
that
is
tied
to
the
email
that
you
applied
to
be
a
shadow
with,
because
a
lot
of
your
access
is
tied
to
that
and,
like
was
mentioned,
we're
finalizing
org
membership,
which,
once
that's
completed,
should
be
all
of
the
access
things
you
need
to
complete
your
your
Shadow
rules,
yeah
and
I.
Think
starting
next
week,
some
of
the
lead
shadows
will
be
hosting
this
meeting.