►
From YouTube: Kubernetes SIG Windows 20170905
Description
Kubernetes SIG Windows 20170905
A
Hi
everybody
welcome
to
another
meeting
for
sick
windows.
Thank
you
guys
for
attending.
So
I
have
a
couple
of
topics
here
and
then
we
have
a
huge
presence
from
from
different
teams
here
on
our
meeting.
So
we'll
have
a
chance
to
to
deep
dive
into
different
topics
that
are
of
interest
to
people.
So
I'll
started
giving
a
high-level
overview
of
where
we
are
on
the
project
and
then
move
on
from
there.
So,
on
the
engineering
side,
there's
a
couple
of
three
different
trucks
that
are
making
significant
progress.
A
You
know
that
it's
good,
that
some
of
those
things
are
working
and
what
Bob
is
doing
is
he's
documenting
all
of
that
work
so
that
you
can
have
a
single
document
that
you
can
showcase
to
people
and
tell
them
hey
you're
on
beta.
This
is
what
you
need
to
do
to
get
these
things.
I've
been
running
with
Windows
on
the
cloud-based
front,
there
they're
basically
continuing
the
ovn
OVS,
and
they
are
talking
with
Microsoft
trying
to
get
looking
into
an
implementation
for
a
CNI
plug-in
built
on
top
of
the
rs3
work.
A
The
Microsoft
is
working
on
and
the
second
track
is
we
had
a
contributor
for
Microsoft
David
that
basically
did
a
lot
of
work
to
bring
some
of
the
statistics
and
resource
information
for
from
containers
on
Windows
and
get
that
up
and
running
so
that
you
can
use
different
capabilities
of
communities
like
auto
scaling
with
Windows
Server
containers.
The
pr
is
open,
there's
conversations
with
sig
note:
they
had
some
feedback
and
apologize
I,
don't
know
exactly
if
we
implemented
a
feedback
yet
or
not.
A
A
Now,
in
the
past,
all
that
talked
about
our
goal
to
go
to
beta
at
the
end
of
with
this
release,
one
date
that
would
no
longer
be
the
case.
It
seems
that
schedules
in
alignment
and
everything
else
is
just
not
really
gonna
work
out.
I
think
the
primary
part
of
that
is
networking.
We
will
not
have
the
networking
backbone
ready
at
that
time.
The
second
part
is,
you
know,
being
short
of
resources
for
a
while,
so
you
know
work
like
the
like
the
Sierra
I
worked
David.
It
just
didn't
get
him
in
time.
A
A
B
There
will
also
have
suppoed,
who
is
primarily
from
the
storage
team
and
is
looking
at
our
on-prem
solutions
for
Windows
with
kubernetes
and
then
lastly,
as
Jiang
team,
who
I
believe
is
also
on
the
call
from
Asher,
so
those
are
kind
of
the
primary
representatives
from
the
Microsoft
side
on
Windows
they're
going
to
be
looking
to
help
the
community
as
much
as
we
can
with
networks.
If
you
do
Dan
storage
all
up,
that's
the
other
update
I
think
you
had
them
pretty
much.
B
We
do
have
support
for
a
lot
of
these
new
features
in
Windows,
Server
insider
builds,
we've
had
one
or
two
bugs
reported
from
Alessandro
and
team
from
cloud-based,
so
that's
been
useful
and
we
getting
those
fixes
in,
but
a
lot
of
the
platform.
Support
for
networking
will
be
available
in
the
Windows
Server
version,
1709
release,
which
should
be
announced
later
this
month,
early
October.
B
So
that
will
have
all
the
compartments
are
shared
Windows,
Server
containers
within
one
pod,
not
with
hyper-v
isolate,
and
this
is
the
shared
kernel
variants
and
then
also
support
for
load
balancing
and
for
a
single
end
point
for
containers
or
pods,
rather
than
the
two
that
we've
had
previously.
So
those
are
the
main
platform
improvements
you'll
see
in
the
insider
builds.
Now,
if
you
ask
those
access
to
those
or
and
the
Windows
servers
at
1709,
they'll
be
publicly
released
soon,
hey.
B
The
DNS
stuff
was
largely
affixing
the
darker
code,
actually
just
so
that
we
can
have
custom
DNS
suffixes
appended
to
those
services
and
so,
rather
than
doing
kind
of
appending
a
bunch
of
suffixes
through
cute
proxy.
Those
are
now
automatically
appended
in
the
pod
spec
template
file
or
the
service
template
file
directly.
So
we
don't
have
those
DNS
workarounds
anymore,.
A
Excellent
and
thank
you,
everybody,
a
patronage
thing
and
so
much
for
for
joining
our
team
were
really
excited
to
have
you
guys
on
the
extended
segundos
family.
D
D
Other
idea
is
the
way
we
are
trying
to
make
this
unit
begin.
We
would
like
to
have
a
pod
support
for
the
new
17
online.
Well,
that
Jason
was
mentioning,
and
also
the
previous
bill
for
Windows
Server,
so
we're
trying
to
support
both
scenarios,
so
people
that
don't
want
to
update
for
some,
whatever
reason
can
still
have
kubernetes
with
the
ovm
solution,
open
running
yeah.
D
That's
the
whole
idea,
so
we
don't
want
to
use
those
users.
I
mean
for
us
is
not
such
a
huge
issue,
or
the
only
thing
I
would
like
is
if
we
could
get
the
capability
of
creating
compartment
without
using
a
chess
as
shim,
maybe
so,
basically
just
create
the
compartment
and
finding
the
the
containers
on
top
instead
of
denying
the
on
the
cma
plugins.
So
you
get
the
poll
every
time.
B
A
Excellent
I
know
that
Patrick
wanted
to
talk
a
little
about
the
pardon.
The
couplet
capabilities
is
that,
unless
someone
else
has
something
else
that
they
were
I
want
to
talk
about
in
the
agenda,
then
we
can
shift
our
focus
a
little
bit
on
on
that
Patrick.
You
wanna
tell
us
a
little
bit
about
specifically
what
you
wanted
to
talk
about.
A
F
There's
no
particular
way
to
choose
what
platform
you're
going
to
run
for
an
image,
and
so
that's
an
area
I'm
looking
for
feedback
on,
as
well
as
when
the
resource
metrics
that
are
there
as
well.
I've
talked
to
a
couple
other
groups
using
kubernetes
and
I've
heard.
A
lot
of
people
are
using
see,
advisor
and
or
Prometheus
over
on
the
Linux
side.
But
it's
sounds
like
there's
a
push
to
get
more
of
those
actually
put
in
went
through
CRI,
rather
than
as
a
separate
type
line.
F
So,
basically,
those
are
the
areas
that
I'm
working
on
trying
to
design
with
the
goal
of
getting
some
of
the
needed
platform.
Support
done
for
for
spring
at
fall
releases
it
next
year.
So
no
any
feedback
you
have
on
prioritization
and
people
that
could
help
it's
more
in-depth
discussions
on.
It
would
be
greatly
helpful,
yeah.
A
I
think
that
yeah
that's
great
Patrick,
that
you
have
that
you
know
the
runway
right
now
that
you
can
start
looking
into
this
and
thank
you
for
bringing
it
up.
I
think
it'd
be
worthwhile
whenever
you're
ready
to
have
that
discussion
to
have
Bob
my
bob
static
and
myself
as
well
as
I,
don't
know
if
David
Porter
is
still
around
the
Microsoft
his
internship
finish,
but
he
should
definitely
be
be
there
and
engine
young
as
well.
A
So
we
can
sit
down
and
talk
about
some
of
the
shortcomings
that
exists
today
in
that
area
and
in
addition
to
that,
look
at
some
of
the
investment
that
you
guys
are
looking
into
as
well.
I
think
that
we'll
start
with
Bob
seems
that
I
know
he's
found
a
couple
of
issues
where
the
couplet
is
missing:
capabilities
on
Windows,
specifically
around
secrets
and
being
able
to
do
a
couple
of
things
that
that
are
easily
done
on
Linux.
So
so,
let's
start
there.
A
F
And
what
there
is
some
especially
be
looking
for
feedback
is
like
I
know
in
the
case
of
Linux
today,
there's
a
lot
of
things
like
the
was
a
host
IPEC
host
Network
host
bid,
but
basically
all
the
different
resource
sharing.
That's
there,
those
tend
to
be
pretty
difficult
on
Windows
and
they
need
a
long
runway.
So
if
there
are
any
that
are
you're
blocking
major
functionality
today,
those
are
things
that
want
to
get
pushed
to
the
top
of
the
priority.
So
we
start
work
sooner
thanks.
A
F
G
You
know
unfortunate
that
some
of
the
discussions
didn't
happen
in
time
to
get
some
of
the
PRS
in
41.8,
but
hopefully
I'm
gonna
start
attending
some
of
the
Signet
meetings
to
try
to
help
make
sure
that
collaboration
continues
to
happen,
and
one
thing
that
some
of
those
people
mentioned
was.
It
would
be
a
little
more
helpful
if
we
would
be
easier
for
them
to
review
Windows
PRS
if
they
were
a
little
more
specific.
If
we
could
try
to
file
more
specific
bug,
reports
make
our
peers
a
little
bit
smaller.
A
Yeah,
absolutely
that
that's
great
feedback,
so
I
started
attending
the
secret
meeting
since
mid-august
as
well.
Unfortunately,
I
won't
be
able
to
attend
today
and
but
you
know,
I
have
been
attending
them
and
you
know
one
of
the
things
that
that
you
had
talked
about
in
there
was.
You
know
the
need
from
someone
from
Windows
to
to
be
there.
So
confessedly
did
that
discussion
and
they
bring
up
new
features
and
discussions.
A
They
want
us
to
talk
about
the
impact
windows
to
that
team,
so
obviously
that
you
know
I
agree
with
the
fact
that
you
know
kind
of
kept
them
in
the
dark
in
the
past
and
that
may
not
have
been
the
right
thing.
We
also
didn't
have
that
many
resources
to
be
able
to
spend
this
work
and
attend
all
the
sick
meetings,
but
we
understand
now
that
you
know
with
some
changes.
A
A
A
B
One
quick
thing:
Michael
Peter.
Well
one
thing
we
were
talking
about
with
Michael
and
others
is
just
for
our
C
and
I
plug
in
I
know,
there's
one
being
developed
by
cloud
base,
but
also
Microsoft
is
gonna.
Have
a
scene
I
plug
in
for
our
one
front
of
our
networking
modes
that
support
it
through
host
networking
service.
B
G
F
So
I
got
a
quick
question
on
how
they
are
sort
of
working
which
discussions
we
should
be
having
this
saying
versus
what
should
go
when
we
should
take
a
discussion
to
something
like
node.
So
as
the
goal
is
sort
of
like
incubate
the
ideas
here
and
then
once
we're
closer
to
like
a
PR
or
proposal
and
take
it
over
the
notes
agor.
How
should
that
be
working?
I
think.
A
It's
on
a
case
by
case
basis,
things
that
impact
directly
the
couplet
were
change
needs
to
be
made
to
the
agent
that
runs
on
the
node.
Then
signaled
owns
the
high
level
architecture
and
ownership
of
that,
like
they
own
the
couplet
right.
So
you
have
the
cupola
run
on
Windows
and
Linux
today,
largely
unchanged,
like
most
of
the
functional
is
the
same.
There's
a
few
cases
where
we
switch
and
we
do
specific
work
for
Windows,
but
for
the
most
part
it's
working
well
and
that's
what
Bob
is
validating
across
the
board.
A
So
when
we
did
the
original
work
and
we
got
alpha
support
for
Windows,
we
didn't
have
to
make
a
lot
of
changes
into
the
couplet
just
a
few,
so
they
only
they
owned
the
codebase,
we're
adding
more
features
into
Windows
or
were
bringing
parody
features
from
Linux.
If
we
have
to
change
the
couplet,
then
the
signal
needs
to
be
involved
that
way
they
can
understand
their
architecture,
approve
it
and
then
move
on.
A
D
A
We'll
get
back
the
rest
of
the
time.
Thank
you
all
for
attending.
It
seems
that
you
know
our
community
has
picked
up
a
lot
of
steam
the
last
month
or
so,
which
is
great
to
see
I'm
very
excited
you
know,
and
especially
excited
about
the
rs3
build
or
1709.
There
will
be
a
great
addition
to
from
Microsoft,
and
obviously
you
can
use
that
and
build
on
top
of
that
and
get
us
to
beta
soon
enough.
Thank
you
guys,
really
appreciate
it.
D
C
A
A
C
A
To
show
up
we'll
talk
and
we'll
figure
it
out,
there's
no
specific
agenda,
we're
just
sharing
progress,
talking
about
the
things
we're
working
on
and
then
figuring
how
we're
gonna
work
on
next
no
set
agenda
is
just
more
of
an
informational
meeting
that
way
everybody
gets
on
the
engineering
side.
Everybody's
is
well
aware
of
what
how
things
are
working
on
I.