►
Description
For more info see https://git.k8s.io/community/sig-docs
B
A
Everybody,
it
is
a
shockingly
bracing
7
A.M
here
on
the
Pacific
coast
of
North
America.
This
is
a
special
edition
of
Sig
docs,
specifically
around
tasks
to
do
with
the
124
removal
of
Docker
shim
I
will
be
hosting
today's
meeting.
My
name
is
Celeste
Horgan.
This
is
a
recorded
meeting
and,
as
all
meetings
do
it
follows
the
kubernetes
code
of
conduct
so
be
nice
to
each
other,
and
if
you
aren't
nice
Please
be
aware
that
we
are
recording
this.
A
So
you
know
I,
guess
the.
D
A
Unless
you
want
to
get
listen,
we'd
try
not
to
practice
what
a
Discord
we
try
not
to
practice
punitive
removals
in
the
community
unless
we
actually
have
to
we
try
to.
We
actually
do
spend
like
most
of
our
time,
trying
to
talk
people
into
or
talk
people
through
being
nice
people
rather
than
yeah,
okay,
okay,
so
I
have
not
dived
into
this.
Since,
before
the
Christmas
break,
however,
I
did
see
that
our
first
blog
post
was
published.
A
That
is
awesome
cat
since
you're
on
the
call
I
think
our
our
next
blog
post
that
we
wanted
to
have
up
was
essentially
the
quick
and
dirty
how
to
know
Frills.
This
is
about
what
you
need
to
do
to
get
a
operating
124
cluster.
What's.
C
Up
yeah,
so
that
is
what
is
happening.
Just
Bare
Bones,
very
I'm
gonna
try
to
keep
the
the
Frills
minimal,
which
is
Believe,
Me,
difficult,
I'm,
a
verbose
person,
but
it's
just.
This
is
how
you
get
a
one,
two
four
cluster
up
and
running.
If
you
are
already
running
on
one
two.
C
Three
like
this
is
what
it
could
potentially
look
like
when
you
upgrade
to
one
two
four
problems
you
might
run
into,
but
specifically
focusing
on
problems
you
might
run
into
you
know
around
Docker
shim,
not
General,
upgrade
issues
I
plan
on
having
that
I
would
I
plan
on
having
a
draft
of
that
done
at
the
end
of
this
month.
C
Okay,
for
people
to
to
look
at
and
then
yeah
I
think
we
should
aim
to
roll
that
out
as
soon
as
possible,
like
one
Docker,
shim
blog
is
already
like
kind
of
ready
to
fire
right.
Okay,.
A
Yeah,
so
that,
actually,
that
one
went
up
last
week
as
I
recall,
I
saw
that
go
by
on
Twitter.
So
thank
you
all
for
not
waiting
for
me.
I
appreciate
it
continue
to
not
wait
for
me
on
things.
A
The
other
thing
I'm
gonna
check
on
while
I'm
here
is
our
lovely
little
umbrella
issue,
because
we've
still
got
some
open
tasks
here.
Okay,
so
for
those
of
you
who
are
unaware,
the
first
check.
The
first
step
in
this
process
was
checking
through
all
of
the
content,
somewhat
manually
somewhat
using
like
control
F,
just
because
of
the
nature
of
certain
things
getting
imported
and
assessing
where
we
actually
have
mentions
of
Docker
that
we
can
untangle
for
the
most
part.
A
From
what
I've
seen
and
again,
we
have
not
checked
on
this
prior
or
I
haven't
touched
on
this
since
December,
so
we're
a
little
behind
for
the
most
part.
Most
of
these
removals
are
actually
pretty
straightforward.
We
don't
have
a
lot
of
straight
up
calls
to
like
Docker
up
or
Docker
compose
or
whatever.
So
it's
actually
not
that
bad.
A
There's
a
couple
of
like
topics
that
just
need
to
be
full
on
Rewritten.
At
this
point
that
I
personally
found
just
because
they're
a
little
honestly,
the
sense
that
I
get
is
that
they
were
written
like
six
years
ago
when
Docker
was
like
the
only
option
and
they
were
so
conceptually.
They
used
Docker
quite
heavily,
and
it's
just
a
matter
of
like
rewriting
those
in
general
because
they're
a
little
outdated
at
this
point.
A
That
would
be
my
advice
and
to
do
for
today,
and
that's
probably
what
I'll
start
taking
care
of
later
today
as
well.
Okay,.
E
Celeste
yeah:
are
there
any
two
questions
on
that?
Are
there
any
things
that
people
wish
you'd
like
prioritized
out
of
the
umbrella
issue?
That's
question.
One.
A
For
people
on
this
call
specifically
because
this
because
y'all
are
the
Troopers,
which
is
why
you're
here
at
various
awkward
hours
of
your
day,
I,
would
love
if
somebody
could
take
over
checking
the
API
references.
So
everything
in
this
references
section
below
needs
a
look
and
I
would
like
somebody
who
is
more
experienced
to
look
through
those
because
one
those
are
fairly
crucial
pieces
of
the
documentation
to
any
changes
that
need
to
happen
as
a
result,
because
those
are
all
auto-generated.
It
just
needs
a
bit
more
experience.
A
I
don't
want
to
throw
it
at
somebody
new,
there's
more
potential
to
go
wrong
in
the
with
anything
in
the
references
section
than
there
is
with
like
anything
above
it.
So
so,
if
you're
looking
for
a
task,
Tim
I
would
love
if
you
could
kind
of
Shepherd
little
over
a
half
through
okay.
Thank
you,
I
appreciate
it.
E
A
A
So
I'm
gonna
look
through
what
fell
out
of
all
of
those
for
the
Sig
docs
meeting
later
today,
and
just
pull
them
out
and
say
like
if
you
want
an
issue
to
work
on
pick
this
up,
because
I,
don't
nothing
I
saw
come
through.
Those
was
like
particularly
glaring
or
particularly
worrying.
A
So
that's
what
I'm
going
to
do
for
later
today
that
and
I'm
going
to
clean
up
our
issue
board
a
little
bit
James.
Do
you
have
any
question
from
a
Sig
release
perspective.
D
Not
explicitly
okay,
so
it's
my
main
thing
is:
what
what
can
we,
as
part
of
the
release,
do
to
help
and
I
mean?
Obviously,
a
big
part
of
that
is
is
going
to
be
comes
and
dark.
That
native
lovers
are
going
to
be
going.
D
Throughout
the
release,
but
also
release
notes
as
well.
D
A
I
think
so
long
as
you're,
able
to
sort
of
for
lack
of
a
better
word
keep
the
rest
of
the
release
away.
From
from
this,
that's
probably
gonna.
E
F
F
A
B
C
Bang
out
an
11
tweet
thread
when
you're
not
thinking
it's
six
in
the
morning,
I'm
not
having
coffee
yet
and
then
all
of
a
sudden
you're
in
El
Reg.
That's
what
that's
what
you
do,
but
actually.
Actually,
though,
that
is
like
a
difficult
thing
to
do,
because
you
know
we
can't,
we
can't
see
what
we
can't
see
and
you
don't
know
what
you
don't
know
and
experts
like
super
easily
forget
what
it's
like
to
not
know
what
the
hell
they're
doing.
So
that
is
like
a
really
delicate
thing.
C
But
it
is,
it
is
a
hard
thing
to
solve,
for
I
saw
the
most
drama
from
software
Engineers,
who
don't
actually
touch
kubernetes
at
all,
but
know
that
they
use
Docker
at
work
like
that
was
by
far
the
largest
and
most
panicked
demographic
with
the
original
drama.
So
that
is
something
we
should
watch
out
for.
C
Yeah
like
like
by
oops
by
far
the
most
common
reaction
from
these
people
was
like,
is
Docker
dead
and
it
got
it
got
very
dramatic
people.
People
assumed
that
like
kubernetes
was
killing
docker
there's
a
lot
of
conflating
of
Docker
and
kubernetes,
and
there
is
a
pretty
widespread
lack
of
understanding
that
a
Docker
container
is
not
a
real
thing
which
is
partially
marketing
on
Docker,
slash,
morantis's
part,
but
yeah.
A
And
that
is
actually
one
thing
to
note
for
James
and
for
the
other,
releasing
folks
I
think
you
said,
Mickey
is
one
of
them.
Hello
nice
to
meet
you
stupid
and
I
should
have
warned.
A
I
should
have
warned
the
folks
who
did
the
first
blog
post,
but
I
brain,
not
on
correctly
in
late
December,
because
there
is
maybe
we
don't
want
to
post
this
recording
by
the
way,
because
there
is
some
delicacy
there
with
Docker
with
morantis
with
how
both
of
those
companies
are
positioned
in
relation
to
kubernetes
and
cncf,
and
there
has
been
a
bit.
The
media
loves
to
pit.