►
Description
The Kubernetes Steering Committee will be available to ask questions from the audience.
A
B
A
B
C
D
I'm
Erin
Kraken,
burger
I,
am
also
on
the
steering
committee.
My
fun
fact
is
I.
By
the
time
I
was
15,
I
had
moved
around
12
different
times.
One
of
those
places
was
Geneva
Switzerland,
Daksha,
Prajapati,
Bertha
sue,
Larson,
Pamela
vocabular
market
petite,
but
yeah.
If
you
want
to
try
practicing
that
come
talk
to
me,.
E
F
F
G
H
G
G
B
I
A
B
We
have
three
other
steering
committee
members
that
I
believe
they're
at
the
cloud
native
computing
foundation
board
meeting.
At
the
moment.
They
were
very
deep
in
a
SWOT
analysis
when
I
left,
so
they
will
join
us
when
they
can
that's
Joe,
bata,
Michelle,
Nirali
and
Brendan
Phillips,
so
they
will
join
us
shortly.
Brandon
Brandon
be
Don
as
I'm
going
to
refer
to
both
of
them.
Yes,.
B
I
A
A
But
I
think
that
the
biggest
guideline
that
we
came
up
with
was
to
try
and
delegate
as
much
as
possible,
and
so
in
some
ways.
If
we
are
making
a
decision,
then
it
means
that
we
failed,
because
our
hope
is
that
we're
empowering
the
community
and
we're
finding
the
right
people
there.
We
go
I
guess
we're
finding
the
right
people
to
make
decisions
for
us
and
in
fact,
in
some
ways
as
we've
gone
down.
A
A
A
A
E
I
At
security,
audit
we've
set
up
a
bootstrap
to
code
of
conduct
committee,
set
up
governance
and
structure
for
sakes
and
and
working
group
scope
and
operations,
updated
our
own
charter
and
solidified
values,
and
this
goes
to
back
to
the
why
what
we're
trying
to
do
is
set
up
a
structure
so
that
the
project
can
can
manage
itself
as
well
as
identify
areas
where
there
isn't
sufficient
ownership
and
then
so
set
up
ownership
within
the
project.
For
that
Tim,
st.
Clair,
congratulations,
you
win.
H
H
We
also
have
a
public
and
private
mailing
list.
If
you
want
to
reach
us
on
the
public
mailing
us
I'm
guessing
this
is
the
public.
One
is
steering
at
kubernetes
at
I/o,
there's
also
sessions
that
Parris
organizes
during
the
meet
our
contributors
section.
So
that
way
you
can
actually
meet
some
of
the
folks
on
the
steering
committee
and
ask
them
questions.
I.
L
E
L
L
But
most
important
things
seems
to
be
around
security
auditing.
What
do
we
do
as
a
policy,
and
is
that
the
first
priority
that
we
have
that's,
for
example,
one
of
the
things
that
we
want
to
talk
about,
but,
more
importantly,
we
are
not
going
to
do
all
the
work
like
people
have
mentioned
before
we
want
to
build
roles
where
we
can
pull
in
people
from
the
community
to
do
the
actual
work
or
delegated
it
to
the
different
six
and
the
sub
projects
of
the
six
and
things
like
that.
D
You
I
want
to
add
a
little
more
color
to
that.
If
the
bosun
will
allow
me
cool
you,
okay,
two
minutes.
This
is
impossible.
If
you
remember,
when
the
steering
committee
was
first
founded,
there
were.
Our
charter
was
massive
to
address
things
like
identify
gaps
within
the
project
figure
out.
What
it
is
ya
do
here,
figure
out
who
actually
owns
each
and
everything
figure
out
how
the
project
should
be
organized
figure
out.
D
The
code
organization
structure
make
sure
that
actually
lines
up
with
the
people
organization
structure
define
what
a
working
group
is
to
find
how
that's
different
from
a
cig
define
how
that's
different
from
a
committee
make
sure
that
there
is
a
committee
that
deals
with
the
code
of
conduct
issues
that
is
not
just
Sarah
and
I.
Think
we
have
more
or
less
addressed
a
lot
of
that
like
between
the
did.
You
know
there
are
36.
There
are
36
actually
31.
There
are
also
10
working
groups-
okay,
oh
there's
32
sig
beard!
D
Thank
you
so
between
all
of
those
we
kind
of
have
to
find
mostly
what
everybody
does
here.
So
it
seems
like
our
Charter
is
largely
redundant
at
this
point
because
you
acts,
we
do
everything.
That's
in
the
Charter.
My
favorite
thing
to
find
in
the
Charter
was
apparently
the
steering
committee
was
supposed
to
sign
off
on
every
single
kubernetes
release
to
bless
it
so
basically
I
think
we're
going
to
turn
our
Charter
into
do
nothing
because
we
we
think
you
know
our
whole
goal
is
to
empower
you
to
do
things.
D
We
think
we
have
mostly
done
that
he
wants.
You
identify
the
remainder
of
things
that
still
seem
to
require
us
for
decisions
and
find
a
way
to
give
them
off
to
you.
We
also
found
that
fully
formed
proposals
given
to
us
we're
the
best
way
to
actually
have
things
get
done
and
we'd
like
to
formalize
that
or
make
more
of
that
happen
this
time
around
and
I
think
that's
it
right.
G
What
do
we
want
to
happen,
and
how
do
we
enable
that?
So,
when
we
have
were
having
the
election,
we
also
wanted
to
ensure
that
there
was
some
continuity
of
people
who
had
been
involved
with
the
project
for
a
long
time
and
whoever
might
happen
to
get
elected.
We
wanted
to
mentor
the
next
generation
of
leadership
and
enable
more
people
to
to
step
up
and
help
organize
the
project
as
a
whole.
G
So
we
had
the
bootstrap
members
stay
on
as
what
we
called
continuity
members
and
had
a
phase
process
for
having
them
rotate
out
potentially
and
having
new
folks
rotated
in
so
we
got
a
whole
new
set
of
people
in
addition
to
the
community
members
serving
on
the
steering
committee
after
the
elections
that
we've
had
so
far
in
the
fall.
When
we
have
another
election,
all
the
community
members
will
be
up
for
reelection
in
the
set
of
seats
available
will
reduce
down
from
where
we're
at
now
is
12
to
7.
G
G
So
you
know,
as
with
all
young
democracies,
you
know
we're
very
concerned
about
the
two
paths
to
elections
have
gone
off
very
very
smoothly.
So
thanks
everybody
for
taking
it
seriously,
and
we
hope
that
what
you
see
coming
from
the
steering
committee
and
we
try
to
address
issues
that
are
causing
recurring
pain
and
confusion
in
the
project,
and
we
hope
that
we're
doing
that.
But
we
really
rely
on
you
to
make
us
aware
of
those
issues.
So
we're
gonna
help.
You
sort
them
out.
J
K
P
Yes,
I
will
speak
up
a
bit.
Thank
you,
George
hi,
I'm
Zak,
so
I'm
I'm,
a
cluster
operator
we're
in
a
industry
that
has
lots
of
security
regulations.
So
last
week
scared
the
bejeebers
out
of
our
CIO,
who
was
white
knuckling
his
desk
as
we
were
updating
nodes
during
the
day
when
traffic
was
important,
so
I
was
curious
to
find
out,
obviously
I.
Imagine
I,
wasn't
the
only
scared
one
in
the
room,
and
you
guys
are
thinking
about
this.
K
So
let
me
walk
through
what
we
currently
do
and
I
love
to
have
feedback,
so
in
the
steering
committee
we've
done.
A
couple
of
things
first
is
that
we
have
a
security
audit
that
we're
starting
to
kick
off.
There's
a
team:
that's
going
to
be
working
with
the
vendor
to
do
a
third-party
security
audit.
The
next
piece
is
a
bounty
system,
getting
a
bug,
bounty
in
place
and
and
doing
that
and
then
the
normal
process
that
we
have
for
disclosures
over
the
last
year,
Jess
CJ
Tim
I'm,
going
to
forget
somebody
Jordan
like
it.
K
N
K
And
Jonathan
we
have
a
team
that
listens
on
security
at
kubernetes
on
I/o,
with
a
rotation.
It's
like
the
world's
worst
rotation,
because
if
you
get
a
ticket
it
might
like
somebody
files,
a
disclosure
you
might
have
to
handle
that
for
like
two
months
and
so
being
on-call
is
quite
a
roulette,
but
we
handle
those
tickets
and
there's
a
documented
process
of
how
that
actually
works
and
how
we
get
vendors
on
a
pre
disclosure
mailing
list
and
how
those
pre
disclosures
translate
into
setting
timelines
and
etc.
K
G
K
F
A
I
heard
the
push
back
over
there,
no
I'm
just
gonna,
say
I,
do
think
the
fact
that
we
are
sort
of
hiring
out
the
security
audit
and
stuff
like
that
points
to
like
we
probably
need
maybe
more
of
a
working
group.
There
I
mean
there
is
the
sort
of
there's
the
response
part
and
then
there's
the
proactive.
What
do
we
need
to
do
fix
part
I?
Think
we've
been
doing
a
good
job
on
the
response.
M
A
L
A
It
yourself,
no
I
mean
like
the
easiest
fix
or
the
thing
that
mitigated
this
thing.
The
most
was
a
flag
that
you
could
have
already
had
on
on
your
cluster
right
and
so
I
think
it
does
speak
to
the
fact
that
being
aware
of,
what's
going
on,
is
also
probably
something
that
an
operator
if
you're
running
your
own
cluster
needs
to
be
thinking
about
it's
on
us,
too
I
mean
the
fact
that
it
was
default.
Unauthenticated,
for
certain
paths
is
probably
a
bad
thing
to.
P
Gonna,
follow,
along
with
I,
remember
having
a
discussion
at
coop
con,
Copenhagen
and
kind
of
getting
the
answer
of
well.
This
is
sig
offs
domain
and,
and
so
the
security
is
delegated
to
them,
but
kind
of
thinking
about
that.
Like
most
of
the
CBE's
we've
seen
generally
weren't.
Well,
I
guess
this
one
was
authentication
related,
but
we're
off
indication
or
authorization
or
admission
control.
It
was
more
like
I
was
path,
mapping,
vulnerability!
It's
like!
Well,
that's
a
node
problem.
P
That's
not
really
a
an
authorization
issue,
so
you
know
you
started
to
mention
I'm
sorry,
I
didn't
notice
who
there
was
so
many
people
that
responded
but
like
as
far
as
security
is
concerned,
could
there
be
a
more
cross
effort
that
happens
as
like
a
general?
We
want
to
advance
the
secure
defaults
of
kubernetes
I,
don't
know.
L
We've
been
doing
that
for
quite
some
time
now,
so
switching
off
the
boats.
You
know
that
aren't
indicated
that
kind
of
stuff
Jordan.
Where
are
you
but
yeah
we've
been
doing
those
kinds
of
things
even
incubating
defaults
and
things
like
that.
We've
been
deperate
deprecating,
the
ports
that
are
not
needed,
and
things
like
that
so
yeah
there
is
an
effort,
but,
as
usual,
we
would
like
more
of
you
to
show
up
for
this
kind
of
work,
not
just
you
Zach,
but
other
people
in
this
room.
So.
L
D
Got
yeah
so
yeah
I
think
if
you
are
proposing
the
formation
of
a
working
group
to
go
across
things.
That
would
be
a
great
thing
to
to
submit
so
the
reason
I
say
it
would
be.
A
great
thing
is
because
it's
the
type
of
work
that
spans
multiple
SIG's
and
it
also
has
a
defined
end
goal,
after
which
point
the
working
group
would
disband,
which
is
the
definition
of
a
working
group,
because
we
defined
it
that
way.
D
I
hope,
yeah,
so
I
kind
of
wanted
to
pull
valve
that
up
or
trampling
that
up
into
a
question.
I
got
on
the
way
in
here
where
I
was
in
the
the
LTS
discussion
and
I,
don't
know
how
many
of
you
are
aware
of
the
number
of
releases
of
kubernetes.
We
have
cut
with
all
of
the
tests
passing
it's
zero.
It
is
a
big
fat,
zero.
Okay,
so
the
question
was:
is
it
the
steering
committees
responsibility
to
throw
the
hammer
down?
D
The
answer
was
also
no
I
think
it's
everybody's
responsibility
in
this
room,
but
okay,
if
it's
everybody's
problem,
that
it's
nobody's
problem
I,
think
it
really
comes
down
to
sig
release
and
the
release
team,
but
I
do
think
it
requires
a
coordinated
effort
and
involvement
from
everybody
in
this
room.
We
can't
fix
your
tests,
for
you.
Y'all
are
the
ones
who
wrote
the
tests.
We
can
definitely
make
it
easier
to
identify
which
tests
are
breaking
and
find
better
ways
to
identify
like
why
either
breaking.
D
But
ultimately
we
need
the
community
to
help
us
with
this
problem
and
I.
Think
one
of
those
tests
could
be
security,
related
tests
or
penetration
related
tests.
I
really
think
that
it's
time
for
us
to
start
documenting
documenting
what
it
means
for
release
to
go
out
the
door
and
start
using
more
checklists
instead
of
like
humans.
D
That
kind
of
interpret
things
and
mostly
get
it
all
right,
like
what
the
release
team
has
shown
to
me
over
the
past
couple
of
years,
is
that
it's,
it's
literally
impossible
for
a
person
to
both
have
the
technical
depth
to
dive
into
each
and
every
feature.
That's
landing
in
kubernetes
and
also
have
the
organizational
skills
to
coordinate
like
20
different
people,
it's
impossible.
D
We
really
need
you
to
help
out
with
the
technical
due
diligence,
but
I've
heard
that,
like
doctors
and
hospitals,
kind
of
get
around
this
by
having
nurses
that
use
checklists
to
make
sure
that
steps
are
not
missed,
even
if
there
are
really
obvious
steps
that
we
all
kind
of
know,
sometimes
we're
a
little
overloaded
and
it's
much
easier
to
use
checklists,
so
I
feel
like
it's
is
a
sig
release,
person
or
sorry
release
lead,
don't
necessarily
like
sig
architecture
kind
of
owns.
The
definition
of
what
a
stable
feature
is.
D
What
HEA
feature
is
what
a
beta
feature
is
I
think
there
should
be
some
level
of
testing
around
that
and
I
think
there
should
be
some
due
diligence
put
into
the
upgrade
and
downgrade
pads
for
those
features.
I
think
that's
a
cluster,
lifecycles
expertise,
I
think
there's
some
checklist
around
the
security
features
of
that,
and
maybe
that's
it
off
there.
Maybe
that's
a
working
group
but
I'm
trying
to
lay
out
the
plan
for
how,
like
it
is
kind
of
everybody's.
Q
Q
Is
it
the
steering
committees
responsibility
to
ensure
that,
if
that's
the
job
that
that
job
is
being
done,
in
other
words,
actually
making
the
call
about
our
release?
I
think
you've
been
very
clear
on?
Is
that
the
steering
committees
are.
You
know,
part
of
the
steering
committee
charter,
that
if
the
release
team
has
set
up
a
certain
set
of
criteria
under
which
they're
going
to
evaluate
whether
our
release
goes
passes
or
not,
if
they're
not
doing
that,
so.
A
So
so
I
think
I'll
try
to
take
a
sorry
out
loud.
Take
a
stab
at
answering
that
I
do
not
actually
think
that
it's
the
steering
committees
job
to
evaluate
whether
or
not
SIG's
are
doing
a
good
job.
I
think
we
can
adjudicate
it,
but
I'm,
not
sure
that
we
should
have
be
in
the
process
of
sort
of
steady
state
evaluating
it
right.
So
the
hope
is
that
some
other
sig
or
some
other
community
member
raises
up
a
question
and
says
they
are
not
doing
a
good
job.
A
We
actually
had
a
very
interesting
discussion
on
precisely
this
topic
like
a
week
ago
and
we
didn't
come
to
resolution
unfortunately,
but
we'll
get
there,
but
so
that's
like
I
think.
If
the
load
of
doing
steady
state
eval
of
every
single
sig
is
not
sustainable
on
the
part
of
the
steering
committee,
there's
33
of
them
as
and
although
we
all
agree
that
Aaron's
beard
is
above
reproach,
so.
Q
Yeah
follow-up,
so
I
think
doing
a
good
job
was
a
very
poor
way
for
me
to
ask
the
question:
what
I
was
really
trying
to
ask
was:
are
the
SIG's
doing
what
they're
saying
they're
doing
I
wasn't
attempting
to
even
discuss
the
qualification
as
to
whether
they've
set
up
the
job
right,
but
what
should
be
the
response
effects?
That's.
H
A
really
hard
question
to
answer
the
problem
with
a
lot
of
SIG's
is
their
volunteer
armies
right
and
they
come
and
go
people
come
into
SIG's,
they
come
out.
They
go
out
of
SIG's
and
sometimes
leadership
even
rotates
too,
as
well
so
they're,
given
a
certain
sense
of
responsibilities,
but
that
don't
miss
that
doesn't
mean
that
they
adhere
to
them
at
all
times.
Right,
I!
F
Wanted
to
add
one
point
like
I
think:
the
failure
mode
that
we
were
very
concerned
with
originally
was
a
group
of
senior
engineers
who
are
very,
very
motivated
to
make
this
the
best
project
possible
dictating
from
on
high
what
the
project
is
and
so
that
failure
mode
is
one
that
concerns
us,
and
so
a
lot
of
the
delegation
aspect
is
we
want
those
people.
If
it's
those
people
who
are
opinionated,
they
should
be
in
a
cig.
They
should
be
delegated
that
responsibility
and
the
sig
has
to
reach
that
agreement.
F
We
do
need
some
sense
of
accountability
but
I.
If
this
group
is
doing
it,
then
that
we
are
also
politicizing
that
aspect
and
so
there's
you
know
this
has
been
discussed
in
some
detail,
but
we
are,
as
concerned
about
this
group,
making
decisions
for
the
community
as
we
are
about
ensuring
the
community
community
functions.
G
Yeah
just
also
say
I
think
it
is
this
during
committees,
job
to
help
make
sure
the
project
functions
as
a
whole.
So
if
the
organization
of
the
project
isn't
working
in
some
fashion
to
help
address
that
we're
trying
to
do
that
with
the
clarification
of
the
responsibilities
of
SIG's,
with
creation
of
all
the
sig
charters
and
the
secret
from
the
sig
charter,
template
and
clarification
of
what
work
crew
be
working
groups
are
for,
and
the
formation
of
committees
like
the
security
team
or
code
of
conduct
committee.
I
Yeah
and
just
added
I
think
maybe
one
question
to
ask
is
like
is
the
sake
empowered
to
do
this,
or
is
there
a
group
of
individuals
and
power
to
do
this
and
then
what
do
they
need
in
order
to
be
able
to
do
it
like
we?
It
would
make
more
sense
for
one
of
us
to
join
the
sig
probably
and
do
it
in
the
context
as
a
member
or
leader
within
that
sig,
that's
empowered
to
do
it,
then
the
steering
committee
to
like
take
it
on
and
then
be
responsible
for
it.
L
Specifically
with
the
release
team,
one
other
thing
that
I
worry
about
is
the
amount
of
churn
every
cycle.
We
have
brand-new
fresh,
but
we
do
have
rules
where
people
are
shadowing
others
before
so
that
kind
of
helps.
But
then
we
need
people
who
are
there
across
multiple
releases
and
who
help
with
you
know
doing
the
patch
management
work,
and
then
things
like
that,
so
we
do
need
help
there.
L
D
We're
all
just
gonna
keep
like
being
super
philosophical.
If
you
don't
have
any
questions,
but
I,
just
I
have
one
I
feel
like
that
ties
into
another
theme
is
yes,
we're
terrible
at
project
management
like
software
developers
are
not
really
great
at
that
I
feel
like.
We
all
can
probably
point
to
areas
where
the
organization
of
this
project
is
a
mess
and
really
noisy.
D
I
want
to
tell
you
about
Matt
Farina,
Matt
Farina
showed
up
to
sing
architecture
and
basically
did
about
standup
Matt
Matt
showed
up
to
sing
architecture
and
did
more
or
less
an
hour
or
twos
worth
of
work,
maybe
per
week,
maybe
not
even
per
week,
to
sort
of
help
actually
organize
what
the
SIG's
workload
was
and
what
it
is
we
actually
work
on
and
why
we're
working
on
those
things
and
how
best
for
us
to
talk
to
each
other.
You
may
have
seen
his
update
at
the
kubernetes
community
meeting
explaining
city
architecture.
D
This
was
all
non-technical
stuff.
We
really
just
needed
somebody
to
come
in
and
treat
the
children
like.
Could
we
please
talk
to
each
other
and
stuff
I'm,
pretty
sure
there
are
lots
of
you
out
there
who
could
do
this
for
us
he'll?
The
steering
committee
even
needs
it
like.
We
got
Jays
to
help
create
his
board
for
us,
because
we're
terrible
at
putting
together
a
backlog
like
I
feel
like
almost
every
city,
could
benefit
from
a
lot
more
just
like
project
management
type
of
stuff
for
getting
people
to
talk
to
each
other
or
organizing
stuff.
D
B
There's
a
whole
lot
of
show
up
and
do
things
and
then
you
get
put
in
charge.
So
that's
a
double
edged
sword
I,
keep
getting
high
signs
that
were
running
out
of
time
and
in
four
minutes,
okay,
but
there
are
a
couple
of
points
that
we
need
to
make.
One
of
which
is
this:
is
your
community?
You
are
empowered
to
talk
to
other
people
and
say:
hey
can
I
help
you
hey
this
isn't
going
as
well
as
it
could
hey.
B
Please
put
more
effort
in
this
way
or
tell
me
how
you
we
can
find
other
people
to
help
you
so
this
is.
This
is
very
much
about
distributing
decision,
making
Authority
distributing
workloads
and
making
sure
that
we
build
a
distributed
computing
because
Conway's
law
says
we
will
ship
the
organization
we
have.
So
if
there
are,
you
know,
13
of
us
at
the
top
making
decisions
we're
going
to
make
a
really
weird
monolith
as
you've
seen
by
the
this
group
sort
of
our
stage
act
up
here,
so
mutter,
mutter,
mutter,
okay,
anyway.
B
So
that's
one
point
second
point
that
I
need
to
make
is
right
stage
act.
Second
point
I
need
to
make
is
in
fact
that
you
are
the
people
who
choose
this
group,
this
leadership
and
how
this
project
gets
gets,
managed,
gets
led,
so
stand
up.
Do
some
work
make
sure
you
vote
in
the
election
this
this
fall.
This
fall.
This
fall
next,
okay,
good
I'm
like
wait
a
minute,
but
it
yeah
yeah.
Fifty
percent
of
you,
while
compared
to
u.s.
B
politics,
may
be
higher
than
average,
but
for
this
group,
given
that
you
are
choosing
the
leadership
for
for
this
project,
and
this
you
know
we
can
make
decisions
that
affect
you.
We
don't
want
to
and
we
don't
want
to
be
forced
to.
We
want
you
all
to
be
self
guiding
and
leading
and
then
escalate
things
to
us
as
you
need.
But
you
are
the
group
that
that
picked
this
leadership
group,
and
particularly
since
we
will
be
dropping
down
to
seven
people
this
next
fall.
B
One
of
the
other
reasons
that
we
didn't
mention
about
the
steering
committee
being
13
members
for
the
first
year
and
now
12
since
Tim
Hawken
has
decided
he
has
too
many
things
to
do
is
that
we
knew
this
was
going
to
be
a
big
glut
of
work
as
we
set
up
this.
This
governance,
so
I
wanted
to
make
sure
that
we
addressed
that
part
and
we've
gotten
a
lot
of
it
done,
and
the
workload
should
be
different
and
evolving.
As
the
the
next
committee
comes
on,
so
vote
make
sure
people
are
the
right.
B
Q
A
B
B
A
B
S
S
We
want
to
go
to
the
contributor
summit,
I'm
sorry
hold
on
all
right,
yeah,
no
I'm
and
Bob,
and
so
many
other
people
who
are
true
volunteers,
Bob
does
not
get
paid
for
this
have
really
helped
us
out
with
the
small
implementation
details
of
running
a
large-scale
event.
You
all
do
not
know
all
the
little
teeny
details
that
go
into
stuff
like
this.
So
thank
you
so
much
to
all
of
our
volunteers.
You
all
are
awesome.
One
more
round
of
applause.
S
S
So
the
CNC
F
does
these
words
right.
Everybody
knows
the
awards
that
are
happening,
but
we
thought
we
being
contributor.
Experience
thought
that
you're
this
community
is
equally
as
deserving
of
awards.
Unfortunately,
there's
so
many
of
you
to
award
on
an
individual
basis.
We
thought
about
awarding
a
group
this
time
contributor
experience.
If
you
will
is
sort
of
a
leg
of
operations
to
the
steering
committee.
We
deal
with
all
contributor
experience,
issues
with
chairs,
how
to
run
their
SIG's
etc.
So.
S
So
we
thought
that
this
time
we
would
honor
a
sig
who
is
really
doing
their
part,
one
that
we
never
have
to
talk
to
one
that
is
always
uploading
their
videos
to
YouTube.
Why?
Because
they're
transparent
one
that
manages
so
many
different
agendas
with
vendors
in
their
group
and
they
do
it
so
well,
their
project
management
skills
are
so
par.
They
have
like
their
own
contributing
guide.
That
sig
is
six
storage,
Saud
and
Bradley.
Are
you
in
the
room.
S
This
is
the
kubernetes
kubernetes
code.
In
a
you
know,
you
can't
see
it's
all.
You
can
see
the
logo,
but
it's
actually
the
code
for
kubernetes
kubernetes
side.
You
all
are
so
awesome,
I'm
gonna.
Actually
it's
like
the
Grammys
I'm
gonna
customize
this
for
you.
So
yes,
you
actually
can't
take
that
home
just
yet.
Alright!
Nobody,
your
whole
cig,
is
so
awesome.
We
never
have
to
talk
to
you
and
I.
Think
you're,
wonderful,
so
yeah.
S
Yeah
this
we
work
with
so
many
wonderful
people
and
it's
so
hard
to
do,
rewards
and
recognition,
but
that's
something
that
our
sig
is
willing
to
not
willing,
but
we
are
going
to
break
ground
on
next
year,
which
is
coming
up
with
more
reward
and
recognition
systems.
I
mean
special,
shout
outs
to
just
a
couple:
people
like
Jordan
Jordan
is
awesome
at
triage.
S
I,
don't
know
if
if
many
folks
in
here
actually
go
into
the
kubernetes
users
group
on
slack
with
53,000
people,
but
Jordan
is
in
there
and
I
have
the
data
to
prove
it
now.
Jordan
is
consistently
in
the
top
three
for
most
messages
on
slack
and
he
consistently
updates
like
C
CVEs
that
are
closed
with
updates,
and
it's
really
wonderful
is
Jordan.
Here
no
I
joined
his
probably
doing
work
so.
O
O
O
So
all
these
people
do
a
great
job
and
what
something
we
really
wanted
to
do
was
give
the
release
team
a
method
of
rewarding
people
who
not
just
do
great
work
on
a
signal
really
single
release,
but
have
been
a
consistent
access
shown
consistent
excellence
throughout
2018.
We've
released
four
releases
this
year,
so
real,
quick,
introduce
yourselves
and
I,
don't
know,
say
something
about
yourself.
B
R
J
R
This
is
the
progression
11
12
13
Josh
a
year
ago
was
poking
me
saying
you
should
get
involved
in
the
release
team
q
Khan.
Last
year
we
left
the
conference
with
people
saying
well,
I.
Think
you're
gonna
have
to
lead
the
next
release,
basically
getting
voluntold
to
do
it,
and
similarly,
with
eyes
like
we,
this
is
a
chain
of
mentoring.
R
For
people
who
don't
know
Jase,
you
may
see
him
right
now
like
helping
with
architecture
or
steering
or
organizational
things
prior
to
that.
He
spent
a
lot
of
time
multiple
releases
on
the
release
team.
Similarly,
organizing
I'd
say
he
had
a
hand
and
bringing
each
of
us
in
the
process
as
well,
so
again
just
actively
mentoring,
bringing
in
the
next
generation
great
robot,
oh
yeah,.
T
O
R
We
went
back
and
forth
on
a
bunch
of
people
who
have
contributed
and
for
people
who
don't
know
the
release
team.
You
know
we
have
a
set
of
volunteers,
we
have
a
set
of
volunteer
shadows
and
then
there's
consistently
three
or
four
people,
and
it
varies
from
release
to
release
across
the
year.
There's
people
who
just
step
up
and
are
an
informal
part
of
the
team.
So
this
is
one
of
those
people
they've
again,
just
so
extremely
active
that
you,
you
don't
even
understand
how
they
have
time
to
do
all
of
this.
U
The
and,
and
particularly
we
selected
the
individual,
because
one
of
the
things
that
happens
with
every
release
during
code
freeze
encoding
to
the
releases
we
get
into
crunch
time,
where
there's
things
that
are
failing,
there's
things
that
are
not
passing
tests,
we're
looking
at
holding
up
the
release-
and
you
know
whoever
would
normally
be
responsible
for
the
technical
areas
for
somebody's
not
available.
And
this
individual
has
been
one
of
the
people
to
step
up
and
try
to
solve
those
bugs.
So
we
can
so
that
their
release
out
in
time
which,
which
we
have
done.
T
Again,
I
go
back
to
the
community.
We
lean
in
on
a
lot
of
individuals
to
get
this
get
the
release
out,
and
this
person
anecdotally,
I,
could
just
just
bring
on
slack
and
say:
can
I
have
a
call
with
you
right
now,
I
need
to
like
just
because
something
and
the
person
was
right
there
to
discuss
it
and
resolve
it,
and
that's
how
accessible
and
yet
highly
technical
and
the
person
is
to
help
us
unlock
the
release
like
to
you,
announcer.
O
O
Of
the
thing
okay,
yeah
just
come
up,
yeah
I
didn't
even
know
he
existed.
I
thought
he
was
like
four
people
in,
like
a
fictional
character
that
they
created
all
right,
so
we're
gonna
do
is
we're
gonna
at
five
o'clock.
We're
gonna
try
to
take
a
group
photo
by
where
we
have
breakfast
real,
quick
on
the
way
out.
The
people
who've
helped
this
event
Megan
at
CN
CF,
along
with
Caitlin
Bob
Jeff,
no
Abrams,
Chris
short
Jason,
Mario
Lauria.
O
Where
are
you
stand
up,
raise
your
hands,
come
on
all
of
the
room,
monitors
that
I
miss
anybody's,
odd
EV,
anybody
else
who
helped
out
with
planning
that
I'm
missing
Paris
great
sweater
ask
her
about
it,
who
else
Lindsey?
Thank
you.
I
miss
anybody
when
I
was
a
new
contributor,
so
yeah
what's
up
okay,
so
new
contributors
really
quick
stand
up.
This
will
be
your
graduation
ceremony.