►
From YouTube: Kubernetes SIG Windows 20181106
Description
Kubernetes SIG Windows 20181106
A
Hello,
everybody
welcome
to
another
single
dose
Meetup.
Thank
you
all
for
attending.
We
have
a
few
items
on
the
agenda
today,
so
I
think
we'll
start
with
Patrick,
and
then
we
moved
to
to
Davie
to
give
us
an
update
on
on
flannel
and
I
also
have
some
updates
on
mine
as
well.
So
platter
go
ahead.
Please,
okay,.
B
A
B
Cool
all
right,
so
this
is
the
the
project
board
that
I've
been
using
to
basically
track
the
various
work
needed
as
part
of
the
13
effort,
and
so
the
good
news
is
that
one
of
these,
the
last
one
that
was
marked
as
a
feature
which
was
for
the
DNS
capabilities
actually
merged
last
night.
So
that's
the
last
one
that
we
have.
That
was
marked
as
feature
the
rest
of
these
are
all
test
related
changes.
B
We
just
need
to
continue
the
work
to
get
these
tests
online,
so
I
I
was
talking
to
Adelina
and
the
others
at
cloud
base
about
those.
So
nothing.
Next
up,
there
is
I'm
going
to
talk
to
to
Aaron
and
probably
been
over
at
Google,
because
they've
managed
the
main,
proud
cluster.
That
would
actually
be
running
the
code
in
this
PR
here
and
so
I
need
to
get
them.
The
azure
sub
that'll
get
that
set
up,
and
then
we
should
be
able
to
get
those
tests
online.
Well,
we
still
have
these
other
open
PRS.
B
There
will
be
some
tests
that
are
are
failing,
but
they
should
all
match
what
we
know
of
that.
I
added
them
in
that
in
the
in
the
windows
GA
docked
down
here,
where
I
basically
put
in
all
the
test
cases
that
we're
gonna
be
running
on
Windows
and
then
for
the
ones
that
we're
going
to
run
on
Linux,
only
I
sort
of
grouped
them
up.
B
So
that's
kind
of
the
next
thing
I'm
pushing
on
there,
where
I
could,
where
I
could
use
some
help
is,
and
actually
this
one
I
need
to
just
resolve,
because
that
was
just
waiting
on
that
other
PR,
where
I
could
use
some
help
is
going
back
over
here
to
the
dock,
sets
I
went
ahead
and
opened
placeholders
for
the
dock
work
that
needs
to
be
done.
I
think
we
have
until
how
long
we
find
it
here.
I.
B
B
A
A
B
I
know
what
it
is:
I
rebased
my
branch,
and
it
did
some
stuff
there,
but
the
the
one
I
was
actually
looking
for
was
one
of
these
has
yeah.
This
is
the
one.
So
what
I
did
was
I
basically
went
back
through
old
notes
and
when
looked
at
the
dock
set
for
what's
there
for
Linux,
and
this
is
basically
sort
of
the
working
outline
that
I'd
put
together
of
topics
that
I
think
we
need
to
have
and
user
focused
documentation,
I
don't
like
today.
B
The
main
stuff
we
have
is
all
than
that
getting
started
guide,
which
has
a
lot
more
details
around
things
like
building
kubernetes
and
stuff,
like
that
I,
don't
think
we
actually
necessarily
need
that
level
of
detail
on
the
kubernetes
website.
I
think,
what's
going
to
be
more
important,
is
that
we've
got
links
to
those
steps
you
know
where
appropriate,
because
it
may
I've
got
this
stuff
for
ACS
engine
I've
already
got
a
link
here
to
what
I
guess
I
didn't
get
the
right
link
on.
There
was.
B
A
B
B
These
other
two
here
around
the
hybrid
clusters.
You
know
I'm
gonna,
keep
pushing
that
issue
with
sig
architecture
because
they
have
not
made
a
decision
there.
Yet
they
agreed
that
we
should
keep
working
towards
defining
how
this
should
run
and
so
we're
basically
using
this
PR
to
say
you
know,
look,
here's
something!
That's
working!
Can
we
merge
this
as
the
point-in-time
solution,
while,
while
sig
architecture
works
on
the
longer
term
plan
for
conformance
profiles?
B
It's
not
really
ideal,
but
I
mean
for
the
test.
Grid
needs
to
show
the
upstream
results,
and
if
we
want
to
have
a
separate
one
for
our
group,
we
can
list
that
there
this
one
was
actually
resolved
and
that
one
okay
don't
get
updated
with
David,
but
I'm
not
aware
of
any
other
major
risks
there.
Other
you
know
at
this
point.
It's
just
finishing
up.
The
I
need
to
get
this
sent
back
out
to
sig
architecture,
sig,
node
and
network.
Just
to
say,
hey
we're
plan
on
going
forward
was
stable.
B
The
test
cases
are
there
and
getting
the
docs
done.
That's
that's
my
understanding
at
this
point.
Okay,
oh
I,
guess
the
one
thing
I
should
mention
is
the
Windows
Server
2019
will
probably
be
cut
from
version
13
just
because
we
don't
have
a
testable
build
yet
and
given
that
we're
both
under
code
freeze
or
not
I,
don't
really
know
if
they
came
out
today,
I
suppose
we
might
be
able
to
get
it,
but
yeah.
A
B
A
C
Sure,
yes,
so
happy
to
think
about
this.
Basically,
in
a
nutshell,
today
or
just
to
recap,
we
only
support
flannel
in
host
gateway
mode
which
uses
bridging
or
L
to
do
to
bridge
network
on
Windows.
This
is
mainly
due
to
scalability
limitations
and
code
changes
required
and
cout
proxy,
it's
utilized
of
the
exelon
mode
and
overlay
networking
mode.
First,
thus
far,
we've
been
referring
people
and
you
know,
using
the
guide-
that's
floating
around,
to
use
these
pre-built
binaries
that
are
built
on
top
of
APR.
C
Like
me,
posted
here
in
chat,
so
the
situation
isn't
very
ideal
now
to
give
an
update
on
what
happened.
Since
then,
we
did
some
work
and
should
be
a
few
days
away
from
merging,
more
updated
PR.
It
also
includes
initial
preliminary
Windows
support
for
both
the
X
LAN
and
l2
bridge
mode
on
the
final
bits.
Now
the
other
large
piece
of
work
that
we
did
is
originally
we
had
another
networking
plug-in
called
twin
C&I
and
we
split
that
up
into
its
respective
networking
mode
so
for
l2
bridge
and
for.
C
So
we
have
also
a
dark
spear
to
point
people
to
these
new
bits,
like
the
wind
bridge
plug-in
into
wind
overlay
plugin.
That's
that's
also
about
to
be
merged.
I'm,
just
waiting
on
the
final
one,
0
42.
U
final,
PR
to
be
merged
as
well!
So
then
I
can
point
people
to
the
newest
and
greatest
bits,
and
the
latest
talks
we're
hoping
to
close
on
that
by
the
end
of
the
week.
C
There's
a
few
typos
and
the
PR-
and
we
will
still
want
to
give
credit
to
thanks
code,
could
see
that
a
lot
of
refactoring
work
and
merged
our
other
two
PRS
together.
So
we're
in
a
bit
of
a
funny
situation.
In
that
we
know
we
have
the
fixes
ready
ourselves
on
our
private
branches,
but
we
want
to
give
credit
as
well
to
Frank's
code,
so
we're
working
with
them
to
address
those
minor
typos,
so
hopefully
it'll
be
in
merchants.
C
This
week,
then
4vx
LAN
mode,
so
I
said,
there's
some
platform
limitations
and
there's
some
coop
proxy
changes.
You
know
to
light
that
up,
so
we
are
developing
and
validating
that
right
now
from
platform,
so
HMS
and
open
source,
flannel
and
coop
proxy
perspective
as
well.
The
coop
proxy
changes.
We
have
private
binaries
right
now
that
were
utilizing
for
testing
and
the
H
and
s
changes
are
there
in
the
next
windows
release.
C
A
C
So
the
scaleability
chain-
well,
there's
two
two
changes.
I
would
say:
one
is
that
if
you're
using
the
the
old
PR
for
our
older,
not
working
plugins
is
that
we
are
leaking
endpoints.
So
that's
that's
an
issue
in
itself.
That's
addressed
with
the
newest
networking
plugins,
then
the
second
issue,
the
scalability
limitation-
that
mainly
applies
to
overlay
or
VX
LAN
mode
and
a
knowledge,
isn't
stolen
or
development.
So
it's
not
being
used
by
people.
The
limitation
there
is
that
programming
all
possible
endpoints
for
remote
subnets.
C
So
it's
a
significant
scalability
and
we're
trying
to
address
that
so
that
you
only
have
unit
remote
and
not
all
possible.
End
points
for
subnets
that
actually
well
I
should
say
the
overlay
networking
mode
is
available
in
darker
swarm,
but
not
in
coronaries,
because
new
proxy
changes
and
the
final
changes,
skill
ability
limitation
applies
there
as
well.
Once
you
address
both
issues
that
is
scalable
and
more
performant
of
vinyl
and.
A
A
C
Yeah
we
are
working
on
this
okay,
it
will
be
there
19:03.
Now
we
are
trying
to
get
it
in
for
Windows,
Server,
2019,
okay,
so
I'll
backboard
it
later
on.
Okay,
that
dad
is
still
not
completely
signed
off,
because
we
still
need
to
work
for
direct
taper
on
that,
but
we
are
trying
to
do
that
as
well.
Well,
1903!
That
is
committed.
Yes,.
A
C
B
A
B
A
B
A
D
A
D
D
And
they
also
add
a
lot
of
annotations
today.
What
is
missing,
although
and
I
would
like
that
you
have
it
by
the
end
of
the
year,
is
oh
no
Vienna
or
no
veers.
We
are
trying
to
move
into
a
model
in
which
you
justify
yama.
Basically,
everything
goes
away,
so
there
is
sound
Aaron
oxide.
There
are
images
already
created
and
so
on.
We're
still
missing
on
Windows.
B
B
A
B
B
C
E
B
D
B
Well,
the
first
thing
is
you're
gonna
need
the
Windows
Server
2000
19
release,
and
then
there
are
some.
You
have
to
look
at
the
right
branch
right
now,
there's
still
some
PRS
that
need
to
merge.
I'll,
put
a
note
for
next
week
and
I'll.
Try
to
get
those
get
a
list
of
those
resources
together
to
share
out
a.