►
From YouTube: Kubernetes SIG Windows 20180410
Description
Kubernetes SIG Windows 20180410
A
We
don't
have
a
lot
of
items
on
the
agenda
today,
so
one
of
it
is
the
group
managed
service
accounts,
Abdi
Patrick's
gonna,
talk
about
that
he's
gonna
be
meeting
with
sig
note
very
soon.
On
that,
then
getting
an
update
on
the
test
updates
and
then
Bob
and
Alan
can
give
us
an
update
on
on
on
the
work
that
they're
doing
around
stabilizing
and
getting
good
steps
for
installing
ovn
and
ovm
kubernetes.
All
right.
Let's
get
started
particular
give
an
update
on
the
group,
managed
service
accounts,
work,
yeah.
B
So
I
just
posted
a
link
to
it
over
there
in
the
zoom
chat
window.
So
this
is
the
same
proposal
that
we
had
talked
about
a
couple
weeks
ago
and
at
the
time
I
had
it
over
on
a
site
called
hack.
Md4
for
comments
and
I
had
a
couple.
People
look
at
it
over
on
the
Microsoft
side
and
then
Peter
had
looked
at
it
as
well.
So
but
I
didn't
see
any
other
questions
from
this
group.
Did
you
have
any
any
outstanding
questions
that
you
wanted
to
go
over
Peter
unless.
B
All
right
sounds
good
yeah,
so
so
I'll
be
taking
it
there,
and
then
someone
also
brought
up
that
there's
a
working
group
for
container
identity,
so
I'll
need
to
present
it
there
as
well
I'm,
not
super
clear
on
if
sig
node
is
going
to
delegate
to
that
working
group
for
approval
or
or
what
that
process
works,
like
so
I
think,
I
think
the
main
thing
today
is
I'm
just
going
to
sig
note,
seeing
whether
or
not
I'm,
assuming
that
we're
going
to
need
their
approval
because
I'm
proposing
changing
the
CRI.
So
it's
more
around
finding.
B
One
of
my
bigger
concerns
about
about
this
one
is
I.
We
need
to
be
very
careful
because
the
way
this
particular
one
is
implemented
in
the
OCI
spec
is
a
window
specific
field,
so
I
may
need
some
support
from
others,
because
if
this,
if
they
try
to
roll
this
into
part
of
a
larger
design
that
covers,
you,
know
non
active
directory
type
type,
work
I,
don't
think
that
would
use
the
same
field
anyway,
and
so
I
may
need
to
make
sure
that
this
is
sort
of
you
know
separate
from
from
another
discussion.
B
A
A
Cool
excellent
yeah
all
right!
Thank
you
all
right
before
you
go
into
the
testing
updates
with
Adelina
between
Bob
and
Eileen,
so
so
Eileen
made
the
pr4
couplet,
Nov
and
kubernetes
Bob
is
hoping
to
test
out
and
validate
that
work.
No
real
update.
The
testing
is
now
complete,
but
as
far
as
I
know,
things
are
going
very
well
on
that.
So
I
think
Eileen
is
on
vacation.
So
we'll
here
get
an
update
next
week
on
on
all
of
that
work,
I.
C
C
Basically,
the
was
a
problem
when
trying
to
use
the
features
in
Aris,
one
from
the
H&S
Network
they've
got
split
to
dinars
free
into
two
different
providers
and
I
think
you
notice,
for
it
got
a
new
name
I'm
trying
to
fix
that.
So
I
can
include
from
Marty
M
across
with
the
outer
sphere
in
orders
for
the
husband's.
A
D
D
D
116
for
passing
test
herself
failed.
We
drove
way.
43
and
84
are
skipped
because
they're
only
GC
or
GK
applicable.
So
that's
out
of
300
350
tests.
We
looked
at
out
of
700
now
on
the
conformance
tests.
We
still
have
nine
failing
tests
and
we
can
skip
35
of
them
cloud.
You
will
give
you
the
details
on
why
so,
basically,
with
the
conformance
we're
pretty
close
to
damn
them
all
done
now
on
the
full
runs
there.
That
I
have
the
avoid
test.
There's
a
category
for
those
they
usually
break
the
deployment.
D
So
I,
don't
know
exactly
what
happens
with
each
and
every
test
we'll
spend
time.
Looking
into
that,
once
we
we
sorted
all
the
tests,
basically
nodes
become
unavailable,
so
there
are
obviously
potential
bugs
there,
which
is
good
news
because
we're
starting
catch
issues
talking
about
bugs
cloud.
You
has
interesting
one.
We
filed
that
sort
of
related
what
we
said
a
couple
of
weeks
ago
about
the
cubelet
hanging
at
99%
CPU.
D
So
that's
on
the
test
and
I
made
a
poor
request
for
the
cube
test
part.
So
basically,
we
can
spin
angel
clusters,
there's
still
some
work
to
be
done.
I'm
proud
that
I'm
planning
to
finish
this
week
and
have
a
precursor
for
that,
so
that
that's
from
me
on
the
cloud
you
talked
to
you
about
the
the
mountains
part
and
the
the
issue
we
found
Kali.
E
Yeah,
hello,
so
two
things,
first
of
all,
the
skips
tests.
Basically,
there
are
two
reasons
that
this
will
be
skipped.
One
of
them
is
whenever
a
test
is
setting
a
what
security
context
when
every
tries
to
set
some
Esalen
absorptions
or
when
it
tries
to
set
the
honest
use
or
honest
group
basically
it'll,
create
it
remains
some
volumes
and
then
try
to
read
the
files
and
so
on
with
different
file.
Permissions.
E
For
example,
lot
of
damage
are
setting
up,
are
setting
for
0:04
permissions
and
then
try
to
run
notice
with
the
different
users
different
group,
most
of
the
time
which
shouldn't
work
but
windows.
It
doesn't
really
set
the
permissions
like
that,
so
we
decided
to
skip
them,
and
the
second
reason
so
that
this
being
skipped
is
because.
E
E
B
Hey
are
you
said
Nick
on
the
call.
B
Okay,
he
said:
guess
he's
not
Mike
no
yeah.
Well,
there's
a
I
thought
that
was
Nick
mo
Moloch
Milwaukee
over
here
Microsoft
yeah
I
could
I
could
talk
to
a
few
people
here
on
the
Microsoft
side
and
see
if
I
can
get
somebody
to
look
at
it
because
I
know
that
we've
also
put
in
a
few
other
changes
related
to
symlinks.
But
I
wouldn't
expect
this
to
be
happening
on
the
cubelets
side,
but
I'll
I'll
see
if
I
can
get
someone
to
to
look
at
that
over
here
at
Microsoft.
So.
A
B
F
We've
been
working
on
here,
so
we've
been
troubleshooting
and
triaging.
These
dns
issues
we
think
most
dns
issues
should
be
resolved
at
this
point,
there's
one
outstanding
bug
fix
that
will
be
available
in
the
April
secure
area,
April
monthly
roll-up
package,
so
that
usually
goes
out
the
second
week
of
April.
So
it
should
be
like
this
today,
potentially
hopefully
today.
This
was
a
service
discovery
related
issue.
F
We
also
are
debugging
a
one
other
issue
related
to
the
NSA
discovery,
which
should
be
available
in
the
rs4
package.
This
is
externally
known
as
Windows
Server
version
1803.
This
one
we're
basically
looking
for
a
sure
to
get
some
self
host
coverage
before
we
roll
it
out
publicly,
but
we
do
have
a
fix
available.
It's
just
not
ready
to
be
ruled
out.
F
So
sorry
I
misspoke,
the
first
one
is.
Actually
we
had
a
problem
with
removal
of
single
endpoint
with
any
policies.
I
would
break
load-balancing
the
second
one
I'm
talking
about
now.
That's
gonna
go
into
Windows
Server
1803
is
a
service
discovery
issue
which
was
broken
with
the
Windows
Server
1803
package,
but
hopefully,
before
that's
released
publicly
will
already
have
the
fix
available.
F
We
did
have
some
other
issues
in
wincy
and
I.
This
is
our
windows,
see
and
I
plugin,
that's
posted
on
our
github
repo
github.com
Microsoft,
Sdn
kubernetes.
This
was
related
to
it,
wasn't
setting
the
default,
DNS,
suffix
and
so
is
breaking
service
discovery
that
plug-in
has
now
been
fixed
and
that
updated
binary
is
available.
F
We're
planning
to
move
away
from
that
plug-in
long-term,
unfortunately,
just
haven't
had
the
resourcing
to
get
there.
We
do
have
several
pull
requests
that
you
probably
seen
on
the
container
networking
repo
for
win
L
to
bridge
and
win
overlay.
These
would
be
the
new
C
and
I
plugin
for
wanting
to
move
towards
a
specifically
for
flannel
integration,
but
those
just
aren't
quite
ready.
Yet
so
when
C
and
I
dot
exe
is
the
one
that
we're
kind
of
officially
supporting
right
now
and
making
fixes
to.
C
Just
one
question:
for
me:
Jason:
did
you
post
somewhere
this?
You
know
code
somewhere
publicly
on
github.
F
Yeah
I
will
do
that
today.
I've
been
meaning
to
do
that
and
just
continue
to
slip
off
my
radar.
My
hope
was
that
we
would
have
moved
off
when
CNI
by
now,
but
we
just
haven't-
and
so
in
the
interim
period
until
we're
ready
to
switch
to
the
new
win
l
to
bridge
or
win
overlay.
Plugins
I'll
put
the
code
up
for
our
win
C
and
I
plug
it
in
our
Sdn
github
repo
that
we
own,
because.