►
From YouTube: Kubernetes SIG Windows 20180109
Description
Kubernetes SIG Windows 20180109
A
Hello,
everybody.
This
is
bob
from
aprender
we're
starting
the
sig
windows
community
meetup
for
this
week
got
a
couple
updates,
Michael
Michael's,
not
here
today,
but
he
did.
Let
me
know
that
the
sig
Windows
blog
post,
the
crooner,
his
blog
post,
did
you
posted
and
I
will
send
out
the
link
to
the
channel.
It's
just
on
kubernetes
studeo
blog
that
grenades.
Today,
oh
he's
doing
a
demo
right
now,
good
go
along
with
that
blog
post,
so
I
guess
from
here,
I
guess:
Patrick!
It's
gonna
take
away
with
the
hub.
B
And
the
mute
button-
okay,
yes,
this
is
a
Patrick
here
Microsoft
and
one
of
the
things
that
I've
been
looking
at
was
trying
to
find
a
way
that
we
could
better
coordinate
and
track.
What
type
of
work
in
the
kubernetes
project
was
effectively.
You
know
ready
to
be
designed
and
coded,
and
what
type
of
work
would
need
changes
to
Windows
itself
before
it
would
really
be
feasible.
B
So
what
I
did
was
I
went
through
the
lists
that
we
had
from
Michael
that
were
already
over
in
the
Google
Docs.
It's
in
the
same
places
and
meeting
notes
and
I
also
went
through
a
list
that
I
built
with
with
the
folks
over
here
at
Microsoft
and
I
basically
tried
to
put
all
of
that
together
into
a
Trello
board,
and
that's
the
second
link
that
I
have
there,
and
let
me
see
if
I
can
actually
go
ahead
and
share
that
just
because
it
might
be
easier
for
me
to
point
people
to
it.
B
One
of
the
things
that
I
was
trying
to
do
was
basically
to
be
able
to
track
some
of
the
higher-level
features
that
were
there
some
of
this
stuff
might,
you
know,
end
up
with
multiple
pull
requests,
just
like
one
example
here
for
this
like
being
able
to
pass
container
resources
through
CRI.
If
we
go
and
look
at
it
the
since
this
one
involves
an
API
change,
we
actually
need
to
get
something
accepted
in
order
to
get
it
into
the
kubernetes.
1.10
release
adds
a
design
proposal
first.
This
is
something
that
we
would
need
to.
B
You
know
discuss
here
in
the
working
group
and
then
take
over
to
sig
node
for
approval
before
they
would
consider
this
API
change
for
the
next
release,
and
so,
when
I'm
working
in
in
github,
it's
nice
to
be
able
to
track
an
issue
and
understand
that
it's
it's
there,
but
I
don't
have
any
of
the
tags
available.
Then
let
me
effectively
say
what
the
priority
would
be
within
the
Windows
sig
or
what,
when
or
whether
or
which
windows
releases
would
actually
be
incompatible
with
this
change,
and
so
like.
B
Although
we
have
multiple
containers
per
pod
that
still
uses
a
shared
kernel
between
them
and
that's
not
something
that
we
believe
is
is
necessarily
the
best
profess
date
way
to
go
long
term
if
you've
been
tracking
the
news
the
last
week.
That's
yet
another
example
of
why
having
a
shared
carnal
between
with
only
user-mode
separation
can
lead
to
security
problems
down
the
road,
and
so
you
know
we're
working
on
the
design
within
windows
to
be
able
to
do
this.
B
But
the
thing
I
want
to
be
able
to
communicate
to
the
community
is
that
you
know
this
is
a
item
that
we'd
want.
Put
on
the
roadmap,
but
it's
not
ready
to
be
coated,
because
it's
gonna
depend
on
changes
of
Windows
itself,
so
I
was
trying
to
get
the
gift
prioritization
that
you
know
we
could
discuss
within
this
working
group
as
well
as
be
able
to
get
the
context
of
what's
in
there
in
terms
of
Windows
releases
and
make
it
easier
to
facilitate.
B
A
C
B
It
doesn't
mean
we
don't
need
issues
tracked
in
github
as
well
they're.
The
way
I
proposed
to
do
that.
Actually,
that's
not
a
good
one.
Let
me
go
over
here
and
look
at
the
Flex
Volume
one.
The
way
I
proposed
to
do
that
was
to
basically
put
all
the
people
issues
or
PRS
that
were
needed.
There
is
a
checklist
so
that
way
we
could
sort
of
you
know
track
what
was
done
so
like
once
this
issue
is
fixed.
B
B
So
what
I'll
do
is
go
on
the
slack
channel
and
it
started
the
threat
there.
Just
basically
ask
people
to
to
PM
me
what
email
address
they
have
associated
with
Trello.
So
I
can
add
people
to
it,
because
right
now,
I
can't
decide,
there's
no
way
that
someone
can
assign
an
item
to
their
self
unless
they're
a
member
of
the
board.
But
anybody
can
look
at
it.
So
all
I
had
people,
and
you
know
we
can-
we
can
sort
of
go
from
there.
B
As
far
as
the
priorities
go,
I
mean
the
main
things
that
I'm
aware
of
that
people
are
working
on
at
Microsoft.
Are
you
know
we're
working
on
supporting
the
hyper-v
isolation
with
the
current
release
of
Windows
there's
a
few
bug
fixes
that
are
needed
there
and
so
I'm
I'm
hoping
to
be
able
to
share
more
details
with
that,
because
that's
part
also
tracked
in
so
there's
another
link,
I
posted
to
to
Jenkins
proposal.
B
So
that's
a
discussion
I'm
having
here
with
with
some
people
inside
and
outside
of
Microsoft,
but
I'm,
basically
trying
to
get
at
specific.
But
my
goal
is
to
get
a
few
specific
people
assigned
to
sort
of
drive
this
effort
on
behalf
of
the
community,
but
I
don't
have
any
I'm
not
ready
to
talk
talk
in
detail
about
it.
D
B
D
D
The
similar
to
the
toxin,
which
is
hook
up,
phase
the
kubernetes
CI,
we
use
another
long,
tang,
similar
to
talk
scene
where
it
used
to
create
happy.
We
container
instead
of
process
containers,
so
the
could
net
use
the
CII
instead
of
talk
to
different
taka
different
container
run
time.
It
talks
a
new
runtime
called
hub
of
Iran.
Had
we
call
it
hydrogen
where
it
is
used
to
create
happy
containers
on
Windows?
D
So
this
is
one
of
the
ongoing
work
that
and
this
the
I'm
working
on
as
part
of
these
note
features
another
another
node.
Another
work
items
relate
to
sick
note
is
the
as
I
working
on
this
happy
container.
Longhand
is
the
window
results.
Configuration
is
a
actually
a
mission
feature
in
for
the
windows
container
in
her
busy
Neelix
Neelix
can
Linux
congenic.
D
Essentially,
basically,
are
they
currently,
the
kookiness
CI
only
support
the
resource,
configuration
and
security
contacts,
security
contacts,
configuration
for
Neelix
containers
and
in
the
CIA
it
does
not
have
the
configuration
for
Windows
scanner
and
windows
container
have
different
configurations
compared
to
the
Neelix
configuration
in
terms
of
CPU
code,
asleep,
you
period
the
memory
as
well
as
the
the
network.
I/O,
therefore
a
to
fill
in
this
gap.
What
patch
can
show
the
second
one
on
she'll
go.
D
Yeah,
that's
good
yeah,
so
I
actually
submit
Pia
of
design
purple
to
the
sick.
Note,
sick,
node
community
propose
feeding
the
scab
or
window
container
configuration
in
CI,
so
what
this
would
enable
is,
when
scheduled,
containers
with
resource
limit
in
request
now
the
container
runtime
would
respect
those
requests
would
be
able
to
respect
those
requests
and
limit
and
take
those
in
for
information
from
the
CI
and
apply
to
the,
for
example.
The
total
long
time.
D
And
so
this
feature,
as
a
Patrick
has
said,
V
is
related
to
the
sick.
Note
also
buddies
for
windows
container,
so
we
plan
to
present
this
to
the
signal
meeting.
The
signal
meeting
I
recently
attended
no
meetings
and
they
have
agenda
layout
for
the
next
for
the
next
few
in
next
few
weeks,
we
could,
if
we
have
agreement
of
this
feature,
I
think
if
we
think
this
feature
is
necessary
and
will
benefit
the
windows
container
in
the
windows
in
the
signal
window
community.
We
could
get
this.
D
Presentational
meeting
and
get
the
work
kick
off
as
a
prototype.
Pond5
from
Shanghai
team
has
already
started
prototype
of
the
what
the
interface
need
to
be
added
in
a
CI
for
Windows
and-
and
there
are
also
other
features
like
if
your
contacts
we
are
working
on.
So
if
you
have
any
feature,
requests
or
any
scenario,
think
it
would
be
nice
to,
if
would
be
beneficial,
just
let
us
know,
and
we
can
add
to
the
state
and
pure
photo-
and
you
can
add
to
this
work.
D
So
that's
basically
they
to
work
out
and
relate
to
the
sick
signal
cooking
at
that
I'm
working
with
different
people
on
that,
and
it
is
race
to
Windows-
can
enter
yeah
so
for
here,
for
this
meeting
or
for
the
progress
of
this
meeting.
I
just
want
to
get
opinions
from
you
see,
what's
missing
what
would
be
what's
needed
to
be
added
yep.