►
From YouTube: Kubernetes SIG-Windows 20221213
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
Welcome
to
Sig
windows,
it's
December
13th!
This
is
a
cncf
project,
and
so
we
follow
cncf
guidelines
that
boils
down
to
being
nice
to
everyone.
If
you
have
any
concerns
or
questions
you
can
reach
out
to
any
of
the
leads
and
or
the
cncf
code
of
conduct
and
otherwise
welcome.
Everyone
I
think
everybody
further
waiting
for
vacation.
So
looking
forward
to
that,
want
to
kick
it
off
here,
so
126
got
released
earlier
this
week.
A
A
We
also
122
reached
end
of
life.
I
think
they
did
one
last
patch
release
this
week,
but
then
from
there
on
out,
there's
gonna
be
no
more
patch
releases,
so
we
removed
it
from
our
dashboards.
Our
test
grid
dashboards
this
week
earlier
on
Monday
I
think
another
announcement
is.
We
are
canceling
Sig
windows
for
the
next
two
weeks.
A
I
think
most
of
the
six
are
doing
that
for
the
holidays,
so
we
will
not
have
Sig
Windows
next
week
or
the
week
after
that,
and
so
we'll
see
y'all
in
the
new
year
and
then
I
think
the
other
big
announcement
is
enhancement.
Freeze
for
127
went
is
tentatively
for
February
9th,
so
we
have
a
little
bit
of
time
once
we
get
back
but
make
sure
you're
thinking
about
that.
Does
anybody
have
anything
that
they
want
to
be
getting
in
for
for
enhancements.
B
I
need
to
update
my
announcement
again,
you
know,
shift
everything
around
yeah
yep,
but
yeah.
It's
like
I
think
it's
just
mechanical
work
at
this
point.
Just
updating
the
version
numbers
and
things
like
that.
Okay,.
A
B
A
Cool
thanks
Dave
we're
sharing
the
link
to
the
blog
post.
There.
A
Cool,
so
we
usually
take
off.
Is
there
any
other
announcements
anybody
want
to
share
anything.
A
Okay,
cool
and
then
we
usually
take
a
minute
for
any
new
contributors.
Is
there
anybody
new?
That
wants
to
say
hello,
no
obligation,
but
you
want
to
introduce
yourself
and
just
say:
hi
we'd
love
to
hear
about
why
you're
here
and
what
you're
interested
in.
C
Yeah
I'm
Dave
Schwinn
I
was
here
last
week
as
well.
I'm
interested
in
I've
been
pursuing
how
to
get
the
ability
to
map
to
a
DFS
share
into
Windows
container
and
that
does
not
currently
work
I'm.
Looking
at
alternatives
to
using
the
Powershell
script
that
the
Powershell
commandlet
that
Maps
a
global
SMB
mapping
that
does
not
support
DFS,
so
I'm,
just
kind
of
looking
for
alternatives
to
that
passively.
In
my
free
time,.
D
I'm
just
curious:
should
we?
Where
would
that
go
if
we
wanted
to
file?
Oh
no
look.
Mike
turned
his
camera
on
now.
You
now
you're,
my
friend
Mike.
D
C
Right
so
I'm
using
a
CSA
driver,
SMB
and
I
can
map
the
I
can
map
sorry,
my
terminology
gets
screwed
the
the
persistent
volume
that
represents
that
share,
but
once
you
hit
a
DFS
Link
in
the
UNC
path,
it
does
not
follow
that
link
to
whatever
server
obstruct
is
abstracted
with
that
link.
Do
you
understand
what
I'm
saying
there.
D
D
It's
in
the
Powershell
command
that
the
CSI
driver
is
running.
That's.
C
Correct,
oh,
you
can
reproduce
the
error
without
doing
it
in
kubernetes,
you
could
literally
just
log
on
to
a
Windows
server
and
say
what's
the
command
new
SMB
Global
mapping
and
point
it
to
a
UNC
path.
That
is
a
DFS
DFS
root,
but
that
has
Targets
in
it.
And
if
you
try
to
go
to
one
of
the
targets
it
fails.
D
D
C
I
posted
an
issue
to
Powershell,
but
yeah
I
inadvertently
did
it
to
the
Powershell
core
and
not
the
the
old
Power
show.
What's
the
term
for
the
old
in
the
new
Powershell
core
and
Powershell
traditional
do.
C
I
I
submitted
it
to
the
wrong
group
and
they
closed
it.
So
I
really
just
need
to
resubmit
that
to
the
windows
Powershell
group,
but
that's
not
an
open
source
project
that
it
will
take.
A
Yeah
so
I
think
there
is
a
probably
a
GitHub
I
can
try
to
find
an
Orient
Post
in
slack.
D
C
Do
do
we
have
the
influence
to
make
that
happen,
yeah,
okay,
all
right!
Absolutely
I
will
take
care
of
of
posting.
If
you
could
find
me
where
to
put
that,
I
will
repost
my
issue
and
we
can
pound
on
them
because
it
is
about.
It
is
a
buggy
in
Powershell
and
not
in
anything
related
to
kubernetes.
So
well,.
D
It's
a
bugging
power
show
but
like
for
us.
It's
also
a
bug
in
kubernetes,
because
if
somebody
comes
along
like
you
and
wants
to
run
a
Windows
bot-
and
you
can't
do
this
thing,
it's
like
yeah.
What
do
you
well,
you
know
what
do
you
care
like
for
you?
It's
a
CSI
driver
bug.
You
know,
maybe
you
don't
consider
it
a
kubernetes
bug,
but.
C
You
know
right
well,
I,
just
dug
into
it
deep
enough
to
know
where
the
problem
stems
from
and
we
can
go
pester
those
people.
A
D
We
want
okay,
so
once
you
file
that
bug
in
the
GitHub,
then
then
we'll
file,
a
CSI
driver
bug
on
the
SMB
driver
as
a
tracking
issue
right:
okay,
cool
I
trust.
You
I,
don't
know,
I
just
made
that
up,
but
I
feel
like.
We
won't
forget.
Yeah.
That
way,
right,
yeah
and
see.
Look
James
has
James
is
happy,
he's
nodding
his
head.
That
makes
sense.
B
D
F
It
was
just
just
partitioning
down
my
hard
drive
or
shrunk.
It
I
have
a
Windows
machine,
so
I,
just
trunk.
The
hard
drive
started
going
through
the
say,
windows,
documentation
and
just
installing
it
on
a
Ubuntu
box,
because
I
just
did
the
dual
boot
thing
on
the
shrunk
proficient
piece.
So
it's
fresh,
install
of
Ubuntu
started
following
the
directions
to
install
ran
into
some
little
bit
of
air,
so
I'm,
just
kind
of
trying
to
step
through
and
put
together
a
guide
to
try
to
do
that.
F
Similar
action
to
get
started
quicker
so
hit
some
errors
and
now
that's
kind
of
where
I'm
at
with
it,
but
definitely
interested
in
taking
a
look
and
trying
to
contribute
some
helpful
guides
to
just
get
more
people
interested
in
it.
D
D
D
If,
if
we
had
that
set
of
instructions,
then
we
that
we
could
give
people
and
say
hey
you've
got
a
Windows
box
partition
it
for
now
partition
it
half
of
it.
Ubuntu
use
that
to
boot
virtualbox,
like
at
least
we
would
have
a
workflow
that
we
could
support
from
Windows
laptops
right,
even
though
it's
not
really
a
Windows
workflow,
but
it's
something
so
yeah.
E
Hey
everyone:
this
is
Lakshmi
I'm
calling
from
India.
This
is
my
first
meeting
here
and
I
vote
for
a
Pure
Storage
Box
teams.
Specifically,
we
are
looking
at
you
know
personally
trying
to
support
Windows
with
the
kubernetes
for
containers
in
our
solution,
which
has
been
predominantly
now
so
far,
I'm
only
Linux
notes.
We
wanted
to
bring
in
Windows
nodes,
and
in
that
aspect
you
know
I'm
doing
the
investigation
to
see
where
we
are
and
what
Windows,
where
currently
it
is
I've.
E
Had
some
luck,
I
mean
really.
You
know
tough
time
trying
to
set
up
the
infrastructure
first
to
get
mixed
kubernetes
environment
with
Linux
and
windows
nodes
eventually,
I
got
it
working
so
really
trying
to
understand
where
we
are
and
anything
that
we
can.
You
know
look
at
our
end
right
now
to
support
it.
I
got
the
CSI
driver
with
iSCSI
working,
and
you
know
you
know
it's.
It's
really
a
POC
effort
at
this
point
in
time.
E
You
just
have
to
understand
all
the
things
to
make
it
work
so
pretty
early
days,
I
would
say
so
just
trying
to
feel
where
the
Windows
support
is
in
terms
of
kubernetes
and
anything
that
we
could
work
on.
Educating
its
stable.
D
E
E
Yeah,
that
is,
that
is
exactly
so
Linux
nodes
will
be
the
storage
providers
Windows
nodes,
which
would
run
only
applications
consuming
volume
from
store.
D
E
I,
don't
know
whether
I
name
it
right,
but
I
believe
we
all
understand
what
I'm
talking
about
so
the
post.
What
what
do
they
end
up
is
I
I
have
issues
you
know,
running
privilege,
commands
of
host
containers.
Several
other
restrictions
like
pipes
cannot
be
imported
and
if
some
of
them
are
privileged,
then
all
the
containers,
that's
part
of
the
Pod-
have
to
be
privileged
as
well.
E
Several
other
you
know,
kind
of
I,
I
would
say
forced
constraints
right
now
and
and
for
some
reason,
I
haven't
still
figured
out
why
I
cannot
run
the
Powershell
commands
from
within
the
host
privileged
containers
in
Windows,
so
I
I
turned
to
actually
running
those
services
like
cubelets
directly
as
the
host
service
and
everything
was
successful
there.
E
So
that's
that's
how
I
I
got
the
CSI
driver
up
and
running
right
now,
so
just
trying
to
see
whether
whether
are
there
anything
that
I
am
missing,
that
that
is
known
to
you
guys
that
I
should
be
aware
here.
A
Yeah,
so
the
CSI
proxy
has
documentation
on
how
to
do
this.
If
you
install
it
on
the
host
and
then
I
just
linked
in
the
chat,
the
kept
that
they've
opened
to
transition
to
that
to
using
host
process
containers,
and
so
you
can
follow
that
for
the
official
way
to
do
that.
I
know.
A
Mark
has
gotten
host
process
containers
working
in
CSI
proxy
and
using
the
host
passing
screeners,
and
so
you
can
follow
that
I
think
we
have
that
in
our
Sig
Windows
tools
as
an
example
so
yeah.
A
So
if
you
want
like
the
Jason
proxy
officially
does
you
know
you
have
to
kind
of
install
it
and
you
install
it
on
the
host
and
you
wire
it
all
up
directly
on
the
host
and
then
we
did
like
a
prototype
where
we
got
it
working
in
host
process
containers
and
then
the
CSI
team,
the
there's
a
Windows
CSI
proxy
group
that
you
can
connect
with,
and
they
they
know
that
they're
they're
trying
to
move
CSI
proxy
into
using
host
process
containers
and
so
that
that's
the
cap
that
I
linked
there.
E
But,
but
on
CSI
proxy
itself,
are
we
I
mean?
What's
what's
the
general
consensus?
Do
we
really
need
them,
given
that
now
these
host
process
containers
can
do
privileged
operations?
Why
are
we
trying
to
carry
that
API
forward,
yeah.
A
Well,
so
that
that's
what
the
cap
outlines
and
they
they,
basically
the
you
needed
the
proxy
beforehand
to
be
able
to
communicate
through
the
containers
and
what
they
want
to
do
is
they've,
because
through
that
proxy,
they
created
a
bunch
of
libraries
that
do
all
of
the
underlying
OS
stuff,
the
windows
OS
stuff,
and
they
want
to
be
able
to
move
those
into
the
actual,
like
the
provider
like
the
CSI
providers
themselves
and
provide
a
Windows
library
for
it
and
I
might
be
mangling
this
a
little
bit
because
I'm
not
super
involved
in
that
process,
but
that
that
is
kind
of
the
idea
is
that
they're
gonna
get
a
I,
think
they're
going
to
get
rid
of
the
proxy
itself
and
then
use
the
the
work
that
they
did
and
turn
it
into
a
library
that
can
be
implemented
by
all
the
other
CSI
providers.
A
B
A
There
is
a
slack
Channel,
CSI
proxy
windows
or
CSI
windows,
or
something
like
that.
Okay,.
A
Thanks
I,
don't
see
sometimes
they
come
to
this
meeting,
but
I
don't
see
any
of
them
today.
E
A
So
I
think
we
can
go
on
to
the
agenda
here.
I'm
Not
Who
sure
who
put
this
on
there,
but
Doc's
pairing
meeting
we
had
one
previously
and
I
think
it
fell
off
Auburn.
Would
you
were
you
I
think
you
brought
that.
B
Up
yeah,
so
this
is
I.
Think
Mark
and
I
were
talking
about
this.
We
just
wanted
to
discuss.
Maybe
we
could
move
this
to
next
year,
but
figure
out
what
to
do
about
that
meeting.
You
know
sort
of
re.
You
know
refocused
at
the
just
something
we
need
to
talk
about.
We
could
maybe
talk
about
it
next
year
when
Mark
is
also
around
it.
There'll
be
more
people.
B
A
Cool
and
then
Windows
Cube
proxy
J.
Do
you
want
to
take
this?
One
I
know
there's
a
little
bit
of
activity
over
last
week,
yeah.
D
So,
okay,
so
we
I
have
a
repo.
It's
I've
got
the
code
put
over
there,
mostly
compiling
and
I.
It
has
a
back.
It
just
has
a
back
end
from
kpng,
which
has
a
sep
completely
separate
Windows,
Coupe
proxy
implementation,
and
we
are
mocking
out
the
front
end
for
kpng
and
importing
the
bits
for
the
client
so
that
we
can
sort
of
start
it
in
a
lightweight
way
and
put
a
basic.
D
D
So
but
that's
not
in
the
repo
that
Mark
put
up
yet
and
Doug
landgraf
said
he
was
interested,
so
I
said:
okay
Doug,
if
you're
interested
I
was
like
here
take
a
week,
see
if
you
could
figure
out
how
to
finish
this
off
and
I'll
put
the
repo
in
the
docs
notes.
So
this
is
the
starting
point
for
it.
Where
is
it.
D
Yeah,
so
that's
it!
That's
a
it's
a
just
a
starting
place
and
Doug's
looking
into
the
code,
if
Doug
doesn't
get
it
working
in
the
next
week,
I'll
take
it
over,
but
I
figured
I'd.
Give
him
give
him
a
few
days
to
look
at
it,
and
and
so
we'll
have
something
kind
of
prototype
that
what
kind
of
works
within
a
within
a
couple
weeks
and
then
and
then
and
then
it's
I'll,
probably
kind
of
ask
Dave
to
start
poking
poking
around
with
it
and
we'll
see
what
to
do
next.
D
If
anybody
wants
to
help
with
some
really,
if
really
if
anybody
wants
to
be
a
co-maintainer
of
it
and
like
be
a
co-owner
of
the
code
base
and
really
dig
in
on
it
and
help,
let
me
know
we'll
transfer
it
to
kubernetes
six
repo
within
hopefully
within
a
month
right.
A
Oh
I,
I,
don't
know
I
I
I
saw
an
issue
open
it,
but
I
don't
I,
don't
know
if
we
actually
created
it.
Okay,.
D
Yeah
I,
don't
think
it's
it's
closed
yet.
But
okay,
but
you
know
the
hard
part
for
now
is
just
getting
all
the
code
migrated
in
a
way.
That's
lightweight
and
everything
so
but
I
think
we'll
be
I.
Think
the
rest
will
be
pretty
easy.
E
At
a
high
level,
I
mean
generally
asking
trying
to
understand.
What's
the
work
put
out
here
so
in
the
in
Linux,
we
we
understand
I
mean
at
least
my
understanding
is
Q
proxy
uses,
IP
tables
and
connection
trackers
to
get
things
done.
What
do
we
have
equivalent
here
in
Windows?
You
see
in
kpng
spinal
cord?
Is
that
something
part
of
the
windows
kernel
that
we
are
using
for
the
key
proxy.
D
Yeah
so
the
the.
D
D
You
have
to
read
all
the
kubernetes
services
right
and
then
you
have
to
sort
of
combine
them
into
some
kind
of
a
data
structure,
some
kind
of
in-memory
data
structure,
that's
easy
to
calculate
diffs
against
because
you
may
be
making
a
new
endpoint
and
then
that
endpoint
is
inside
of
a
service
and
you
need
to
now
add
a
new
endpoint
behind
a
service
right,
and
so
you
need
to
know
like
is
the
service
already
already
created?
And
then
now
this
new
endpoint?
D
If,
if
this
service
is
created,
add
this
endpoint
to
that
service
and
so
on
and
so
forth,
and
so
you
need
to
know
like
has
something
changed
in
the
overall
State
space
of
kubernetes
network
right
and
that
involves
changes
to
Services
changes.
Standpoints
changes
to
topology
addition
of
new
types
of,
maybe
somebody
makes
a
service
of
type
load
balance,
or
maybe
somebody
changes
a
service
of
type
cluster
IP
to
a
service
of
type
node,
Port
right,
there's
all
these
Deltas.
D
So
so
yeah,
it's
the
same,
logical
thing,
but
with
hns
you
have
to
do
it's
different
because,
like
for
example,
you
know
it
has
to
decide.
Is
this
a
network
overlay?
And
if
so,
do
this?
Because
hns
is
the
Windows
networking
subsystem
right?
And
so
it's
like?
Okay,
if
it's
an
overlay,
do
this
create
an
endpoint
this
way,
if
it's
not
an
overlay,
create
an
endpoint
some
other
way
when
I
first
start
up,
I
need
to
make
the
hns
device
whatever.
D
That
is
that's
a
special
thing
that
you
have
to
do
for
Windows
that
you
don't
have
to
do
for
IP
tables,
so
there's
like
little
little
little
minor
differences
in
the
way
that
the
hns
windows
networking
apis
work
because
they
were
built.
For
you
know,
iptables
was
built
as
a
firewall
and
hns
was
built
for
doing
virtual
networking
for
virtual
machines
and
you're,
taking
both
of
those
and
hacking
them
up
so
that
they
can
run
as
a
as
a
as
a
load
balancer
for
kubernetes
right.
So
it's
a
total
different.
A
Yeah
and
and
to
be
clear,
this
already
works.
We
already
have
a
coup
proxy,
it's
in
tree
right
now,
and
the
work
that
we're
doing
right
now
is
to
take
that
from
entry
and
move
it
out
a
tree.
We're
not
re-implementing
anything
at
all.
It
all
is
already
there
and
Jay's
been
kind
of
leading
the
effort
to
move
that
out
of
tree
so
that
we
can
move
faster
and
iterate
and
you
know
be
able
to
contribute
a
little
bit
more
effectively
as
a
Sig.
D
Yeah
and
the
way
this
all
started
is
a
guy
made
a
project
called
kpng,
where
he
he
made
explicit.
The
stuff
I
was
talking
about
where
it's
like.
Oh,
you
need
a
thing
to
talk
to
the
API
and
aggregate
that
model,
and
then
you
need
another
thing
to
write
back
in
networking
rules
and
he
separated
those
things
out.
His
name
is
Mikhail
Clouseau
and
that
repos
kubernetes
Sig
slash
kpng.
D
So
he
started
getting
that
to
work
with
all
these
different
back
ends
and
then
somewhere
along
the
way
as
Sig
Windows
we're
like
well
geez,
since
this
is
kind
of
working
outside
of
the
entry
proxy.
What
if
Sig
Windows
had
its
own
Coupe
proxy?
That
was
out
of
tree
and
then
we
could
patch
it
whenever
we
wanted,
we
could
add
features
to
it.
We
wouldn't
be
blocked
on
other
cigs
and
so
on
and
so
forth.
Right.
So
that's
how
that
whole
thing
is
evolved.
E
Okay,
well,
that's
great
to
know
one
one
thing,
I
know
just
as
a
follow-up
I
mean
I,
don't
know,
I'm
thinking,
it's
a
follow-up,
so
the
service
endpoints
right
so
I'm
I'm
on
circling
back
to
something
that
I
have
been
following
up.
So
two
questions:
I
have
one
one
is
directly:
where
is
the
NFS
support
in
Windows?
So
we
were
talking
about
SMB
for
shared
volumes
from
Windows,
but
is
there
any
talk
of
NFS
being
supported
in
Windows
natively?
E
A
I
I,
don't
follow
the
proxy
the
CSI
side
of
the
world
very
closely,
but
I
do
think
there
is
an
NFS
CSI
driver.
So
I
can
quickly
look
yes,
Paris
yeah,
okay,.
F
E
Back
ran
into
some
issues
and-
and
we
had
to
give
up
Midway,
so
is
this
officially
supported
by
the
Microsoft
team.
A
So
most
of
the
CSI
proxy
stuff
is
developed
by
the
community
and
so
I
think
the
only
ones
that
Microsoft
really
contributes
very
heavily
to
is
the
like
Azure
file
and
Azure
disk
CSI
proxies.
The
rest
of
them
are
mostly
Community
Driven.
E
D
E
E
Server
outside
and
then
consumes.
You
know
volumes
out
of
it
on
on
Linux
nodes,
I'm
trying
to
Circle
it
back
to
you
know:
Windows
node,
being
part
of
the
whole
cluster
along
with
Linux
nodes
and
how
sharing
of
volumes
from
Linux
nodes
to
windows,
Can
Happen.
So
in
that
aspect,
I'm
looking
at
NFS
because.
F
E
Natively
there
on
Linux
and
we
can
export
those
volumes
and
if
NFS
I
mean
if
Windows
knows,
could
actually
import
them
and
they
understand
NFS
client
actions.
We
should
be
able
to
establish
an
I
o
path.
A
What
I
would
suggest
is
that
you
join
the
CSI
Windows
meeting
if
you're,
not
in
the
slack,
already
go
ahead
and
join
slack.
Do
you
know
how
to
join
slack
yeah.
A
And
then
so,
there's
a
CSI
Windows
Channel
reach
out
to
them
find
out
when
their
meeting
is
and
they're
going
to
be
the
ones
that
are
experts
in
this
area.
A
I,
don't
know
that
we
have
I,
think
some
of
us
have
set
them
up,
but
I
don't
know
that
we're
the
ones
developing
them
and
the
experts
here
so
I
would
reach
out
to
them
and
join
their
meeting
and
they're
going
to
probably
be
able
to
answer
a
lot
like
the
question's
a
lot
more
easily
than
we
than
we
will.
E
Okay,
okay,
see
the
other
question.
I
had
was
service
endpoints
that
we
see
so
I
I
see
iSCSI
is
supported
on
Windows
I
mean
it
sits
there,
but
can
can
we
export
the
you
know
the
volume
to
a
service
endpoint
to
the
Windows
modes?
And
can
we
let
the
you
know
the
the
isci
target?
That's
that's
part
of
the
windows
nodes
move
in
case
the
node
fails
and
still
I
o
path
will
be
okay.
E
So
this
is
this
accepted
for
deployment
from
Windows
nodes
in
kubernetes,
environment.
E
Should
I
be,
you
know
talking
about
this
again,
CSI
windows.
E
A
That's
where
I
would
go,
do
you
have
do
you
know
anything
here,
yeah.
B
I've
posted
some
links
that,
like
me,
you
can
read
it,
but
I
I'm
I'm,
with
with
James
on
this
I,
think
the
best
place
for
all
this
is
slack.
You
should
start
some
threads
on
the
CSI
windows
and
they
would
be
able
to
like
direct
you
in
the
right
direction.
A
Okay,
cool
yeah:
he
dropped
a
few
notes
in
the
meeting
chapter
so
check
those
out
and
we're
about
five
minutes
past
time.
So
Finance
we'll
see
you
all
and
then
the
New
Year
remember,
there's
no
meeting
next
two
weeks.