►
From YouTube: Kubernetes SIG Windows 20200218
Description
Kubernetes SIG Windows 20200218
A
A
A
D
E
A
B
D
I
think
at
this
point,
I
haven't
heard
of
any
decisions,
but
it's
the
matter
of
freely
linking
people
together
and
making
sure
that
we
are
all
on
the
same
page.
I
was
on
I
mean
I
was
planning
on
writing
a
document,
a
draft
document
to
start
with
and
to
start
all
the
discussion
with,
but
I
haven't
had
the
chance
to
do
it
just
yet
I'm
planning
on
reserving
time
this
week
to
do
it.
Okay,.
B
F
G
The
QA
DM
in
bootstrap
and
upgrade
is
different
from
what
Jocelyn
is
coming
with.
Jocelyn
is
like,
if
you
want
to
do
it,
for
enabling
Windows
in
cluster
API
I,
think
we
should
do
it
in
a
way
where
every
provider
like
Google
Amazon,
Microsoft
VMware,
everybody
can
use
it.
So
we
are
thinking
of
going
up
with
the
proposal
to
do
that
for
Windows,
whether
to
use
cloud
in
eight
days
or
Clower
unattained
or
like
whatever.
H
A
I'll,
let
you
guys
also
sync
offline,
then
and
come
back
and
talk
about
that.
So
the
next
issue
on
and
we'll
have
a
few
peers
that
we're
going
to
discuss
right
after
this.
But
the
next
issue
was
around
lock,
monitor
mark
you
when
I
look
into
dogs
from
MSDN
opportunities
to
link
to
github
or
basically
add
that
into
as
more
field
section
in
our
documentation
for
SiC
windows.
Did
you
get
a
chance
to
look
into
that
yeah.
F
I,
just
posted
the
link,
so
that's
on
the
the
the
project
is
on
github,
so
I
think
it
might
make
sense
to
just
link
to
the
github
readme
page.
It
wasn't
really
really
stun
MSDN,
so
I
think
that
there
were
some
concerns
about
that
content.
Changing
I
think
I
have
less
concerns
about
the
readme
quemic
up
to
date
on
github,
but
other
than
that.
F
A
F
F
A
F
A
A
I
I
took
a
look
at
it,
had
some
comments
that
I
believe
or
no
he
addressed,
and
so
yes,
someone
else
took
a
look
at
Anthony,
yeah
Anthony,
oh,
not
like
he
address
them
already.
Someone
else
took
a
look
at
it.
Well
took,
look
as
well
and
I
think
the
picker
is
in
decent
shape.
I
did
make
a
comment
that
we
need
some
each
retest,
so
that
needs
to
be
it.
I
I
I
This
is,
if
you
like,
the
Uruk
you
saying
and
this
texture
so
to
change,
but
other
than
that
it
didn't
seem
like
it
was
doing
too
many
changes
pretty
much
just
adding
a
name,
a
name
pipe
for
some
of
the
device
discovery
software
the
plugins
can
come
and
attach
to
not
to,
unlike
the
plugin
watcher,
that
we
did
for
si
si
grazie.
So
in.
I
B
A
A
A
B
A
B
F
A
B
B
F
And
most
can
probably
help
fill
in
some
details
to
you,
but
so
what
happened
was
for
the
last
Patch
Tuesday
and
you'll
see
a
lot
of
references
to
to
B
and
those
are
just
the
February
windows
patches.
There
was
a
regression
where,
without
going
through
many
details,
you
couldn't
start
containers
that
were
patched
with
the
February
patches
on
hosts
that
were
older
than
that
didn't
have
also
the
February
patches
so
and
on
Tuesday.
F
At
about
2
p.m.
the
Microsoft
team
published
container
images
with
the
to
be,
or
with
the
February
patches
to
MCR
and
an
updated
all
of
the
quote-unquote
latest
tags,
so
LTS,
C,
2019
or
1809,
and
for
the
nano
server
and
server
core
image
and
then
quickly.
Following
that,
a
bunch
of
other
teams
in
Microsoft.
They
did
their
images,
including
the
dotnet
images.
F
So
since
then,
they've
I
think
that
they
still
kept
the
the
container
tags
pointing
to
the
January
patches
and
are
trying
to
figure
out
exactly
what
what
to
do
here.
I
think
that
they
have
have
another
round
of
patches
that
make
it
so
the
container
images
will
start
so
that
February
patch
level
container
images
will
start
on
January
or
previous
hosts,
but
they
have
so
there's
still.
Some
questions
about
compatibility,
I.
F
Think
that
there's
a
known
issue
where,
if
you're
on
a
February
host,
there
may
be
issues
with
January
or
previous
container
images
around
some
of
the
while
3:2,
while
layer
and
32-bit
containers
that
are
still
looking
at
so
because
of
that,
there's
still
kind
of
this
big
question
about
compatibility
and
host
and
container
compatibility
and
the
only
guy.
The
only
definitive
guidance
right
now
is
to
run
the
same
patch
level
in
the
container
ends.
The
host
and
I
think
that's.
This
is
still
kind
of
evolving,
but
this
is
rather
unfortunate.
F
I
know
it
took
out
a
bunch
of
our
tests,
great
jobs
for
about
48
hours.
Well,
the
container
tags
are
published
or
while
the
container
tags
were
still
pointing
to
February,
but
this
also
kind
of
leads
to
a
question
of
how
do
we
keep
tests?
The
test
images
in
that
we're
using
kind
of
in
step
with
the
host
images,
and
how
do
we
safely
do
this
transition
from
January
pension
to
February
pageant.
A
F
So
our
teams
testing
and
have
not
found
any
compatibility
issues
if
you
are
on
the.
If
your
host
is
on
the
February
I
know
if
you're,
if
your
host
is
on
January
and
your
containers
are
on
February,
you
should
be
fine,
but
there
may
be
some
issues
if
your
host
is
on
February
and
your
containers
are
prior
to
February,
but
that
will
be
fixed,
ultimately
I,
don't
know
I
think
I
may
be.
They
may
not
be
able
to
fix
that.
That.
A
F
J
A
F
A
F
J
J
B
B
B
Okay,
well
we'll
try
to
reach
out
to
them
on
slack
and
see,
but
because
February
images
may
be
published
or
updated.
I
think
we
want
to
just
like
pin
to
something
stable.
So
that
way
we
can
make
sure
that
we're
not
introducing
bugs
and
the
kubernetes
repo
first
and
then
move
forwards.
The
new
Windows
Server
version
in
another
week
or
two
does
that
make
sense.
K
K
F
K
A
F
I
think
it's
that
one
should
be
pretty
straightforward:
I
had
to
remove
a
lot
of
code.
Well,
I
removed
a
lot
of
code
in
some
test
code,
because
all
of
there
was
a
bunch
of
tests
making
sure
that
you
could
drop
the
fields
which
started
failing
so
I.
Think
that's
the
only
that's
the
bulk
of
the
PR
yeah.