►
From YouTube: Kubernetes SIG Windows 20190423
Description
Kubernetes SIG Windows 20190423
A
Hello,
everybody
and
welcome
to
their
sick
windows,
meetup
I.
Thank
you
all
for
attending
the
the
first
order
of
business
is,
if
you
are
doing
API
reviews
make
sure
you
follow
the
the
process
that
outlining
the
API
review
document.
That's
posted
in
our
meeting
notes:
I'll
post
it
here
on
slack
as
well,
but
please
make
sure
that
you
include
the
right.
Approvers
Jordan
Leggett
has
been
the
guy
from
capi
&
Seek
architecture
has
been
following
most
of
our
sake,
he's
very
well
aware
of
some
things
were
working
on.
B
Yeah
so
the
container
day,
one
I
got
some
good
feedback
on
the
g'tok
version
of
it
last
week,
but
I
still
need
to
move
that
into
the
cap
template
and
get
that
moving
forward.
So
I'm
hoping
to
have
some
time
to
work
on
that,
maybe
maybe
today
otherwise,
tomorrow
and
I'll,
follow
up
with
the
enhancement
team
just
to
let
them
know
that
it's
coming
in
a
bit
late,
okay,.
C
Cap
and
loop
Amir
took
a
look
at
it
yesterday,
so
I
have
to
take
another
look
this
morning.
I'd
appreciate
if
Patrick
could
also
take
a
look,
it's
already
starting
to
be
in
cab
format
and
Lou
premier
told
me
the
place
where
I
should
make
the
pr2
put
that
in
enhancement.
So
that's
the
next
step
and
also.
A
So
for
the
for
the
QbD
m4
for
approvals,
we
need
to
make
sure
that
Tim
Sinclair
for
reviewers
it
could
be
me
Patrick
and
you
and
lube
Amir,
so
that
should
work
now.
One
thing
you
know
from
some
of
the
things:
I'm,
the
lubberman
and
I-
don't
see
him
shion
today,
I'm
seeing
balancing
here,
it's
pretty
late
for
him,
but
the
one
thing
is:
we
don't
need
to
solve
all
the
technical
problems
now
right.
So
we
need
to
make
sure
that
we
outline
what
our
process
should
look
like
and
least
some
unknowns.
A
If
we
have
them
and
then,
as
you
go
through
the
implementation,
we'll
figure
out
how
certain
things
work,
I
mean
the
entire.
The
cab
is
there
to
architectural
II,
discuss
how
this
is
gonna
work
and
talk
about
some
of
the
features
and
test
cases
that
we
plan
to
incorporate
and
what
it
will
look
like
for
for
beta
or
production
workloads.
But
you
don't
have
to
solve
everything
today
right,
so
we
should
make
forward
progress.
Finalize
a
cab
I
went
through
your
dog
before
I'll.
A
A
A
D
E
D
A
D
A
A
The
feature
from
alpha
to
beta
I
think
that
in
general
sense
from
Q&A
standpoint
is
it's
kind
of
two
things:
stability
for
the
stability
as
in
like
making
more
improvements,
and
then
time
basically
make
sure
that
it's
been
out
there
for
a
period
of
time.
It's
undefined
how
long
the
our
users
have
had
the
chance
to
access
it
from
our
feedback
and
and
let
the
feature
stabilize,
but
there's
no
clear-cut
criteria
right.
Some
of
it
is
subjective.
You.
B
B
One
of
the
criteria
that
I've
heard
and
I'm
not
sure
if
it's
written
down
is
that
during
alpha,
it's
okay
to
break
api's
once
you
reach
beta
you're,
not
supposed
to
like.
So
that's
supposed
to
be
kind
of
a
test
for
stability.
There
like
the
API,
is
finalized
and
then
once
it's
been
through
a
little
bit
more
break
time,
then
it
promotes
to
stable
yeah.
E
D
D
A
B
B
But
this
is
something
that
we
were
discussing
back
and
forth
on
the
slack
channel
with
with
Peter
last
week,
but
sometimes
if
you've
got
concurrent
shutdown
of
pods,
some
of
them
can
get
stuck
in
a
state
where
just
as
terminating-
and
it
just
sticks
there
forever.
And
so
we
found
a
problem
with
cleaning
up
to
the
network.
Endpoints
and
I've
got
a
command
on
there
that
you
can
use
to
help,
look
to
see
if
those
are
being.
If
those
are
being
leaked
and
if
that's
the
case,
then
the
power
gets
stuck
in
the
terminating
state.
B
F
E
A
A
B
A
So
have
a
few
excellent,
so
on
Monday
during
the
contributor
summit,
we
have
a
three-hour
reservation,
so
I
will
make
sure
all
of
you
guys
have
an
invite
that
we
give
us
an
opportunity
to
sit
down
and
chat
and
outside
of
this
very
quick
half
an
hour
meetings
and
talk
about
you
know
what
we
want
to
go
as
sick
windows,
people
for
one
of
its
open-ended
for
us
to
chat
about
anything.
I
know.
We
also
have
a
session
during
the
conference,
but
you
know
that's
mostly
when
I
get
a
lot
of
users.