►
From YouTube: Kubernetes SIG Windows 20190514
Description
Kubernetes SIG Windows 20190514
A
Hello,
everybody
and
welcome
to
another
sick
windows
Meetup.
This
is
their
14th
of
May.
Thank
you
all
for
attending
as
always
be
aware
that
this
is
going
to
be
publicly
posted,
so
follow
the
code
of
contact
of
the
kubernetes
community.
I,
see
I
even
said,
they're
the
official
field
today,
so
we
need
to
follow
a
code
of
conduct
all
right.
A
So
a
couple
of
notes
here:
Adam
if
we're
gonna,
be
able
to
talk
about
the
first
one,
but
the
second
thing
on
our
agenda
is,
for
the
folks
are
attending
the
Kubik
on
in
Barcelona
next
week.
Please
make
sure
you
sign
up
for
the
face-to-face
meetings.
Segundos
has
one
and
then
also
please
sign
up.
The
contributor
summit
has
a
party
slash
networking
event
for
Sunday
night
that
believe
it's
at
5:00
p.m.
local,
it's
at
the
different
venue
from
the
pubic
own
or
the
contributor
summit.
So
please
try
to
attend.
A
A
Is
the
chat
icon
run
away
from
me,
so
I
posted
here
on
zoom
as
well?
That's
the
ticket
with
the
identifying
by
the
login
options.
In
our
last
meeting
we
had
talked
about
having
someone
from
Microsoft
look
for
some
resources
on
that,
since
Patrick
is
not
on
I,
don't
know.
If
anybody
else
has
an
update
on
this
Kalea
or
city
nation
yeah.
A
C
A
Doses
well,
yeah.
That's
I
asked
Claudia
to
comment
on
that.
That
was
one
of
the
tickets
resurfaced
last
week.
So
last
week
one
things
I
did
Elena
was
I
found
like
four
or
five
issues
that
we
wanted
to
do:
additional
follow-up
beyond
or
three
or
four
caps
and
assigned
honors.
So
Claudia
was
a
sign
them
now
on.
So
if
this
is
more
PR
we
can
do.
I
saw
I,
saw
some
comments
and.
C
D
C
A
A
Excellent
I
think
thank
you
for
taking
care
of
that
and
kind
of
the
purpose
of
that.
Api
review
was
to
Train
Pat
Drake
and
deep
and
myself,
but
I'm
not
really
gonna
be
an
API
reviewer,
so
they
can
actually
start
handling
API
reviews
for
sick
Windows
and
then
our
goal
here
is
that
eventually
we're
gonna
have
three
API
reviews.
Foxy
Windows
is
gonna,
be
Ben
if
he
wants
to,
of
course,
Patrick
and
the
and
those
are
going
to
be
the
three
API
review
on
or
so
the
next
meeting
will
get
been
involved.
A
All
right,
I
think:
that's
it
everybody.
We
got
twenty
minutes
back.
I
know
it's
a
short
meeting
today.
Next
week,
no
meeting
Kubek
on
so
virus
attending
enjoy
whoever's.
Not
attending.
Will
we'll
catch
up
with
you
guys
the
week
after
and
you
keep
getting
at
it.
The
deadlines
for
1:15
are
really
really
quickly
approaching,
so
the
folks
are
working
on
different
work
streams
where
that's
around
his
username,
the
container,
D
or
or
cube
ATM.
Let's,
let's
keep
at
it.
A
B
So
basically,
Ben
on
the
project
now
Lumiere
and
I
were
able
to
use
cube
EDM
to
join
a
Windows
node
to
a
cluster
with
a
little
bit
of
hacking.
So
most
of
it
is
there
I
think
the
big
issue,
and
then
you
can
like
jump
in
is
the
file
path.
So
basically
just
how
Windows
interprets
the
code
like
it'll,
append
some
file
paths
instead
of
going
from
like
there
really
so.
E
B
So
basically,
Lumiere
has
a
PR
out
for
that
right
now,
but
it's
not
anticipated
to
go
in
I.
Think
there's
some
contention
about
the
best
way
to
resolve
that
and
right
now
with
our
like
I
guess,
our
tests
are
like
us
working
with
cube
ATM
in
its
current
state,
we've
been
using
the
cube
light
config,
that's
in
the
cluster,
the
Linux
default,
so
Ben,
lube,
Amir
and
I
are
going
to
have
a
meeting
right
after
this
to
discuss
how
we
want
to
handle
the
Windows
portion
of
that.
A
My
apologies
guys
here
on
the
Taiping
here
at
home,
I
have
a
silent
keyboard.
This
laptop
is
not
silent.
I
think
the
mic
is
probably
near
the
near
the
keys.
We
actually
never
had
dedicated
notes.
Taker
so
may
have
to
do
that.
Eventually,
great
great
progress
on
cube
ADM,
the
is
luke
for
me
being
able
to
kind
of
I
know
we
had
an
unnecessary
an
issue,
but
there
was
a
concern
by
c-class
lifecycle
that
you're
putting
too
much
workload
on
him
in
terms
of
both
as
a
reviewer,
as
well
as
a
contributor
to
cube
ADM.
B
A
B
A
If
you
guys
can
find
any
ways
to
kind
of
lighten
his
load
and
and
and
kind
of
take
some
of
these
items-
and
there
is
no
I'm
saying
that
this
will
have
another
fact
in
the
future.
What
would
you
see
cluster
lifecycle
because
they
were
only
able
to
allocate
that
was
small
portion
of
his
time
and,
if
he's
taking
significant,
more
they'll
be
less
likely
to
give
us
additional?