►
From YouTube: Kubernetes SIG Windows 20170516
Description
Kubernetes SIG Windows 20170516
A
All
right,
hello,
everybody!
This
is
another
meeting
for
sick
windows,
this
microf
from
a
prenda.
I
have
a
couple
of
updates
that
I'm
going
to
give
you
guys
from
some
of
the
work
that
the
sigma
team
is
doing
on
the
development
front
and
then
we'll
move
around
to
to
test
map
is
from
additional
folks
and
and
also
come
up
with
some
of
the
next
steps
of
what's
happening
on
on
the
cig.
A
So
from
from
a
printer
perspective,
one
of
the
things
that
we're
doing
we
introduced
a
couple
new
team
members
to
seek
windows
as
as
engineers,
slash
developers
that
are
going
to
help
us
towards
the
road
for
beta.
Our
goal
here
is
to
have
a
better
support
for
cig
windows
sometime
this
summer,
very
likely
will
miss
the
1.7
train
folks
who
come
in
shortly
after
that.
A
The
goal
here
around
the
better
support
is
to
kind
of
finalize
and
productize
a
lot
of
the
work
that
parish
and
allene
were
doing
a
link
from
from
cloud
based
on
ovn
and
obvious
and
getting
that
to
be
fully
stable,
including
including,
but
not
limited
to
the
functionality
around
internal
networking
inside
the
containers.
The
ability
to
schedule
more
than
one
container
in
the
same
pod,
the
ability
for
pods
to
share
a
single
network
namespace,
as
well
as
dns
and
DNS,
search
to
work
inside
the
container.
A
A
lot
of
that
work
required
the
use
of
a
gateway
and
that's
what
Alan
his
team
introduced
to
the
to
the
mix.
So
we're
going
to
build
up
on
top
of
that
work
and
get
it
fully
productized.
The
the
second
thing
that
we're
going
to
do
as
part
of
that
community
effort
for
beta
is
to
get
secret,
storage
and
volume
all
working
very
well,
and
that's
pretty
much
the
line
that
you
can
I
cut
off
for
our
better
for
for
GA
and
general
availability.
A
There's
tremendous
amount
of
additional
work
needed
around
bringing
CRI
I
to
the
mix
getting
installers
available
for
for
sick
windows,
as
well
as
other
freedom
finish.
Where
does
anybody
have
any
questions
on
kind
of
our
road
map
and
some
of
the
things
that,
in
the
way
that,
when
I
approach
things
here,
this.
A
A
Right
now
and
Bob
can
give
us
an
update
on
some
of
the
efforts
that
they're
doing,
but
a
big
big
focus
of
the
team
that
that's
just
starting
up
right
now
is
education
and
getting
fully
up
to
speed
with
kubernetes
in
general.
Go
development
as
well
as
Windows
and
Windows
networking
and
the
ovn
P,
so
they're
they're
working
hard
to
get
up
to
speed
and
then,
in
addition
to
that,
they're
doing
some
automation
to
be
able
to
ease
the
deployments
of
basically
seek
Windows
work.
Bob.
D
A
All
right,
excellent
Bob,
so
so
this
brings
us
to
our
second
topic
here.
So
a
cloud-based
folks,
one
of
the
things
that
we
wanted
was
to
have
the
ability
to
to
get
in
a
room
with
you
guys
for
a
couple
of
hours
and
understand
the
state
of
things
from
the
ovn
and
obvious
standpoint.
In
terms
of
you
know,
what's
the
remaining
work?
Where
can
we
teaching?
How
can
we
better
integrate
with
some
of
the
features
and
functionality
that's
coming
through
and
I
know:
I'll
Indian
your
team
were
were
gone
last
week
easier.
A
You
probably
don't
need
to
schedule
this
right
now
and
talked
in
the
chat
room
that
you
guys
are
available
for
that.
So
why
don't
you
guys,
sync,
with
Bob
and
also
post
in
the
chat
room
when
you
guys
are
planning
the
talk
that
way
for
other
members
of
the
shake
are
interested
in
learning
more
about
the
internals
of
of
the
Nov
s
and
how
it
relates
to
kubernetes
they
can
come
in
and
listening
would
I
be
a
would
I
work.
Okay,.
A
C
A
A
All
right,
then
we
have
a
jason,
has
volunteered
to
start
taking
some
of
the
meeting
notes.
Jason.
Thank
you.
I'll
share
the
dog
with
you
and
Anton
as
well,
and
if
you
guys
can,
you
know,
can
help.
You
know,
contribute
some
of
this
and
take
some
notes.
That'd
be
awesome.
It's
usually
hard
for
me
to
type
at
the
same
time
as
I'm
talking,
and
they
always
think
so
so
I
wouldn't
I'm
I
was
not
able
to
take
a
lot
of
the
meeting.
A
E
E
We
want
to
do
a
much
better
job
at
shepherding
the
cloud
provider
forward,
for
example,
right
now,
there's
an
issue:
that's
coming
up
with
a
for
a
number
of
people
about
throttling
of
the
arm
api
because
of
bug
in
the
way
that
couplet
and
some
other
components
talk
to
arms.
So
it's
constantly
doing
a
check
and
it's
exceeding
the
API
call.
E
Limits
so
I'm
actually
acting
as
the
product
manager
for
this
work,
that's
going
to
be
happening
within
Microsoft
for
now,
so
we're
trying
very
hard
to
to
create
a
very
strong
thread
between
community
and
all
the
work
that's
happening
in
ACS
and
as
a
result,
I
also
want
to
be
heavily
involved
in
this.
Take
to
help
you
Michael
in
any
way
I
can
to
help
ease
your
burden
of
all
the
work
that
goes
into
turning
a
sig.
So
I
am
I
am
your
servant.
E
A
I
think
that
you
know
that
is
very
valuable
and
thank
you
for
for
coming
into
the
community
and
contributing
this
awesome.
Well,
one
of
the
biggest
things
that
that
we're
going
to
do
down
the
line
as
we
product
ice
there.
The
work
with
ovn
and
OBS
is
to
make
sure
that
it
runs
very
well
on
every
public
cloud
provider,
including
on-premise.
So
obviously
our
team
will
not
be
able
to
scale
to
that
extent.
A
So
we're
going
to
look
forward
to
members
of
the
community,
like
you
Jason,
to
help
us
test
in
various
plots
and
so
someone
who
have
to
pick
up
Google
and
we
have
people
from
Google
here,
like
Peter
and
his
team.
Someone
will
have
to
do
a
sure
we
did.
You
know
with
the
day
WS
as
well
as
on-premise,
and
make
sure
that
any
anybody
that
wants
to
try
there
were
kubernetes
and
sig
windows
on
any
of
those
cloud
providers
or
on-premise
to
have
the
same
experience.
Fantastic.
E
A
E
If
you
want
to
put
any,
if
you
want
to
comment
as
a
plus-one
on
the
the
proposal
that
was
sent
to
Governor
DS
death,
that
would
be
super
helpful,
because
a
lot
of
people
have
been
concerned
in
the
past
that
we
did.
We
didn't
want
to
have
cig
sprawl
and
stomp
on
top
of
the
amazing
things
you're
doing
here
with
it.
Yet
another
cig.
That's
you
know
more
windows
focus
so
obviously
we're
not
really
windows
focus
for
the
acs,
okay,
yeah.
A
C
Right
actually,
I
had
a
I
had
a
question
Mike.
Can
you
share
anything
or
maybe
it's
a
completely
different
effort?
So
maybe
there
isn't
much
sure
I
think
there
was
a
reason
enough
announcement
by
OpenShift
on
that
net
support
and
I
was
wondering
if
that
was
pretty
backing
in
any
of
the
said,
Windows
worker,
that's
just
a
separate
effort,
and
can
we
join
forces
on
that
or
what's
happening
on
that
so.
A
I,
don't
know
the
the
internals
of
the
what
OpenShift
used
for
the.net
announcement
that
they
made
and
having
really
dissected
that
so
I
don't
know
the
answer
to
that.
I
don't
know
if
there's
anybody
in
the
community.
That's
on
the
course
here
that
has
a
better
answer
in
terms
of
what
they
used.
I
know.
C
A
A
E
A
B
B
F
This
is
fountain
found,
Google
and
also
from
signal-c
and
kubernetes
signal.
Does
the
other
humans
in
our
roadmap
and
the
humans
and
90
mg.
A
you.
The
plan
to
integrated
component
is
a
move
to
the
CRI,
so
I
assume
that
now
the
industry,
secession,
but
now
you
are
integrating
with
kubernetes
through
folks.
The
proven
ideas
is
that
you
know.
A
And
so
so,
some
of
the
development
is
happening
and
it's
in
private
branches.
But
you
know
our
what
our
work
is
already
back:
ported
back
into
and
reverse
integrated
back
into
kubernetes,
so
we
submitted
PRS
for
for
the
couplet
and
the
coop
rocks
in
previous
in
previous
milestones
and
they
were
approved
and
immersed
into
their
fou
covenants
product.
So
we're
not
working
on
any
private
branches
or
Forks.
F
A
A
All
you're
doing
is
that
were
allowing
it
to
get
a
Windows
node
added
to
your
kubernetes
existing
cluster
and
now
Windows
Server
containers
can
be
scheduled
on
Windows
server
nodes
through
kubernetes
so
essential
in
order
to
make
that
possible
who
had
to
make
changes
to
the
couplet
as
well
as
a
queue
proxy
to
facilitate
the
their
ability
to
first
run
on
Windows
and
second
to
to
be
able
to
participate
in
and
be
able
to
talk
to
the
API
server
in
kubernetes,
scheduled
containers,
work,
node,
node,
port
and
load
balancer
and
stuff
like
that.
So.
F
A
So
so,
on
our
alpha
that
we
released,
we
basically
use
a
different
networking
architecture
than
they
wander
them
under
development
right
now.
At
that
point,
we
use
node
port.
Sorry,
we
use
the
port
proxy
and
nemesis
age
from
Microsoft
as
a
technologist
to
isolate
the
routing
of
packets
to
individual
parts
were
no
longer
following
that
approach.
A
We're
going
we're
working
with
a
cloud-based
and
a
linen
TSP
they're
on
the
call
right
now
to
create
a
novia,
novia
solution
that
allows
us
for
all
the
N
and
obvious
to
be
the
network
backbone
for
kubernetes
without
architecture
in
mind.
The
the
coop
coop
rocks
is
no
longer
going
to
be
necessary
and
then
the
only
changes
we'll
have
to
make
from
sick
windows
will
be
to
the
couplet
and
it
will
be
the
couplet
of
specifically
runs
on
Windows,
not
not
the
one
that
runs
on
Linux.
Yes,.
F
That
now
so
many
review
with
to
the
invited
you
get
over
to
the
signals
give
or
Daniel
I
know.
Last
time
we
have
just
met
Phyllis,
you
a
high
level
architecture
with
Vitamix
to
like
the
more
than
happy
bro.
So
so
this
matter
we
have
some
achievement
and
also
ways
to
talk
about
this
such
and
how
to
move
to
make
meant
the
Titanic
needs.
So
so
so
I
was
invited.
You
guys
to
give
us
a
demo
some
time
so
next
month,
yeah.
A
So,
as
our
guys
right
now
are
still
ramping
up
so
I
mean
could
demo
I
mean
the
only
demo
could
do
today
is
the
same
technology
that
Google
next,
which
is
a
recorder
presentation,
that's
available
on
YouTube,
so
we
could
do
that
there.
Now,
essentially,
you
know,
since
the
guys
are
still
ramping
up.
It
will
probably
take
us
a
month
before
we
start
making
changes
to
the
code
to
to
move
forward
on
some
of
the
goals
I
mentioned
earlier,
like
DNS
DNS
search,
networking,
accessibility
inside
containers,
as
well
as
multiple
containers
in
a
pod.
B
B
A
B
A
Nice
cool,
you
can
ask
a
question
now
on
the
on
the
nothing.
Does
that
mean
now
that
you'll
be
able
to
use
transparent,
networking,
transparent,
dr.
networks
on
cig
windows
for
for
sorry,
for
Windows
Server
containers
and
then
not
have
to
have
the
Gateway
for
Internet
connectivity
to
the
knot
or
you.
B
B
A
B
E
B
E
B
E
B
E
A
Alright
I
guess
that's
it
and
letting
nobody
else
has
any
more
questions
or
concerns
or
something
I
wanna
update
us,
that's
it
for
today.
I
will
see
you
guys
in
two
weeks
look
forward
to
having
our
discussion
on
all
the
internal,
yes
and
definitely
testing
the
me
supporting
student
and
not
support
for
Windows.
Thank
you,
everybody
and
have
a
great
rest
of
the
day.