►
From YouTube: Kubernetes SIG Windows 20180605
Description
Kubernetes SIG Windows 20180605
A
Okay,
hi
I'm,
Patrick,
Liang
Michael's,
currently
traveling
right
this
week,
so
I'll
be
hosting
the
big
windows
Meetup
so
anyway,
if
anybody
has
anything
else,
they
want
to
add
to
the
agenda.
The
yeah
I'd
like
to
ask
that
you
I'm,
going
to
update
the
Google
Doc
and
I'll
refer
back
to
that
top
of
the
list
is
making
sure
that
we're
getting
everything
needed
for
closing
up
on
the
version.
A
Remember
if
those
Alex
did
this
one
I
may
be
paying
phytate.
We've
got
a
dashboard
fix
for
the
so
that
way,
the
dashboard
canal,
Raunak
command
or
powershell,
and
then
I
know
that
Alan
was
working
on
getting
the
some
stuff
around
over
yes
working
correctly
I
Windows,
Server
2016
and
it
looks
like
it's
been
merged
into
kubernetes,
but
there's
still
an
outstanding
one
over
on
the
switch
side
is
that
is
everything
else.
That's
needed
on
the
curb
side,
I'm
Alan.
B
B
B
A
We've
got
a
PR
that
adds
run
as
user
support
in
there.
This
is
already
supported
and
docker,
but
it
wasn't
enabled
in
the
cubelet
yeah,
so
we've
updated
the
security
context
to
allow
our
windows
username
there
and
I
was
waiting
on
final
merge,
for
that
was
anybody
tracking
any
other
things.
I
need
to
be
emerged
for
1.11
at
all.
C
A
B
B
C
A
Well,
that's
different
issue
I
just
seen
something
over
on
signal,
but
that
was
reducing.
The
API
calls
for
the
node
status,
not
for
CNI,
so
I
was
take
there.
Okay,
well
I'll
keep
pinging
folks
on
sig
note
on
this.
Not
getting
that
last
one
merge
for
the
security
contexts
and
then
we
should
be
good
to
go
for
that
release
and
then
I'm
going
to
go
ahead
and
submit
the
release,
notes
that
I
had
I,
don't
know
where
I
just
lost
the
gist
I
had
it
open
a
second
ago
there.
A
B
I
think
I
have
another
if
to
report
on
the
inner
side,
when
you
set
the
DNS
servers
for
an
end
point,
they
do
not
get
passed
to
the
other
containers
that
are
sharing
the
same
namespace
or
network
compartment.
If
you
just
look
and
see,
do
I
click,
config
and
then
all
compartments,
you
can
see
the
DNS
server
based
in
Ystad
there.
If
you
go
on
the
infra
container,
you
have
the
DNS
server
set,
so
you
can
think
actually
any
domain.
B
If
you
go
on
the
other
container,
that
is
within
the
name
net
within
the
same
metal
compartment,
it
doesn't
work
and
from
what
I've
seen
I
looked
in
the
HSN
app
again
and
they
create
the
network
which
the
DNS
set
from
couplet,
but
I
think
that
there
might
be
that
might
fix
the
issue.
But
what?
If
the
DNS
changes,
because
the
cni
would
is
not
looking
if
the
network
has
different
DNS
and
existing
one
CNI
just
creates
the
network
and
set
the
DNS.
B
A
A
B
I
mean
I
can
tell
you
even
anything.
You
just
created
normal
end
point
you
attach
it
to
the
container
and
then
just
look
at
it
and
you're
gonna
see
that
the
second
container,
that's
within
the
same
order,
does
not
get
the
DNS
servers.
Okay,
do
you
have
an
issue
open
on
this,
yet
no
I'm
still
trying
to
see
if
it
fixes
the
thing
if
I
said
the
DNS
to
the
h
NS
network,
but
that's
just
a
temporary
fix.
In
my
opinion,
okay.
A
Alright,
well
be
sure
to
get
an
issue
open
on
this
one,
and
that's
probably,
and
once
you
have
that
if
you
could,
if
you
could
paying
David
and
I
over
in
the
slack
channel,
we
can
get
get
somebody
to
double
check
that
as
well
for
consistency
to
figure
out.
If
that,
what's
going
on
in
the
because
that
you're
using
the
OBS
C&I
right.
B
Yeah
but
I
think
I
can
just
not
use
anything
and
then
just
do
playing
partial
command.
That's
like
create
a
container,
create
an
end
point
using
PowerShell
attach
the
end
point
to
the
container,
don't
spin
up
another
container
to
and
attach
it
to
the
same
network
compartment
as
the
first
container,
and
we
should
not
get
past
I
haven't
tested
out,
but
you
should
happen
the
same
so
know
when
you
see
an
eye,
only
plain
common,
that's
or
shall
we.
B
A
A
A
D
C
C
C
A
And
then
I'll
probably
go
ahead
and
add
a
CSN
gin
to
this,
just
because
that
is
the
s
easiest
way
to
set
something
up
on
Azure
right
now,
and
it
brings
in
all
the
right
Network
plugins
that
are
there.
I,
don't
know
that
I'll
necessarily
document
setting
it
up
manually,
just
because
the
steps
used
to
set
that
up
through
a
CCS
engine
are
still
changing
on
a
on
a
pretty
regular
basis.
D
A
All
right
sounds
good
yeah
and
if
there's
specific
topics
that
you'd
like
to
see
added,
you
know
feel
free
to
to
open
an
issue
on
that,
and
then
one
of
us
can
get
on
that
too,
because,
ultimately,
if
we're
going
to
update
things
over
here
on
the
skinny
start
guide,
we'll
need
to
do
it
through
they're
getting
up
anyway.
Yes,.
D
I
feel
like
the
the
pardon
is
or
more
clarification
is
the
networking
plugins,
because
that
I
feel
like
that
is
the
part
that
is
a
little
bit
fuzzy
there
I'm,
not
exactly
which
ones
are
enable
or
supported
at
the
moment,
and
you
know,
with
the
new
releases
like
18
or
80,
I,
think
that
something's
got
fixed
but
I'm
not
sure
exactly
which
what's
working
or
what's
not.
If
we
can
clarify
that
that
we
pray.
C
Thank
you
yeah.
There
is
a
list
of
networking
issues
out
on
github,
as
well
known
issues
and
previous
versions
that
have
been
fixed
with
18
Oh
free
release.
I
can
post
that
in
shot
as
well.
That
being
said,
there
are
some
issues.
Still
there
are
kind
of
propping
up
now
that
18
no
free
has
been
released,
but
that
data
lists
will
soon
be
updated
there
as
well.