►
From YouTube: Kubernetes SIG Windows 20180522
Description
Kubernetes SIG Windows 20180522
A
Alright,
hello,
everybody
welcome
to
another
sick
windows.
Meetup!
Thank
you
all
for
for
attending.
It
looks
like
we
don't
have
a
lot
of
folks
attending
today.
So
maybe
it's
going
to
be
a
quick
update.
So
on
our
end,
I
know
that
Bob,
Alex
and
and
team
are
basically
are
doing
a
couple
different
things.
They
are
finalizing
some
of
the
vagrant
setups
that
we
have
on
setting
up
the
Windows
environment
with
with
kubernetes
and
there
they
made
good
progress.
I
think
that
it
always
that's
working
very
well.
A
They
had
some
IP
issues
and
networking
issues
lately
that
they're
trying
to
track
down
and
then
also
both
Bob
and
Alex,
have
been
reviewing
some
of
the
PRS
that
came
out
of
ping
Fei
and
vice
care.
So
we're,
like
you
know,
a
lot
of
good
work
came
they're
around
around
the
CRI
work
and
log
and
FS
stats
for
will
contain.
B
Sure
yeah,
so
yesterday,
I
spent
some
time
you
obtain
the
Trello
board,
and
so
several
the
items
are
marked
as
done
now,
all
the
and
so
the
Windows
Server
1803
release
it's
available
on
Azure
now
and
so
that
actually
fixed
the
symlink
issues
that
we
needed
for
for
secret
and
config
map
support
and
then
Andy
Zhang
at
Microsoft
has
a
PR
open.
Actually,
no
I
think
it's
already
merged
to
fix
local
volume.
B
Support
so
should
have
some
good
storage
improvements
there
and
then,
let's
see,
and
then
your
peg
he's
got
the
log
volume
and
the
rest
of
the
pod
and
kilo
metrics
in
a
PR
a
peter
is
that
something
they
that
you
might
be
able
to
review
or
or
you
might
building
friend
us
a
second
for
any
chance.
So
you
here,
I'll
I'll
paste
the
link
in
there.
B
Actually
looks
like
he
just
added
a
few
people
to
it,
so
I
can
definitely
take
a
look
and
offer
anything.
I
might
have
yeah
and
I.
Think
okay
looks
like
Alex
Alex
said
apprentice
looked
at
it
already,
so
I
just
don't
know
if
you
or
if
you
had
anybody
else,
you
recommend
reviewing
it
because
that's
going
to
be
a
big
one
and
I'm
hoping
that
that
is
enough
time
block
horizontal
pod
auto-scaling,
but
I
haven't
had
a
chance
to
test
it.
Yet.
B
So
that's
that's!
The
main
stuff
I
have
I'll
just
be
falling
falling
up
on
those
and
making
sure
I
get
the
release
notes
submitted
sometime
this
week
for
the
1.11
and
then
I'm
going
to
start
working
on
the
group
managed
service
account
changes
again.
So
there
were
some
suggestions
from
the
cig
off
folks
on
how
to
rework
this
and
I
still
need
to
do
that
so
I'm
hoping
to
get
that
in
for
412.
Now,
because
we're
past
feature,
freeze,
411,
so
I
think
that's
all
I
got
for
now.
A
C
A
C
Go
ahead,
yeah,
so
I
work
for
a
Donnelly
financial,
I'm,
I
kind
of
focused
on
the
the
cuvette
infrastructure
here,
and
so
we're
we're
just
starting
to
test
out
windows,
actually
we're
working
on
some
windows
container
stuff
with
ACS
engine
right
now,
so
I
don't
have
any
specific
action
items
for
the
windows
side.
I
know
I
was
hoping
to
try
out
18:03
and
see
if
the.
If
the
version
of
docker
that's
installed
with
that
images,
is
newer.
C
I
know
with
some
of
the
older
versions
of
other
windows
nodes
we
had
to
go
through
and
annually
update,
lot
darker
versions
and
do
some
hacking,
the
kitchen
windows
containers
to
actually
work
so
I
know.
That's
probably
the
only
relevant
thing
that
I
can
even
talk
about
on
this
column
is
only
comes
to
the
window
side
of
the
project.
D
A
D
Because
from
what
I've
seen
at
one
I
think,
this
is
kind
of
like
a
bug,
because
couplet
calls
the
CNI
for
every
container
and
says
yeah
come
to
CNI
for
this
container,
and
this
is
the
sandbox
container.
So
basically
the
couplet
calls
the
CNI
and
the
CNI
will
think
that
every
container
for
me,
which
in
the
pod
is
sandbox
container.
That's
there
are
some
issues
in
the
CNI
because
of
that,
but
the
fix
is
pretty
easy
and
I
have
another
question
on
the
privilege.
A
B
Privileged
containers
aren't
supported,
yet
we
do
have
a
way
that
you
can
use
named
pipes
in
a
mount
if
you'd
want
to
talk
to
something
like
the
docker
demon
on
the
host,
and
so
that's
something
that's
possible.
Although
there's
currently
a
bug
in
docker
around
the
file
open
flags,
they're
being
used,
that
would
need
to
be
fixed,
but
that
might
make
it
possible
to
run
something
like
a.
B
D
B
D
B
And
the
reason
that
one
has
privilege
true
is
actually
because
I
was
running
it
under
open
shift
and
there
they
always
try
to
apply
a
default
security
policy
for
selinux,
which
of
course
doesn't
work
on
Windows.
And
so,
if
I
do
privilege
true
on
open
shift,
then
it
will
go
ahead
and
schedule
it
with
no
modifications.