►
From YouTube: Kubernetes SIG Windows 20200519
Description
Kubernetes SIG Windows 20200519
A
Hello,
everybody
and
walk
up
to
another
sick
Windows
meetup,
it's
their
19th
of
May.
Remember
this
is
a
recorded
meeting,
so
please
adhere
to
the
SNCF
code
of
conduct
as
well
and
let's
get
started
so
119
is
underway
who
have
new
milestones
and
new
dates.
I
know
if
you've
seen
it,
but
one
119
will
ship
in
early
August.
So
that
gives
everybody
a
few
more
weeks
of
runtime.
In
terms
of
you
know,
getting
their
PRS
kidding
the
ratios.
Getting
everything
set
up.
That's
gonna
help.
A
A
The
deadline
was
last
week
if
you
were
interested
in.
If
you
had
a
session
for
for
the
virtual
cubicle
event,
the
deadline
was
last
week
to
make
sure
that
you
accepted
or
denied
client
your
sessions
from
sick
windows.
I
accepted
the
one
that
me
and
Mark
are
doing.
I
don't
have
any
insight
into
the
other
session,
hopefully
was
accepted
as
well.
I
guess
Mazur
you're
I
think
you're
the
owner
of
the
second
session.
Did
you
accept
it.
B
A
B
A
And,
let's
see
what
dates
they
give
us
and
what
times
my
problem
was.
Are
we
just
coming
back
from
vacation
if
the
vacation
ever
happened?
So,
let's
wait
and
see
I
mean
I
could
just
probably
create
this
issue
much
earlier
and
I'll
work
with
mark
to
has
some
other
personal
things
going
on
we'll
figure
the
Adam
I'm
I'm
not
worried
these.
Are
you
know,
given
the
fact
that
you
know
you
pre-recorded,
you
have
a
lot
of
freedom
to
figure
out
how
to
do
this
thing.
You
don't
have
to
be
live.
A
A
Given
there's
no
travel,
if
someone
wants
to
actually
do
it
them
or
something,
if
folks
just
come
to
me,
amaz,
let's
talk
about
it
but
I'm,
assuming
math
and
you're
one
you're
gonna
talk
a
little
bit
about
container
D
you're
gonna
show
some
of
the
work.
That's
happening
there
and
kind
of
excite
people
on
what's
coming
up
next
and
one
of
the
biggest
things
I
want
to
see.
That
is,
we
want
to
tell
them.
You
know
why
is
continued
the
important
for
you?
What's
that?
A
What's
experience,
gonna
change
and
what
are
things
are
gonna,
come
by
the
right
from
performance
from
security
from
information
that
you
get
from
observability
all
those
things
that
come
with
container
D
the
ability
to
add
hyper-v
isolation
in
the
future
or
all
those
things
you
know
we
need
to
highlight
on
them
so
that
they
can
get
excited
about
it.
Yeah.
C
A
A
C
Freeze
I'm,
just
letting
everybody
know
the
kept
enhancement
freezes
today
and
for
people
who
haven't
been
following
there's
a
new
section
that
has
been
added
to
the
kept
templates
for
production
readiness
review
section
that
it's
I
think
it's
optional
for
EPS
this
round.
But
it's
going
to
start
to
become
required
and
there's
different
levels
of
there's
different
sets
of
questions
depending
on
what
milestone
you're
targeting
for
release.
So
just
keep
that
in
mind
if
anybody's
authoring
or
updating
cups
and.
A
By
the
way,
Dinesh
just
brought
up
on
the
slack
on
the
sorry
are
there
on
the
chat
that
the
removal
of
the
mud
multiple
end
point
calls
is
huge,
win
container,
D,
absolutely
and
I
know
the
folks
from
cloud
base
have
been
waiting
for
that
for
obvious,
that
was
a
thrown
on
the
side
of
a
lien
and
others.
So
you
know
huge
one
Dinesh,
it's
gonna
be
a
huge
huge
win.
There.
A
A
C
E
A
F
C
I
think
if
there's
not
significant
changes
between
the
at
least
the
user
facing
scenarios
for
Windows
and
Linux,
it
should
be
fine
to
reuse
the
same
cap
if
there
are
going
to
be
significant,
I
guess
user
facing
scenarios
or
differences
that
might
be
when
did
do
another
cap
but
I'm
guessing.
That's
not
the
case
here.
Yeah.
E
C
E
E
A
A
They
confirm
there's
no,
nothing
specifically
for
one
ten
nineteen
deliverables
for
for
CSI,
so
they
just
basically
continue
working
on
it
all
right.
There's
the
sick
windows
questions
for
contribute,
experience
interview
as
we
know,
might
to
do.
For
a
few
days
now,
I
had
a
chance
to
review
it.
I
need
to
think
you
probably
mark
I.
Did
it
here,
so
everybody
else.
If
you
have
questions
you
can
add
or
comments,
please
do
that.
Did
they
give
us
an
ETA
mark
for
when,
when
we
have
to
be
able
to.
C
I
think
that
they
said
that
they
were
going
to
give
us
until
this
week
because
they
were
busy
with
enhancements
in
just
general,
okay
life
cycle
stuff.
Alright,
I,
don't
think
that
there
was
an
ETA
but
I
think
that,
probably
by
the
end
of
this
week
it
would
make
sense,
yeah,
I
I
need
to
go
and
add
in
a
few
more
telling
a
few
more
other
questions.
Yeah.
A
C
I
did
so.
This
is
a
peer
that
we've
been
tracking
for
a
while
that
we
need
in
order
to
pass
the
right
information
into
the
continuity
run
time
to
pull
the
correct,
pause
image
and
start
sandbox
Azure,
with
the
same
or
with
the
correct
kernel
version
to
run
with
hyper-v
isolation
that
PR
merged
I'd
wanted
to
just
update
folks
here,
I
think
the
next
steps
for
this
work
for
enable
and
continue
or
hyper-v
isolation
is
work
in
the
container
D
layer
and
there's
some
folks
from
the
windows
container
platform.
A
E
A
E
A
E
F
G
C
Added
that
last
one
so
Kel
on
Friday,
just
messaged
to
me,
saying
that
there
was
a
discussion
in
the
last
Thursday's
Signet
working
meeting
around
changing
the
behavior
of
how
host
names
get
set
in
pods
and
wanted
well
to
know.
If
we
were
aware
of
this
and
I
thought,
I'd
bring
it
up
here
for
comments
to
see
if
anybody
in
sig
windows
who
had
any
concerns
with
this,
he
mentions
that
there
was
no
kept
for
these
changes
so
that
might
slow
these
down.
A
So
there's
kind
of
two
things:
I
came
to
mind
when,
when,
when
you
mentioned
this
marked
the
first
one
is
you
need
to
make
sure
the
windows
tests
are
passing
right,
so
whatever
PR
they
have,
they
need
to
sync
with
Adelina
or
you
know,
Randy's
and
make
sure
they
have
clean
tests
throughout,
not
just
all
the
kubernetes
tests,
but
the
windows
test.
Specifically.
The
second
thing
is,
you
know,
I
wonder:
will
it
have
any
impact
to
an
app
right?
A
So
anything
you
will
I
mean
Windows
apps
in
general
to
understand
what
I
own
fqdn
is
and
in
as
long
as
DNS
is
able
to
resolve
that
which
I'm
assuming
like
they're,
not
doing
this
change
just
on
the
hostname
right,
they're
doing
it.
This
change
also
the
DNS
like
were
using
DNS
or
some
other
DNS
capability.
You
are
able
to
resolve
that
fool,
fqdn
correct
they.
They.
D
D
So
I
was
looking
at
something
in
parallel,
basically
fully
quite
fun.
Fully
qualified
domain
names
are
working
in
in
Windows
and
hostname
level.
Partially
qualified
domain
names
also
work
with
Windows.
The
only
ones
that
do
not
are
the
ones
which
have
dots
in
them,
because
Windows
will
consider
them
as
fully
qualified
domain
names,
and
then
they
are
not
going
to
be
resolved
in
any
way.
I
don't
know
if
this
was
but.
A
That's
more
of
a
problem
for
the
person.
That's
basically
defining
the
host
name
right
then
it
for
basically
thoughts
in
the
in
it.
I
mean
it's.
It's
I
mean
they're,
strict
rules
that
you
cannot
have
a
dot
in
the
in
any
of
the
names
in
Windows
right.
So
the
NetBIOS
name,
for
example,
cannot
have
a
dart.
So.
A
D
That's
something
that
I've
I
tried
again
I
think
last
week
or
two
or
two
weeks
ago
on
some
issue
that
was
raised
by
another
person.
If
I
can
just
find
find
that
that
issue.
But,
for
example,
it
doesn't
work
that
the
only
command
that
actually
does,
that
is
nslookup
and
that's
it
not
for
Karl
not
for
W
get
not
for
pink,
not
for
pretty
much
anything.
E
A
E
C
B
Right
and
and
what
I'm
also
worried
about,
is
it's
not
just
the
windows,
the
vi
test,
it
may
not
catch
it.
Some
of
the
existing
applications
may
break
with
this
change,
especially
for
Windows,
and
we
may
not
be
able
to
catch
it.
So
that's
right,
I
feel
like
this
is
a
bigger
change.
We
shouldn't
rush
into
it
because
there
are
two
distros
in
linux
were
trying
to
get
this
done.
Let's.
A
Make
sure
those
concerns
to
on
the
thread
that
way
they
know
that
there
shouldn't
be
willy-nilly
making
that
update
right
away,
but
but,
like
I,
said
on
Windows,
you
may
have
no
no
change
right,
because
you
know
there's
no
fqdn
so
with
it
like
it
looks
like
they're
getting
whatever
is
in
the
pot.
The
pot
itself
has
no
fqdn,
so
for
us
he
might
be
just
a
knob.