►
From YouTube: Kubernetes SIG Windows 20190402
Description
Kubernetes SIG Windows 20190402
A
Hello,
everybody
and
welcome
to
another
sip
windows.
Meetup,
it's
the
second
of
April.
You
guys
are
lucky
right:
it's
not
the
1st
of
April,
because
I
loved
putting
a
lot
of
pranks
on
April
Fool's
Day.
So
you
know
we're
safe
here
all
right.
So,
let's
dive
into
the
agenda.
I
added
a
few
things
in
there
in
terms
of
communications
and
things.
I
have
happened
in
the
last
week,
overall,
mostly
good
things
for
for
our
sakes.
So
let's
run
through
them.
The
first
thing
is
Craig.
B
Specific
topics
for
women's
container
to
the
community,
so
I
am
definitely
committed
to
sort
of
moderating
and
mediating
communications
in
there,
but
I'd
also
appreciate
it.
If
other
folks
active
in
the
SIG's
would
participate,
I
think
we
can
do
a
lot
to
help
people
use
this
new
capability
more
easily.
One
thing
to
note
about
this:
is
it's
got
a
pretty
good,
Google
SEO
characteristics
as
well,
so
anything
you
you
post
in
there
with
links
and
stuff
will
have
show
up
pretty
well
in
searches.
B
A
B
A
C
C
C
A
A
All
right,
well,
I,
guess
you
guys
can
I
can
do
that
and
start
watching
the
topics.
Excellent!
Thank
you.
Thanks
thanks
Craig.
So
the
second
topic
for
today
there's
a
three
blog
post
that
came
out
recently
that
all
of
them
are
super
valuable
in
terms
of
of
both
educating
customers
and
users
on
key
features
of
kubernetes
key
features
of
kubernetes
with
Windows,
specifically
as
well
as
the
overly
networking
that
worked
on
Microsoft
is
doing
and
driving
for
kubernetes
on
Windows.
So
Craig
and
Taylor
wrote
one
of
them.
A
A
The
next
topic
is
George
kind
of
has
been
driving
these
office
hours
for
kubernetes.
Think
of
them
as
an
opportunity
for
users
to
come
in
and
talk
to
subject
matter
experts
in
the
kubernetes
community
kind
of
voice,
their
concerns
get
their
voice
heard
and
you
know
facilitated
discussion.
So
we
are,
we
are
gonna,
be
participants
in
that
on
April
11th
at
ADM.
I
expect
some
some
of
the
key
members
I
have
delivered
functionality
in
1:14
that
they
should
attend.
A
C
A
C
D
A
So
you
names,
you
said
Kalia
or
Kalia,
Kalia,
Kalia,
very
nice,
so
there's
there's
as
part
of
this
work.
That's
gonna
need
to
be
a
partnership
between
the
windows
team
and
the
C
cluster
life
cycle
team.
So
can
you
just
ping
me
like
after
this
and
I'll
I'll
put
you
in
contact
with
someone
from
the
C
class,
the
lifecycle
team?
That
is
also
tasked
to
kind
of
help
in
this
endeavor.
So
I
guess
the
first
step
would
be.
A
You
know,
take
stock
of
what's
out
there,
what
exists
and
what
doesn't
exist
and,
if
possible,
we
need
to
create
a
plan
on
adding
this
support
and
we'll
need
a
cap.
So
we
can
help
you
with
you
know
they
can
process
fairly.
Well-Documented
Knights
couldn't
be
the
second
release.
We're
gonna
be
following
it,
but
our
goal
is
to
kind
of
get
the
cab
out
there
as
soon
as
possible.
A
C
And
so
I
took
a
brief
look
at
this
before
and
the
main
main
hurdles
that
I
think
I
think
we
need
to
work
on
are
right.
Now,
Qube
ADM
gets
a
cubelet
config
that
has
a
lot
of
Linux
specific
options
set,
and
so
there
needs
to
be.
You
know
some
sort
of
filtering
or
an
equivalent
Windows,
config,
created
and
I
think
the
closer
lifecycle
folks
will
have
some
guidance
on
what
the
right
way
to
do.
That
is
because
I
think
they
actually
have
a
goal
of
storing
the
configuration
in
kubernetes
itself,
and
so
maybe
when.
C
The
configuration
it
needs
to
just
generate
so
doing
that
versus
an
adapter
would
be
a
discussion
for
them
and
then
the
other
thing
is
that
it
uses
a
lot
of
Linux
specific
pads,
and
so
when
it
goes
and
creates
the
files.
The
going
libraries
will
automatically
create
those
paths
on
Windows.
But
you
end
up
with
you
know
like
a
slash
at
c:
/
kubernetes,
slash,
cubelet,
config,
or
something
like
that,
and
some
of
those
paths
may
need
to
change.
C
C
A
Let's,
let's,
let's
start
the
process
of
documenting
everything
that
we
plan
to
do
here
and
that
way
we
can
eventually
put
it
in
a
cab.
You
can
start
a
Google
Doc
if
that
that
might
be
a
little
bit
easier
for
us
to
all
document
and
thread
in
iterate
and
look
at
the
kind
of
timelines
for
the
previous
release.
It
looks
like,
and
the
cab
enhancements
proposal
freeze
was
end
of
January
before
so
I
assume
that
it
will
probably
be
third
week
of
April
for
this
for
this
release.
A
E
So
I
think
a
couple
of
weeks
back
James
and
you
jus
and
I
as
well
as
Nick
from
Microsoft.
We
started
discussing
like
what
should
be
the
future
of
you
know
what
are
some
of
the
things
we
could
do
on
the
storage
side
for
Windows
and
I
wrote
up
a
doc
I
think
we
briefly
went
over
it
during
the
last
meeting.
But
basically
the
idea
was
to
collect
most
of
the
thoughts
there,
get
it
reviewed
by
you
to
enging
and
then
present
it
a
six
storage
to
kind
of
get
the
overall
opinion
from
them.
E
So
we
did
manage
to
go
over
it
during
the
last
six
oil
meeting
and
it
seemed
like
the
destroyed
folks,
mainly
Saud
and
others
we're
like
really
supportive
of
like
fake,
like
exploring
the
storage
proxy
proxy
option
that
I
laid
out
there
to
enable
CSI.
The
idea
being
you
know,
take
it.
Can
we
have
some
sort
of
a
proxy
privilege
binary
that
does
some
of
the
privileged
operations
to
get
things
across,
specifically
the
mounts
and
things
like
that
that
the
other
CSI
drivers
can
make
use
of
so
so
they
were
like
there
weren't.
E
E
But
they're
not
maintained
in
a
kubernetes
SIG's
repo,
so
that
obviously
meant
that
bad
met
like
quite
a
bit
more
resistance.
Cuz.
You
know
the
bar
for
entry.
Plugins
right
now
is
very
high,
so
I
think
the
solution
there
was.
You
know,
explore
the
CSI
option
if
there
are
any
major
blockers
and
that
cannot
be
delivered,
then
go
to
cigarete
and
ask
for
an
exception
around
SMB.
But
we
were
thinking.
Maybe
I.
Scuzzy
is
something
we
can
introduce
some
of
the
Windows
PowerShell
scripts
into
where
they
use
ice
cuz.
E
The
idiom
only
today
the
main
thing
that's
going
to
enable
is
external
provision
or
scenarios
where
you
can
use
something
like
say,
Trident
from
that
app
or
from
some
other
storage
vendor
and
be
able
to
provision
dynamically
provisioned
Peavey's,
not
just
that.
Go
for
the
Linux
volume
services,
but
also
Windows.
A
F
Yes,
so
I
think
sometimes
also
disable
those
secrets
tests,
because
those
are
like
kind
of
using
meanings,
sake
permissions
to
test
and
it
does
not
applicable
for
Windows.
So,
but
you
know,
those
tests
are
like
a
part
of
conformance
test.
I
think
we
need
to
have
some
tests
for
those
either
way
we
need
to
like
modify
the
tests
and
to
fit
in
like
Windows
environments
or
another
way.
It's
kind
of
like
there
is
a
some
program
trying
to
translate
from
Linux
permission
to
Windows.
F
A
F
G
Look
at
it
later,
but
for
the
most
part
so
setting
fire
permissions
will
be
ignored
by
windows
cubelet.
So
unless
is
just
checking
for
the
default
file
permissions,
those
cannot
pass
on
on
Windows
and
they
should
the
test.
The
tests
should
have
the
Linux
only
tag
primarily
other
tests,
which
are
checking
the
default
644
permissions
or
Windows
Server
5/5.
F
G
So
there
are
primarily
three
types
of
tests
for
actually
which
we've
disabled
regarding
storage.
One
of
them
is
regarding
file
permissions,
which
we
do
not
support,
running
as
user
or
root,
which
we
did
not
support.
Learners
group,
which
we
do
not
support
and
running
on
storage,
medium
memory,
so
anything
on
in
these
categories.
G
F
F
Just
for
test
I
will
ping
like
a
snack
but
those
tests
again,
and
so
the
item
is
just
like
I
pre
mentioned
before
the
stop
has
rena
is
working
for
like
this
cannot
GCPD
this.
But
there
is
an
issue
saying
SMB
does
not
support
supposed
so
I'm
wondering
on
our
documents.
Should
we
clarify
like
what
is
support?
What
is
not
supported,
because
right
now
is
just
saying
some
house
is
not
sorted.
I
think
I.
G
A
F
A
C
A
C
A
A
F
A
I
C
I
E
A
I
I
H
A
A
H
A
A
E
C
H
C
A
C
I'll
circulate
a
doc
in
the
meeting
notes
for
for
next
week.
I'm
still
finishing
up
some
investigations
there,
but
the
short
summary
is
that
we're
going
to
need
to
update
multiple
caps
related
to
run
time
class,
and
so
I
need
to
write
up
two
use
cases
for
this
and
I'll
do
that
before
next
week.
The
builds
that
we
actually
need
don't
exist
yet,
but
I
think
most
of
the
code
is
there.
C
If
we
don't
depend
on
the
upstream
build
there,
then
maybe
we
pick
another
repo
and
say
you
know
for
the
course
of
alpha
we're
gonna
build
from
Patrick
land
container
D,
or
something
like
that.
But
I'll
get
those
details
out
there
so
and
and
I'll
be
getting
that
to
sig
windows
and
sig
node
for
for
discussion
next
week.