►
Description
Kubernetes 1.20 Release Team Shadow Orientation - 10/01/2020
A
Let's
go
okay,
fantastic
hello
and
welcome.
Today
is
thursday
october
1st.
It
is
october
october
2020..
You
are
at
the
120
release
team
shadow
orientation
meeting.
So
welcome
to
everybody
thanks
for
joining
us.
We
are
recording
this
and
I
don't
know
yet
if
it
will
be
posted
publicly,
but
let's
just
assume
it's
going
to
be
posted.
Let's
assume,
there's
some
great
content
in
here
that
we
can
give
to
the
other
shadows
that
can't
make
it
to
this
call.
A
So
I'm
going
to
state
that
it
will
be
posted
publicly
now
and
all
conversations
that
happen
here
fall
under
the
kubernetes
code
of
conduct,
which
says
please
be
respectful
and
treat
your
fellow
community
members
with
respect
in
everything
that
you
say
and
do
including
the
chat
so
happy
october.
Everybody
we've
got
a
jam-packed
30
minutes.
B
A
A
Thank
you,
let's
get
into
it,
so
quick
agenda
shadowing
what
shadowing
and
mentorship
is
for
the
kubernetes
release
team
and
how
to
get
in
there.
Why
we're
here?
What
we're
trying
to
do
and
what
we're
trying
to
achieve
together
in
the
120
release
cycle,
how
to
get
the
most
out
of
shadowing?
What,
if
something
comes
up,
how
you
can
get
in
contact
with
other
people
in
the
community
who
are
here
here
to
help
and
support
you
and
the
magic
question
is
what
happens
after
this
release
cycle?
A
We
have
plenty
of
shadows
come
through
and
say:
what
can
I
do
next?
There
is
a
world
of
possibility
that
awaits
so.
I
want
to
open
up
your
minds
to
other
ways
you
might
contribute,
including
you
know,
other
release,
teams
and
other
parts
of
the
community.
So
that's
the
rough
agenda
I
have
here
so
shadowing
and
mentorship,
so
we
call
these
shadows,
but
really
it's
a
mentorship
program,
and
it's
it's
supposed
to
be
folks
that
have
done
the
role
or
had
experience
in
roles
or
supporting
roles
in
the
kubernetes
community.
A
So
it's
a
great
program
you're
in
a
great
program,
you're
in
great
hands.
If
you
haven't
shadowed
before
if
you've
shadowed
before
you
may
already
know
this,
but
there's
still
the
opportunity
to
learn
and
actually
teach
others
too.
So,
even
if
you're
a
more
experienced
shadow
or
you're
trying
a
new
role,
it's
not
there's
nothing
to
say
that
a
lead
must
be
in
control
of
shadowing
other
shadows.
A
If
you
have
experience
that
you
want
to
share
share
that
with
other
people,
you're
empowered
to
do
that,
it
doesn't
have
to
be
all
coming
from
the
lead.
So
I
know
there
are
several
members
of
the
team
that
may
have
shadowed
other
roles
or
been
leads
in
other
roles
in
the
now
shadowing,
so
feel
free
to
help
other
team
members
we're
all
a
team
here
and
we're
united
for
a
single
purpose
and
that's
getting
the
120
release
out
of
the
door
to
finish
round
out
year
2020.
A
A
Obviously,
your
time
is
your
time
and
you've
stated
in
part
of
the
shadow
application
and
the
leads
took
that
into
consideration
how
much
time
you'd
be
able
to
spend,
but
obviously
we
want
to
just
be
cognizant
of
burnout
managing
your
own
time
and
setting
your
own
boundaries
with
your
time,
everybody's
here
to
volunteer
nobody's
sitting
up
with
a
pager
specifically
on
release
teams.
Maybe
maybe
some
people
are.
A
I
know
that's
tough
position
to
be
in,
but
we
got
to
just
respect
each
other's
time
and
be
cognizant
that
people
are
in
other
time
zones
around
the
world.
So
what
might
be
a
great
time
for
you
to
drop?
Something
in
slack
doesn't
mean
it's
a
great
time
for
somebody
else,
and
they
may
respond
eight
hours
later
and
that's
okay.
A
They
may
respond
12
or
24
48
hours
later,
so,
let's
just
be
respectful
for
each
other.
The
time
zones
that
we're
working
in-
and
you
know,
set
up
your
slack
notifications
to
be
paused
at
the
appropriate
time
that
you
have
to
take
a
break
but
we're
all
in
this
as
volunteers.
It's
all
a
lot
of
our
personal
time.
Some
people
have
time
to
do
it
during
their
jobs,
but
let's
just
be
respectful
of
all
the
time
that
we're
spending
together.
And
finally,
you
get
out
of
shadowing
what
you
put
in.
A
So
as
it's
a
volunteer
role,
come
ask
questions
say
I
have
time
I
can
help
with
this.
Is
there
anything
else
you
need
help
with
we're
not
going
to
as
the
leads
force
things
for
people
to
do.
You
need
to
do
that.
You
need
to
do
this.
There's
none
of
that
kind
of
behavior
here
it's
more
hey
here
are
some
here
are
some
jobs.
I
have
time
so
please
ask
if
you
have
time
and
you
want
to
focus
on
things.
A
I
know
me
personally-
I
carve
several
hours
out
a
week
to
focus
on
kubernetes
contribution,
so
I
I
could
try
to
stack
things
up.
Here's
a
list
of
things
I
can
do,
and
here's
when
I
will
do
them
rather
than
steps
you
know,
peppering
it
in
and
out
of
the
day.
That's
just
the
way
I
work,
but
you
find
what
works
for
you
and
I'll.
Give
everybody
a
chance
to
ask
questions
at
the
end
I'll
go
through
this
deck
fairly
quickly.
A
So
how
do
I
actually
get
the
most
out
of
shadowing?
So
as
a
shadow
leverage,
your
lead
ask
them.
Questions
get
feedback
if
you're
new
to
the
kubernetes
community
or
even
somebody,
a
seasoned
community
member
communication
is
key.
So
when
we
communicate
in
kubernetes,
we
have
two
large
avenues
that
I
see.
One
is
on
github
issues
and
pr's
we
can
communicate
through.
That
means
it
really
depends
on
which,
what
which
audience
you
want
to
reach,
and
then
we
have
the
slack
channels.
A
We
have
the
sig
release
slack
channel.
We
have
the
release
management
slack
channel.
There
are
a
few,
but
I
would
say:
sig.
Release
is
a
good
place
to
start.
So
if
you
haven't
joined
the
sig
release
channel
go
in
there
and
you
can
ask
questions,
don't
feel
embarrassed
or
shy
to
ask
obviously
we're
all
here
to
help
each
other
and
the
only
if
you
don't
ask
there's
no
way
for
you
to
find
out
and
there's
no
way
for
us
to
help
us.
So
you
can
either
ask
your
leads.
A
Ask
anybody
in
the
supporting
role
and
I'll
show
you
everybody
on
the
team
and
their
slack
handles
towards
the
end
of
this.
So
you
can
do
that.
I
also
want
to
encourage
everybody
to
communicate
in
the
open,
so
join
the
slack
channels.
I
know
it's
easy
to
start
a
dm
with
your
lead
right
and
ask
have
a
one-to-one
conversation
with
the
lead
that
the
challenge
with
that
is
the
other
shadows.
A
Here's
when
I
have
time
here's
when
I'm
going
to
be
looking
at
this,
can
I
do
anything
to
help.
Can
you
help
me
with
this?
I
don't
I
need
more
details.
Can
we
jump
on
a
call,
but
that
kind
of
asynchronous
communication,
via
slack
or
even
sometimes
synchronous
is
kind
of
good
behavior
and
what
we
want
to
encourage
so
feel
free
to
communicate
when
you're
a
shadow?
We
expect
you
to
ask
questions.
We
don't
expect
you
to
have
all
the
answers
right.
We
don't
expect
you
to
know
where
to
look.
A
A
It's
your
opportunity
to
learn
volunteer
as
much
time
as
you're
able
to
help
with
the
release.
Obviously
I
want
to
say
that
with
set
clear
boundaries
for
yourself,
we
don't
want
to
encourage.
You
know
you
to
burn
out
and
work
extra
hours,
because
we
have
many
shadows
for
each
role
and
the
reason
we
do
many
shadows
for
each
role
is
so
that
we
can
all
support
each
other
so
that
we
don't
have
one
person
completely
working
around
the
clock
burning
themselves
out.
We
should
be
able
to
pass
the
ball
to
our.
A
You
know,
shadows
to
help
us
achieve
what
we
need
to
get
done,
attend
the
sig
release
meetings.
There
are
other
appropriate
sigs
as
well.
So
if
you're
working
in
an
area
where
you're
like
I
am
in
an
enhancement
shadow-
and
I
have
these
five
enhancements
and
one
enhancement
is
in
sig
network-
and
I
haven't
heard
anything
from
syd
network-
you
could
go
to
the
sig
network
meeting.
You
can
add
something
to
their
agenda
and
say
hello,
I'm
a
shadow
from
the
120
release
team.
A
You
have
an
issue
in
for
an
enhancement,
I
haven't
heard
anything
from
it
and
if
I
don't
hear
anything
from
it
in
the
next
two
weeks,
it's
not
going
to
be
tracked
and
more
often
than
not
those
people
go.
Oh,
I
didn't
know
that
that
was
the
case.
Thank
you
for
showing
up
and
helping
me
do
the
right
thing.
So
you
know
everybody's
here
everybody
has
fairly
good
intent.
Everybody
has
good
intent
in
the
in
the
community
to
get
things
done
so
often
don't
feel
like
you
just
have
to
come
to
our
meetings.
A
A
A
Take
the
opportunities
to
talk
to
other
non-released
team
members
in
the
community.
So
if
you
are
building
a
relationship,
let's
go
back
to
that
comms
that
comms
example
hey,
stick
node
has
a
new
enhancement,
maybe
building
a
relationship
with
the
person,
who's
responsible
or
people
that
are
responsible
for
that
enhancement
is
a
great
way
to
build
new
relationships.
You
might
form
a
relationship
and
that
might
take
you
places
down
the
road
in
your
kubernetes
contribution
journey.
So
that's
I'll
just
quickly
check
questions.
Is
there
anything
burning
that
I
need
to
answer
now?
A
I
see
a
couple
of
chats.
Yes,
yes,
okay!
Well,
I
think
we're
okay
I'll
keep
moving.
Okay.
Now
what?
If
something
comes
up?
What,
if
I
have
something
that's
burning,
hey
somebody
has
fallen
ill.
I
need
to
take
a
couple
of
weeks
off.
That
is,
okay,
just
talk
to
somebody
about
it,
okay,
going
dark
and,
and
not
letting
us
know.
Obviously
there
can
be
extreme
circumstances,
but
just
let
us
know
circumstances
change.
The
world
is
a
little
bit
crazy
at
the
moment.
A
We
understand
that
you
have
grounds
to
talk
to
people
so
obviously
the
chain
of
how
we
would
like
to
talk
to
your
lead.
The
lead
is
the
person.
That's
going
to
be
most
impacted
by
any
changes
and
they
are
the
one
you're
going
to
have
the
closest
relationship
with
throughout
the
120
release.
There's
me
the
emeritus
advisor
if
you're
having
challenges-
and
you
need
to
talk
to
somebody
else,
you
can
obviously
come
to
me.
A
I
am
a
support
role
for
the
whole
release
team
and
specifically,
one
of
my
tasks
is
to
help
shadows
through
this
journey.
So
if
you
have
questions
about
the
shadow
program,
hey
lucky,
I
have
an
idea
hey.
This
would
have
been
a
much
better
thing.
If
you
did
this
lucky
hey,
you
could
support
shadows
like
this
you're,
a
shadow
you're
empowered
to
change
it.
Don't
think
because
the
way
the
program
is
now
is
the
way
it
needs
to
stay.
A
If
you
see
opportunities-
and
you
say
I'm
going
to
go
after
that
for
this
release-
and
I'm
going
to
make
a
change
to
that
you're
empowered
to
do
that-
that
is
okay.
If
you
come
to
me
and
say,
hey
lucky,
this
orientation
would
have
been
way
better.
If
you
hadn't
talked
about
this
this
this
this
and
this,
I
am
okay
to
hear
that
I
am
okay
to
hear
that
feedback
come
to
us.
We've
got
so
you've
got
jeremy
as
the
120
release
lead
as
well.
Obviously,
anything
really
burning
gated
up
to
jeremy
as
well.
A
A
So
you
may
see
glory
around
the
channels
and
showing
up
to
the
release
team
meeting
and
saying
here's
our
project
board
she's,
actually
taking
on
the
responsibility
of
making
sure
all
the
longer-lived
items
and
strategy
start
to
get
done
over
time
between
releases.
So
you
will
see
her
showing
up
to
many
meetings,
say
hi
to
laurie.
She
has
a
very
important
role
to
take
care
of
all
the
larger
ticket
items
that
don't
necessarily
just
fit
into
one
release:
a
mid-release
cycle
shadow
survey.
A
So
I'm
going
to
send
out
a
survey
in
the
middle
of
this
release
to
kind
of
checkpoint,
where
everybody
is
that's
your
chance
to
give
us
feedback
about
your
time
as
a
shadow.
How
you're
going
with
your
leads?
How
you're
going
with
the
role
do
you
have
support?
It
will
take
you
five
minutes
to
complete.
I
will
send
out
a
note
and
then
at
the
end,
we
have
the
release
retro.
A
So
the
release
retro
dock
is
actually
at
the
end
of
it.
If
you
haven't
done
a
release
before
we
go
and
have
a
meeting
and
say
what
worked
well,
what
didn't
work
well
and
what
are
we
going
to
commit
to
improving
in
subsequent
releases?
If
you
see
something
that
document
is
available
right
now,
I'm
going
to
show
you
how
to
get
a
link
to
it.
You
can
just
pop
put
in
an
item.
A
This
worked
well,
this
didn't
work
well
with
your
name
and
brackets
and
then,
when
we
do
the
release
retro,
we
go
over
each
of
those
items
and
we
say
here's
what
went
well,
here's
what
we
his
room
for
improvement
and
here's
what
we
might
commit
to
doing
in
the
next
releases.
So
that's
a
really
important
feedback
document,
so
I
find,
as
you
go
and
think
of
things
write
them
down
as
you
go,
it's
always
hard
at
the
end
of
the
release
to
remember.
A
Oh,
what
well,
what
didn't
go
well,
so
that
document
is
open
and
accessible
now.
Second,
to
last
what
happens
after
this
release
cycle
great
question?
So
if
you
wanted,
if
you
want
to
continue
on
the
release
team
after
you
absolutely
can
you
can
talk
about
your
expectations
and
what
you
would
like
to
do.
There
is
no
requirement
that,
if
you've
shadowed,
you
have
to
leave
lead
and
if
you've
shadowed
in
one
role,
you
can't
shadow
another
there's
none
of
those
requirements
but
talk
to
your
lead.
A
I
would
encourage
that
if
you
are
interested
in
leading
the
role
that
you're
shadowing,
let
your
lead
know.
Obviously,
it's
not
guaranteed
and
and
there's
only
a
fixed
amount
of
leads,
but
just
let
them
know
if
you
feel
like
you
want
to
learn
more
in
another
area,
apply
to
a
different
role.
If
you
want
to
learn
more
in
the
same
role
up
reapply
to
the
same
role.
That
is
absolutely
okay.
There's
no
restrictions
on
doing
that.
A
So
and
if
you
want
to
try
out
other
groups,
that's
fine,
there's
also
the
release
manager
associates
group
as
well.
So
if
you
find
through
this
release,
oh
I'm
really
interested
in
how
the
artifacts
are
built
and
how
the
branches
are
cut
and
how
the
releases
are
done.
There's
a
whole
team
that
takes
care
of
that
engineering
side.
So
you
can
go
over
and
take
a
look
at
that
as
well,
and
we've
had
many
members
of
the
release
team
say
that
that
is
actually
really
interesting
to
me.
A
If
you,
obviously,
there
are
roles
and
sigs
associated
with
different
roles,
so,
for
example,
if
you're
working
in
the
comms
role
or
the
docs
role-
or
maybe
even
the
release-
notes,
you
might
say,
hey
sig
docs
might
be
a
place.
I
could
actually
go
and
contribute
to.
I
really
like
documentation.
I
want
to
go.
Do
that
sig
pm,
which
is
now
defunct,
but
there
is
a
team
that
owns
the
caps.
If
you
really
like
the
cap
process,
you
can
go
and
help
with
the
cap
process
under
enhancements.
A
So
there
are
many
different
areas.
The
great
thing
about
the
release
team
is
it's
a
great
place
to
find
your
footing
be
supported
in
finding
your
footing
in
the
kubernetes
community,
but
there
is
no
requirements
for
you
to
stay
in
the
release
team.
If
you
say
hey,
I
love
what
seeknote's
going
to
do
is
doing
I'm
going
to
go
work
over
there.
That
is
okay.
A
The
whole
community
is
at
your
disposal
disposal.
I
should
say
in
terms
of
where
you
want
to
contribute,
there's
no
restrictions
there
and
if
you
don't
think
the
release
team
is
a
right
fit,
you
can
go
explore.
Many
other
place
parts
of
the
kubernetes
ecosystem,
the
cncf
ecosystem-
that
is
aok
as
well.
So
I
just
want
you
to
set
your
scope.
You
can
either
come
back
to
the
release
team
or
you
can
go
to
other
parts
of
kubernetes
or
you
can
go
to
the
other
parts
of
the
cloud
native
ecosystem.
A
All
of
those
things
are
a-okay
and
what
you'll
find
with
the
skills
you've
learned
in
in
the
release
team?
You
can
take
them
that
can
completely
transferable
the
way
you
learn
the
way
you
contribute,
they're,
completely
transferable,
to
other
projects
within
the
ecosystem
and
other
projects
with
you
know,
sub
projects
of
kubernetes
itself.
A
Finally,
resources
for
shadows.
There
is
actually
an
onboarding
guide.
I
sent
out
a
link
here.
Let
me
click
it.
If
I
can
there's
actually
an
onboarding
guide
here
for
you
to
walk
through
and
it
talks
about.
You
know:
contact
sheets,
mailing
lists,
different
forms
of
communications,
how
we
actually
take
care
of
things
and
how
owner
file
works,
there's
a
whole
onboarding
guide.
There
there's
also
you
the
readme.
So
let
me
pop
pop
now
over
to
the
repo
itself
and
I
will
actually
navigate
it
from
that
direction.
A
So
your
one
big
resource
here
for
go
to
knowledge
is
in
the
sig
release.
So
if
you
go
to
kubernetes
sig
release
repo,
I'm
going
to
show
you
how
to
navigate
it
here.
Obviously
this
is
the
top
level
readme
areas
that
are
going
to
be
probably
of
extreme
interest
to
you
is,
first
and
foremost
the
releases
directory
should
have
every
release,
so
you
can
go
and
look
at
previous
releases,
but
obviously
we're
in
release
1.20.
A
This
is
the
page
table
of
contents
for
everything
that
you're
going
to
need.
So
here
is
the
meeting
minutes,
so
you
can
pop
them
out
for
here.
Here's
the
release
calendar,
here's
the
slack
channels,
contact
info
enhancements
tracking
sheet.
So
if
you
wonder
what
the
enhancements
teams
up
to
here's
the
enhancements,
they're
tracking
retro
document-
I
mentioned
that
before.
A
If
you
want
to
go
start
looking
at
the
retro
dock,
you
can
go
here
and
and
click
into
it
right
now
and
say:
oh,
what
went
well,
you
know
I
think
the
shadow
orientation
went
well
brackets
lockheed.
You
can
do
that
right
now,
so
this
is
one
of
the
most
important
things
that
you
can
have
also
the
timetable.
When
is
code
freeze
when,
as
when
is
the
release
going
out,
you
can
take
a
look
at
all
these
bits
and
pieces
they're
all
here
for
you
to
look
at
the
other
bit.
A
That's
really
useful
is
release
underscore
team.
Who
are
the
people
that
I'm
shadowing
with
who
are
the
leads?
Who
are
the
lead
shadows?
Everything
is
up
here
for
you
to
see
you
have
access
to
to
folk
slack.
So
if
I
wanted
to
contact
celeste,
I
know
how
to
contact
celeste
just
for
an
example.
Anybody
here
is
contactable
via
the
github
or
so,
if
you
need
to
add
somebody
on
github
or
slack.
That
also
is
a
great
thing
to
have
in
your
back
pocket
figuratively.
A
Let's
go
back
up
to
the
top
level.
The
other
thing
that
is
very
interesting
for
me,
too,
is
the
release
team
release
dash
team.
You
under
there
you
have
the
role
dash
handbooks.
What
role
am
I
in
I
am
in
enhancements
here.
Are
the
responsibilities
of
the
enhancements,
lead
and
shadows
it
walks
through
everything
here,
so
these
role
handbooks
are
living
documents.
A
If
you
see
things
that
you
no
longer
think
are
appropriate
to
the
role
talk
to
you
later
about
it,
they're
only
a
pr
away
to
fix,
so
this
thing
isn't
scribed
into
stone,
feel
free.
If
there's
things
that
are
missing,
make
updates.
As
you
read
through
them,
we
just
expect
that
these
documents
get
updated
as
a
matter
of
course,
in
each
release.
A
A
A
Everything
that
jeremy
jeremy
will
be
following
this
late,
so
that
is
all
the
content
I
wanted
to
get
through.
I
want
to
leave
a
couple
of
minutes
for
questions
here
and
obviously
the
questions
don't
have
to
stop
at
the
end
of
the
time.
Thank
you
for
listening.
I
hope
that
you
found
that
informative,
but
let
me
go
and
take
questions
feel
free
to.
A
B
So
for
us
to
be
really
able
to
do
a
better
job,
I
believe
we
need
to
understand
the
bigger
ecosystem.
So
for
me,
for
example,
if
I
benchmark
on
the
ci
signal,
I
can
go
narrow
down
and
I
know
exactly
what
is
the
handbook?
What
is
my
role
supposed
to
be
doing
and
so
on,
but
I
believe
there
is
a
huge
potential
once
we
understand
the
ecosystem
around
us,
which,
to
be
honest,
is
still
for
me
overwhelming.
B
Okay
to
understand
the
other.
Things
understand
how
we
actually
the
overall
platform
itself,
how
we
be
more
creative.
This
required
us
to
invest
more
time
and
more
effort
to
understand
the
ecosystem.
To
be
honest,
I
still
failed
to
find
that
reference
to
help
me
understand
how
this
all
works
together.
I
know
that
it
comes
with
experience,
but
still
a
bit
overwhelming.
B
A
Yeah,
thank
you.
Thank
you
for
bringing
that
up
and
and
I'm
gonna
go
and
investigate.
I
know
we
have
consid
contributor
experience.
It
might
be
worth
throughout
the
course
of
a
release
that
you
opt
into
some
of
the
material
and
courses
that
they
run.
So
let
me
go
talk
to
them
and
see
what
they
think
the
best
next
step
is
but
yeah.
I
totally
understand
that
it
is
overwhelming
and
I
I
I
get
that
it's
it's
always
challenging
to
how
much
information
can
you
give
in
in
a
short
amount
of
time?
A
A
No
okay,
excellent!
Well!
Thank
you
very
much
for
your
time.
This
concludes
the
shadow
orientation.
What
I
will
say
is
reach
out
to
your
leads.
If
you
haven't
had
an
orientation
or
a
conversation
with
them
about
role
expectations,
they
should
all
take
on
getting
you
the
knowledge
and
orienting
you
on
how
they're
going
to
operate
in
this
release,
and
I
will
encourage
them
to
make
sure
that
they
reach
out
and
do
that.
So
that
concludes
the
general
shadow
orientation.