►
From YouTube: Kubernetes SIG-Windows 20210907
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
All
right,
hello,
everybody
and
welcome
to
the
september
7th
2021
iteration
of
the
kubernetes
windows
community
meeting.
As
always,
these
meetings
are
recorded
and
uploaded
to
youtube
should
be
sure
to
adhere
to
the
cncf
code
of
conduct.
Let's
get
started
announcements,
I
don't
think
we
have
many
announcements.
The
cap
or
the
enhancement
freeze,
is
scheduled
for
this
thursday
september
9th.
I
believe
we
we're
tracking
three
enhancements.
One
of
them
was
carryover
from
122,
and
we've
done
all
the
necessary
milestone
updates
to
get
that
tractor
123..
A
The
other
two
are
listed
here
and
I
wanted
to
discuss
those
in
a
little
bit
more
depth
after
this,
the
other
announcement
is
kubecon
is
I
believe
that
if
people
are
interested
in
attending
virtually,
they
are
still
accepting
kind
of
registrations.
For
that,
I
think
that
the
in-person
ones
are
either
are
closed.
A
A
If
anybody
has
any
other
announcements,
just
drop
them
in
the
chat
or
just
feel
free
to
interrupt
me.
I
did
want
to
talk
a
little
bit
about
the
two
caps
that
we
have
going.
Ravi
mentions
he's
not
going
to
be
available
today,
but
we
can
still
discuss
that
cap
that
is
or
that
that
enhancement
update.
I
think
that
we
have
consensus
and
we're
just
kind
of
settling
on
some
final
details
to
put
into
the
cap.
A
The
general
approach
looks
like
there's
not
much
disagreement.
The
disagreement
is
well
there's
not
there's
not
many
disagreements.
There's
just
some
asking
for
clarification.
A
I
think
the
tricky
bit
with
this
one
is
that
normally
it's
advised
to
not
have
other
features,
act
on
or
be
aware
of
features
that
are
in
alpha,
because
those
are
generally
off
by
default
and
harder
to
turn
on.
A
But
with
this
one,
there's
a
lot
of
kind
of
interplay
between
the
new
pod
security,
admission,
plugin
and
the
os
new
os
field
in
the
kep
and
the
behaviors
being
discussed
here
are
that
it
would
be
desirable
to
have
the
new
the
built-in
pod
admission
controller,
which
is
going
to
beta
in
123,
be
aware
of
the
new
os
fields.
If
that
feature
is
turned
on
in
a
cluster.
A
So
there's
just
a
lot
of
clarification
around
what
behaviors
to
expect
with
that.
If
anybody's
interested
the
prs
and
the
notes
just
feel
free
to
read
through
it
or
like
update
or
ask
some
questions,
the
next
one
is
the
progressing
the
host
process
containers
to
to
beta
in
123..
A
I
need
to
go
and
ping
some
of
the
other
reviewers
there's
not
a
lot
of
comments.
Jordan
did
have
a
couple
of
questions
or
just
some
clarifications,
you'd
like
to
see
in
the
either
in
the
kepper
and
the
pr
or
both,
so
I'm
going
to
work
with
some
folks
to
get
all
of
those
answered
after
some
of
the
community
meetings
this
morning.
A
A
James
certavon
has
also
been
doing
a
lot
of
work
to
get
a
cluster
api
for
azure
or
the
cluster
api
provider
for
azure
to
work
with
the
cni
or
with
host
process
containers.
So
there's
a
lot
of
good
reference,
pr's
that
I'll,
try
and
link
to
after
this
meeting
as
well.
A
Okay,
I
think
that
now
we
can
talk
a
little
bit
about
windows,
server
2022,
so,
as
I
think,
a
lot
of
people
have
been
following,
but
windows
server
2022
has
been
generally
available
for
a
couple
of
weeks.
There
was
a
kind
of
press
and
marketing
embargo
set
for
microsoft,
employees
until
september
1st.
So
that's
why
a
lot
of
folks
like
brendan
myself
and
a
number
of
pms
couldn't
really
talk
about
it,
but
now
we
can
so
we're
here
to
kind
of
highlight
some
of
the
new
new
functionality.
A
B
Not
necessarily
the
best,
but
I
I'll
start
so
I
hope
everyone
have
seen
the
we
have
two
blogs
on
the
september
1st
I
like
mark
said
the
ga
date.
If
you
guys
follow
the
mcr,
you
know
when
the
image
published
it
was
published
a
little
bit
earlier
august
18th,
but
because
the
pricing
was
not
ready
until
a
little
bit
later.
B
So
marketing
did
the
launch
stage
stage
launch
on
september
1st
and
that's
why
we're
not
able
to
talk
publicly,
but
now
it's
available,
I'm
first
on
our
tech
community
blog,
we
explain
kind
of
give
overview
and
the
links
to
the
new
features.
B
B
B
B
Some
of
the
work
actually
fled
in
earlier
on
stack
release.
If
you
were
using
2004
or
20
2,
you
already
see
the
image
optimization,
you
know
compared
to
2019,
but
you
a
lot
of
our
customers.
B
Even
you
know,
for
us
aks,
you
know
we're
right
only
adopting
eight
ltsc,
so
you,
if
you
compare
2022
with
2019
image,
size,
actually
smaller
and
we
are
continuing
on
the
journey
to
optimize
as
well,
but
definitely
the
significant
image,
optimization
mainly
of
the
net
engine
images
we
remove
and
the
the
default
base
os
image
and
only
have
it
in
net
images.
So
you
know
whoever
built
on
the
base
image.
They
no
longer
need
to
take
on
the
the
comments
or
extra
engine
image
only
kept
a
few.
B
So
that's
the
image
observation
for
server
core
and
the.
Similarly,
over
the
last
few
years,
we
did
a
lot
of
improvement
on
performance
reliability,
especially
from
container
deported,
because
we
are,
you
know,
have
been
developing
with
to
start
doing
the
development
community
back
in
2019.
B
A
lot
of
internal
teams
are
using
that
so
a
lot
of
optimization
for
canadian
and
also
we
are
optimized
server
core
that
server
itself
for
general
server
and
then
that
performance
reliable.
Actually,
you
can
see
reflecting
the
container
image
as
as
well,
so
that's
for
an
image,
composition
or
a
size
point
of
view
and
related.
Also,
we
add
another
new
image
which
is
server.
Image
like
used
in
in
the
past
is
the
windows
image
it's
more
kind
of
based
on
a
client,
sku
and
now
for
this
round.
B
We
repair
it
to
based
on
a
server
sku.
So
all
the
features
especially
features
related.
You
know
a
few
things,
because
people
in
the
community
report
it
related
to
is,
for
example,
the
if
you,
you
know
in
the
past,
there's
a
license
constraint
and
you
can
only
do
10
connection
and
now,
with
a
service
queue
based
on
service
skills.
No
longer
such
limitation
and
we're
looking
at
bring
more
light
and
more
application
compatibility
from
the
server
skill,
for
example,
we
have
done
work
on
gpu
related.
B
You
know,
hardware,
acceleration
related
work,
we'll
continue
working
on
that.
There
are
also
other
api
missing
from
the
windows
image
and
we
hope
this
with
the
server-based
image
things
are
there.
I
would
definitely
welcome
you,
know
community
to
valid,
and
let
us
know
if
that's
not
the
case
and
rather
speaking,
that
image
is
also
smaller
than
the
windows
based
image.
So
that's
for
an
image
appointed.
B
We
have
those
three
and
then
in
and
also
we
have
quite
a
few
networking
related
improvements
and
I
think
in
the
detail,
in
the
blog
on
and
along
the
same
release
wave
also,
we
have
two
related
improvements
in
you
know,
along
with
windows,
admin
center
and
also
azure
migrate.
B
So
that's
at
high
level
in
terms
of
the
new
image,
so
there's
no
semi-annual
release
with
this
one.
So
you
can
see
the
tag
is
only
ltsc
2022..
I
know
for
2019,
it's
confusing
there
too.
There
was
one
point
I
was
thinking.
Okay,
should
we
converge
because
1809
will
give
people
the
perceptions
of
sack,
but
I
check
with
mark
and
mikey
mark
confront
you
given
a
lot
of
people.
B
Are
student
attack,
we're
not
going
to
change
that,
so
you,
like
marcus,
said
you
can
almost
use
ltsc,
2019
and
18
right
interchangeably,
there's
very
small
like
hash,
I
think
related
small
attack
related
difference,
but
the
bits
everything
is
saying.
So
we're
not
changing
anything
but
going
forward.
B
So
server
2022
only
one
tag,
but
you
can
use
a
different
variation
like
tag
itself
or
with
a
kb
or
with
the
actual
build
number,
and
the
last
thing
I
want
to
highlight
is
we
intend
to
support
continuity
from
our
first
party
kubernetes
services
for
aks
and
aks
hci?
B
We
wanted
you
know
here.
Let
the
community
know
that's
our
intention
and
definitely
welcome
the
impac
feedback
here.
So
that
was
more
like
the
first
blog
on
september,
1st
now
september,
2nd
blog
was
mainly
addressed.
A
lot
of
community,
not
just
kubernetes,
but
in
general,
especially
folks,
are
on
site
accommodating.
Even
you
know,
people
are
relying
on
sac
or
relying
process
isolate
container
with
on
running
on
windows,
10
machine,
so
that
was
that
main
focus.
B
I
think
the
main
main
takeaway
is.
You
know
we
looking
at
community.
We
are
with
the
maturity
of
the
container
windows
container
and
also
we're
seeing
the
adoption
trend.
We
will
be
focusing
on
ltsc
only
and
and
of
course,
will
what's
you
know
we're
not
going
to
do
zach
and
so
we'll
be
without
zach.
Of
course,
there's
concern
like
how
fast
how
agile
we
can
ship
new
features.
We're
aware
of
that,
and
I
think
what
at
least
you
know
a
few
actually
going.
B
One
is
how
you
know
we'll
definitely
focus
on
how
to
work
with
our
servicing
team
to
make
updates
or
patches
faster,
so,
like
monthly
update,
how
do
we
get
things
faster
because
I
know
in
the
past
it's
painfully
taken
much
longer
time.
So
that's
that
and
then
the
the
firm
process.
Isolation
point
we
know
it's,
it's
a
pain
point
for
a
customer
to
know
the
process
and
hyperventilation
the
difference.
So
the
biggest
announcement
coming
from
this
one
is.
B
We
have
been
spending
effort
to
support
down
level
process,
isolation
so
meaning
that
that
effort
starts
with
the
server
2022,
meaning
if
you're
running
server,
22
2020
image
for
anything
any
hosts
the
same
or
future.
Now
you
can
sort
of
to
download
support
you,
you
can
from
customer
point
of
view.
You
know
you
sort
of
like
a
build
application
once
and
you
don't
need
to
rev.
B
You
don't
need
to
wrap
application,
but
you
can
update
your
host
and
specify
in
this
context
for
customers
who
want
to
use
server,
2022
process
isolation.
You
can
use
windows
11,
because
windows
11,
actually
a
build
number
is
higher
than
windows,
server,
2022
and
it
does
not
work
server.
2022
image
does
not
work
on
windows,
10
or
even
20,
h1
2,
those
and
sorry
not
20h1,
build.
I
think,
the
latest
one,
because
the
those
windows
10
build
are
based
on
older
branch.
B
So
I
want
to
call
out,
but
moving
forward,
we'll
continue,
optimize
the
down
level
version,
compat
and
and
right
now
just
preview-
and
I
know
brandon
on
the
call
he
can
definitely
drill
deeper,
but
there's
something
very
exciting
that
we
want
to
share
with
the
community,
especially
who
are
a
developer.
Who
have
you
know:
wanna
run
windows
10..
B
I
think
that's,
probably
a
high
level,
though
that
I
would
capture,
I
don't
know
if
I
missed
anything
like
mods.
Whatever,
on
the
call
you
can
add,
and
I'm
happy
to
take
questions.
C
D
So
I
have
one
question
regarding
the
2019,
the
ltsc,
so
our
customers
yeah
using
the
full
image
or
nano
so
that
1809
tags
will
be
kept
maintained
going
forward.
And
yes,
okay.
B
Yeah
yeah
yeah.
What
you
know,
unless
you
guys
tell
me
differently,
I
did
I
was
thinking
like
hey,
want
to
converge
on
ltsa
2019
at
the
tag
and
then
remove
1809,
because
829
is
more
like
the
convention.
Wise
you're,
using
the
sac
release
convention
like
1903
or
1909
right
like
can
be
misleading,
but
I
checked
with
mark
and
others,
and
I
think
people
prefer
to
live
in
there
and
we
will
I'm
okay
to
continue
support.
A
Yeah,
I
think
that
we
shouldn't
stop
updating
the
1809
tag
for
the
nanoserver
image,
but
if
we
wanted
to
maybe
create
a
new
tag
and
update
them
both
that
might
be
good,
but
I
think
that
if
we
just
stop
updating
the
1809
tag,
there
are
people
who
are
not
going
to
get
that
memo
and
are
going
to
run
into
some
compatibility
issues
yeah.
I
would.
D
See
yeah,
I
would
suggest
we
add
the
new
tags
because
yeah
we
had
this
confusion
from
one
of
the
customers,
because
new
repo
has
only
the
ltc
22
for
the
full
image,
so
they
were
asking
like
yeah.
We
need
actually
22,
because
2019
doesn't
have
support
for
full
image,
so
I
believe
it
makes
confusion
to
customers
like
since
they
are
not
seeing
the
ltc
tag.
It's
it's
like.
It's
not
supported.
A
Yeah
so
initially
the
1809
tag
and
nanoserver
were
only
supposed
to
have
the
same
support
timeline
as
the
1809
semi-annual
channel
release,
which
is
18
months.
But
after
that
has
elapsed
there,
we
microsoft
did
commit
to
supporting
the
nanoserver
image
for
windows,
server
2019
for
the
full
life
cycle
of
that
product.
Yeah.
B
C
Correct
yeah:
we
don't,
we
don't
want
to
break
the
existing
ones
but
to
ibrahim's
point
and
thank
you
for
the
feedback.
Brian
there
yeah
the
lts
cp,
you
know,
but
now
the
announcement
of
sag
going
away
people
may
get
confused.
So
I
think
it's
a
good
point
to
keep
the
to
add
a
ltst
tag
but
not
break
the
existing
images.
Make.
B
Sense,
okay-
and
I
think
I
also
heard
some
mention
the
window.
You
know
windows
image,
the
specific
the
windows
image
is
the
this
one.
We
are
not
starting
with
server
2020
we're
not
releasing
that
one.
So
if
you're
using
windows
image
the
third
image
for
starting
windows,
server,
2022,
you
want
to
move
to
the
server
image.
D
B
Okay,
how,
like
what
do
you
recommend
we
should.
D
Do
I
would,
I
would
say
at
least
we
update
the
existing
ones,
the
regular
windows
full
and
nano
ones
just
add
new
tags
that
call
it
ltsc
2019.
D
So
at
least,
if
someone
is
searching-
or
we
want
to
point
them,
we
will
say
yeah.
You
can
see
the
ltc
2019
tags
in
the
old
one
and
then
the
new
repos
can
just
be
kept
for
22
going
forward.
So
it's
just
an
additional
tag
will
probably
help
getting
the
confusion
away
because,
with
today's
tags,
it's
only
mentioning
1809
and
iplivia
for
any
new
person
who
don't
he's
not
aware
about
yeah
1809
came
with
ltc
and
they
are
the
same
bits.
D
B
I
I
have
a
question
just
kind
of
full
up.
If
nobody's
asked,
that's
a
question
yeah.
I
I
think
we
didn't
come
cause
I
last
night
and
then
you
know
jane
talked
and
last
meeting.
We
probably
ran
out
of
time.
The
question
was
like
you
know,
which
kubernetes
version
we
should.
Oh,
yes,
support
right
for
server
2022.
B
I
know
I
think
we'll
talk
about
sir
123,
which
is
scheduled
for
december
release
and
also
currently
the
122
and
the
122.
I
think
ender
support
is
october
next
year,
and
so
I
want
to
you
know,
get
understanding.
What
do
you
guys
recommend.
A
So
I
think
we've
talked
about
this,
maybe
a
year
or
18
months
ago,
but
from
the
sig
windows
community.
We
did
say
that's
for
support
for
new
windows,
os
versions
that
we
would
like
that
also
included
us
building
all
of
the
test
and
infrastructure
container
images
for
a
given
release
and
committing
to
running
tests.
A
For
that,
I
believe
that
there
have
been
pull
requests
already
opened
into
the
kubernetes
repository
to
build
the
test
images
for
windows,
server,
2022
images
for
the
123
release
and,
in
general
those
like
we
wouldn't
be
able
to
necessarily
back
port
the
the
test
image
definitions
to
update
them
to
use
the
new
tags
just
because
of
the
nature
of
the
changes
and
the
kind
of
guidelines
for
backboarding
changes.
A
So
I
believe
we
will
well,
at
least
in
terms
of
like
running
tests
and
kind
of
actively
identifying
any
issues
that
come
up
from
test
automation,
we'll
start
with
123
and
move
forward.
A
But
if
anybody,
I
guess
does
find
any
issues
that
are
specific
to
running
windows,
server,
2022
on
older
version
or
on
older
versions
of
kubernetes.
Please
let
sig
windows
know
when
we
can
kind
of
triage
and
evaluate,
then
some
issues
may
be
able
to
be
fixed.
Some
may
not.
It
just
depends
on
where
they
come
up
with,
but.
B
Okay,
so
your
marker
is
saying
like
we
are
proactively:
adding
new
test
drops
for
123,
so
more
like
full.
Looking
and
there'll
be
new
work
that,
in
your
engineer,
work
right
and
then
and
you're
saying
for
122
is
so
more
reactive
like
if
people
are
validating
as
is
or
running
what
our
execution,
I
mean,
validation
as
is,
and
we
running
the
issue
we
take
a
look
at.
But
what,
when
there's
no
need
or
nobody's,
probably
creating
new
test
jobs?
Is
that
what
you're
saying.
E
B
Then,
when,
when
we
release
later
on
like
declare
in
the
server
2020
is
ready
and
then
kubernetes
windows
like
what
would
be
the
message,
you
would
declare
it's
on
123
support,
123
and
122,
or
how
do
you.
A
A
This
table
gets
updated
and
we'll
update
this
table
for
the
122
for
the
123
docs
or
to
list
either
windows,
server,
2022
or
windows,
server,
20
or
side
by
side
with
that
version,
and
then
we'll
have
to
figure
out
how
to
phrase
that
we're
we'll
we'll
phase
these
out
as
they
go
out
of
their
support
life
cycle
and
then
we'll
update
the
docs
to
point
to
the
new
pause
image
that
has
windows
server
2022
support,
because
that
needs
to
go
hand
in
hand
with
deploying
a
windows,
server,
22
cluster
and
then
we'll
there's
a
couple
other
references
to
a
specific
functionality
here
that
we'll
update
so
we'll
we'll
start
with
mentioning
windows,
server
2022
in
the
docs
for
123..
A
But
if
anybody
is
like
trying
it
out,
like,
I
think,
usually
like
when
new
stack
releases
come
out.
It's
usually
some
infrastructure
providers
already
support
it
before
the
release
is
out
because
things
just
work
and
we
hope
that
that's
going
to
be
the
same
for
windows,
server,
2022.,.
B
A
Yeah,
so
these
these
docs,
the
way
it
works,
is
near
the
end
of
the
well
sometime
in
the
middle
of
the
kubernetes
release.
The
docs
team
will
fork
the
kubernetes
website
repository
and
create
a
a
dev
123
branch
and
then
updates
go
with
into
that
branch.
If
they're
specifically
targeting
the
123
release
and
then
when
the
123
release
occurs,
the
the
website
will
go
live
along
with
all
the
kubernetes
bits
so
well.
We
can
take
care
of
that.
B
Who,
who
I
mean
like
how
I
I
I
don't
think
this
windows
meeting?
Will
you
continue
to
you
know?
I
don't
think
it's
the
best
time
to
talk
about
this,
probably
somewhere
on
some
other
work
stream
that
we
should
suddenly
hook
up
with
to
to
make
sure
we
are
plugging
and
work
with
the
community
to
update.
Is
that
right,
like
with
the
123
release
team
dock
team,.
B
A
All
right,
I'm
going
to
stop
my
screen
share
now.
If
nobody
else
has
any
questions,
I'm
going
to
hand
it
over
to
jay
for
the
pairing.
F
One
thing
I'll
note:
on
the
down
level
version
compatibility:
this
is
a
big
thing
that
we've
been
working
on
for
quite
a
long
time
now
and
we'll
we'll
have
a
dedicated
blog
post
about
it.
Talking
about
all
of
its
specifics
and
nuances,
but
at
least
the
moment,
if
you
do
try
running
a
windows,
server,
222,
container
image
on
either
windows,
11
or
windows,
server,
292
and
you
come
across
any
version.
Compatibility
bugs.