►
From YouTube: Kubernetes SIG Windows 20200526
Description
Kubernetes SIG Windows 20200526
A
Hello,
everybody
and
welcome
to
another
sick
windows.
Meetup,
it's
the
last
one
of
the
month
of
May,
it's
the
26th
of
May
today
and
as
always,
it's
a
recorded
meeting.
So
please
adhere
to
the
CN
CF
code
of
conduct,
I
hope
everybody
had
a
great
great
weekend.
I
do
based
in
the
United
States
and
you
got
to
observe
Memorial
Day
and
got
at
least
three
days
off.
If
not
more,
you
know
we
have
a
very
light
agenda
today.
I
would
also
call
it
non-existent
I
kind
of
expected,
given
the
the
long
break
in
the
u.s..
A
A
couple
of
quick
things
so
mark
and
I
worked
with
seek
contributor
experience
team
last
week.
Well,
I
did
it
last
week,
Marty
the
week
before
I
believe
and
basically
produced
a
document
that
basically
talks
about.
You
know
you
know
how
sick
windows
was
formed.
What
is
that
you
know
some
of
the
challenges
of
experiencing
how.
A
How
we
are
attracting
new
contributors
and
users,
you
know
what
are
some
of
our
goals
in
mind
and
we're
all
going
as
a
community,
and
you
know
it
thinks
at
the
high
level
like
that,
so
that
as
new
folks
are
interested
in
coming
through
into
kubernetes.
Is
this
something
that
they
might
be
interested
in
and
I
think
you
know,
sick
windows
offer
some
very
unique,
very
unique
things
that
nobody
else
does
so,
for
example,
a
you
wanna
learn
go.
You
can
learn
that
both
on
Linux
or
on
Windows.
So
we
have
it.
A
Do
you
want
to
learn
how
to
do
the
communities
API
and
and
and
learn
communities
itself?
We
have
it
like
sick
windows.
Much
does
everything
from
storage
to
networking
to
compute
cluster
lifecycle
as
well?
Do
you
wanna,
learn
windows
containers
specifically?
That
would
definitely
have
that
too.
So
it
gives
you
probably
an
experience
to
dip
your
toes
in
a
lot
of
different
seats
within
kubernetes,
while
belonging
to
a
single
sig
and
work
on
a
variety
of
problems.
So
it
definitely
you
know,
I
find
that
to
be
attractive.
A
A
It's
not
easy
to
get
resources
now
in
any
company
with
this
new
climate,
but
I'm
looking
for
resources
in
three
specific
areas:
I'm
gonna,
itemize
them
because
they're
of
critical
importance
and
I
kind
of
colored
in
the
priority
internally,
someone
that's
gonna
work
on
c-class,
a
lifecycle
to
help
us
kind
of
get
to
alpha
or
beta
force
across
the
lifecycle
for
Windows,
and
that
you
know.
Ideally,
we
should
start
on
three
things:
either
VMware
this
year
and
AWS.
A
Those
are
going
to
be
the
three
providers
when
I
try
to
build
I
know
that
cloud-based
need
and
some
of
the
work
that
the
Lena
and
Ben
most
in
the
past.
You
know
gonna
leverage
that
and
build
on
top
of
that.
Also,
the
cube
ATM
work
that
we
did
that's
one
area,
so
I'm
trying
to
get
to
resources
for
that
those
two
resources,
one
of
them
will
be
split
and
we
want
them
to
work
on
image.
Filter,
I,
didn't
know
familiar
with
image
filter.
A
That's
basically
the
capability
allows
you
to
bring
your
own
OS
for
for
basically
cluster
API
for
Windows.
It's
going
to
be
very
important
right
because
nobody
has
the
distribution
rights
for
Windows,
so
everybody's
gonna
have
to
build
their
own
template
before
I
call
it
that
way.
Every
every
project
course
is
something
different,
but
folks
are
gonna
have
to
bring
out
their
own
template
and
they're
gonna
have
to
customize
that,
and
you
have
the
necessary
tools
in
that
image
for
the
tool
to
be
able
to
deal
with
Windows.
A
So
so
that's
the
second
area,
so
those
two
resources
will
work
on
those
two
and
then
I'm
also
trying
to
see
if
we
can
get
someone
in
the
storage
department,
so
they
can
actually
enable
the
CSI
provider
for
vSphere
and
and
whatever
else
we
will
need
on
the
CSI
front
to
hop
deep,
I,
know
kind
of
lacking
there
and
we
don't
have
a
lot
of
resources.
So
you
know
I,
don't
have
any
data
in
terms
of
I'm
gonna
be
able
to
bring
those
resources,
but
those
are
two
big
areas
that
the
under
invested
right
now.
B
And
then
I
think
I'll
add
from
my
end,
were
mainly
focusing
on
the
container
D
and
high-end
runtime
class
support
for
Windows
from
Microsoft
right
now,
so
they
never
forget
more
resources,
they're
most
likely
going
to
go
to
that
and
followed
by
cluster
API
and
kept
C
support
just
in
terms
of
priorities.
Yeah.
A
So,
on
comes
the
support
you
saw
that
mark
we
go
the
one
guy.
That's
basically
gonna
be
responsible
for
making
sure
that
the
cubsy
provider
is
great,
but
that's
Russia.
That's
one
Linux!
First,
so
I
put
him
in
contact
with
mark
and
he's
looking
at
figuring
out
what
automation
exists
and
what
he
needs
to
do
to
make
sure
that
we'll
have
a
great
experience
there
mm-hmm.
A
C
A
C
B
A
A
We
need
will
be
there
and
available,
and
you
know
from
from
a
window
standpoint:
they
are
gonna,
enable
network,
namespace
network
policies,
so
it's
going
to
become
a
full
feature-rich
CNI
that
gonna
be
at
the
high-level
feature
compatible
with
calico,
and
it's
going
to
be
full
open
source
and
potentially
down
the
line.
You
know
you
know:
I,
don't
know
what
the
role
Matt
takes
us,
but
you
know
it's
going
to
be
driven
up
completely
in
the
open
source
and
possibly
governed
by
open
sources,
all
so
good
stuff.
There.