►
From YouTube: Kubernetes SIG Windows 20180116
Description
Kubernetes SIG Windows 20180116
A
A
A
We
don't
have
to
do
it
today
because
we
just
started
it,
but
within
the
next
week
or
so
we're
going
to
start
looking
at
the
trailer
board,
looking
at
some
of
the
individual
items
on
there
and
making
sure
that
everybody
is
aware
of
the
efforts
are
happening
and
and
the
progress
of
that
and
I'm
pasting
here
in
the
chat
window,
the
link
to
the
Trello
board
or
anybody
can
can
access
that
it's
also
pink
towards
like
channels.
So
that's
there
as
well.
A
If
you
guys
want
to
take
a
look
at
that,
I
do
encourage
folks,
if
you,
if
there's
something
in
there,
that's
of
interest
to
you
and
you
want
to
pick
it
up,
go
ahead
and
do
that.
For
example,
there's
a
test
there
to
support
Windows
services,
so
we
can
make
both
the
couplet
and
the
procs
into
Windows
services.
A
lien
sardine
from
from
in
his
team
from
cloud-based
solutions
have
picked
that
up
so
they're
gonna
do
that
work.
We
do
have
a
few
other
workaround
CNI
plugins
and
networking
that
Microsoft
has
picked
up.
A
So
so,
overall,
there's
a
lot
of
tasks
for
one
to
ten
and
not
a
lot
of
time
to
basically
get
through
that
release.
So
I
do
encourage
folks
if
you
want
to
contribute
and-
and
you
like
you
like
this
effort,
go
ahead
and
and
and
pick
something
up,
even
if
you
don't
get
get
it
done,
any
any
contribution
is
valuable.
A
B
I
did
have
one
quick
question
is
Robert
for
looking
at
one
of
the
issues
they
brought
up
the
put
in
Cuba
and
to
proxy
and
Windows
services.
I
think
it
totally
makes
sense
for
cooler
to
be
a
Windows
service,
but
I
was
curious.
What
the
rationale
was
for
a
KU
proxy
as
as
I
understand
it
runs
as
a
it
runs.
What
as
a
pod
or
as
Damon
said,
or
something
with
on
a
Linux
IDE.
So
I
was
curious.
If
there's
more
information
behind
that
I
mean.
A
In
in
Windows
and
I,
let
Allen
since
he's
on
the
call
as
well
to
answer
that,
but
in
Windows,
in
order
for
that,
once
that
no
it
gets
added
to
kubernetes
a
coupling
is
to
always
be
running.
So
if
you
end
up
having
to
the
Buddha
node,
not
being
a
Windows
service
means
that
you
won't
be
able
to
access
a
node.
A
So
that's
kind
of
the
high-level
rationale
behind
that
right
from
the
moment
that
the
couplet
is
installed
on
a
node
to
make
sure
it's
running
and
then
well
then
node
gets
added
or
not
added
to
kubernetes
cluster,
then
that
couplet
is
basically
gonna,
be
doing
nothing.
So
it's
a
no
op
for
it.
It's
not
really
servicing
any
requests
and
less
till
you
are
added
to
a
kubernetes
cluster.
A
C
C
C
A
A
A
D
B
A
A
A
C
D
A
D
Okay,
as
long
as
this
document
is
somewhere
and-
and
we
know,
sort
of
what
we're
delivering
cuz
I
mean-
that's
really
the
whole
power
of
this
is
that
you
know
like
we
saw
in
1/9
where
we
can
do
a
lot
of
publicity.
It's
really
just
to
get
the
word
out
and
make
sure
that
people
know
that
this
great
work
is
happening.