►
From YouTube: Kubernetes Release Team Meeting for 20230111
Description
Kubernetes Release Team Meeting for 20230111
A
All
right
welcome
everyone
to
the
first
release
meeting
of
the
1.27
kubernetes
release
cycle,
just
a
quick
reminder
that
this
meeting
does
abide
by
the
kubernetes
code
of
conduct,
which
can
be
summarized
as
please
be
excellent
to
one
another.
A
A
A
Lead
I've
been
involved
in
the
release
team
since
version
1.20,
so
this
will
be
yeah
seventh
time
around
professionally
I
work
at
Microsoft
on
open
source,
yeah
and
super
excited
to
have
y'all
here
and
I
I'm
joined
by
some
really
amazing
lead
Shadows
that
have
been
a
part
of
the
release
team
for
a
while
now
too
and
I'll
kind
of
pause
here
for
for
any
of
them.
That
would
like
to
introduce
themselves.
B
I'll
go
good
morning
hi,
my
name
is
Kat.
I
have
been
on
the
release
team
since
one
two,
two
one,
two
one
I
I
forget
it's
been
a
minute.
It's
been
a
minute.
This
is
my
second
cycle
as
a
release.
Lead
Shadow
I
have
also
been
on
comms
a
couple
times
and
Lead
calms
and
I
am
excited
to
be
here
once
again.
C
Hey
I
can
go
next,
hello,
everyone,
my
name
is
Priyanka
sagu
I
am
part
of
the
release.
Team
from
1.23
I
was
a
shadow
to
Xander,
an
enhancement,
Shadow
and
then
I
led
enhancements
in
1.25
and
was
part
of
the
release
team
as
a
lead
shadow
in
1.26
on
professional
front
I
am
I
work
at
Souza,
part
of
the
operating
system,
team
and
yep
happy
to
join
the
team
again
welcome
to
everyone.
A
Thanks
Priyanka
I
see
Heba
on
the
call.
Do
you
want
to
go
next.
D
All
right,
hi
everyone,
my
name,
is
I've,
been
involved
in
a
release.
D
Kubernetes
released
since
1.18
started
at
the
shadow
for
enhancement
and
then
moved
to
bacteriage
and
the
couple
you
know
like
couple
of
cycles
and
now
as
a
lead,
Shadow
so
happy
to
be
here:
I'm,
more
I,
I
work
for
Microsoft
and
AKs
team
and
happy
to
be
here
and
happy
to
help.
A
Because
thank
you
heather
and
then
Hussein.
It's
the
last.
E
Thank
you,
hello.
Everyone.
My
name
is
Jose
I've
been
a
part
of
release
team.
Since
release
121
I
entered
as
a
CS
signal,
Shadow
I've
been
yeah,
then
I
was
leading
CS
signal
and
I
was
part
of
enhancement
and
then
Fox
triage
shadow
with
Heather
and
then
leading
bug
triage.
E
It's
a
great
honor
to
be
here
professionally
I
work
as
Cloud
native
consultant
at
liquid
reply
from
Germany
yeah.
That's
it.
A
Awesome,
thank
you.
Super
super
happy
to
have
you
all
here
yeah.
This
is
like
a
a
big
job
that
I
don't
think
one
person
can
do
and
so
I
I
feel
a
lot
better
going
into
it.
Knowing
that
I
have
the
support
of
y'all
and,
like
all
the
other,
leads
and
shadows
to
know
that,
like
you,
can
certainly
lean
on
the
lead
Shadows
for
support
at
any
time
during
this
this
product,
like
this
cycle,
it's
I
know
it
can
get
to
be
a
lot
at
certain
times
and
like
that's.
A
What
we're
all
here
for
is
to
to
help
support
you
through
that,
let's
move
on
to
enhancements
with
Mark.
F
I've
been
involved
with
kubernetes
for
probably
four
or
five
years
now,
mostly
As,
the
chair
of
Sig
Windows,
but
as
part
of
that
role,
I've
kind
of
popped
in
and
out
of
a
lot
of
different
sigs
to
work
with
everybody
in
terms
of
the
release.
Team
I've
been
in
enhancements
Shadow
since
125
I
started
under
Priyanka
and
then
was
an
enhancement
Shadow
under
126
and
I'm.
F
Now
leading
the
release
team,
everything
at
the
enhancement
team,
professionally,
I
work
for
for
Microsoft
on
an
open
source
team,
I,
actually
work
with
Xander
and
yeah
I
see
a
couple
of
the
enhancement
Shadows
on
the
call.
So
if
you
guys
want
to
introduce
yourselves
go
ahead,
but
Nina,
do
you
want
to
start
yeah.
G
I
can
start
I'm
Nina.
This
is
my
first
time
actually
being
an
enhancement
shadow,
so
I'm
excited
and
professionally
I
work
at
solo,
which
is
a
I
work
on
the
multi-cluster
istio
team.
So
we
have
a
product
that
lets.
You
manage
your
multi-clusters
to
your
installation,
so
I'm
an
engineer
there.
H
Yeah
hello,
so
this
will
be
the
third
time.
Third
release
that
I'm
joining
my
first
one
was
in
comps
with
the
with
cats.
As
the
as
the
leads
then
I
was
the
comms
lead
for
the
last
release,
and
now
Mark
was
still
young
enough
to
to
to
ask
me
to
to
join
it
as
a
as
an
enhancement,
shadow,
professionally
I
work
at
the
SAS
Institute
as
a
cloud
and
architecture
lead
for
for
Europe
around
that
analytics
and
kubernetes
and
Cloud
native
stuff
and
I'm,
based
in
Lisbon
Portugal.
F
J
I
Also,
for
my
first
time
joining
as
a
shadow
I'm,
currently
a
student
of
computer
science
but
I
also
work
part-time
at
a
cncf
company
called
kubermatic.
As
a
software
engineer,
yeah,
let's
look
forward
to
working
with
you
guys.
A
Thank
you
good
thanks
for
introducing
yourself,
everybody
I'm,
looking
forward
to
working
with
y'all
yeah
I,
don't
I
can't
imagine,
there's
probably
questions
yet
we
haven't
hit
that
I've
made
it
that
far.
So,
let's
go
over
to
CI
signal
with
Laura.
G
K
Can
you
hear
me
yep,
okay,
great,
the
little
green
dial
was
being
very
delayed,
but
hi
everybody.
My
name
is
Laura
I.
Am
the
CI
signal
lead
for
this
release?
Previously
I've
been
a
shadow
for
CI
signal
and
a
shadow
for
the
enhancements
team
in
the
past,
and
mainly
this
week,
I'm
preparing
to
onboard
my
Shadows
once
the
shadow
selection
is
totally
finalized
and
honestly
just
getting
myself
reacquainted
with
some
of
the
dashboards
and
tooling.
K
From
last
time,
I
was
CI
signal,
Shadow
myself,
so
that
I
can
help
them
out
yeah.
K
L
Yes,
hello,
my
name
is
Angelos.
I
was
I
Am
The
Bachelorette
for
120,
seven
I
was
previously
The
Butchers
for
126,
and
it's
a
great
opportunity.
It's
it's
great
to
be
with
the
team
again
this
cycle.
L
So
from
my
side,
the
back
jazz
is
it's
very
early,
so
nothing
being
done
yet
I'm,
mostly
looking
at
the
discussion
between
a
discussion
where
we
we're
going
to
set
up
either
a
brown
zone
or
GitHub
action
for
the
for
updating
the
board
and
same
as
Laura
I'm
preparing
for
onboarding,
my
Shadows
once
the
selection
is
analyzed.
A
Now,
thank
you
and
I.
Don't
see
Mickey
on
the
call
I
will
reach
out
to
him
to
make
sure
that
he
has
the
calendar,
invite
that's
actually
gonna
I'm
gonna
touch
on
this
string
during
my
section
here.
We're
still
working
out
some
like
group
membership
stuff
that
control
some
of
the
calendar
invites
and
and
things
so,
but
we
will
get
that
resolved
ASAP
here.
A
So
let's
actually
just
jump
down
to
release
notes.
Then.
M
Hi
everyone,
my
name,
is
Harsha
I
was
released
on
Shadow
last
last
time
around
I
was
working
with
Rodolfo
and
before
that
I
spent
a
couple
of
Cycles
with
enhancements
before
and
119
and
I
believe
117
I
had
been
on
a
break
in
the
middle
for
a
while
I
professionally
I
work
at
Cisco
I'm
part
of
a
team
that
manages
builds
a
bunch
of
infrastructure
for
on
premise,
kubernetes
cluster.
A
J
A
Awesome
welcome
and
looks
like
cc
is
on
the
call
here.
Welcome
back
CeCe
good
to
see
you
do
you
have
anything
to
share
for
a
release.
Branch
management.
N
Hi
hi
happy
New,
Year
everyone,
it's
nice
to
come
back,
I
guess.
Currently
we
don't
have
any
update,
I'm,
still
working
with
second
release
list
to
decide
of
a
associate
for
on
this
release.
So
just
I'm
not
sure
if
I
need,
but
maybe
just
give
a
quick
self
introduction.
N
Hi
everyone,
I'm,
Cece,
Cece,
Huang
and
I
used
it
to
be
the
release.
125
release
lead
and
in
the
127
release,
I'll
be
acting
as
the
release
branch
manager
so
nice
to
see
a
lot
of
familiar
faces
here,
and
it's
really
awesome
to
work
with
you
again
yeah.
Thank
you.
A
O
O
It's
a
little
bit
of
introduction
I've
been
on
the
release
team
in
some
capacity,
another
from
118
which,
when
I
started
through
124
continuously,
where
I
was
released,
a
lead
and
now
I'm
back
for
127
as
EA.
So
this
is
my
eighth
release.
Team
I
think
something
like
that:
yeah
professionally
I'm,
a
Staff
Solutions
engineer
at
jet
stack,
which
is
a
kubernetes
consultancy
based
out
in
the
UK
and
I,
do
a
whole
bunch
of
work
around
on
kubernetes.
O
In
that
way,
yeah
I
don't
have
any
Shadows,
because
EA
doesn't
have
shadows
because
I
kind
of
look
after
everyone,
speaking
of
Shadow
collection,
is
ongoing.
It's
it's
basically
complete
I.
Think
all
the
leads
have
given
me
a
short
list
of
of
Shadows
to
look
at
so
I'm
just
going
to
do
some
final
checking
there.
O
We
had
a
couple
of
conflicts
where
Shadows
were
selected
by
multiple
people,
but
we've
now
resolved
those
so
I
think
we
have
a
final
list
I'm
just
going
to
do
some
last
checking
on
that
tonight
and
then
probably
give
a
go
ahead
for
everyone
to
start
reaching
out
to
their
Shadows
soon
and
then,
once
that's
complete
I'll,
probably
once
we've
got
confirmation
forever,
I
can
send
out
the
the
email
to
everyone
and
all
the
rest
of
it,
and
then
we
can
move
on
to
it
on
boarding,
so
that
should
hopefully
be
resolved
soon.
O
Our
self-imposed
deadline
for
resolving
all
of
this
was
next
week
this
Tuesday,
so
it
should
be
a
little
bit
ahead
of
that
which
is
nice,
so
everything's.
Looking
good
I
also
have
some
proposed
EA
handbook
changes
to
kind
of
help
codify
some
of
this
stuff
around
Shadow
selection
right
now,
I've
just
got
a
tracking
issue.
I've
just
thrown
some
ideas
in,
and
we
could
talk
about
that
in
a
secretly
speaking
at
some
point,
but
get
the
idea
and
I
have
some
to-do's
around
Shadow
orientation.
O
And
setting
up
virtual
meetings
so
I
don't
know
why
yeah
that's
what
I've
been
doing.
A
Awesome,
thank
you
and
I.
Just
have
a
couple
small
things
to
mention
here,
so
everyone
make
sure
that
you
are
a
part
of
the
two
Google
Groups
that
I
have
linked
here.
I
know
this
sig
release
one
you
should
be
able
to
just
join
yourself
and
then
kubernetes
release
TV
may
have
to
be
added
to
a
PR
to
case.io,
which
I'm
taking
care
of
once
I.
Have
the
entire
list
of
Shadows,
with
their
email
addresses.
I
can
get
folks
added
to
that
with
a
PR
right
now.
A
All
of
the
leads
should
be
added
that
was
done
and
so
yeah.
Anyone
where,
if
you're
like
trying
to
add
to
the
dock
here-
and
it's
prompting
you
to
comment
rather
than
add
that
likely
means
you're,
not
in
one
of
those
groups,
which
is
how
this
doc
was
shared.
So,
like
I
said,
we
will
get
that
started
out
in
the
next
couple
days
here,
especially
once
we
have
all
the
Shadows
completely
locked
in
and
then
second
note
back
contact
sheet.
A
A
Yeah
I
think
those
were
the
only
couple
things
that
I
had
next
week.
When
we
meet
again,
we
will
give
time
for
all
of
the
new
Shadows
to
introduce
themselves.
Oh
and
then
the
last
thing
was
the
code.
Freeze
date
may
change
based
on
some
initial
feedback
from
the
community,
and
you
know
I
figure,
if
we're
gonna
do
that,
it's
probably
better
to
do
that
earlier
than
later
so
I'm
gonna
James,
you
and
I-
should
chat
about
that
today.
A
But
I
may
push
the
code
freeze
date
back
a
week
which
will
for
sure
be
decided
by
the
end
of
this
week.
Yeah
that
was
all
that
I
had
so
from
here.
I'm
gonna
stop
the
recording
and
we
can
chat
about
anything
else.
That's
left.