►
From YouTube: KBE Insider: Elana Hashman
Description
We feature Kubernetes thought leaders and talk about different topics to get you thinking inside and outside of the box.
Learn more at https://www.kubernetesbyexample.com/community/kbe-insider
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
healing
from
welcome
to
the
latest,
cube
by
example
show
I
am
chris
short
joined
by
the
one
and
only
mina
camera.
I
can't
say
your
name
I'll,
just
hi
mina.
Sorry,
it's
been
a
long
past
three
days.
For
me,
I've
gone
without
power,
cell
service
or
internet
for
some
almost
two
days
and
getting
back
into
the
groove
of
things
when
going
from
like
glamping
to
interneting,
is
really
really
like
different.
B
B
So
and
I'm
langman
white
so
also
the
host
of
another
show
called
the
level
of
power,
and
this
is
a
show
that
we
do
to
try
to
give
you
some.
So
we
recently
launched
this
cube
by
example
website
to
try
to
connect
people
into
you,
know,
understanding
kubernetes,
and
so
you
know,
hopefully
from
a
pretty
introductory
perspective,
but
really
to
try
to
take
you
through
quite
a
long
way
and
there's
and
and
what
we're
trying
to
do
with
the
site
is
actually
support.
B
Multiple
learning,
styles
right,
so
there's
written
stuff,
there's
video
stuff,
there's
and
then
we
also
are
trying
to
give
you.
What
I
think
is
one
of
the
things
really
important
about
a
software
project
which
is
to
understand
where
it's
going
or
like
what
its
ethos
is,
and
the
reason
is
is
because
it's
it's
much
easier
to
make
a
decision
about
like.
Should
you
commit
to
this
thing?
If
you
can
say
oh,
this
seems
like
it's
a
line
to
where
I
want
to
be
and
where
the
project
wants
to
be
in
five
years
right.
B
B
Okay,
if
I
take
you
know,
if
I
take
this
person's
vision
and
that
person's
vision
and
that
person's
vision,
I
can
come
to
an
amalgam
of
where
I'm
I
can
align
my
work
or
my
projects
or
or
my
it
department
or
whatever,
with
where
I
understand
kubernetes,
to
be
going
because
the
people
who
really
know
where
kubernetes
is
going.
If
people
who
are
typing
in
the
code,
not
the
analysts,
you
know
not
the
pundits
and
all
that
stuff
so
that
that's
what
we're
trying
to
do
with
the
show,
and
today.
B
We
invite
alana
hushman
and
we
will
ask
her
to
introduce
herself
in
a
few
minutes,
but
before
we
do
that
we
have
a
little
news
segment
where
mina
gives
us
an
update
first
on
how
to
pronounce
her
last
name,
but
then
also
how
what's
going
on
in
the
cube
community.
Since
our
last
episode
in
our
last
episode,
we
run
the
show
the
last
tuesday
of
every
month,
so
we've
done
one
real
episode
so
far.
B
We
also
did
a
behind
the
scenes
episode
where
we
kind
of
get
into
more
detail
of
what
I
just
explained.
So
we'd
love
you
to
watch
those
two
and
obviously
come
back
next,
tuesday
or
sorry
a
month.
You
know
on
the
last
tuesday
of
the
month,
and
you
know
and
as
we
don't
say,
often
enough
click
like
and
subscribe,
that's
how
we
can
show
that
we're
performing
exactly.
Thank
you
a
lot.
B
D
A
B
D
D
So
what
this
means
there
was
a
survey
of
a
thousand
cloud
developers
and
it
found
that
this
deep
learning
curve
and
about
57
of
those
thousand
cloud
developers
said
this
new
terminology,
as
well
as
new
concepts
and
commands
are
the
most
significant,
significant
challenges
they
faced.
What's
more,
many
were
frustrated
by
how
long
it
takes
to
spin
up
a
working
kubernetes
cluster.
So
this
is
a
pretty
pretty
important.
Finding
a
thousand
people
definitely
go
check
this
article
out.
D
If
you
are
interested
in
hearing
more
about
it,
we
also
highlighted
the
top
10
hottest
kubernetes
startups
of
2021
in
2021.
I'm
not
gonna
list
all
of
those
right
now,
but
I
will
put
all
of
the
links
to
these
articles
in
the
chat
after
I'm
done
so
definitely
go
check
them
out.
We
also
talked
about
how
kubernetes
and
containers
are
powering.
Tomorrow's
applications-
digital
businesses
today,
are
leveraging
cloud-native
technologies
to
power
their
applications,
their
application,
stacks
and
kubernetes
and
containers
are
essential
in
enabling
them
to
achieve
this.
D
The
author
highlights
a
couple
points
in
this
article
importance
of
data
centricity
when
it
comes
to
businesses
staying
ahead.
Today,
container
adoption
speaks
for
itself.
According
to
a
451
research,
95
percent
of
new
apps
are
developed
in
containers
today.
Micro
services
and
containers
are
a
perfect
match,
as
containers
are
the
perfect
building
block
for
micro
services.
They
present
a
lightweight
and
consistent
environment
for
microservices
that
can
follow
the
application
from
the
developer's
desktop
to
testing
to
final
deployment.
D
Packaging
applications
with
their
dependencies
are
the
trend.
Today.
That's
what
people
are
doing
and
not
all
container
services
are
equal.
Kubernetes
is
a
black
hole
of
unpredictable
spent.
According
to
a
new
cncf
report
in
association
with
the
fin
ops
foundation
shows
that
costs
of
kubernetes
are
rising
and
companies
struggle
to
predict
them
accurately.
D
D
And
then
we
looked
at
the
future
of
cloud
computing
and
what
trends
will
impact
your
organization?
One
manage
kubernetes
in
the
cloud
will
be
a
really
really
big
focus.
Two.
The
idea
of
multi-cloud
will
become
a
lot
clearer.
Three
server,
serverless
computing
will
quicken
and
simplify
cloud
operations.
D
Four
managed
open
source
services
are
going
to
be
in
the
forefront
of
things.
Five
service
mesh
networking
will
become
the
norm.
Six
automation
and
policies
will
ease
cloud
management
and
seven
better
integration
between
cloud
and
data.
Centers
is
something
that
we're
going
to
see.
We've
also
seen
some
kubernetes
security
issues
through
different
articles.
Nearly
all
survey
respondents
in
a
recent
state
of
kubernetes
security
report
cited
at
least
one
incident
stemming
from
kubernetes
security
issues.
D
Again
I
will
drop
the
links
in
to
these
articles,
but
we
also
have
seen
some
kubernetes
clusters
attacked
via
misconfigured
argo,
workflow
instances.
Security
researchers
are
warning.
Argo
workflows
is
an
open
source
container
native
workflow
engine
for
orchestrating
parallel
jobs,
on
kubernetes,
to
speed
up,
processing,
time
for
compute
intensive
jobs
like
machine
learning
and
big
data
processing.
So
these
are
pretty
important.
I
definitely
encourage
you
guys
to
check
these
out.
There
was
a
lot
of
noise
going
around
this
on
threat,
post
and
and
social
media
as
well.
D
Another
announcement
coming
from
kubernetes
is
as
the
kubernetes
api
evolves.
Apis
are
periodically
reorganized
or
upgraded
when
apis
evolve,
the
old
api,
the
old
apis
they
replace,
are
deprecated
and
eventually
removed.
Kubernetes
1.22,
due
for
release
in
august
2021,
will
remove
a
number
of
those
deprecated
apis.
These
are
beta
apis
that
you
can
use
in
current
supported
kubernetes
versions
and
they're
already
deprecated.
D
B
Which
I
I
thought
was
impressive
way
back
in
the
day
openshift.com
when
it
was
openshift
ii.
One
of
the
biggest
challenges
is
basically
it
offered.
You
know
kind
of
free.
You
know
things
like
containers,
but
they
used
to
be
called
gears
to.
You
know
the
general
public
and
basically,
they
had
to
have
a
constant
watching
for
bitcoin
and
mining.
A
B
That
was
a
big
chunk
of
the
effort
involved
so
again,
we'd
like
to
welcome
alana.
Thank
you
so
much
for
appearing
on
the
show,
thank
you
mina
and
if
you
could
give
us,
maybe
a
brief
introduction
to
yourself.
You
know
you.
We
know
you
work
for
red
hats.
That
means
we
have
no
idea
what
your
title
is
or
who
you
work
for,
because
it
changes
too
regularly
to
keep
track
of
you
know.
C
Yeah,
absolutely
elena
hashman.
I
currently
work
for
the
ocp
node
team.
As
a
principal
software
engineer,
and
previously
I
was
on
the
azure
red
hat
openshift
team
as
a
principal
sre
and
one
of
the
tech
leads,
so
that
was
only
recent
change.
I
only
moved
over
to
the
open
shift
engineering
side
of
the
house
in
january
of
this
year.
B
B
Yeah
right
right,
I
one
of
my
first
kind
of
job
offers
out
of
college
was
working
on
ibm's
level,
two
global
backbone
for
their
internet
and
yeah.
Two
weeks
out
of
the
month,
you
weren't
allowed
to
be
more
than
two
hours
away
from
from
the
office
wow
because
they
would
get
calls
like.
Oh
san
francisco
is
down.
Please
fix.
C
E
C
C
Cool
but
like
what
am
I
supposed
to
do
with
this,
but
you
know
like
it
being.
I
don't
know
like
probably
2006
or
something
like
that
I
was
I
was
installing.
I
think
it
was
ubuntu
hardy,
herron,
6.06
and
so
like.
I
was
like
okay
great,
like
I
think
the
sound
worked,
but
the
wi-fi
did
not,
and
so
I
got
to
fight
with
endis.
C
To
open
source
software
but
like
prior
to
that,
I
had
been
using
firefox,
which
I
thought
was
super
cool
and
I
was
mostly
just
kind
of
a
user
for
the
longest
time
and
then
in
university.
I
like
went
to
some
conference
and
there
was
like
an
open
source
themed
lunch
table,
so
I
sat
down
at
the
table
and
I'm
like
checking
my
email
or
something
like
that
and
the
guy.
Next
to
me,
he
like
looks
at
my
shoulder.
He
says
is
that
alpine
I
was
like
yeah
he's
like
hi.
C
And
so
there
was
an
open
source
day
at
the
conference
that
year
and
he's
like
you
should
come
and
contribute
to
this
cool
project
called
open
hatch.
I'm
like
well,
you
know,
like
I've,
been
using
open
source
for
so
long
but,
like
I
don't
really
know
like,
like
I
match
to
like
contribute
to
wordpress
or
something,
but
I
don't
like
no
php
he's
like
no
come
contribute
to
open
hatch,
and
so
I
did-
and
I
started
fighting
with
this
bug,
which
he's
like
oh
yeah,
a
pretty
easy
bug.
That's
why
I
started
digging.
B
C
Bug
you
know
you
can
fix
it
today.
No,
it
did
not
happen,
but
I
ended
up
learning
python
and
I
became
open,
hash's
gsoc
student,
so
I
completed
google
summer
of
code
and
like
fast
forward,
then
I
started
working
for
rackspace.
Then
I
got
more
involved
in.
Like
other
pythonic
things,
I
was
working
with
paul
carrer,
so
I
wasn't
like
directly
contributing
to
cryptography,
but
I
was
encouraged
to
do
things
that
might
help
cryptography
and
that
got
me
like
sucked
into
the
world
of
like
well.
C
Why
don't
you
try
out
this
many
linux
thing
and
like
help
us
build
wheels
better,
and
then
you
know
how
that
goes
like
you
stare
into
the
void
and
you
become
an
expert
on
the
void
and
suddenly
I'm
like
the
only
person
who
understands
how
this
symbol,
versioning
logic
goes
for
like
the
abi
compatibility
and
audit
wheel
and
yeah
well,
I
maintained
that
for
a
while,
I
still
participate
with
the
the
python
packaging
authority.
At
the
same
time,
we
used
a
lot
of
closure.
E
C
We
really
need
like
this
thing,
which
is
the
build
tool
for
closure
called
line
again,
like
someone
should
really
package
that
for
debbie,
and
I'm
like
that
sounds
like
a
terrible
idea
like
what
a
bunch
of
unfair
who
would
be
so
dumb
as
to
like
go
and
waste
all
this
time.
Working
on
that
yeah,
I
was
nerd
sniped
into
it.
So
I
guess
like.
However,
many
years
later
I
became
a
debian
developer,
I'm
now
serving
on
the
debian
technical
committee
and
yeah.
C
B
Right
right
see,
I
mean
that
that's
the
the
key
right
is,
you
know,
bring
him
in
young
right
and
you
know
get
him
get
him
into
the
mix.
And
then
you
know
you
can
you
can
finally
hand
some
things
off?
It's
the
dream
right
right.
You
know.
I
still
maintain,
though,
because
of
your
maintenance
of
closure,
that
you
are
a
closet,
lisp
lover
and
therefore.
B
I
I
yeah
it
was
very
funny.
I
I
totally
agree
with
you.
Actually
I
would
say
scheme
is,
is
more
like
that
than
lisp,
but
you
know,
but
they
do
have
a
whole
book
called
the
little
schemer,
which
is
amazing
all
right,
so
bringing
it
back
to
the
focus
of
the
actual
show
all
right.
So,
okay,
you
know
we
see
how
you
kind
of
got
into
open
source
right
more
than
just
software
per
se.
So
what
brought
you
to
kind
of
kubernetes?
So
you
know
where,
where
did
that.
C
C
C
C
E
C
C
C
B
C
I
landed
at
a
financial
company
where
they
were
like,
so
we've
got
like
these
gigantic
kubernetes
clusters,
which,
by
the
way,
we're
a
finance
company
so
for
us
they're
like
tiny,
but
we've
got
these
gigantic
on
purpose
kubernetes
clusters
and
I
was
working
with
like
you
know:
10
000,
core
clusters
and
those
were
toy
clusters
and
they're
like
we
need
somebody
to
like
help.
Our
ops
team
administer
these
things
because
we
have
a
bunch
of
software
engineers
if
you
don't
have
a
lot
of
operational
backgrounds.
So
I
was
like.
C
E
C
For
our
clusters-
and
you
know
like
there's
this
heapster
thing
but
like
we
really
need
better
implement
instrumentation,
so
I
was
like
okay
and
I
like
looked
at
various
solutions,
and
I
was
looking
at
various
fender
products,
and
I
was
like
these
all
just
kind
of
like
sit
on
top
of
like
the
open
source
stack
like
there's,
nothing,
there's
no
particular
secret
sauce
other
than
you
know
the
like
from
what
I
could
see
playing
around
with
these
trial
products.
At
that
time,
in
like
2018,
I
was
pretty
early.
C
C
I
spent
much
time
working
on
cube
state,
metrics
performance
testing,
cube
state
metrics
because
it
turns
out
our
clusters
were
big
and
I
ended
up
getting
involved
in
sig
instrumentation
as
a
result
and
for
the
longest
time
I
was
like
you
know,
kind
of
there
as
like
sort
of
an
oxy
focused
user.
I
wasn't
doing
very
much
in
terms
of
code,
but
I
did
submit
a
two-line
patch
that
like
broke
the
entire
world,
trying
to
like
best
yeah
trying
to.
E
A
C
Label
normalization
because
I'm
like
well,
I'm
doing
this
like
horrendous,
join
in
order
to
like
make
these
metrics
match
these
metrics
and
they
don't
conform
to
the
kubernetes
like
instrumentation
guidelines.
So
like
can
we
fix
these
they're?
Like
sure
they've
been
a
pull
request?
Well,
it
was
more
like
make
a
cap
and
then
submit
a
request.
A
C
B
That's
cool,
so,
let's
talk
about.
Let's
continue
talking,
maybe
about
instrumentation
right.
I
think
you
know
there's
a
lot
there
right.
I
mean
because
trying
to
understand
the
environment,
particularly
when
you
talk
about
anything,
that's
cloud
native
is
often
one
of
the
hardest
parts
right.
You
know
with
the
second.
He
introduce
these
microservice
things
right.
The
problem
is,
is
trying
to
understand,
what's
actually
happening
at
any
given
moment,
and
so
what
do
you
see
like
or
what?
B
D
C
Things
that
are
in
flight
right
now
that
I
am
very
excited
about
that,
I
think,
will
significantly
improve
instrumentation.
So
one
is
that
api
server
tracing
is
happening.
So
this
means,
if
like
a
given
request,
goes
into
the
api
server.
You
can
generate
a
span
which
shows
like
I
spent
time
here.
I
spent
time
here
I
spent
time
here.
Oh
look
this
one's
very
wide.
Maybe
we
should
see
why
we're
having
performance
issues
here
and
so
on
and
so
forth.
C
A
C
E
D
C
Flight
that,
I
think,
will
be
super
helpful
right
now.
You
know
kubernetes
generates
a
lot
of
logs
and
as
a
systems
administrator
like
it's
all,
syslog
and
syslog
is
kind
of
a
pain
to
deal
with,
and
it
makes
it
really
hard
because
you
have
to
do
like
post-processing
with
regexes
and,
like
all
sorts
of
other
stuff,
to
try.
E
C
C
C
So
like
it's
much
larger,
an
effort
versus
like
a
single
cap
and
yeah,
it's
it's
been
quite
a
wild
ride,
so
like
in
121,
I
spent
a
bunch
of
time
working
on
trying
to
migrate
the
cubelet
to
structured
logs
and
then
ensuring
that
we
had
like
automated
tooling
that
it
wouldn't
regress,
and
so
that's
been
awesome
like
cubelet.
It's
bond,
structured
logging,
but
structured
logging
is
an
effort
of
stolen
alpha
and
we
still
have
every
other
component
to
migrate.
C
C
B
I
yeah
totally
area
a
long
time
ago
now,
like
you
know,
2000
or
so
maybe
before
that
a
friend
of
mine
and
I
had
built
a
system
that
did
visual
basic
over
http
and
one
of
the
things
that
was
most
important
about.
It
was
actually
doing
a
visualized
logger
to
show
where
you
know
where
it's
stuck
right.
You
know,
because
it's
just
so
necessary
one
thing
I
did
want
to
quickly
cut
a
sidebar
here,
a
little
bit.
B
B
B
Right,
that's
a
that's
a
whole
another
discussion
anyway.
So
yeah,
if
you
do
want
to
know
more
about
cap
theory,
go
the
wikipedia
page
is
actually
remarkably
good.
I
would
definitely
go
search
that
all
right.
Well,
maybe
it'll
come
up
again
or
maybe
I
misheard
you.
So
why
don't
we
move
on
from
there
and
talk
about
a
little
bit?
B
So
you
know
we
talked
a
lot
about
instrumentation,
which
seems,
like
you
know,
you're,
very
passionate
about
and
now
you're
working
with
the
node
sig,
which,
if
you
could
tell
us
a
little
bit
about
what
you're
working
with
there
and
what
you
see
there
and
actually
explain
what
the
node
sig
is.
That
would
be
a
good
start
as
well.
B
A
C
Nice,
very
nice,
okay,
so
you
see
kubernetes.
This
is
the
kubernetes
cluster,
the
logo
right,
so
the
hub,
that's
the
api
server
and
then
all
of
these
other
things
are
controllers
talking
to
the
aps,
or
everything
goes
through
the
api
server.
So
a
node
is
a
special
controller,
and
why
do
we
need
a
node?
Because
we
want
to
run
workloads
so
the
the
node,
the
cubelet
is
the
thing
that
turns
something
into
a
kubernetes
node.
It
is
a
special
controller
and
all
controllers
and
kubernetes
they
tend
to
operate
on
a
certain
object.
C
In
this
case
the
the
cubelet
cares
about
pods.
So
the
cubelet
is
the
thing
that
natively
understands
pods
and
what
to
do
with
them
and
all
of
that
jazz.
So
sig
node
is
responsible
for
the
node
and
when
we
say
the
node,
we
mean
like
a
cubelet
really
and
other
things
that
interact
with
like
node
lifecycle.
So
sig
note
is
a
really
interesting
and
large
sig
to
be
in
because
you
know
the
most.
E
E
C
E
C
Many
pods
into
that
thing
as
you
want.
It
won't
do
anything
but,
like
that's,
that's
a
perfectly
legitimate
kubernetes
cluster
but,
like
notes
are
really
interesting.
Stuff
happens,
I
think,
and
so
that
was
kind
of
what
like
interested
me
in
signal
like
if
I
care
about
the
sort
of
like
kubernetes
as
like
nice
abstractions
to
like
parallelize
linux
on
a
distributed
scale.
C
C
I
am
working
on
many
things,
but
probably
like
my
top
three
things
are
so
I'll
start
with
the
least
exciting,
maybe
and
go
to
the
most
exciting
least,
exciting,
making
sure
it's
not
broken
so
like
working
on
the
flaking
tests
and
paying
down
tech,
debt
and
long-term
tax
strategy,
and
that
kind
of
thing
that
has
been
really
interesting.
Working
on
the
last
two
releases,
node
was
like
a
little
bit
stagnant
for
a
while,
and
so
like
one
of
the
things
that
I've
been
looking.
C
Debt,
how
do
we
make
node
go
faster?
How
do
we
ensure
that
like
features
are
happening
and
that
kind
of
thing-
and
so
like
one
of
the
most
important
things
you
can
get
from
that
is
like?
Are
our
tests
working?
Are
our
test
rates
running
the
way
that
we
expect
them
to
and
so
on
and
like?
Are
they
giving
us
good
signal?
Because
we
have
a
bunch
of
test
suites
right
now,
for
example,
that
are
failing.
C
C
A
C
B
Well,
another
thing:
that's
kind
of
related
to
another
question
we
like
to
ask
is
from
a
getting
involved
perspective.
I'm
sure
it's
doing
like
amazing
things,
for
your
understanding
of
the
code
base
that
you're
now
working
with
right.
You
know,
like
that's
one
of
the
greatest
things
about
kind
of
fixing
tests
when
you're
new
to
a
project
is
like
you,
you
really
have
good
tactical
things
to
kind
of
help.
You
learn
it,
which
is
hard
to
do
in
kind
of
the
abstract.
B
C
Possibly
the
most
horrible
thing
I
have
ever
submitted
to
cube
ci,
which
was
like
I
sent
in
a
work
in
progress
pr
with
like
at
the
beginning
of
the
cubelet.
I
modified
it
to
like
shell
out
to
df
and
dump
everything
and
because
the
cubelet
in
certain
test,
suites
it
like
constantly,
is
restarting
the
cubelet
because
of
the
dynamic
public
config
and
so
like
you'll,
see
the
cubelet
restarting
and
therefore
every
time
it
restarts
it'll
jump
like
df
again
and
so
yeah.
That
was.
C
D
C
D
C
E
C
A
C
Yeah
yeah
yeah,
and
so
like
one
of
the
first
things
that
I
did
is.
I
was
like
I
can't
grok
this,
I'm
gonna
like
make
a
little
board,
so
I
can
like
visualize
like
the
things
I
need
to
pester
people
to
approve
the
things
that
are
like
ready
for
me
to
put
an
lgtm
on
the
things.
I
should
not
look
at
and
like
the
things
that
somebody
needs
to
look
at,
and
so
I
put
together
this
new
triage
board
when
I
joined
the
sig
and
then
I
like
showed
it
to
some
people.
C
They're
like
this
is
super
useful.
Make
this
like
accessible
the
whole
thing,
but
I
did,
and
so
now
we've
been
using
that
for
node
triage
and
that
has
been
making
it
a
lot
easier
to
deal
with,
like
our
glut
of
prs
that
we
deal
with
on
a
given
basis.
We
previously
had
a
board
for
just
test
and
ci
things
only,
but
because
it
was
just
test
and
see,
I
think
only
it
meant
most
of
our
prs
weren't
actually
like
getting
looked
at
in
the
same
way.
C
C
Yeah,
like
I
feel,
really
bad,
because
I
want
to
be
able
to
look
at
every
single
incoming
bug.
I
don't
have
the
time,
especially
because
a
lot
of
them
are
somebody
asking
a
kubernetes
question
and
like
not
it's
not
a
real
bug
and
therefore
I
can't
really
like
spend
like
three
hours
of
support
every
day.
Looking
at
their
questions
and
trying
to
answer
like
there's
just
not
enough
hours
in
a
day,
I
wish.
B
C
D
C
E
E
B
A
C
B
Which
is
the
I
mean
to
be
frank
right
like
that's,
that
is
the
right
answer.
That's
how
you
build
a
community.
That's
how
you
you
know!
This
is
how
you,
you
know,
be
kind
of
a
good
person
in
software,
but
at
the
same
time,
to
your
point,
that's
a
reduction
in
the
amount
of
time
that
you
can
spend
on
on
other
things
right,
and
so
we
you
know,
we
always
need
help.
I
think
in
kind
of
doing
the
things
that
actually
require
human
components
more
than
they
require
technical
components.
You
know
it's
like.
B
If
you
have
a
little
bit
of
kubernetes
expertise,
go
try
to
find
the
places
where
you
can
say.
Oh,
I
know
I
recognize
that
this
isn't
actually
a
bug,
and
I
recognize
that
oh
I've
run
into
this
problem
before.
Let
me
go
help
that
person
so
that
somebody
who
is
working
in
engineering
or
qe
or
whatever
can
from.
E
A
E
E
C
Yeah,
like
it's,
it's
a
superpower
and
I'm
like
a
little
bit
weird
in
that
when
I
became
chair
of
sig
instrumentation
like
I
had
like
four
lines
of
changes
in
all
of
kubernetes
kubernetes.
Like
I,
I
was
an
ops
chair
for
a
sig.
That's
like
kind
of
owned
code,
instrumentation
kind
of
owns
code.
We
have
a
small
amount
of
code,
but
it's
horizontal
so
like
each
each
component
owns
their
own
metrics
and
whatnot.
We
don't
own
them.
We
just
try
to
help
them
out,
but
yeah.
It
was
like.
C
What
metrics
or
like
things
should
I
look
at
to
figure
out
that
it's
like
broken
and
so
that
team,
when
I
was
initially
envisioned,
was
very
small.
It
was
three
approvers
for
all
enhancement
proposals
and
we
get
something
like
60
each
cycle
workload.
So
I
I
volunteered
as
tribute
I
am
now
the
fourth
approver
on
this
team,
who
will
look
through
this
and
be
like?
Yes,
you
have
a
good
upgrade
or
downgrade
strategy
or
like
have.
E
C
Thought
about
this
as
it
applies
to
version
sku
or
like
yes,
this
is
not
eligible
or
no
no,
no,
this
is
applicable
and
you
don't
have
to
add
a
metric
just
like
we
need
a
metric
because,
like
I
don't
know
how
this
thing
is
working
like
what
should
I
look
at?
What
are
you
the
author,
looking
at
to
see
if
this
thing
is
working?
No,
oh,
I
hadn't
thought
about
that.
I
was.
B
E
B
C
E
C
C
C
B
One
of
the
things
it's
actually
kind
of
an
internal
red
hat
freeze,
that's
been
kind
of
going
on.
I
don't
know
if
I'm
gonna
quote
it
quite
right,
but
it's
like
you
know.
The
person
who
wins
is
the
one
who
writes
the
code.
You
know
and
and
to
some
extent
it's
a
looser
version
of
that
which
is
like
you
know.
You
can
kind
of
just
show
up
and
start
doing
stuff.
B
C
B
C
Well,
so
swap
support
is
special
because
it
didn't
exist
before
and
now
it
exists,
and
you
may
ask:
why
did
it
not
exist
and
the
answer
is
nobody
sat
down
to
do
the
work
right?
I
mean
there
was
like
definitely
some
concerns
in
terms
of
like
how
are
we
gonna
do
this
in
a
way?
That's
not
gonna
blow
up
kubernetes
clusters.
C
Please
give
us
a
proposal
that
convinces
us
and
then
we
will
be
happy
to
implement
it
and
that
just
kind
of
sat
there-
and
I
was
like
you
know
what
I'm
passionate
about
this
because,
like
the
first
of
all,
it's
one
of
those
things
where,
like
you've,
gotta
take
into
account
the
needs
of
like
so
so
many
users,
and
so
like
the
first
thing.
I
just
spent
a
whole
release
just
talking
to
people
being
like.
How
do
you
swap
like?
Is
this
document
of
use
cases
like
exhaustive
for
you
like?
C
Is
this
going
to
work
for
you?
Here's
like
a
sort
of
a
straw,
man
proposal
like
what
do
you
think
about
that
and
they'd
be
like
no,
I
hate
this.
Let
me
look
again
what
if
I
change
this
thing
then
like
do
you
still
hate
it?
No,
no,
that's
pretty
good
and
and
so
on
and
so
forth.
I
like
doing
that,
which
is,
like
you
know,
kind
of
like
very,
like
thankless
behind
the
scenes,
and
then
I
show
up
with,
like
you
know
what
was
effective
like
an
80
line.
C
C
C
C
C
Java,
like
node,
you
know
actual
virtual
machines
like
whatnot,
not
you.
It
could
be
potentially
useful
for
virtual
machine
live
migration
where
you
have
to
like
very
briefly
over
commit
memory
like
all
sorts
of
applications.
This
could
be
helpful
because
you
know
memory
is
a
tight
resource,
sometimes
especially
on
edge
systems
or
my
favorite
example
of
an
edge
system.
My
raspberry
pi,
I.
A
B
Perhaps
so
I
didn't
pick
up
on
that
right
now,
so
so
to
kind
of
cover
that
back
up
all
right.
So
so
the
kind
of
I
think,
the
last
question
that
we
have
time
for
because
we're
almost
out
of
time
is
so.
What
do
you
think
is
you
know
kind
of
in
kubernetes
in
general?
What
is
the
thing
that
you're
kind
of
most
watching,
or
what
do
you
think
the
biggest
and
both
from
a
positive?
B
B
C
Like
it's
really
important
for
me
to
be
like
okay,
you
know
I'm
thinking
like
a
year
or
two
down
the
line
like
who's
going
to
be
doing
this
in
the
future.
Is
it
going
to
be
me?
Do
I
want
to
keep
doing
this?
If
not,
how
am
I
setting
up
that
person
for
success,
and
so
I
have
done
a
couple
of
cohorts,
one.
I
was
working
with
a
bunch
of
people
to
try
to
show
them
how
to
become
node
reviewers.
C
C
Often
like
running
the
meetings
or
running
like
the
ci
sub
project
meetings
or
that
kind
of
thing,
so
it's
really
really
important.
I
think
to
like
build
and
uplift
this
sort
of
like
next
generation,
that's
going
to
be
doing
the
work
in
kubernetes
and
so
that
I
think,
like
is
really
the
thing
I
mean
not
to
be
like
everybody's,
like
cheesy.
It's
about
the
community,
but.
C
About
people
you
know
this
is
ultimately
at
the
end
of
the
day.
This
is
a
job,
and
so
like
people
move
on
from
thing
to
thing,
people
find
new
interests
and
yeah.
I
just
want
to
ensure
that,
like
for
the
time
that
people
do
spend
here,
they
have
the
best
experience
that
they
possibly
can,
and
you
know
when.
E
B
C
A
A
E
C
As
a
bdfl,
like
you
know,
you
first
of
all
like
there's,
so
these
ridiculous,
crushing
expectations,
I've
been
that
person.
I
was
the
whole
maintainer
of
a
thing
that,
like
the
entire
weight
of
binary
python
distribution
lay
upon,
I
was
like
I
can't
do
this
anymore,
like
it's
stressful,
I
don't
have
the
time
and
like
I'm
letting
everybody
down,
so
I
quit
right.
C
D
E
B
B
E
B
B
A
B
B
There's
all
of
those
reasons
right:
it's
not
it's
not
even
just
the
simplistic
kind
of
the
like
or,
like
sorry,
not
simplistic
more,
like
there's
lots
of
good
reasons
to
encourage
a
lot
of
community
that
are
like,
sometimes
it's
because
of
burnout,
but
sometimes
it's
because
you
want
to
do
you
know
you
really
get
into
one
little
deep,
dark
corner
of
node
right
and
you
want
to
stay
there
and
finish
that.
But
what
happens
to
all
the
rest
of
the
stuff
while
you're
doing
that?
You
know
so
there's
just
so
many
reasons.
C
But
you
end
up,
you
know
your
bandwidth
constrained
by
that
one
person
it's
really
hard
to
hold
them
accountable,
because
they're,
the
ones
called
all
of
the
shots.
They
have
effectively
all
of
the
power,
and
so
like
that
sort
of
thing
you
know
it's
just
like
it's
hard
to
be
able
to
step
back
and
move
on
it's
hard
to
be
able
to
sort
of
like
hand
off
the
torch.
But,
like
honestly,
I
think
that
you
know
it
thinking
about
the
tech
and
what
not
like.