►
From YouTube: Kubernetes SIG-Windows 20230718
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody
and
welcome
to
the
July
18th
2023
iteration
of
the
kubernetes
and
windows
community
meeting.
As
always,
these
meetings
are
recorded
and
uploaded
to
YouTube
so
be
sure
to
adhere
to
the
cncf
code
of
conduct.
All
right,
let's
get
started
with
announcements
announcement.
Well,
first
announcement
is
code.
Freeze
is
tonight,
I
think
it's
July
19th
UTC
tonight.
A
Oh,
you
can
check
the
exact
time
in
a
little
bit,
so
I
think
we
can
also
after
the
agenda
items
that
are
on
here,
talk
a
little
bit
about
some
of
the
issues
that
are
that
we're
still
tracking
that's
all
I
have
if
anybody
has
any
announcements,
feel
free
to.
B
A
B
Right
next
give.
A
Some
space,
if
there's
any
new
contributors,
you
want
to
introduce
themselves
I,
think
everybody
on
the
call
is
familiar
or
familiar
with
them.
So
but
I'll
still
pause
for
a
minute
to
see
feel
free
to
just
raise
your
hand
on
YouTube
speak.
If
you
want
to
say
anything.
A
All
right,
I
think
we
can
move
on
to
the
agenda
items
Judy.
Did
you
want
to
talk
about
this
new
Windows
Server
annual
channel
for
containers.
B
Yeah
thanks
Mark
I
just
wanted
to
spend
a
couple
minutes.
It's
kind
of
exactly.
B
There
I'm
wondering
actually,
if
I
can
steal
the
screenshot.
A
B
Let
me
let
me
okay,
actually
I'm
not
super
familiar
with
zoom.
Let
me
know
if
everybody
can
see
my
screen.
Yes
well.
I
can
see
that
yep,
okay,
perfect,
so
I
just
have
a
couple
slides
put
together
just
to
talk
about
the
new
Windows
Server
annual
channel
for
containers.
This
is
something
that
we
are
very
excited
about,
and
we
recently
just
launched
the
Public
Announcement
talking
about
this.
So
I
kind
of
wanted
to
follow
that
up
in
this
setting
with
a
couple
more
details.
B
So
currently
today,
as
you
know,
Windows
Server
gets
released
on
a
three-year
Cadence.
So
this
means
you
know
in
some
sense
it's
a
bit
slow
for
Innovation
and
we
do
a
lot
of
back
ports
with
features
and
bugs,
and
three
years
is
a
pretty
long
time
and
currently
today
also
the
for
Windows
containers.
The
host
and
the
container
images
must
match.
So
this
can
cause
pretty
complicated
upgrades,
especially
if
you've
done
a
recent
one
from
2019
to
2022.
B
You
know
that
you
have
to
upgrade
both
your
container
image
and
your
container
host
with
this
idea
or
what
we're
proposing
is
going
from
the
three-year
Cadence
to
an
annual
release.
So
this
gives
us
a
faster
Cadence,
especially
going
from
three
years
to
one
year
and
we're
also
introducing
portability
for
customers
to
be
able
to
run
older
container
images
on
newer
hosts.
So
this
is
the
part
that
we're
most
excited
about.
B
B
This
also
means
that
we
would
be
providing
a
simpler
upgrade
story
for
people,
especially
or
on
APS,
or
any
of
the
other
Cloud
providers,
just
to
kind
of
break
it
down
a
little
bit
further
with
the
release
Cadence,
it's
a
bit
I
I've
just
created
a
diagram
to
kind
of,
hopefully
make
it
a
little
bit
simpler,
but
essentially
we're
going
to
be
releasing
a
version
of
Windows
Server
every
year,
and
this
is
going
to
be
serviced
for
two
years.
B
However,
we
are
still
going
to
be
maintaining
that
10-year
ltsc
every
three
years,
so
next
year
is
going
to
be
2025,
that's
going
to
still
have
that
10-year
servicing
Channel,
but
and
our
container
images
are
still
going
to
be
released
on
that
three-year
Cadence,
so
in
tandem
with
ltsd,
which
is
how
it
works.
Today,
however,
we're
going
to
have
that
container
host
every
single
year,
if
that
makes
sense,.
A
With
tags
for
this
new
Windows
Server
annual
channel
for
containers,
or
is
it
just
going
to
be
Windows
like
ltse
2022.
B
So
the
container
image
release
is
going
to
be
the
same,
so
you'll
see
all
those
tags
every
three
years
so
next
year,
you'll
still
have
Nano
server
server
core
full
server,
but
we
are
going
to
be
releasing
the
container
host
every
single
year.
So
you're
not
going
to
get
container
images
every
single
year,
we're
going
to
be
introducing
that
portability
with
stable
API
so
that
you
can
have
older
container
images
on
that
newer
host,
great.
B
Cool
I
think
my
ask
feel
free
to
jump
in
if
anyone
has
any
other
questions,
but
my
ask
here
was
really
I
know
that
there
needs
to
be
some
support
in
the
Upstream
Community,
especially
adopting
this
faster
Cadence
on
test
grid
and
I'm.
Curious
to
see
you
know,
is
that
doable?
How
can
I
kind
of
kick
start
that
process
in
this
setting.
A
If
all
of
the
Windows
Server
2022
container
images
can
run
on
this
host,
it
probably
should
not
be
too
much
work
to
set
up.
Another
has
grid
test
pass
to
run
this,
like
a
lot
of
the
complications,
is
usually
on
getting
those
container
images
built
and
and
running.
B
A
A
Be
done
in
the
container
image
to
make
sure
we
can
kind
of
Enlighten
that
to
say
these
post
images
can
pull
container
images
with
a
different
version.
B
Yeah
so
there's
work
going
on
in
containerdy
right
now.
There
is
a
PR
out
able
to
have
that
mismatch.
I
know
that
there's
that
platform
matcher
problem
that
is
currently
active
and
I
know
that
one
of
our
devs
is
actively
looking
for
people
to
review
that
we're
hoping
to
get
that
back.
Ported
in
both
container
D
1.6
and
1.7
it'll
be
starting
next
week.
A
A
B
So
right
now
we're
in
the
preview
phase
and
we're
hoping
to
get
a
preview
build
onto
the
server
insiders
community
and
we're
planning
on
doing
this
in
October
and
that's
going
to
be
released
on
msdn
and
also
anyone
who
has
a
VSS
subscription.
D
Couple
of
questions
as
well,
if
I
may,
of
course,
so
first
of
all
one
concern
I
have
is
that
I
am
quite
skeptical
when
it
comes
to
backboarding
to
connect
container
D
1.6,
because
that
may
potentially
be
a
breaking
change
for
the
current
2019
and
2022
Windows
servers
which
do
not
support
this.
Yet
correct
me
if
I'm
wrong,
so
I
really
doubt
that
they
are
gonna,
accept
it
and
there
might
be
some
issues
if
they
do
even
for
our
CIS
and
secondly,
how
backwards
compatible.
D
Is
this
going
to
be
like
one
year
two
year,
three
years
when
it
comes
to
the
host
over
hostel
OS
version
and
the
container
image
was
the
version.
B
Yeah,
so
for
on
the
first
one,
I'm
not
entirely
sure
what
you
mean
by
it's
not
supported
on
2019
or
2022.
Like
are
you
talking
about
the
the
ability
to
run
the
older
container
images
with
the
newer
host
yeah,
so
I
think
the
plan
and
I
would
definitely
I.
B
Think
there'll
be
more
details
in
the
pr
itself,
and
I
can
definitely
check
out
that
link
for
you,
I
believe
it
should
be
for
sure
it
should
be
with
this
release
and
upwards,
and
this
kind
of
leans
into
the
next
question
of
how
backwards
compatible
will
it
be.
Our
plan
currently
is
to
be
able
to
allow
you
to
run
the
most
recent
ltsd
and
the
one
before
so
that's
a
bit
confusing,
but
basically
it
means,
like
you,
can
run
2022
images
on
newer
hosts
up
until
2025.
B
So
then,
if
you're
on
2025
today,
you
can
run
either
the
2025
images
or
the
2022
images,
and
then,
when
2028
comes
out,
it'll
be
able
to
run
the
2020
eight
images
and
the
2025
and
all
the
annual
channels
in
between
will
be
able
to
host
the
2025
images.
There.
B
D
B
Definitely
something
you
can
comment
on
I'll.
Let
me
dig
out
the
link
right
now
and
see
whether
or
not
that
might
have
some
more
details
for
you.
A
B
This
is
just
in
case
there
were
further
questions
and
I'm
realizing
now
it
might
have
been
more
useful
to
put
on
a
table
with.
You
know
the
images
and
the
host
compatibility,
this
kind
of
just
shares
like
a
high
level
of
the
portability
effort
that
we've
been
doing,
and
this
has
kind
of
been
a
couple
years
in
the
making.
But
we
think
this
is
you
know
one
of
the
biggest
things
that
we're
looking
forward
to
with
this
annual
release.
B
So
it
talks
about
here
exactly
what
I
just
said:
the
M
plus
one
compatibility,
and
that
just
is
between
the
lcsds
meaning.
You
could
run
the
2025
images
on
2025
and
you
can
run
the
2022
images
on
the
2025
host.
D
Yeah,
so
one
thing
that
I
was
thinking
is
that,
after
those
continuity,
changes,
merge
and
basically
continuity
is
able
to
pull
an
older
image
as
well.
It
might
be
interesting
to
have
some
smoke
tests
in
test
grid
as
well
to
actually
verify
that.
Indeed,
it's
working
with
other
images
as
well,
but
I'm,
not
exactly
sure
how
that's
gonna
look
because
we're
currently
building
and
Publishing
image
manifest
lists
so
which
will
contain
all
the
OS
versions,
including
older
ones,
newer
ones
current
was
and
so
on
so
forth.
A
D
B
B
Yeah
for
sure,
I
just
dropped
the
link
of
the
containerd
pr.
That
I
was
talking
about
into
the
meeting
chat
there.
For
you.
B
Awesome,
that's
kind
of
really
what
I
wanted
to
walk
through
thanks
for
giving
me
the
time
of
day
mark.
D
Thanks
I
actually
have
another
question,
but
I
think
that's
going
to
be
addressed
in
the
for
requests
you
mentioned
as
well.
For
example,
if
you
have
a
manifestly
switch
image,
is
gonna
first
check
for
the
current
one
or
an
older
one,
but
I'm
assuming
it's
going
from
current
One
backwards
so
always
check
it
for
the
newest
is
what
I
assume
at
the
moment.
D
D
A
B
Not
yet,
but
we're
just
working
on
the
final
details
for
that
one.
A
Okay,
let
us
know
when
they
are.
A
I
added
the
next
agenda
item.
This
I,
don't
think
our
event
is
here,
but
Fabian
you
were
here
too.
I
was
trying
to
set
up
some
of
the
tests
with
the
no
log
query.
Tests
and
I
did
not
real.
It
seems
like
those
tests
are
meant
to
be
run
only
on
for
for
Linux.
Is
that
correct,
Fabian.
A
That
that
was
my
assumption.
I
didn't
have
a
chance
to
look
too
deeply
into
it,
but
I
did
see
things
like.
If
you
specify
like
the
boot
ID,
it
returns
back
a
message
saying
that
that's
not
not
or
not
valid
for
Windows
should
we
update
those
tests
in
add
a
Linux
only
tag
or
are
the
plans
to
update
those
tests
and
check
with
like
the
node
OS
is
and
then
change
the
behavior.
C
A
A
A
Let's
add,
let's
add
Linux
only
for
now,
I
think
that's
the
the
simplest
change.
Do
you
want
me
to
try
and
do
that
today,
since
today's
code
freeze
to
get
that
in
or.
C
A
Okay,
that
was
the
only
other
agenda
item.
I.
Think
I
wanted
to
talk
a
little
bit
about
the
crusade
of
the
piers
that
we
had
open
that
we
were
tracking.
C
Talk
about
the
Windows
support
for
employee
spot
vertical
scaling.
Apparently
the
test
James
created
are
having
some
issues
and
I
couldn't
find
out.
Why.
A
Okay,
so
these
are
probably
okay,
so
it
wait.
So
this
was
working
on
other
clusters
or
did
something
change
with
the
way
that
the
Clusters
that
James
set
up
were.
C
A
A
Okay,
I
think
we'll
probably
need
to
take
a
look
at
that
and
deeper
look
at
that.
This
probably
won't
make
it
for
code
freeze
today,
then,
though,
unfortunately,.
A
Did
you
need
help
with
James
to
look
at
it
to
look
at
the
cluster?
Is
this
something
that
you
were
going
to
try
to
look
at
too.
B
A
Okay,
I
think
we'll
just
continue
to
look
at
that
for
the
CRI.
Only
stats,
I
messaged
Bruno
again
this
morning
to
look
at
it
Martin
all
said.
Oh
looks
like
no.
This
is
the
container
D1.
It's
I
think
that
there's
a
link.
A
A
B
A
D
A
A
A
The
vpa
one
is
the
only
one
that
likely
won't
make
it
for
code
freeze
today,
we'll
try
and
take
a
look
at
that
Bobby
and,
if
I
think
James
is
out
today.