►
From YouTube: Kubernetes SIG Windows 20200922
Description
Kubernetes SIG Windows 20200922
A
A
A
A
A
Currently
it's
compiled
into
the
cubelet,
where
container
calls
talk
to
docker
over
the
docker
api
directly
and
that
there's
been
a
lot
of
workarounds
in
kind
of
the
docker
shim
code
path
and
the
cubelet
code
path
in
general.
Some
of
them
are
for
windows.
Some
of
them
are
actually
for
other
kind
of
architectures
of
projects
and
because
of
that,
there's
it's
been
kind
of
identified
as
hard
to
maintain.
A
So
the
current
proposal
is
to
take
that
docker
ship
code,
and
I
think
the
first
steps
were
just
to
have
build
flags
in
kubernetes
to
not
build
it
and,
I
believe,
there's
a
docker-less
environment
variable
you
can
set
when
you're
building
the
cubelet
and
that
will
cause
the
docker
shim
to
code
to
not
get
built
in
favor
of
using
cri
code.
Pass
cri
stands
for
the
container
runtime
interface
and
it
was
meant
to
be
a
more
general
and
extensible
way
for
different
container
runtimes
to
plug
into
kubernetes.
A
Some
of
the
issues
that
we
have
specifically
with
windows
and
the
cri
and
docker
shim
are
that
well
there's
a
couple
things.
One
is
that
the
docker
itself-
and
this
is
because
so
docker
uses
the
mobi
moby-
has
its
kind
of
container
runtime
platform
under
the
hood,
and
the
mobi
platform
only
currently
supports
running
talking
to
windows
over
the
hcs
v1
protocol,
which
is
kind
of
old
and
outdated.
A
A
I
think
that
was
probably
about
18
months
ago,
and
that
was
when
container
d
was
very,
very
kind
of
early
development
for
windows,
and
that
has
been
completely
kind
of
untested
and
unmaintained.
So
there's
still
some
kind
of
unknown
or
ambiguity
around.
If
that
will
work,
but
so,
more
importantly,
the
way
that
you
configure
the
cube,
what
to
use
either
docker,
shame
or
a
different
container
runtime
is
with
a
fl,
a
docker,
a
cubelet
flag
called
container
runtime,
and
that
has
two
values.
A
Those
two
values
are
docker
and
remote
and
if
you
specify
the
remote
and
point
you're
expected
to
give
it
a
grpc
address
for
or
just
an
address
for
how
docker
or
how
the
keyboard
can
talk
to
the
container
runtime
and
that's
and
that
kind
of
triggers
the
cri
code
pass
with
windows
in
particular,
there's
a
number
of
switches
in
the
cubelet
code
base,
both
in
docker
shim
and
outside
of
docker
shim.
That
check
to
see
if
the
container
run
time.
A
But
if
that
variable
is
set
to
docker
or
not,
and
if
it
is
such
a
docker,
it
triggers
some
docker
specific
behavior,
which
was
needed
to
kind
of
help
kind
of
bootstrap.
The
windows
containers
in
general,
in
addition
to
some
of
the
end
most
of
those
kind
of
tweaks,
are
that
I
was
able
to
see,
are
just
related
to
a
path
kind
of
path,
massaging
either
replacing
backslashes
with
forward
slashes,
vice
versa
or
appending
the
a
volume
letter
to
those
pads.
A
A
A
The
the
default
timeout
for
scraping
the
metric
send
points,
and
that
would
result
in
a
number
of
things
like
cube,
control
top
to
stop
reporting.
Metrics
for
windows,
notes
and
also
it
would
prevent
a
horizontal
pot,
auto
scaling
from
working,
which
is
a
kind
of
a
big
draw
for
kubernetes
and
you
in
the
use
cases
there.
A
So
the
in
addition
to
all
of
that.
So
those
are
some
reasons
why
kind
of
windows
in
particular,
is
interested
in
this
docker
shim
deprecation
discussion
is
that
currently
container
d
is
the
only
runtime
that
kind
of
is
supports,
being
run
over
the
cri
interface
for
and
has
windows
support,
and
this
is
still
kind
of
an
experimental
feature
for
kubernetes
we're
saying
it.
A
So
that
made
sense
and
also
say,
cluster
life
cycle
life
cycle
expressed
some
concern
for
updates,
because
right
now,
the
sierra
it's
not
really
documented
how
to
uptake
an
existing
cluster,
that's
using
one
cri
or
or
docker,
and
upgrade
it
to
use
a
different
one.
It
was
always
kind
of
assumed
that
nodes
and
node
builds
would
just
be
created
with
a
single
container
runtime
and
and
that's
it.