►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Getting Involved in the K8s Release Shadow Program - Divya Mohan, HSBC
As an aspiring contributor, it can be daunting to get started with the vast ecosystem of the K8s project. The Release Shadow program is the perfect way for all contributors - novice & veteran to be familiarized with different aspects of the release + different SIGs within the ecosystem. Join in to learn more about - What a K8s release looks like - What the Release Shadow program is - how you, as a student, can get involved - some pre-requisites
A
A
That
being
said,
I
feel
like
it's
a
little
bit
more
important
to
talk
about
our
subject
matter
from
the
standpoint
of
what
it
isn't,
the
reason
being.
A
lot
of
information
is
already
available
as
to
what
it
is,
and
we
also
will
be
covering
it.
So
don't
worry
too
much
about
that,
but
a
lot
of
stuff
around
the
internet
or
whatever
you
search
for
it,
doesn't
really
detail
as
to
what
it
is
so
so.
A
The
release
shadow
program
is
a
mentorship
program
for
sure,
but
it
is
not
a
coding
or
a
documentation.
Internship
program
with
the
kubernetes
project
show
kubernetes
project
is
involved
with
the
lfx
outreach
sheet.
Google
season
of
dogs,
google
season
of
food.
Previously,
it
has
been
sorry
and
we
have
had
successful
participation
in
those
particular
programs,
but
the
kubernetes
release
shadow
program
is
not
related
to
that
and
just
as
a
reminder,
it
is
not
the
only
way
to
get
started
or
you
know,
contribute
to
kubernetes
or
open
sausage.
A
So,
even
if
you
don't
get
it
and
even
if
you
don't
make
it
in
the
very
first
attempt,
please
don't
be
demotivated,
because
this
is
not
to
do
all
and
beyond
of
your
open
source
journey
or
your
journey
even
in
the
kubernetes
project,
and
the
last
line
is
something
that
I
felt
needed
an
explicit
shout
out
there.
It
is
a
great
line
on
your
resume.
A
The
second
thing
is,
it's
obviously,
a
very
great
opportunity
to
learn
more
about
the
kubernetes
ecosystem,
as
well
as
the
open
source
ecosystem
in
general.
So
as
part
of
the
release
date,
you
get
the
opportunity
to
interact
with
various
stakeholder
special
interest
groups
and
some
of
the
best
and
kindest
folks
in
the
tech
community,
and
I'm
not
exaggerating
so
as
part
of
those
interactions.
A
You
are
going
to
have
exposure
to
how
it
works
in
my
day,
job,
for
example.
I
did
not
have
that.
You
know
standpoint
from
where
I
could
understand
what
a
typical
release
process
looked
like,
but
being
a
part
of
the
open
source
community
communities
rather
helped
me
gain
more
understanding
and
also
gave
me
pretty
good
exposure
to
how
a
release
looks
like
in
an
open
source
ecosystem
last,
but
not
the
least.
A
I
did
mention
that
it
is
not
an
internship
program,
but
it
is
definitely
a
mentorship
opportunity,
so
you
are
going
to
shadow
or
work
under
a
role
lead
and
that
will
be
obviously
basis.
The
application
form
that
you
fill
and
the
choice
that
you
make.
While
you
fill
that
application
form
and
irrespective
of
the
role
that
you
are
shadowing,
it
primarily
encompasses
coordination
and
facilitation
of
the
various
artifacts
that
go
into
a
kubernetes
release.
A
So
there
is
no
actual
coding
or
writing
documentation
required
as
part
of
being
in
the
release
team,
but
you
will
be
doing
a
lot
more
than
that.
So
it's
a
very
great
learning
experience,
if
I
may
say
so
and
honestly,
it
also
is
as
much
of
an
effort
from
your
side
as
much
as
it
is.
You
know
getting
into
the
release
team,
so
getting
into
the
release.
Team
is
a
competitive
effort.
A
I
know
that
because
last
release
this
release
cycle,
rather
we
received
185
plus
applications
alone,
so
it
is
obviously
a
very
competitive
program.
But
again,
like
I
said
before,
what
you
get
out
of
the
experience
is
what
you
put
into
it.
So
unless
you
are
ready
to
make
that
time
commitment
and
unless
you
are
ready
to
make
that
effort
commitment
for
the
time
frame,
I
would
highly
recommend
you
to
assess
your
skills,
assess
your
strengths
and
then
go
ahead
with
the
application.
A
This
is
not
to
deter
anyone,
but
is
just
giving
a
realistic
picture
of
how
it
is
so
now
that
we've
spoken
about
all
of
this
who
organizes
this
whole
effort,
because
at
the
end
of
it
somebody
needs
to
be
organizing
this
particular
program
right.
So,
within
the
kubernetes
project
itself
we
have
various
groups
and
in
the
kubernetes
project
like
with
every
other
large
organization,
we
have
specific
nomenclature,
so
the
governance
aspects
are
managed
by
the
committees.
A
User
groups.
Are
you
know,
folks
who
have
similar
interests
areas
and
do
not
have
any
ownership
of
the
code
base
working
groups
and
six
are
short.
So
six
are
special
interest
groups
before
you
know
anybody
gets
confused,
so
special
interest
groups,
like
the
name
suggests,
is
dedicated
towards
special
interests
and
furthering
those
interests
into
an
actual
artifact
for
each
kubernetes
release,
and
maybe
not
even
that
at
some
time.
A
So
there
are
special
interest
groups
that
do
not
have
anything
to
do
with
the
release,
but
have
like
a
meta
role
to
play
within
the
project.
So
just
as
you
know,
brief
it
there
are.
Various
groups
within
the
kubernetes
project
would
be
a
short
summary
of
you
know
how
our
project
is
organized,
but
it
is
the
sig
release
that
organizes
the
release.
A
You
know
the
release
shadow
program
and
the
release
team
is
one
of
the
sub
projects
within
the
special
interest
group
release,
so
who
is
actually
eligible
because
I've
said
a
lot
about.
You
know
who's,
organizing
it
what
it
is,
what
it
is
not
but
who
actually
is
eligible
so,
like
I
mentioned
before,
anyone
really
because
as
a
prerequisite,
you
do
not
need
a
lot
of
things
but
it.
A
But
let
me
remind
you
once
again
that
it's
a
highly
competitive
program,
so
the
narrowing
down
or
the
selection
depends
on
a
lot
of
factors.
So
you
can
apply
if
you
are
really
interested
and
you
do
not
need
any
experience
being
part
of
a
release
team.
You
do
not
need
coding
expertise
and
you
do
not
need
to
have
knowledge
or
you
know,
expertise
on
kubernetes
having
it,
however,
is
not
a
disadvantage.
I
will
definitely
help
you
but
fun
fact.
I
did
not
start
off
having
kubernetes
knowledge.
A
When
I
joined
the
release
team
last
year.
My
whole
idea
of
joining
kubernetes
as
a
project
was
to
learn
more
about
kubernetes
as
a
tool
or
a
technology.
So,
honestly,
if
you
are
interested,
you
definitely
should
consider
signing
up
and
genuinely.
There
are
no
specific
prerequisites,
except
for
the
time
and
effort
commitment
from
your
end.
A
So
I've
spoken
at
length
about
the
release
team
and
you
know
I've
I've
retweeted
the
release
team
so
many
times
you
must
want
to
see
a
pictorial
depiction
of
how
you
know
the
release
team
looks
like
I
mean
I
cannot
put
the
faces
because
we
are,
we
don't
have
like
a
consistent.
What
do
you
say?
Membership
every
cycle,
so
the
release
team
as
a
whole
basically
looks
like
this.
So,
as
you
can
see,
there
are
a
lot
of
verticals
in
the
release
team.
There's
an
enhancements
vertical.
A
A
A
It
also
deals
with
the
blog
that
actually
gets
released
on
the
release
date,
and
you
know
all
the
coordination
with
cncf
all
of
that
comes
under
the
comms
vertical.
Now,
if
you
go
to
the
docs
bit,
it's
it's
a
no-brainer
right.
You
need
documentation
for
every
release
artifact,
so
the
dog's
vertical
is
responsible,
is
responsible
for
ensuring
that
there
are
relevant
documentation
available
for
every
release,
artifact
or
enhancement
that
goes
in
and
speaking
of
enhancements.
A
Lead
is
basically
just
the
tracking
of
enhancements
has
an
overall,
you
know
gist.
So
now
you
may
ask:
what
does
the
release
lead
to
and
what
is
the
emeritus
advisor
in
green?
So
as
with
everything
you
require
chief
and
command
commander,
chief
or
chief
in
command?
I'm
sorry,
I
forget
the
term
here,
but
you
require
someone
at
the
helm
to
sort
of
bring
everyone
together
and
shepherd
the
shepherd
them
towards
driving
the
release
to
the
completion
right.
A
So
the
release
lead
actually
does
that
job
along
with
his
hor
or
their
shadows,
and
the
emeritus
advisor
is
a
previous
release
lead
who
actually
ends
up
functioning
as
an
advisor
of
sorts
to
the
release
lead
release.
Richard
was,
and
literally
every
everybody
in
the
team
base
based
on
his
her
or
their
experience
in
the
release
team.
So
where
do
you
come,
and
that
is
where
I
would
like
to
show
you.
So
if
you
can
see
here,
there
are
a
lot
of
shadows
written
across
each
vertical
right.
A
But
the
shadowing
aspect
is
where
you
will
be
working
along
with
your
vertical
rollie
and
ensuring
that
the
artifact
or
the
deliverables
assigned
to
you
are
completed
by
the
specific
time.
Now,
even
in
this
whole
image,
there
are
specific
times
in
the
release
when
each
of
these
are
more
active.
For
example,
comms
is
a
more
end
of
the
release,
heavy
role,
which
doesn't
mean
that
coms
doesn't
do
anything
in
the
start
of
the
release.
A
We
are
more
often
prepping
towards
the
end
of
the
release,
so
that
a
lot
of
the
work
doesn't
bulk
up
towards
the
end,
as
opposed
to
which
enhancements
is
the
start
of
the
release
heavy
role,
because
only
once
you
start
tracking
the
enhancements.
Will
you
be
able
to
actually
get
the
release
out
right
and
the
relevant
talks
out
in
the
relevant
release?
Notes
up
so
different
roles?
A
Have
you
know
different
time
commitments
and
different?
You
know
different
areas
in
the
release,
not
different
areas
different
times
in
the
release
when
they
are
more
active,
but
as
an
overall
time
commitment
like
I
mentioned
in
a
couple
of
slides
before
it
should
be
around
three
to
four
months
now
coming
to.
How
do
you
apply
so
at
the
end
of
every
release?
This
was
the
shadow
selection
for
kubernetes
1.22.
A
This
was
sent
out
after
the
kubernetes
one
dot,
not
after
or
towards
the
end
of
kubernetes
1.21,
and
this
is
sent
to
the
kubernetes
dev
and
kubernetes
there,
google
groups
and
a
couple
of
other
avenues
within
the
kubernetes
project.
We
also
try
to
amplify
it
via
our
twitter
handle.
So
those
are
good
avenues
where
you
can
keep.
A
You
know
track
of
this
particular
email
or
you
know,
notify
a
notification,
so
the
emeritus
advisor
for
that
current
release
would
be
the
one
who
will
be
sending
it
out
in
case
you
have
signed
up
for
the
google
groups
and
obviously
there
will
be
communication
sent
out
and
slack
as
well.
So
those
are
three
four
places
where
you
should
keep
your
eyes
peeled.
If
you
are
interested
in
joining
the
release.
A
Now,
some
of
the
things
that
I
would
like
to
you
know
reinstate
before
we
close
off
for
the
day.
It
is
not
the
only
way
to
get
started
in
kubernetes
or
open
source.
It
does
seem
like
it
because
you
know
of
the
lower
entry
level
barrier
where
you
don't
require
any
prior
experience
in
a
lot
of
avenues,
but
it's
not
the
only
way
to
get
started.
A
So
if
this
doesn't
work
out,
you
definitely
can
sort
of
you
know
pick
and
choose
from
other
opportunities
that
are
available
not
necessary,
mentorship
or
internship
programs.
But
there
are
tons
of
other
opportunities
like
documentation
and
non-code
contributions
that
are
available
not
only
within
kubernetes
but
with
other
open
source
projects.
A
So
you
need
to
imagine
the
scale
that
we
are.
You
know
sort
of
scale
of
applications
that
we
are
sort
of
receiving
and
the
amount
of
rejections
that
have
to
be
sent
out.
So
it's
an
extremely
competitive
program
and,
as
a
result,
it
is
also
very
easy
for
a
rejection
to
come
by,
given
the
competitiveness,
so
don't
get
demotivated
and
as
always,
there
are
other
avenues.
A
This
personally
took
a
long
while
for
me
a
little
while
for
me
to
understand,
I
won't
say
long
a
little
while
for
me
to
understand,
because,
as
with
everything
else
and
as
with
everybody
else,
I
was
expecting
quick
results.
But
sustainability
and
sustainability
of
the
contributions
is
the
key
here,
because.