►
From YouTube: Kubernetes SIG Windows 20180123
Description
Kubernetes SIG Windows 20180123
A
Everybody
and
welcome
to
another
meeting
for
sick
windows,
so
we
provide
a
couple
of
updates
and
then
we
can
take
a
look
at
some
of
the
items
that
we
had
on
the
trailer
board
to
see
if
you
know
get
a
quick
update
on
those
so
from
from
the
things
I
know.
So
me
and
Minn
alessandro
from
cloud
base
had
a
couple
of
discussions
around
a
variety
of
topics.
The
first
one
is
they're
finalizing.
A
The
proposal
for
the
CI
CD
and
end-to-end
test
pipeline
they'll
be
able
to
share
that
with
the
community,
both
in
terms
of
the
goals
of
the
automated
tests.
The
scenarios
that
we'll
cover
I
think
of
this,
as
primarily
covering
the
windows,
server
additions
to
kubernetes,
making
sure
our
pods
can
be
deployed.
They
can
be
scaled
CNI
solutions
like
Aviano
vs
and
a
few
others
can
be
picked
into
the
test
infrastructure
and
exercise
making
sure
the
pods
can
communicate
with
the
internet
and
so
on
and
so
forth.
A
So
kind
of
the
high-level
goals
of
our
testing
and
when
Alessandra
is
ready.
He'll
share
some
of
these
details
both
around
the
architectural
plan,
as
well
as
the
execution
details
on
that.
The
second
item
that
Alessandra
and
I
talked
was
around.
You
know
and
that's
something
that
might
be
leveraged
by
our
end-to-end
test.
But
think
of
this
is
a
simplified
installer,
simplified
installer.
A
That
would
allow
you
to
set
up
kubernetes
environment
with
Windows
Server
added
to
that
this
wall
there
some
of
the
backbone
infrastructure
of
this
work,
who
might
be
able
to
leverage
it
in
the
king
somatic
Enterprise
toolkit,
which
is
an
open
source
project.
That
apprentice
is
basically
maintaining
that
allows
you
to
stand
up
a
kubernetes
cluster,
so
we
will
add
Windows
Server
to
that
to
that
solution
as
well
and
who
might
be
able
to
leverage
the
word
cloud
base
and
Alessandra
steam
will
deliver.
A
That's
some
of
the
high
level
updates
there's
more
direct
updates
to
work
around
the
around
the
work,
both
on
the
scene,
I
work
and
as
well
as
around
the
CRI
and
container
stats
that
gentian
has
been
has
been
working
on.
So
let's
pass
the
torch
to
different
folks,
so
they
can
give
us
those
updates
and
and
then
we'll
open
it
up
for
questions
so
Patrick.
Do
you
want
to
start
or.
B
Yeah
yeah
I,
don't
have
a
ton
of
stuff
for
today,
so
yeah,
as
you
mentioned,
you
know,
we've
been
talk
talking
with
cig
testing
and
trying
to
just
sort
of
get
get
some
plans
and
proposals
together
to
clarify
what
Windows
testing
is
needed,
so
we'll
probably
be
able
to
share
more
about
that
later.
But
that's.
What's
still
in
the
planning
phase
at
10:00,
we
were
going
to
go
to
sig
note
and
continue
the
container
resource
discussion.
B
Please
share
it
on
a
slack,
Channel
or
feel
free
to
open
issues,
but
I
think
that
that
I
think
this
is
a
first
step
towards
us
being
able
to
get
the
secrets
volume
support
fixed,
and
so,
if
anybody
else
has
got
you
know
lab
setup.
I'd
love
to
hear
your
feedback
on
that
build
and
I
think
that's
pretty
much.
The
main
stuff
I
had
forward
to
for
today.
A
C
C
Completely-
and
the
second
point
is
the
for
Windows
compared
to
Linux
the
the
security
context
and
the
special
configuration
is
not
used,
I
could
not
II
could
net
right
now.
Therefore,
the
feedback
is
the
probably.
Instead
of
the
current
the
meeting.
Last
week,
we
were
in
a
subsequent
meeting
to
give
a
high-level
overview
of
all
the
what
can
be
implemented
in
Windows
for
currently
the
resource
control
for
CPU
and
memory
for
Windows
looks
good.
C
So
in
this
meeting
we
are
trying
to
discuss
break
down
the
windows
configuration
base,
the
first
part
of
CPU
and
the
memory
resource
control.
We
already
have
a
key
on
so,
let's
see
we
can
get
that
move
forward
first
and
then
Patrick
and
happy
folks
will
work
on
overview
design
of
other
windows
configurations
and
the
result.
Control
for
CPU
memory
would
benefit
definitely
the
windows
native
container,
as
well
as
happy
container.
So
this
would
be
a
cuisine
we
can
get
that
in
the
1.10
release
yeah.
So
that's
been
from
my
side.
A
D
Synoptic
from
me,
I
didn't
manage
to
fully
Sun
the
PR
because
they
just
implemented
the
I'm
talking
about
the
adding
service
support
to
the
couplet
and
coop
proxy
I
just
finished
the
cold
butter.
You
managed
to
test
it.
So
I,
don't
know
if
that
can
get
into
1.10.
If
that
counts
as
a
feature
or
does
it
counts
as
a
code,
because
I
think
the
feature
freeze
was
yesterday:
well,
hey
yeah.
D
A
Okay,
thank
you.
Thank
You
Ellen
for
the
for
the
update,
see
I
had
one
last
thing
that
I
had
was
we
had
a
couple
of
folks
that
last
week
volunteered
to
to
basically
help
us
with
both
looking
at
over
our
documentation
on
the
getting
started
for
Windows,
trying
out
the
different
CNI
plugins
and
identifying
areas
that
that
were
not
very
well
documented
or
didn't
work
very
well.
So
so
we
had
so
so
the
folks
that
have
basically
opted
in
to
do
that
work.
One
of
them
was
Jess
from
container
D.
A
E
A
F
B
B
A
F
A
That's
the
one!
So
if
you,
if
you're
not
getting
any
traction
on
that,
let's
try
to
get
that
in
as
soon
as
possible,
so
we
might
make
it
into
into
19.2,
for
example.
So
if
you,
if
you're,
not
getting
interaction,
just
ping
me
on
the
PR
and
maybe
Adelina
swirled,
that
way
we
can
get
a
couple
of
reviewers
in
and
just
it's
just
pushed
off
very
possible.
Yes,.
A
B
One
last
thing:
I
forgot,
so
I
also
opened
up
a
PR
that
I
mentioned
on
the
channel.
One
of
the
things
sig
noted
was
looking
for
was
more
clarity
on
what
things
worked.
It
didn't
work
out
in
API
level
and
so
I
took
the
draft.
I
had
shared
around
cue,
Kong
and
I'm,
trying
to
see
if
I
could
put
that
in
the
community
repo,
and
so
if
anyone's
got
feedback
on
you
know.
B
If,
if
that
content
is
right,
it
or
if
that's
the
right
place
for
it,
I'd
love
to
hear
it,
but
I
think
that
sort
of
the
goal
there
is
that
they
want
to
understand
an
API
level.
What
things
are
going
to
need
to
change
for
Windows
over
time.
So
that
way
as
they're
evaluating
things
like
the
resource
constraint,
PR,
that's
open
that
they
get
a
better
view
of
whether
or
not
it's
going
to
conflict
with
any
work.
We
need
to
do
later.