►
From YouTube: Kubernetes Office Hours 20220316 (SIG Docs Edition)
Description
Office Hours is a live stream where we answer live questions about Kubernetes from users on the YouTube channel. Office hours are a regularly scheduled meeting where people can bring topics to discuss with the greater community. They are great for answering questions, getting feedback on how you’re using Kubernetes, or to just passively learn by following along.
For more info: https://k8s.dev/events/office-hours
A
If
it's
flipping
over
okay
yeah
we're
live
in
youtube,
so
let
me
go
here
and
guess
started
with
the
march
office
hour,
so
welcome
everyone
to
today's
kubernetes
office
hours,
where
we
answer
your
user
questions
live
on
air
and
our
steam
of
panels
and
experts.
You
can
find
us
on
office
hours
on
the
kubernetes
slack
and
check
the
topic
on
the
url
on
the
information.
A
If
you
want
to
reach
out
to
to
the
youtube
or
ask
questions
in
the
kubernetes
community
slack
channel,
we'll
look
at
that,
and
then
I
will
start
with
the
episode
today.
So
before
we
begin,
let's
start
a
roundtable
introducing
introducing
ourselves
star
system,
I'm
in
carolina,
ibm
cloud
community
building
for
for
kubernetes
and
helping
hosting
this.
This
show,
and
also
I
run
a
kubernetes
book
club
that
that's
something
that
I
really
like
I'm
doing
every
week.
A
We'll
go
to
chris.
B
Yeah,
my
name
is
chris
privateer.
I
work
over
at
equinix
metal
and
I
like
kubernetes,.
C
Go
ahead:
eddie
well,
hi,
I'm
eddie
zaneski!
I'm
a
developer
advocate
on
the
eks
team
at
amazon
web
services
and
I
help
maintain
cube
control.
D
Hey
everybody,
my
name
is
mario.
I've
been
doing
this
for
a
long
time
happy
to
be
here
yet
again.
Office
hours
is
great,
a
great
part
of
the
community,
I'm
a
staff
engineer
at
carta
financial
services
company.
If
you
have
employee
stock,
you
might
have
heard
of
us.
We
are
right
now
going
through
an
evolution
and
I'm
kind
of
helping
us
adopt
kubernetes
in
a
more
sane,
secure,
reliable
way,
so
lots
of
fun
challenges-
and
I
have
questions
myself.
E
Very
good
archie
hi,
my
name
is
archie.
I'm
cncf
ambassador,
organizing
one
of
the
largest
canadian
meetups
for
cncf
these
days,
I'm
teaching
cloud
native
at
the
university
of
mcgill
and
I'm
also
working
at
google
cloud
as
a
application.
Modernization
specialist
happy
to
be
here
again
nice
to
see
the
new
good.
F
So
hello,
everyone,
I'm
divya,
and
I
am
a
technical
writer
at
souza
as
part
of
my
day,
job
and
within
the
kubernetes
community.
I
am
a
sick
dogs
co-chair
in
addition
to
being
a
contributor
on,
I
mean
having
been
a
contributor
or
the
release
team,
so
played
a
bunch
of
roles
and
over
and
over
this
I'm
also
cncf,
ambassador
and
co-organizer
of
the
cncf
student
user
group.
So
I'm
excited
to
be
here.
A
Student
user
group
very
good,
I
think
I
saw
joey-
show
up
and
disappear.
Hopefully
he
can
join.
So,
let's
get
a
house
in
order
before
we
start
here
at
the
ground
rules.
This
is
a
kubernetes
event,
so
the
code
of
conduct
is
an
effect.
Please
be
excellent
to
each
other.
This
is
a
judgment
judgment
freezone.
Everyone
has
to
start
from
somewhere.
So
please
help
help
out
your
body
by
having
a
supportive
environment
panel.
A
Like
I
said,
while
we'll
do
our
best
to
answer
your
questions,
the
panel
doesn't
have
access
to
your
cluster,
so
live
debugging
is
off
topic.
We
would
love
to
debug
your
cluster,
but
we
don't
have
access,
but
we
will
do
our
best
to
get
your
moving
down
the
next
step,
but
at
least
you're
encouraged
to
expand
and
answers
on
answers
and
your
experience
on
the
pro
tips.
That's
why
we
have
experts
on
the
panel
audience.
A
You
can
help
by
pasting
urls
in
the
channel
to
official
books
blogs
like
this
morning.
Some
people
was
already
asking
questions.
People
are
helpful
enough
to
share
some
blogs
around
scheduler
post.
Your
questions
on
discuss,
kubernetes
dot,
io,
that's
where
we
check
every
month
for
the
top
questions
on
the
latest
questions
to
to
answer
them
and
or
somebody
else
would
answer
a
question
for
you.
I
also
we
also
have
a
stack
overflow
and
the
kubernetes
attack
dispatch.
This
panel
is
made
entirely
volunteers.
A
If
you
want
to
rotate
in
please
let
us
know
we
love
to
have
you:
have
the
people
rotate
learn
from
what
you're
working
on
kubernetes
and
then
always
community
chat
out
and
just
just
coming
into
the
office,
our
track
channel?
So,
let's
get
started
with
that,
and
now
in
this
year
is
a
little
bit
of
a
change
in
the
office
hours.
We
want
to
introduce
a
sig
a
different
sick.
A
Every
month,
last
last
month
was
contributor
x
before
that
eddie
was
here
showing
up
about
six
cli
and
today
we're
going
to
have
sick
dogs,
so
we
have
deeja
spring.
Five
minutes
pronounced
your
name
libyja
mohan,
I'm
from
six
talks
and
she's
going
to
tell
us
about
what
is
it
dogs?
What
do
they
do?
What?
How
can
you
help.
F
Thank
you
for
that
introduction,
carlos
and
you
pronounced
my
name
right.
Thank
you
for
that.
So
I
know
that
you
know
nobody
asked
me
to
do
a
presentation
and
but
I'm
just
like
a
presentation
geek
at
this
point,
and
I
thought
that
it
would
be
good
reference
material
for
whoever
actually
wants
to
refer
to
this
later
on
so
yeah.
So
as
already
aforementioned,
I
am
the
mohan
and
I'm
one
of
the
co-chairs
for
sick
dogs
on
the
kubernetes
project.
F
One
of
the
things
that
you
know
carlos
has
already
mentioned
is
that
we
are
all
you
know
a
part
of
a
very
big
community
or
so
in,
irrespective
of
it
being
officers
or
outside
of
it.
Please
be
you
know
nice
to
one
another
and
refrain
from
using
any
sort
of
harmful
language
or
abusive
language
on
the
chat
with
that
psa
out
of
the
way.
To
be
honest,
I
realized
that
you
know
a
small
introduction
to
who
is,
you
know,
who's
a
part
of
sick
dogs
and
who
are?
F
We
is
a
little
important
so
as
far
as
you
know,
the
contributor
stats
and
stuff
like
that
are
concerned,
I
will
be
throwing
some
numbers
at
you,
but
please
be
very
well
assured
that
we're
all
you
know,
people
who
are
extremely
passionate
about
kubernetes
and
cloud
native
technologies
and
we're
not
bots
so
far
at
least,
but
maybe
bots
do
take
over
the
show
at
the
end,
so
yeah.
So
we
are
all
there.
F
You
know
a
huge
community
and,
as
I
already
mentioned,
you
know
a
very
diverse
one
at
that.
F
So
far,
at
least
as
of
the
2020
one
numbers
that
we
have
had
on
the
devstats
website,
we
have
our
contributor
base
spread
across
98
companies
and
the
best
part
about
this,
in
my
opinion,
and
something
that
we've
even
flagged
in
our
annual
report
is
that
a
lot
of
these
contributions
are
coming
in
from
you
know,
independent
contributors,
which
is
very
heartwarming
to
see,
because
I
was
once
an
independent
contributor
myself,
having
worked
out
worked
outside
of
my
day
job
on
the
kubernetes
project.
F
So
you
know
it
shows.
It
truly
shows
that
this
community-
and
you
know
this
project-
is
built
out
of
passion
and
out
of
the
commitment,
and
you
know
because
of
the
contributions
of
so
many
people,
but
that
being
said
you,
I
obviously
must
also
introduce
you
to
the
people
who
make
all
this
magic
happen
in
the
right
way
by
you
know
stirring
and
governance
and
stuff,
like
that
from
the
leadership
team.
So
of
course
I'm
one
of
the
coaches,
but
I
have
a
stellar
team
with
me.
F
Unfortunately,
jim,
who
is
one
of
the
coaches,
has
decided
to
step
down.
This
is
not
news
if
you've
been
around
in
kubernetes
in
the
kubernetes
slack
channel
or
on
the
mailing
list,
but
it's
it's
a
terrible
terrible.
You
know
blow
to
all
of
us
because
he's
laid
some
fantastic
foundation
for
a
lot
of
us
to
you
know,
carry
on
the
work
that
he
has
initiated.
F
We
have
currently
natalie
ray
and
myself
as
the
co-chairs
for
sick
dogs,
and
we
have
a
stellar
tech
leads
team
to
which
we
have
recently
nominated
and
added
kimming
tim
tim
bannister,
taylor,
taylor
and
karen,
were
you
know?
The
already
existing
tech
leads
and
localization
like
carlos
said,
is
not
something
very
new
to
the
kubernetes
project
per
se,
but
it's
basically
something
that
we
have
been
already
passionate
about
as
a
project.
We
really
want
to.
F
You
know
bring
in
the
cncf
values
of
creating
a
diverse
and
inclusive
environment
for
all,
so
localization
was
just
one
of
the
ways
we
intended
to.
You
know
create
that
sort
of
environment,
and
it
was
not
a
formalized
initiative
so
far,
so
as
of
q1
2020
22,
I
believe
we
are
in
q1
still
so
we
have
like
a
cap.
That's
a
kubernetes
enhancement
proposal
drafted
towards
formalizing
this
sub
project
and
one
of
the
tracking
issues.
I
mean
not
one
really,
but
the
tracking
issue
for
that
is
on
your
screen.
F
Right
now
and
another
thing
that
you
know,
we
are
absolutely
passionate
about
in
terms
of
you
know,
community
outreach
and
you
know,
contributor
experience-
is
the
actual
initiation
of
new
contributors.
Now
we
know
that
you
know
now.
I
know
really,
and
all
of
us
here
on
this
panel
know
that
contributors
when
you
are
absolutely
new
to
an
ecosystem,
it's
an
intimidating
place
to
be,
and
it
would
help
you
know
if
there
was
someone
who
could
cure
you
and
guide
you
and
help
you
out
in
the
very
first
couple
of
days.
F
So
new
contributor,
ambassador
role
was
a
part
of
the
whole
ecosystem,
but
it
was
never
sort
of
formalized
within
the
sig
docs.
You
know
charter,
and
this
is
another
thing
that
we
are
you
know
currently
doing
and
formalizing
and
documenting
properly,
so
that
we
can
have
this
role
or
the
person
in
this
role,
rather
mentor
newer
folks
into
the
documentation
subgroup.
Now
ash
is
the
new
contributor
ambassador
for
this
year,
and
you
know
all
these
things
all
these
nominations
that
have
happened
over
or
via
community
consensus.
F
You
know
driven
across
mailing
lists
and
slack
threads,
so
pretty
proud
of
the
team
we've
got
here
and
we
also
have
you
know
the
sub
projects
that
I
did
not
mention
in
the
previous.
You
know
slide
and
I
am
going
to
talk
about
bit
about
it,
so
we
have
the
blog
as
well
as
the
reference
dog
sub
project
under
our
remit
and
the
scanning.
F
These
qr
codes
will
basically
lead
you
to
the
owner's
file
and
you
can
check
out
who
are
the
reviewers
and
approvers
for
this
particular
sub
project,
and
should
you
want
to
get
involved,
you
can
definitely
reach
out
to
them,
and
you
know
or
us
or
any
one
of
us
really
and
we'll
definitely
do
our
best
to
help
you
get
started,
but
that's
a
lot
of
content
being
thrown
at
you
at
this
point,
and
I
realized
that
you
know
I
have
still
not
spoken
about
what
we
have,
what
we
actually
work
on.
F
Given
that
you
know,
sick
docs
is
the
name
of
the
special
interest
group.
Documentation
is
a
given
at
this
point.
It's
something
that
we're
obviously
going
to
work
on,
but,
like
I
mentioned
before,
the
documentation
is
actually
hosted
on
our
main
website,
which
is
kubernetes
dot
io.
So
all
the
content
on
there,
whether
it
be
the
blog
whether
it
be
talk,
you
know
the
actual
manually
written
documentation,
the
you
know
reference
documentation
and
you
know
all
the
localization
content.
F
All
of
that
is,
you
know,
sort
of
handled
by
all
the
amazing
contributors
who
we
saw
a
statistic
of
in
the
very
I
think,
third
slide.
If
I'm
not
mistaken,
so
you
know
what
we
do,
and
one
of
the
things
that
you
know
might
have
that
you
might
have
thought
of
right.
F
Now
is
how
do
we
keep
in
touch,
given
that
our
contributor
base
is
like
extremely
huge
at
this
point,
like
I'm
not
even
talking
about
just
sick
dogs,
because
sick
dogs
is
like
a
subset
of
you
know
the
wider
kubernetes
community,
and
how
do
we
actually
keep
in
touch
so
in
the
kubernetes
community?
F
We
basically
do
it
via
mailing
list
slack
and
zoom
meetings,
but
again,
given
the
number
of
contributors
that
we
have,
we
are
trying
to
be
more
inclusive
of
you
know
people
from
other
time
zones
as
well,
so
one
of
the
things
we've
started
doing
is
that
we
alternate
between
slack
threads
and
zoom
meetings
every
week,
because
we
have
weekly
meetings
and
just
so
that
you
know
we
are
inclusive
of
folks
from
the
asia
pac
diaspora.
F
We
have
apac
friendly
zoom
meets
every
once
in
a
month,
and
this
is
necessarily
a
zoom
meet,
not
a
slack
thread,
because
you
know
we
we
love
having
in-person
meets,
but
unfortunately,
because
of
time
zone
conflicts-
and
you
know
personal-
is
getting
in
between
it
becomes
difficult.
F
So
that's
that's
one
thing
and
then
the
last
thing
is
you
know
we
try
and
maintain
a
lot
of
our
decision
making
and
consensus
driving
discussions
on
slack
threads
and
on
mailing
lists,
like
I
mentioned
before,
because
it's
not
possible
for
everyone
to
have
you
know
or
not
have
really
to
attend
a
meeting
or
to
see
a
slack
thread
the
minute
it's
posted.
F
So
we
try
and
do
that
and
have
a
lazy
consensus
period
as
well,
so
that
you
can,
you
know,
mull
upon
it
and
sort
of
dry
come
to
a
decision
overnight,
after
sleeping
on
it
or
whatever.
So
that's
how
we
keep
in
touch,
but
now
I've
got
like
a
quick
thing
for
everyone:
who's
watching
in
right.
Now
we
have
a
a
24
hour,
slack
trend
meeting
in
going
on
right
now
on
the
sick
dogs
channel.
F
So
what
I
want
you
all
to
do
if
y'all
are
interested
and
if
y'all
want
to
you
know
be
a
part,
is
actually
go
to
the
slack
link
that
is
slack
dot,
kh
dot,
io
find
the
channels,
sick
dogs
and
sick
dogs
blog,
because
those
are
the
channels
where
we
do
most
of
our
work
and
communicate
and
say,
hi
come
over
and
say
hi.
We
promise
we
won't
eat
you.
F
I've
already
had
my
dinner,
so
I
definitely
can't
youtube
but
say
hi
and
introduce
yourself
even
if
you're
a
locker,
it's
completely
fine.
I
was
a
locker
for
nearly
one
month
before
I
had
the
guts
to
go
and
say
hi
on
a
meeting,
so
don't
feel
afraid
if
you're
not
able
to
go
at
the
very
first.
You
know
introduction,
but
it
would
be
great
if
you
could.
F
You
know,
introduce
yourself
and
say
hi
on
the
slack
channels
that
I've
mentioned
on
this
slide,
so
I
will
stop
right
there,
and
you
know
you
know,
navigate
to
a
little
more
practical
thing
of
how
do
you
get
involved,
because
at
this
point,
you're,
like
she's,
been
boxing
on
for
so
long
about?
You
know
how
great
sake,
dogs
is.
How
can
we
get
involved?
F
You
definitely
need
to
know
what
can
you
do
right,
because
all
of
this
is
great
to
listen
to,
but
unless
you
actually
do
something,
it
doesn't
really
have
any
effect.
So
one
way
to
find
you
know
your
way
into
the
project
is
via
good
first
issues,
if
you're
an
absolute
beginner-
and
I
was
an
absolute
beginner
when
I
started
off
so
these
issues
were
a
boon
when
I
started
off
like
I
was
a
novice
not
only
at
the
two
kubernetes.
F
You
know
not
only
at
the
kubernetes
as
a
tool
or
a
technology,
and
I
I
basically
did
not
know
how
a
static
site
generator
worked
either.
This
was
way
back
in
2020.
I've
come
a
long
way
since
then,
but
you
know
if
you
want
to
get
started.
If
you
have
no
idea
about
the
you
know,
static
site
generator
and
you
want
to
contribute.
This
is
your
you
know,
go
ahead
for
this.
F
You
can
click
this
link
and
don't
worry,
this
presentation
will
be
up
and
we'll
post
the
link
to
it
shortly
on
the
slack
channels.
Don't
worry
about
it.
You
will
be
having
a
reference
to
this
presentation
soon.
F
Now,
if
you
are
slightly
more
experienced-
and
you
know,
you
still
want
to
contribute
to
the
documentation
and
good
first
issues
are
just
not
your
theme,
you
can
just
filter
for
the
help
wanted
labels
now,
just
a
psa
help
wanted
labels
sometimes
also
have
good
first
issue
labels
tagged
with
them
in
that
case,
if,
if
you're,
not
a
beginner,
please
don't
attempt
the
good
first
issues,
because
it's
going
to
be
really
simple.
It's
for
an
absolute
beginner
to
start
off
with.
F
So,
if
something
more,
what
how
do
I
say
it?
If
something
more
complex,
is
you
know
your
jam?
Please
go
ahead
and
hit
this
link
and
you'll
be
able
to
sort
of
get
access
to
the
issues
that
are
slightly
more
complex,
another
psa
before
we
move
ahead
when
you're
working
on
an
issue
right.
F
Please
please,
please
assign
the
issue
to
yourself
or
ask
the
issue
for
it
to
be
assigned
to
you,
because
the
more
number
of
issues
that
go
unassigned-
and
you
know
if
somebody
else
happens
to
chance
upon
that
issue-
there's
gonna
be
a
lot
of
duplicate
work
and
a
lot
of
bad
blood
spilled
because
of
this
unassigned
issue
or
debica.
So
please,
please,
please,
if
you're
working
on
an
issue,
consider
assigning
yourself
to
the
issue
as
well.
F
That
being
said,
I
think
this
is
the
last
slide
and
I'm
going
to
shut
up
after
this.
Don't
worry
so
one
of
the
last
slides
that
I
will
leave
you
all
with
is
the
contributor
ladder
within
kubernetes
and
as
a
whole
and
sick
dogs.
You
know
as
a
subset,
so
I
started
off
at
the
bottom.
Just
just
so.
You
know.
I
did
not
enter
the
kubernetes
organization
right
at
the
top
just
saying
so
I
started
off
as
a
non-member
contributor
made.
A
couple
of
contributions
got
accepted
into
the
release.
F
Team
became
a
member
and
you
know
the
privileges
increased
as
and
when
you
know
the
contributions.
Number
of
contributions
and
number
of
you
know
valuable
contributions
started
increasing,
so
it's
basically
a
ladder
that
you
ascend
and
a
privileged
ladder
that
you
ascend
in
terms
of
you
know
the
amount
of
trust
the
community
has
in
you.
So
it's
it's
absolutely
essential
that
you
do
not
get
demotivated
in
the
process
and
you
know,
even
if
your
first
issue
doesn't
go
that
well,
you
do
not
get
demotivated
and
you
know
just
stop.
F
A
A
So
I
I
I
know
that
you
need
to
leave
for
another
meeting.
I
don't
want
to
ask
a
lot
of
questions,
it's
great,
that
you
show
this
ladder
of
getting
involved
because
a
lot
of
people,
I
think,
should
drop
I'll,
continue,
pointing
out
out
that
that
ladder
is
similar
to
the
other
six
and
other
areas.
Where
a
lot
of
people
join.
A
I
guess
they.
They
start
with
kubecon
right.
A
lot
of
people
join
kubecon
and
they
ask
like.
I
want
to
get
started
in
open
source
or
want
to
get
started
in
kubernetes
and
one
one
misperception
is
like
they're
being
when
they
work
on
github.
They
have,
they
have
their
own
github
repo
and
they
have
right
access
and
they
can
do
changes
and
they
don't
have
the
any
experience
with
a
video
bank
on
contributing
and
sick
ducks
is
a
easy
way
to
get
to
get
started.
A
But
you
have
there's
always
a
ladder
from
where
you
start
like
helping
with
small
things,
and
then
you
saw
the
the
change
to
be
helping
with.
I
guess,
like
small
things,
contributing
to
the
actual
work,
because
there's
a
lot
of
people
and
then
you
switch
to
be
more
of
a
mentor
helping
others,
so
you
switch
from
contributing
assets
to
contributing
helping
others
contribute
assets
and
that
scale.
So
that's
that's
a
great
that's
a
great
thing
that
you
ended
up
there.
A
I
know
you
need
to
leave,
but
and
that
one
question
of
that
people
may
always
ask,
is
how
come
if
a
new
feature
in
kubernetes
is
being
planned
and
that's
maybe
another
sig
that
we're
going
to
have
kept.
How
does
kubernetes
make
sure
that
when
a
new
feature
or
a
new
big
change
is
going
to
make
it
into
kubernetes
that
we
don't
end
up
with
the
project
of
like
that
thing,
not
documented,
which
happens
in
a
lot
of
projects
right,
there's
new
features.
F
A
F
Absolutely
that's
a
very,
very
good
point
and
the
way
we
do
it
is
it's
a
whole
process
and
a
lot
of
stakeholders
are
involved
in
this.
So
let
me
be
very
brief
about
the
whole
process,
because
it's
a
long
one
so
there's
an
entire
release
team
that
handles
this
whole.
F
You
know
end-to-end
release
process,
basically
doing
the
coordination
between
the
various
stakeholders,
so
sig
docs
is
basically
just
the
reviewer
and
approver
for
all
the
documentation
that
goes
in
during
a
release
process
and
what
tends
to
happen
is
one
vertical.
Within
the
release
team,
every
release
team
has
multiple
verticals
one
vertical
within
the
release.
Team
is
responsible
for
only
the
docs.
There
are
others
that
are
responsible
for
notes
for
blogs
for
comms
everything,
so
the
one
responsible
for
docs
right
will
sort
of
track.
F
Whether
or
not
that
particular
feature
requires
documentation
once
it
is
tracked
that
you
know
that
particular
feature
requires
documentation.
It
needs
to
have
a
draft
pull
request
open
against
the
k
website
repository,
so
that
particular
vertical.
That
really
stream
vertical
is
the
one
that
ensures
that
you
know
we
have
content
to
approve
and
review
every
feature.
F
Every
cycle
every
release
cycle
and
it's
an
amazing
process
to
be
a
part
of
because
you
get
to
learn
a
lot
of
stuff
from
interacting
with
so
many
other
folks,
and
it's
not
just
dogs
that
you
know
they
liaise
with
they
list
with
all
the
stakeholders.
F
A
Yep
yeah,
I
I
that's
the
question
where
I'm
familiar
with
I'm
currently
a
shadow
for
the
release,
notes
and
I'm
I
I
know
that,
there's
a
team
I
I'm
in
charge
of
we
are
in
charge
of
the
release
notes.
So
it's
it's
a
it's
a
it's
a
gate
like.
If
there's
a
pr
change,
you
have
to
say
that
there's
actually
no
release
notes
same.
E
A
For
a
change
in
in
a
cap
like
a
cap
needs
to
be
evaluated
if
it
needs
knocks,
and
the
docs
needs
to
be
done
by
the
release
time,
so
we're
going
to
release
1.24
in
april
next
month
and
and
that's
part
of
the
work.
So
if
people
are
interested
in
the
shadow
program
you
can
you
can
be
a
shadow
for
release,
no
sig
dog,
sitcom
six
signal
and
and
learn
about
that,
but
yeah.
I
just
wanted
to
say
we
thank
you
for
for
your
time.
A
I
appreciate
the
information
today.
Hopefully
you
get
more
contributors,
and
that
was
a
great
idea
to
to
tell
people
to
go
ahead
and
and
don't
be
shy,
go
to
slack,
join
slack
and
just
say
say:
hi
right
and
if
you
yeah,
I
want
to
get
your
first
pr
right
or
first
first
contribution
to
kubernetes
join,
get
sick
ducks,
say
hi
in
slack
and
then
grab
a
first
good
issue.
So
I
think
that
you
nailed
it
there.
So
any
any
comments.
A
Mario
ready
chris,
you
already
made
your
documentations
prs.
I
did.
I
did
one
long
time
ago,
a
spanish
translation,
so
I
did
some
spanish
translation
so
just
wanted
to
get
a
pr
in.
So
that's
I
started
with
that.
Like
every
every
project
that
I
joined,
I
start
with
either
with
read
me
change
or
a
website.
F
F
A
So
with
that,
out
of
the
way
any
comments,
that's
common
in
sick
dogs-
I
I
think
the
kubernetes
six
documentation
is
is
very
good,
but
sometimes
we
don't.
We
don't
think
how
many
people
are
behind
that
that
website
right,
compare
not
to
put
the
it
being
another
open
source
project,
but
they
struggle
because
they
don't
foster
the
documentation.
A
People
that
much
or
or
so
there's
need
to
be
a
lot
of
appreciation
for
the
people
doing
docs,
that's
actually
valuable
that
that's
their
part
of
the
community,
not
just
the
the
line
of
code
or
the
of
the
infrastructure
that
we're
doing
kubernetes
and
there's
a
lot
of
folks
from
another
different
countries,
a
lot
of
folks
from
different
countries
doing
translations.
Actually.
A
So
with
that,
let's
get
started
with
a
little
a
few
questions,
and
I
don't
know
if
people
are
asking
slack,
but
I
pick
one
from
discord
from
discuss:
kubernetes
dot.
Io.
Let
me
see
if
I
can
find
it.
Okay,
this
one
is
an
interesting
one,
which
I
have
been
having
a
bit
piece.
So
I
pick
it
up
why
config
maps
is
that's
paraphrasing.
A
I
think
that
the
person
is
trying
to
understand
why
config
maps
is
a
string
to
string
the
schema
and,
for
example,
when
the
person
is
working
with
home
values
yaml.
If
you're
familiar
with
home
values,
it's
a
structured
gamma.
You
can
have
a
raise,
so
the
person
was
struggling
with
why
he
he
wants
to
have
a
in
a
config
map,
a
key
map
to
a
array
instead
of
a
just
a
string
and
the
actual
question
site
also
also
our
config
maps
and
values.
A
Objects
in
hell,
values
are
different
because
we
can
specify
a
list.
For
example,
an
array
of
value
objects,
while
not
in
configms
below,
is
the
value
of
those
gamma
which
is
successfully
parsed
by
helm.
So
is:
is
this
yeah?
This
has
a
disconnect
of
an
array
for
a
key
in
a
yama
file,
in
this
case,
working
with
with
helm
and
config
maps
being
a
string
to
string.
A
And
team
team
answer
it,
but
I
think
it's
the
person
still
having
some
difficulties
of
setting
a
config
map.
So
if
I
have
a
config
map-
and
it
says.
A
C
Yeah,
so
my
quick
reading
through
this
is
like
tim
said,
the
data
field
in
a
configmap
is
a
string
field.
It
is
not
an
array
field,
and
so
I
believe
it's
working
in
helm
because
hell
must
be
doing
a
join
on
the
array
and
turning
them
to
a
string
altogether,
so
that
might
just
be
helm
kind
of
masking
how
that
all
works
behind
the
scenes.
But
the
implementation
of
the
data
field
on
a
config
map
is
a
string,
so
it
has
to
be
treated
as
a
string.
A
Yeah
yeah,
that's
correct,
so
the
what's
happening
behind
the
scenes
is
that
in
the
helm
template
they
have
a
string
to
string
value
of
like
fruits,
and
then
they
have
a
string
what's
happening,
and
I
see
this
often
and
and
it's
a
problem
that
I'm
hitting
a
lot
is:
if
you
have
fruit,
for
example,
in
kipcitl6cli
expert
here
right,
you
have
the
the
correct
config
map
and
you
can
pass
like
value.
A
You
know,
variable
equals
value
right
and
that
will
create
string
string
or
you
can
say,
variable
equals
a
file
and
it
would
read
the
file
it
could
be.
A
text
file
could
be
xml.
A
It
needs
to
be
something
that
is
like
base64,
like
do
not
have
binary
data,
and
it
will
be
put
into
the
config
map
as
a
string
with
enough
lines,
for
example,
but
that's
a
file
that
gets
loaded,
that
the
problem
that
I
see
in
the
field
and
it's
something,
maybe
that
that
maybe
this
blog
post
or
something
like
that,
it's
like
people,
will
put
a
configuration,
yaml
file
in
a
single
variable,
and
when
you
see
this
in
things
like
openshift
gui
other
guise,
they
look
like
there's
a
structure
below
that
that
variable-
and-
and
I
see
this
also-
I
saw
this
in
the
scaffold
slack
channel
asking
like
how
can
I
use
customize
to
change
one
of
the
values
within
that
file
stream
and
there's
no
such
thing,
because
it's
just
a
blob
for
example.
A
So
that's
where
you
like,
don't
have
the
utility
where,
where
I
know
that
argo
does
this
other
tools
to
this,
where
the
whole
configuration
of
the
of
the
system
or
that
project
is
a
single
string.
If
you
twist
your
eye,
some
guys
would
like
you.
You
would
think
that
it's
part
of
the
structure
of
the
schema,
but
it's
not
it-
has
a
pipe
at
the
beginning
and
a
lot
of
people
struggle
with
that.
A
So
I
don't
know
if
there's
something
and
then
what
you
need
to
do
is
just
go
back
to
like
helm,
set
an
awk
find
and
replace
that
string
manipulation.
So
that's
the
doesn't
understand.
So
helmets
are
very
good.
He
hides
that
from
you,
so
you
do
the
manipulation
by
a
templating
and
then
you
put
in
the
different
strings
in
the
helm,
template
your
information
in
there.
A
So
I
don't
know
if
other
people
have
have
that
issue
or
not.
I
know
any.
Maybe
you
know
well,
maybe
not
a
customized
has
a
new
thing
called.
I
think
it's
a
function,
it's
a
program
that
you
write
and
it's
an
extension
to
customize
that
you
put
in
client
side
that
can
parse
the
information.
I
don't
know
that
could
be
a
solution
for
that
people
that
want
to
manipulate
that
config
map
string,
pass
it
to
this
to
the
customized
program
and
in
gold.
You
read
the
whole
file.
A
Try
to
make
it
a
structure,
change
it
and
then
put
it
back.
So
that
could
be
an
alternative
for
this
person
if
they
want
to
use
either
helm
or
they
want
to
use
customize.
A
C
And
that's
yeah:
it's
basically
a
specification
for
input
output
streams
that
you
can
modify
resources
as
they
come
in
through
hell.
Tran
through
customized
transforms,
I'm
definitely
not
the
most
experienced
in
that,
but
I'm
gonna
plug
real
quick.
We
do
have
our
customized
bi-weekly
bug
scrub
coming
up
in
18
minutes.
If
you
all
want
to
join
that.
A
Very
good
that
was,
that
was
the
only
thing.
Some
people
were
asking
that
in
in
slack
about
like
how
to
use
customize
to
change,
because
they
can
change
all
the
things
right
in
deployments
and
services,
everything
that
is
on
their
spec,
but
when
it
comes
to
a
config
map
that
is
like
30
lines
long
and
it
looks
like
a
like
a
yaml
that
is
proper
schema
is
not
right.
They
miss
that
it's
a
actually
string,
but
some
some
gu
is
actually
like
painted,
like
there's
actually
part
of
the
of
the
schema
too.
A
So
it's
readable
okay,
so
that
that
was
that
I
didn't.
I
think
that
was
a
good
question.
It
came
up
on
here,
but
I
remember
that
it
came
up
around
customized
scaffold.
I
struggle
with
it,
because
I
need
to
change.
I
I
work
with
argos
cd
and
I
need
to
change
a
lot
of
configuration
for
margo
cd,
so
I'm
using
all
said
finally
replacing
bash,
manipulating
that
that
thing
and
then
and
then
check
it
in
to
get.
Let
me
let's
take
the
other
one,
the
other
one
is
around.
A
This
is
a
maybe
a
more
high
level.
Generic
one
is,
I
can
post
the
link
also
to
this
one,
it's
around
ssh,
so
these
folks
have
just
some
juniper
notebooks
that
they
want.
A
The
developers
are
creating
uniform
notebook
spots
that
they
have
the
ssh
enabled
and
for
some
reason
they
want
to
ssh
into
this
juniper
notebook
pod
that
has
the
ssh
demon
running
and
they're
kind
of
wasting
or
not
or
or
like
it's
costing
them
a
lot
of
public
ip
addresses
in
some
cloud
provider
in
this
case
eks.
A
But
I
was
looking
for
information
of
like
a
lot
of
information.
I
wanted
to
look
like
an
ingress,
but
for
ssh
right,
so
there's
a
lot
of
increases
for
http
https
out
of
the
box
to
have
like
one
loan
balance
or
one
ip
public
ip
address
and
then
through
that
everybody
can
get
to
to
a
pod.
So
what
about?
What
about
this?
One
on
how
to
use
a
single
pulley
cap
free
address
for
ssh
in
into
pods?
Well,.
B
A
So
the
I
was
looking
for
the
ng
next
you're
saying
that
the
ngnx
has
a
configuration
that
you
can
have
in
a
config
map
and
set
a
tcp
ip
address
right,
a
tcp
port,
for
example
9000
or
it
could
be
two
two
two
two
two
right
and
then
that
will
be
exposed
and
that'll
be
tcp,
and
then
you
send
it
to
a
service.
A
So
you
have
to
make
sure
that
that
that
service
like
unique
enough,
that
hits
the
one
pub
that
is
unique
enough,
that
the
person
coming
in
is
that
port
number
right
or
I
don't
know
if
it
can
be
this-
can
can
it
be
routed
through
a
host.
Somebody
knows
so.
However,
user
gets.
C
A
host
name-
I
was
yeah
that
so
that's
how
I
would
approach
this
is,
I
would
have,
I
would
generate
either
a
host
name
or
a
url
path
for
each
pod,
and
then
you
can
just
use
nginx
to
load
balance
on
the
host
names
and
still
listen
on
port
22
or
something
right.
So
you
can
listen
on
the
default,
ssh
port
and
then
map
that
host
name
to
the
correct
pod.
So
you
could
dynamically
generate
that
nginx
config
with
those
different
routes.
A
But
but
the
ingress,
the
typical
ingress,
is
usually
used
for
http
out
of
the
box
right.
Those
configurations
are
http
https.
You
have
to
get
kind
of
out
of
your
way
to
find
out
either
the
cloud
provider
provided.
Ingress
supports
tcp
ports
right,
for
example,
a
database.
Like
my
sql,
I
have
my
sql.
I
want
to
connect
to
my
sql,
that's
not
ssh
or
https.
How
do
I
expose
my
sequel
other
than
a
noteboard
right
that
nobody
wants
to
put
those
those
public
appearances
directly,
but
something
that
is
in
the
very?
A
But
that's
I
don't
know
if
actually
proxy
and
the
other
ones
was
wondering
if
somebody
knows
but
the
ingress
is.
I
I
found
a
lot
of
hits
that
there's
a
config
map
that
you
can
figure.
I
think
the
sample
was
9000,
but
you
have
to
come
with
a
clever
way
of,
like
you
were
saying,
allocating
that
service
to
that,
but
that
that
user
wants
to
connect
right
who
to
give
the
access
like
they're,
trying
to
to
do
that
and
they're
using
a
bastion.
A
So
I
would
say
that
they
can
also
do
something
like
a
proxy
right.
They
can
have
a
pod,
that
is
a
proxy.
It
has
a
management
stack
and
doing
that.
The
other
option
I
found
was
teleport,
I
think
teleport
is-
is
a
was
built
for
this
right.
A
It
was
built
for
ssh
in
into
into
nodes
right,
but
you
can
make
it
so
that
using
the
containers
of
teleport,
it's
open
source
to
have
the
two
options
out:
the
open
source
and
the
payer
option,
but
the
open
source
I
wish
rocco
could
be
here
because
he's
he's
doing
a
course
in
rockford
academy
about
teleport.
A
So
if
you
want
to
know
more
about
teleport
watch,
his
youtube
channel
he's
doing
some
segments
on
teleport
and
teleport,
something
that
you
can
like
launch
as
a
demon
set
and
handle
the
authentication
easy
authentication
from
the
cli.
It
has
a
cli
and
you'll
be
able
to
connect
to
two
different
folks
and
have
the
authentication
so
that
that's
what
that
to
me
was
kind
of
another
attendancy,
but
it
depends
right
if
it's
a
development
environment
versus
like
a
production
environment
that
changes
the
game
like
who's.
A
But
if
it's
for
developers,
I
think
maybe
teleport
is
it's
a
good
thing
versus,
like
you
know,
you're
building
a
sas
and
and
people
are
allocating
in
the
station.
You
you
charge
for
for
the
time
that
the
person
is
connected.
Then
maybe
you
need
like
a
management
layer
like
like
managing
that
connections
and
that
authentication
and
and
exposing
it
so
there's
different,
there's
different
options,
but
if
it's
development
try
teleporting
teleport
might
be
an
easier
answer
than
growing
your
own.
E
I
agree
with
you,
I
remember
kelsey
hightower
was
saying
like
do
not
give
developers
keep
cuddle
and
don't
let
them.
You
know
ssh
into
the
the
pods
like
this
is,
like
probably
you
know
not
a
good
pattern.
I
would
say-
and
you
know
you
need
to
provide
tools
for
developers
to
to
see
the
logs
or
other
things,
but
I
think
machine
learning.
I
think
that's
the
use
case
for
the
having
it's.
E
A
Something
right:
yeah,
that's
not
the
best
way
but,
like
you
mentioned
just
to
be
sure
that
maybe
they're
not
that
they're
aware
keep
ctl
exec
right,
you
can.
If
the
developer
has
skip
config
access,
they
can
use
skip
ctl.
I
call
it
kip
ctl,
nobody
be
a
chain.
A
I
cannot
pronounce
the
other
versions,
so
you
can
use
skip
ctl
to
go
through
the
through
the
cube
api
server
right
and
connect
ssh
right,
but
you're
actually
executing
a
bash
or
executing
sh
and
getting
a
standard
input
standard
output.
So
you
can
do
keeps
detail
that
essec
ip
to
the
bot
that
got
assigned
that's
usually
like,
for
maybe
us
can
include
everyone
like
infra
people
right
trying
to
debug
and
setting
up
kubernetes
and
troubleshoot
something
not
a
developer,
like
you
know,
getting
their
hands
with
blood.
E
E
One
ip
address
and
then
they
just
add
as
many
you
know,
dns
and
points
they
have
and
you
know
do
they
either.
Like
you
know,
company
slash
api
x,
ipi
y
ips
or,
like
you
know,
there's
either
using
host
path
or
or,
like
you
know,
different
paths
for
their
ingress
resources.
I
don't
think
that'll.
A
A
Yeah
they
were
having
a
bastion
and
then
jumping
a
jump
box
for
that,
but
many
many
ways
to
do
it.
It
depends
really
like
the
type
of
audience
and
if
it's
production
versus
versus
development,
if
it's
all
the
time
but
yeah.
If
it's
ssh,
look
at
look
at
teleport,
they
have
like
containers
already
like
with
the
ssh
demon
a
way
to
to
connect
to
it.
Has
they
have
a
nice
gui?
A
I
have
I
learned
about
it
through
the
cluster
led
program,
chronicles
setup
and
I
was
able
to
like
ssh,
but
it
was
more
for
the
notes,
but
I
think
that
they
can
map
to
a
pod,
maybe
through
a
cycle
or
maybe
through
the
demon
set,
so
the
next,
the
last
one
before
we
run
out
of
time.
Actually
I
have
three
questions,
so
we
are
perfect
on
time.
A
Paraphrasing
the
question
was
how
to
allow
a
how
to
allow
and
block
so
this
is
a
person
like
he
wants
to
allow
and
also
like
block
certain
cider
ranges
using
ingress
network
policy.
So
the
actual
question
is:
can
I
use
an
increase
type
network
policy
to
block
certain
insider
ranges
but
allow
all
other
egress
traffic
thanks
in
thanks
in
advance?
E
Yeah,
so
you
know,
unfortunately,
that
kubernetes
network
policies
itself
they
today
they're
not
supporting
like
deny
action.
So
what
we
can
do
with
kubernetes
network
policies,
we
can
do
deny
all
and
then
allow
specific
cidrs.
This
is
how
it
works
then
like.
If
you
really
need
this
functionality,
you
can
look
into
possible
alternatives.
E
The
first
alternative
would
be
using
calico
network
policy.
So
if
you
go
into
the
telecom
network
policy
website,
they
have
actually
a
different
api
element,
so
you're
kind
of
going
towards
more
vendor-specific
api
you're
not
going
to
be
using
pure
kubernetes
api.
So
you
have
to
consider
that
and
there
they
actually
have
a
possibility
to
to
specify
actions.
You
can
specify
action,
allow
or
action
deny,
and
then
you
can
specify
your
cidr
block.
So
calico
apis
provide
this
capability,
but
it's
kind
of
commercial
product.
E
Potentially
you
can
use
something
from
open
source
there,
but
like
it's
a
different
api
and
then
we
also
have
ebpf
based
psyllium
networking.
So
celium
also
allows
you
to
configure
deny
policies
for
different
actions,
so
it
could
be
your
cidr
and
even
they
have
a
like
fqdn.
E
F
E
Like
the
short
answer,
is
you
can't
use
kubernetes
network
policies,
as
is
you
have
to
either
look
into
the
psyllium
or
look
into
the
calico
networking
policies?
E
If
you
don't
want
to
like
install
different
different
networking,
cni
like
if
you
want
to
stay
with
the
your
calico
stuff,
then
you
probably
need
to
look
into
the
calico
policies
and
then,
if
you
want
to
go
to
the
something
more
advanced
which
is
ebpf
and
I
think
a
lot
of
tractions
right
now
for
so,
I
think
this
would
be
a
silly
networking
policy
would
be
able
to
do
that.
A
E
I
just
want
to
make
sure
it's
just
like
I
think
for
me,
like
I
always
try
to
use
kubernetes
apis
because
they
are,
you
know
like
there's,
no
lock-in
right,
so
you
can.
You
can
use
these
policies
everywhere
where,
like,
if
you
really
care
about
this,
you
know
things
like
you
want
to
your
policies
be
working
everywhere.
E
Then
kubernetes
network
policies
are
better
right
like
because
they're
standard,
whereas
like,
if
you
start
using
property
or
apis
like
italic
or
then
you
need
to
make
sure
that
this
you
know
this
apis
are
installed
and
configured.
That's
the
only
concern
I
have
otherwise.
If
you
really
need
this
use
case,
I
think
yes,
you
should.
A
Yeah
and
then
just
because
we
cannot
assume,
like
all
the
content,
that
the
person
knows
right.
So
if
you
don't,
if
you
don't
know
how
to
work
out
the
kubernetes
network
policies
right,
like
actually
was
saying
you
say,
the
typical
way
of
thinking
about
it
is
like
like
firewall
like
break,
you
know,
deny
everything
and
then
open,
often
the
only
the
things
required
and
that's
kind
of
like
I
would
say,
not
the
best.
It's
kind
of
the
best
practice
right
from
a
like.
A
I
want
to
block
everything
and
then
just
allow
the
things,
because
then
you
know
what
actually
gets
gets
out
right,
you're
not
going
to
allow
anything
from
a
certain
pod
to
leave
out
of
this
spot
except
right.
So
you
would
do
a
deny
all-
and
you
can
say
you
know,
allow
this
starter
range
with
the
ip
block
and
that's
the
documentation
talk
about
documentation
today.
Documentation
has
examples
of
like,
usually
they
put
them
in
the
in
the
in
the
ingress
and
the
examples.
That's
what
I
noticed.
A
They
don't
put
it
in
the
egress
section
as
an
example,
but
in
the
eager
section,
if
you
look
at
the
reference,
you
can
put
a
two
and
then
you
have
the
the
egress
to
the
cider
block
and
then
ip
block
put
a
cider
and
then
within
that
you
can
say
accept
so
with
even
with
that
that
slider,
if
you
make
it
very
large,
you
can
use
the
accept
to
say,
accept
this
except
this
except
this,
and
then
you
can
maybe
create
what
you
want
right.
A
Allow
allow
these,
except
these
things,
and
you
got
you-
can
have
your
mix
there
with
the
kubernetes
one,
if
you
so
give
it
a
try.
First
to
the
kubernetes
network
policies
like
archiset,
so
it's
it
supported
the
the
ip
block
it
supported,
except
best
practices
deny
deny
all
and
then
open
the
holes
where
you
want
access
to
be
allowed
to
to
go
to
somewhere.
That's
why
they
do,
if
not
look
at
great
open
source
alternatives,
right,
celium
and
network
policies.
Those
those
will
be
different.
A
Cd
crds
that
you
will
put
your
api
group
instead
of
like
the
kubernetes
one,
you
put
the
calico
one
or
the
or
the
celium,
and
then
that
will
give
you
maybe
matching
something
that
you
have
in
legacy
that
you
have
to
continue
using.
That's
the
only
reason
I've
seen
people
want
to
do.
This
is
like
they
have
certain
way
that
they
work
today
without
containers
and
they
move
into
containers
and
they
want
to
have
the
same
configuration.
Then.
A
Are
two
good
ones
any
other
thoughts.
E
A
I
know
I
know:
there's
a
new
network
policy.
Sig
network
is
working
on
new
network
policy
things.
I
don't
think
this
is
covered,
it's
more
of
like
the
the
global
network
policies
of
like
grouping
namespaces
like
namespaces
that
have
this
label
right
apply
this
network
policy.
Don't
don't
let
the
network
policy
network
policies
if
people
don't
know
is,
is
bounded
to
one
single
namespace,
correct,
yes,
and
but
if
you
want
to
that's,
that's
a
new
thing
that
I
don't
think
I
think
is
still
in
discussion.
A
So
if
you
want
to
join
that
conversation
and
learn
more
about
the
the
sig
join
the
state
network
and
net
network
policy
that
they're
having,
but
I'm
aware
that
they're
working
on
something
globally
where
they
can
say,
like
you
know,
namespaces
of
like
team
a
may
own
three
or
four
namespaces.
You
want
to
set
up
the
network
for
individual
namespaces
to
the
network
policies
at
that
granular
level
take
over
right.
A
So
maybe
you
have
one
you
have
more
governance
of
like
the
configuration
and
have
it
in
a
single
place
itself
like
if
you
have
I've,
seen
people
with
a
lot
of
namespaces
like
copying.
Namespaces
over
and
over
and
over
and
over
and
over
it
gives
repetitive
and
mistakes
happens
when
that
happens,
so
maybe
having
in
one
place
is
another
alternative,
so
yeah
if
anyone
to
contribute
and
network
policies
join,
join,
seek
network,
and
hopefully
that
will
be
one
of
the
six
that
we
have
in
the
office
hours.
A
So
with
that,
I
think
we
are
at
time,
so
I
want
to
give
a
chance
to
the
panel
to
either
comments
or
something
interesting
that
happened
lately,
that
they
want
to
share.
That
is
useful
or
some
event
that
is
happening
in
their
companies
before
we
end
the
episode
or
if
you
want
to
shout
out
for
your
sig,
if
you
belong
to
a
sick
and
you
want
like
join
my
sig,
my
seek
is
better
than
his
sig.
C
A
Mario
archie
chris,
so
I
mean
I
mean
in
sick
release,
I
guess
as
a
shadow,
so
I'm
going
to
shadow
something
about
6cli.
So
if
you
want
to
know
like
the
change
change
log
or
the
release
note
for
one
component,
usually
you
go
to
the
change
log
file
in
kubernetes.
You
see
this
huge
file,
you
there's
a
website
called
release,
release
notes
only
for
uris
nose
and
you
can
like
filter
by
the
version
of
kubernetes
and,
for
example,
keeps
detail.
A
So
you
can
actually
see
all
the
changes,
all
the
changes
to
gibson
tail
in
version
1.23
and
actually
we're
putting
there
in
the
1.24.
So
if
you
want
to
be
ahead
of
the
game,
I
want
to
see
what
are
the
new
things
in
gypsy
tails?
1.24,
you
can
click,
you
can
check.
1.24
click
cube
ct
and
you
will
see
actually
the
changes
to
give
ctl
and
a
very
easy
format
in
a
website.
So
that's
that's
my
plug
for
sick
release.
A
So
with
that,
thank
you
for
the
panel.
Thank
you
that
you
got
for
from
sick
dogs.
We
missed
rocket
today
as
a
host
so
because
of
the
mixed
up
of
the
time,
but
we'll
fix
it
for
april
and
hopefully
for
april.
I
think
maybe
we
will
do
it
around
the
release
date
of
1.24
and
maybe
answer
a
few
questions
of
darker
sheen.
I
heard
it's
a
thing
being
removed,
so
beware
of
dockercine
being
removed,
but
don't
be
scared.
A
If
you
read
the
talks,
you
read
the
blog,
so
there's
a
lot
of
blocks
coming
happening.
Sick
comes,
it's
crazy.
Sending
tweets,
I
think,
was
lately
so
follow
those
tweets
and
follow
the
blog
post.
So
thank
you.
Everyone
and
I
appreciate
the
volunteers
today
they
saved
my
life.
So
thank
you.
Everyone
bye.