►
Description
For more info see https://git.k8s.io/community/sig-docs
A
Yeah,
let's
record
the
cloud
hello:
everybody
today
is
Tuesday
January
25th.
It
is
704
a.m
here,
where
I
am
in
Vancouver,
BC
Canada
and
it's
probably
very
different
times
for
the
rest
of
you.
This
is
a
special
edition
of
Sig
doc.
Slash
Sig
release
realistically.
A
For
specifically
sorry
I
can't
do
two
things
at
once:
James
and
I
can't
do
it.
I
gotta,
stop
talking
and
then
I
gotta
do
it,
and
this
is
the
special
edition
of
this
meeting
for
the
docker
shim
removal.
Once
again,
this
is
a
recorded
meeting.
We
have
not
chosen
to
upload
it
anywhere
yet
formally
regardless
it
is
recorded
and
we
do
follow
a
code
of
conduct,
so
please
be
kind
to
each
other.
Now
I
can
kick
the
thing.
A
A
So,
for
those
of
you
who
were
unaware
or
not
around
I
am
leaving
my
current
position
at
the
Linux
Foundation.
This
is
my
last
week.
A
A
A
However,
at
this
point,
knock
on
wood
and
I-
don't
want
to
overestimate
or
underestimate
the
difficulty
of
this.
Our
biggest
task
is
actually
done,
and
that
was
essentially
checking
and
being
very
thorough
about
going
through
the
docks
to
make
sure
that
we've
captured
all
the
work.
That
needs
to
be
done,
and
we
have
done
that.
So
really.
What
we
need
to
do
going
forward
is
work
through
our
backlog
and
make
sure
that
everything
that
we
committed
to
gets
done.
So
it's
a
pretty
simple
operation
from
here
on
out.
A
A
Are
you
hoping
to
sort
of
be
assigned
a
ticket
for
work?
Are
you
just
sort
of
checking
this
out?
What
are
you
looking
for
from
me
in
this
meeting.
A
Okay,
okay
folks
want
to
be
assigned
work
all
right.
Okay,.
A
And
I
want
to
go
through
and
assign
your
work,
let's
just
kind
of
start
with.
A
Unassigned
tickets,
then
one
thing
I
will
note
for
you
Nate
just
right
now
is
there
are
a
lot
of
these
tickets,
which
have
been
assigned
my
first
order
of
business.
If
I
were,
you
would
be
going
through
all
the
assigned
tickets
and
if
somebody
hasn't
actioned
on
those
and
they've
had
the
ticket
for
a
week
or
two
I
would
cut
it
off,
I
would
remove
them
and
I
would
look
to
help
resign.
Those
okay,
I'm
gonna,
skip
these
top.
A
Two
one
is
collating
a
list
of
third-party
resources
on
the
topic,
though.
Actually
this
is
a
pretty
good
one
for
somebody
to
be
assigned
I'm
not
going
to
skip
it
so
collating
a
list
of
third-party
resources
on
the
topic.
This
is
actually
a
pretty
good
one
to
assign,
especially
given
that
I
believe
Microsoft
tweeted
out
or
wrote
an
article
on
all
of
this
as
well.
So
this
might
actually
be
very
timely.
A
The
goal
here
is
to
have
a
list
available
of
other
resources
on
the
topic
from
vendors
who
are
looking
to
help
their
like
manage
customers
handle
this
change,
any
other
blog
posts
on
the
topic,
etc,
etc,
etc.
So,
essentially
do
a
web
scour.
A
This
probably
is
beneficial
to
somebody
who
knows
the
the
overall
ecosystem,
particularly
the
managed
provider
ecosystem
pretty
well,
because
I
imagine
imagine,
managed
providers
in
their
blogs
or
where
we're
actually
going
to
find
the
most
content
on
this.
So
with
somebody
with
a
little
vendor,
familiarity
like
to
take
on
scouring
the
internet.
Looking
for
looking
for
stuff.
A
If
that's
something
you
want
to
do,
Please
assign
yourself
I
would
say,
spend
like
a
bit
of
time
on
this
be
thorough,
but
I
don't
like
this
is
about
going
out
and
finding
resources
that
we
haven't
created.
A
So
if
you
don't
find
much,
you
know
don't
scour
the
depths
of
the
internet.
Don't
turn
this
into
a
full-time
job,
be
timely,
do
your
best
and
we
will
probably
either
publish
this
resources
as
a
blog
post
or
other
piece
of
content,
so
be
prepared
for
the
follow-up
on
that.
Okay,.
C
Quick
comment:
I'm
not
able
to
assign
this
to
myself.
Could
you
add
me
as
a
contributor.
A
I
cannot
because
that
is
not
how
kubernetes
Works
can
I.
Can
you.
C
A
C
C
D
A
A
I
want
some
time
to
think
about
that
I'm,
not
ready
to
decide
that
yeah
and
the
part
of
the
reason
I'm
not
ready
to
sign.
That
is
because
I
thought
it
might
be
a
duplicate
Tim.
Do
you
mind
if
I
close
your
initial
issue,
because
I
think
I
have
a
you
know
what
no
I'm
not
gonna
deal
with
either
of
those
right
this?
The
second.
A
No
no
I
definitely
said
Tim
and
I'm
not
going
to
deal
with
either
of
those
right.
This
second
I
want
to
assign
content
issues.
Okay,.
A
So
this
is
a
small
collection
of
tasks,
they're
pretty
straightforward.
In
terms
of
what
needs
to
happen,
however,
there
is
an
action
around
removing
like
wholesale
tabs
that
were
that
talk
about
Docker
ee,
so
you
do
need
to
be
a
little
bit
familiar
with
how
the
templating
works
on
the
website.
It's
not
hard.
It's
it's
pretty
straightforward,
but
I
wouldn't
want
you
to
to
dive
in
unawares,
who
wants
like
a
nice
small
collection
of
tasks
to
take
care
of.
A
Okay
and
so
Chris,
just
like
with
Rolf,
let
me
drop
you.
The
link
to
this.
E
I
have
a
tip
for
anyone
who's
setting
up
a
non
Docker
environment.
You
know
like
locally,
if
you're,
using
mini
cubos
on
the
tool-
and
you
end
up
with
a
container
de
docker
free
environment-
keep
it
around
because
there
might
be
PR's
to
review
and
having
that
environment
around
is
going
to
be
handy
to
like
oh
yeah,
I
tested
this
and
you're
right.
E
That
is
the
sample
output
kind
of
thing,
especially
the
longer
you
spent
fixing
a
place,
the
more
it's
worth,
keeping
a
script
around
or
just
keeping
the
thing
running,
or
what
paused
or
whatever
last.
C
A
A
Okay,
it's
going
to
be
this
is
a
slightly
more
involved
update
if
I
recall
correctly,
recreate
the
code
sample
under
code
containers,
lifecycle,
hooks
debugging,
hook,
handlers
if
I
recall
what
this
change
was
and
I'm
just
gonna.
A
I
would
take
the
opportunity
to
maybe
just
like
revisit
this
topic
in
general,
but
really
this
is
just
regenerating
the
test
output
with
containerdy.
This
is
actually
pretty
trivial.
You
know
what
no.
This
is
Trivial.
The
more
I
think
about
this
is
actually
pretty
extraordinary.
Show.
A
That's
pretty
trivial
and
I'm
actually
going
to
Priority
backlog
that
one
because
it
is
the
update
needed,
is
like
removing
phrases
like
error
executing
a
Docker
container.
That's
not
really
going
to
trip
anybody
up.
That's
probably
gonna,
be
fine,
so
I'm
not
going
to
bother
our
pretty
little
heads
Okay,
who
wants
like
a
chewier
writing
task.
A
So
this
is
a
rewriting
one
of
the
high
level
concept,
Pages
very
specifically
around
the
idea
of
a
container
environment.
Surprise:
surprise,
because
when
this
page
was
written,
I
think
Docker
was
really
the
only
container
environment
available
as
such,
it's
a
pretty
short
topic,
but
it's
very
intertwined
with
the
idea
of
Docker
and
just
needs
to
be
Rewritten
in
a
more
General
manner.
A
A
No
I
think
this
is
a
really
good
fit
for
your
particular
skill,
set
once
again
slash
a
sign
leave
a
comment,
saying
slash
a
sign
in
this
ticket,
and
it
will
be
yours
and
just
as
a
reminder
for
everybody
who
is
on
this
call
when
you
are
going
through
the
process
of
actioning
and
opening
items
on
this
ticket
and
the
like.
The
pr
review
process
is
exactly
the
same
as
it
would
be
for
any
other
ticket.
A
It
is
not
special
because
this
is
a
dog
or
shim
removal
thing
unless
you
have
been
otherwise
told
so
you
open
a
PR.
The
people
who
approve
it
are
sort
of
the
reviewers
of
the
week.
If
you
need
technical
review
tag,
signode
or
tag
the
the
area
or
the
Sig
responsible
for
the
functionality
that
you're
working
on
there
are
a
few
exceptions
to
this
rule.
A
So,
for
example,
if
you're
writing
a
blog
post
specifically
around
all
of
this,
that
probably
needs
a
particular
set
of
eyes
of
your
writing
documentation,
very
specifically
about
the
migration
itself
or
about
migrating
itself.
That
needs
a
particular
kind
of
review,
but
for
the
most
part,
these
are
routine
updates.
Okay,
everyone,
okay!
A
A
Yeah
I
got
my
so
this
is
another
one,
which
is
a
conceptual
rewrite
once
this
will
once
again,
if
you
want
to
sort
of
practice
your
conceptual
documentation
writing.
This
is
actually
a
really
really
good
task
to
take
on.
Similarly,
if
you
want
to
like
study
for
the
cka
exam,
it's
solid,
this
is
a
much
longer
page
and
as
a
result,
it
is
a
much
longer
rewrite.
A
So
this
is
the
conceptual
page
on
container
images
and
surprise.
Surprise
is
very
intertwined
with
ideas
of
Docker,
because
when
kubernetes
was
created,
that
was
kind
of
like
where
you
were
getting
your
container
images
from
so.
A
What
I
suspect
the
writer
of
this
is
going
to
have
to
do
is
differentiate
between
Docker
as
a
platform
Docker
engine
and
be
able
to
sort
of
tease
those
pieces
apart
and
I
have
a
feeling
that,
in
the
process
of
this
you're
going
to
probably
want
to
rewrite
large
portions
of
this
foreign.
E
A
E
A
If
I
recall
correctly,
you
are
like
a
technical
writer
right,
Abby,
yes,
I
am
okay
yeah.
This
you'll
be
able
to
do
this.
I
promise.
A
It
is
very
much
a
writer's
task
more
so
than
it
is
like
a
developer's
task.
So
I
think
you
are
actually
really
well
suited
for
this.
A
A
Just
so
that
you
fully
understand
the
change
needs,
so
the
change
is
needed.
So
if
I
were
you
Abby,
I
hope,
Abby's,
probably
an
appropriate
Abigail.
How
I
would
approach
this
is
I
would
read
through
the
topic.
I
would
sort
of
identify
where
we
start
talking
about
Docker
and
then
what
you
want
to
do
is
figure
out
how
to
tease
apart
what
component
of
Docker
we're
actually
talking
about
and
make
your
changes
appropriately.
A
I
think
this
particular
update
is
going
to
be
a
blend
of
being
more
specific
about
what
part
of
Docker
we're
talking
about
like
whether
it's
Docker
compose
versus
like
Docker
registry
versus
Docker
engine,
as
well
as
actually
removing
mentions
of
Docker
and
just
sort
of
saying,
contain
rise
or
use
a
container
image
and
just
being
more
General
in
our
language.
I
have
a
feeling
it's
going
to
be
a
bit
of
column,
main
column
Beyond
this
one.
Okay,.
A
E
C
A
A
And
I
think
this
is
the
last
one
that
I'm
actually
gonna
assign
for
today,
and
this
is
another
one
of
these
ones
that
I'm
actually
a
little
worried
about.
So.
A
A
Down
Tabitha
for
this,
that's
actually
what
I
was
gonna
say.
Cat
the
nature
of
security
in
kubernetes
is
that
it
is
a
pretty
domain.
Knowledge
is
required,
I
guess,
Bob.
You
raised
your
hand,
yeah.
B
The
one
thing
this
might
not
be
too
I'd
have
to
check
on
the
current
state
of
the
PSP
replacement,
but
this
might
not
actually
matter
too
much
in
the
grand
scheme
of
things.
Oh.
B
A
Yeah,
so
the
other
thing
that
I'm
gonna,
say
Nate
by
the
way
is
these
are
all
updates
in
relation
to
the
124
release
and
as
such,
all
things
are
responsible
for
doing
their
own
updates.
A
So
the
I
think
our
recourse
in
this
is
I'm
going
to
post
this
Tuesday
security
and
say
I.
Don't
think
that
we
have
the
domain
knowledge
to
make
this
update
ourselves.
However,
it
does
need
to
be
done
in
relation
to
the
124
release,
so
please
triage
evaluate
and
make
the
update.
Thank
you
bye,
so
I
think
that's
where
we're
going
I.
A
C
C
A
Is
it
is,
it
was
a
screenshot
of
Valerie,
Lansing
and
Seth
macombs,
but
I
have
no
idea
how
I
did
that
either
goddamn,
okay.
A
A
A
Because
you're,
all
wonderful
adults,
if
you
did
not
get
assigned
a
ticket,
please
look
at
the
project
board
in
your
own
spare
time.
Please
look
at
the
bath
plug
and
pick
something
that
matches
your
interests.
A
So
next
week,
you'll
be
hosted
by
Nate,
okay,
peace
out,
lovely
people.
D
Kind
of
quick,
quick
question
sure
so
I
was
gonna.
Ask
Nate
this
because
this
kind
of
overlaps
with
the
work
we're
doing
for
the
release.
A
Maine
there's.
A
Yeah
I
initially
wondered
if
we
should
do
them
against
the
release
Branch,
but
these
aren't
going
to
be
breaking
for
123
necessarily
and
the
release
branch
has
to
track
a
bunch
of
important
things
and
we
just
sort
of
decided
to
make
it
less
complicated
for
the
people
who
were
specifically
tracking
against
the
release.
B
B
So
like
there
is
one
of
the
things
in
the
conversation
in
slack.
We
were
talking
about
it
and
so
like
we
like,
if
they're
emitted
from
123
in
the
future
that
will
make
like,
could
potentially
make
it
harder
for
people
to
like,
like
fully
migrate
like
for
smaller
things,
no
big
deal,
but
for
for
larger
things.
I
would
at
least
put
the
pointer
in
towards,
like
our
docs
on
Docker
shim
replacement,.
C
D
B
This
specific
came
up
in
the
runtime
class,
where
Docker
is
an
option
in
it
where
the
the
question
came
up.
C
Have
mixed
feelings
on
that
right,
like
if
people
are
reading
the
docs
today
and
they're
on
latest
right
and
they're,
assuming
they'll
always
be
on
latest
for
whatever
reason
like
we're?
If
we
leave
the
big
stuff
behind
they're
going
to
start
new
things,
I
mean
I,
understand
versioning,
don't
get
me
wrong,
but
I'm
concerned
about
the
implications
of
doing
that.
B
Like
like,
for,
instead
of
just
like
blanket
removing
it,
the
the
sections
that
might
talk
about
like
Docker
as
it
stands,
right
now
like
if
you
don't
have
a
suitable
replacement,
like
that's
what
I
think,
where
the
like
having
the
warning
or
the
the
header
that
just
says
like
hey,
go
look
over
here,
because
this
is
this
is
gonna.
Get
you
know,
removed
in
like
three
months,
yeah.
A
You
know
so
at
least
for
the
sections
that
I
checked
Bob.
There
really
isn't
actually
anything
like
that.
Oh
surprisingly,
there's
a
lot
of
small
things
where
it's
like.
Oh,
we
need
to
update
some
steps
in
a
tutorial
and
in
that
regards
updating
to
say
cry,
CTL
or
containerd.
A
A
What's
really
gonna
throw
people
for
a
loop
is
if
they're,
using
Docker
in
their
day-to-day
like
in
that
particular
workflow
and
they're
gonna
have
to
switch
tools,
but
in
terms
of
like
how
kubernetes
actually
works,
I
think
we've
probably
slowly
been
moving
away
from
it
for
a
while,
and
now
it's
just
for
kind
of
sweeping
up
a
lot
of
details.
So
surprisingly,
fingers
crossed
it's
actually
not
that
dramatic.
Surprisingly,
but.