►
From YouTube: Kubernetes Windows Office Hours 20190411
Description
Join us for this special Windows Edition of Office Hours! This is a live stream where we answer live questions about Kubernetes and Windows from users on the YouTube channel. The developers from SIG Windows will be available to answer your questions.
Feel free to bring your questions, give feedback to the team how you’re using Kubernetes and Windows, or to just passively learn by following along.
For more info: https://github.com/kubernetes/community/blob/master/events/office-hours.md
A
B
A
Windows,
so
the
way
this
is
gonna
work
is
we
are
hanging
out
in
hash
sig
windows
on
the
kubernetes
slack,
if
you're
watching
the
live
stream
on
youtube,
just
follow
the
instructions
that
I've
put
in
the
text
below
and
we
will
be
live-streaming
the
chat
over
here
actually
over
here.
This
sidebar,
you
should
see
the
slack
sig
windows
channel
you're,
definitely
encouraged
to
hop
on
in
ask
some
questions
for
the
next
hour
and
then
hang
out
with
the
team
and
find
out
all
that
you
need
to
know
about
this
feature.
C
B
E
A
Alright,
I
think
that's
everybody,
okay,
so,
let's
get
started
the
way
it
works
is
feel
free
to
just
whack
your
question
into
the
slack
Channel
just
preface
it
with
question
:,
so
I
could
see
it
in
the
meantime,
while
while
everybody
gets
ready
and
starts
queuing
up
their
questions,
I'm
just
gonna
start
opening
can
can
you
all
just
kind
of
fill
us
in
on
on
the
features
in
general
like
what
it
what
it
took
to
get
here
like
when
you
say,
kubernetes
and
windows?
That
can
mean
a
lot
of
things.
A
B
C
So
I
think
probably
the
first
bit
of
background
I
should
share
on
that
is
that
you
know
what
Microsoft's
start
developing
Windows
containers
as
a
feature
in
Windows
Server
2016,
and
that
is
using
the
same
docker
tooling,
that's
available
on
Linux.
The
only
real,
real
difference
there
is
that
it's
able
to
run
up
a
Windows
app
on
a
Windows
machine.
C
This
this
doesn't
mean
you
could
take
a
Windows
app
and
like
magically
run
it
on
Linux
or
vice
versa,
but
it
does
give
you
the
same
kind
of
tooling
that
you
can
build
into
your
developer,
workflow
and
what's
really
nice
about.
That
is
because
the
same
image
format
is
shared
across
multiple
orchestrators.
C
B
Absolutely
so
I
think
that
you
know
that
was
a
tremendous
benefit
to
be
able
to
kind
of
use
the
same
underpinning
infrastructure
so
being
able
to
use
the
docker
API
and
the
docker
engine
to
build
the
infrastructure
on
top
of
ways.
You
could
build
containers
give
us
a
lot
of
benefits
because
you
could
reuse
a
lot
of
the
same
code
and
practices
and
tooling
the
kubernetes
was
using.
B
So
we
took
a
lot
of
that
work
and
Microsoft
created
and
started
working
on
Windows
kubernetes,
with
a
goal
to
allow
windows
developers
to
bring
their
apps
into
kubernetes
and
introduce
worker
nodes
better
on
Windows.
So
took
us
a
little
bit
over
three
years
to
do
that
effort,
and
during
that
time
there
were
tremendous
contributions.
B
I
went
into
Windows
Server,
with
Windows
Server
2000
until
I
had
a
lot
of
the
work
around
the
host
network
service,
which
was
the
underpinning
for
creating
the
CNI
networking
plugins
and
were
able
now
to
provide
our
users
with
a
full
kubernetes
cluster
that
includes
a
kubernetes
master
running
on
Linux
Linux
worker
nodes,
as
well
as
Windows
worker
nodes.
So
you
have
a
heterogeneous
environment
where
you
can
run
all
the
apps
that
are
important
in
your
environment
and.
A
Needed
sorry,
I'm
gonna
ask
all
the
basic
questions.
So
how
does
this
work
for
the
developers
that
say
I'm
at
work,
I
have
a
mixed
team.
I
have
some
Linux
folks
like
how
does
it
figure
out
where
to
put
the
stuff
right
if
I
my
neighbor
has
Windows
stuff
like?
Is
there
workflow
differences?
Are
there.
B
B
From
the
windows,
developers
and
Linux
developers
are
a
little
bit
different.
We,
but
from
the
workflow
standpoint,
the
reason
and
that's
actually
the
part
of
kubernetes
as
a
if
you
have
a
CI
CD
system
that
built
to
deliver
apps
and
kubernetes,
so
you
have
monitoring
setup
or
you
have
any
other
best
practices
or
expertise.
Building
your
organization,
you
don't
have
to
call
them
in
so
you
get
these
kubernetes.
You
just
use
the
same
yum
of
specifications
to
deploy
your
applications.
You
just
need
to
understand
the
context
under
which
Windows
applications
are
deployed
and
Linux
apps.
B
You
build
your
app
into
a
Windows
container
and
using
some
of
the
best
practices
of
Microsoft
and
docker
have
provided
and
then
keep
kubernetes
a
young
specification
and
boom
your
I've
been
running
in
a
matter
of
seconds
and
you
get
to
utilize
all
the
power
of
kubernetes
from
the
high
availability,
that
is,
that
ability,
the
health
checks,
the
logging
all
of
that
good
stuff
that
you
guys
from
kubernetes
just
come
to
you
for
free.
So
that
is
a
tremendous
power,
but
by
the
way,
I
also
want
to
introduce
a
couple
of
new
members.
B
A
C
C
C
But
within
here
you
know,
I've
already
built
a
cluster
up
yesterday
afternoon,
but
I've
got
four
different
nodes
in
there.
Two
of
them
happen
to
be
running
Windows
Server
data
center.
Two
of
them
are
running
a
bunt
to
1604,
and
you
know,
even
though
I'm
connected
from
Linux
since
the
Saku
Bernays
api,
the
same
you
know
the
same
tools,
so
keep
control
are
still
working.
C
C
But
the
you
know,
all
the
syntax
is
pretty
much
the
same
here.
The
main
difference
is
just
that.
The
image
that
I'm
actually
deploying
is
one
that
was
built
on
built
based
on
a
Microsoft
Windows
server,
and
this
is
using
the
one
of
the
inbox
rolls
your
an
affirmation
server,
which
is
just
near
the
web
server
in
Windows,
and
so
you
know
really
simple
amyl
just
you
know
starting
one
container,
opening
port
80
and
then
mapping
a
load
balancer
service
on
that.
C
I
guess
it's
a
sort
of
Miss
name:
this
is
the
AIAS
service.
The
type
is
load
balancer,
but
because
I'm
running
this
on
Azure,
it's
actually
configured
on
as
your
load
balancer
here,
okay
and
so
if
I
wanted
to
set
up
ingress
using
nginx
I
could
do
that
and
just
run
nginx
on
one
of
the
windows
nodes
and
use
that
as
that,
as
the
controller
here.
C
A
B
C
C
But
anyway,
that's
you
know
actually
deploying
the
workloads
is
exactly
the
same,
and
so
all
the
same
tooling
that
people
are
already
familiar
with
whether
they're
you're
using
cube
ctrl
on
you
know:
Linux
Mac,
OS
windows.
You
know
that
that
tooling
is
all
the
same,
and
so
the
only
thing
that's
really
different
from
the
windows
developer.
Experience
is,
of
course,
how
they're
building
the
the
windows
containers.
C
Just
because
you
know
the
application
that
they're
running
inside
is
a
little
bit
different,
so
maybe
they
use
Visual,
Studio
and
dotnet
framework
and
then
build
and
then
run
docker
build
afterwards.
You
know
there's
plugins
for
doing
that
within
you
know
like
the
traditional
Visual,
Studio
and,
of
course,
there's
also
stuff
there
and
like
Visual
Studio
code
as
well,
so
it's
really
kind
of,
but
it's
really
kind
of
up
to
the
user,
for
what
their
preference
is
in
the
tooling
there.
It's
there's,
not
any
you
know.
One
thing:
that's
that's
require
that's
substantially
different.
A
B
And
then
what
also?
On
top
of
that
or
were
a
lot
of
our
effort
is
going
to
bring
in
all
the
same
CNI
providers
that
are
available
on
Linux,
also
on
windows.
Your
sin,
flannel,
host
gateway
is
available
or
idea
as
a
GA
feature
who
have
flannel
the
excellent.
That's
a
better
feature:
we're
working
with
folks
from
some
of
the
other
commercialized
CNI
providers
to
also
bring
them
in
Windows.
G
A
B
Don't
work
across
the
board,
you
know,
there's
a
are
you
see
and
I?
That's
specifically
really
tight
wire,
but
if
you're
using
flannel,
for
example,
or
any
of
the
other
wind
bridge
or
sea
and
ice,
then
we
could
definitely
corrupt
it
at
your
environment.
The
key
thing
here
is
that
the
you
know
most
of
the
contraband
is
your
upside.
Your
ya
know
specs
your
containers
and
if
those
are
available
across
any
cloud
where
that's,
who
have
private
registry
or
a
public
registry,
then
your
choice
of
networking.
B
As
long
as
the
capabilities
are
the
same,
she
doesn't
really
matter
that
much
but
yeah.
Most
of
our
CNI
providers
are
available
throughout
the
board
same
thing
for
storage.
So
we
do
have.
We
don't
have
the
same
storage
integration
that
exists
for
Linux,
while
you're
working
on
that,
but
anything
you
choose
will
like
flex
volumes.
It
will
be
available
throughout
any
cloud
environment.
You
have
deployed
yeah.
C
C
One
of
them
is
open
virtual
networking
and
that's
I'm,
using
the
open
virtual
switch
underneath
if
you've
got
more
questions
around
that
is
there
I
think
Alan
was
in
the
channel,
he's
new
he's
been
working
on
that
and
then
we've
also
got
support
for
flannel
and
that's
part
of
what
what
Callias
team
has
been
working
on.
Do
you
want
to
talk
more
about
that
Kalia.
E
Okay,
I
can't
see
that
picture
that
he
posted,
but
oh
no,
that's
separate.
Okay,
currently
right
now,
there
are
no
plans
that
we
have
to
support
network
policy
API
because
I
think
right
now
we
would
have
two
windows
network
policies
to
support
that,
but
if
there
is
a
need,
if
there's
a
specific
need,
you
can
talk
to
me
and
then
we
can
go
over
that.
But
currently
there
are
no
plans
because
we
haven't
had
too
many
customers
asked
for
it.
Yet.
B
A
Yeah
love
be
a
bit
of
delay
while
he
responds
so
we
have
76
people
watching
right
now,
but
not
a
lot
of
questions
so
feel
free.
Those
of
you
that
are
listening
in
you
can
join
the
slack
I,
follow
the
instructions
below
and
just
feel
free
to
just
ask
your
question
and
we'll
read
it
on
the
air.
I
see
some
people
typing
furiously,
so
we'll
give
them
some
time
to
ask
their
questions
and.
B
And
also,
if
anybody
has
a
couple
of
minutes,
they
can
finish
it
fill
that
poll
that
I
posted
earlier.
If
you
scroll
up
just
a
little
in
the
slide
channel,
we
will
go
through
that
and
kind
of
talk
about
some
of
the
items.
If
someone
doesn't
want
to
ask
a
question
directly
after
the
photo
will
be
completely
anonymous,
yep.
A
E
B
A
H
Think,
like
one
interesting
thing,
we
worked
on
in
114
on
the
identity
side
was
bringing
in
GMS
a
support.
So
the
idea
there
was
in
the
typical
Windows
Enterprise
scenario:
you
have
this
concept
of
Active
Directory
and
identities
associated
with
your
workloads,
so
that
as
Patrick
was
showing
you
may
have.
Is
that
says
hey
only
if
you
have
a
certain
identity
from
Active,
Directory
associated
with,
say
an
app
running,
and
that
is,
it
can
go
and
authenticate
against
database
write
a
sequence
over
database
to
the
backend.
H
So
one
of
the
things
we
prototype
as
an
alpha
in
in
114
was
bringing
in
that
support
to
kubernetes
containers
and
workloads.
So
some
of
the
inner
Plumbing's
of
that
was
already
present
in
in
through
the
dollar
engine
and
through
the
HCS
subsystem
below,
and
what
we
did
was
bring
up
that
support
like
surface
it
up
into
the
kubernetes
layer,
initially
through
annotations,
where
you
can
create
these
GMS
identities
in
the
cluster
as
custom
resources
and
then
associate
them
with
your
you
know,
say:
IAS
work.
A
A
It
sounds
like
he
was
asking
exactly
what
you
were
talk
about
us
and
Claire.
If
you
can
not
ask
if
you
have
a
specific
follow-up
question,
let
us
know
if
his
is
little
overview.
There
answered
your
question
and
then
s
question.
What
are
recommendations
for
hyper-v
versus
native
containers?
I
heard
security
is
a
major
reason.
Hyper-V
is
recommended,
but
what
are
the
security,
implementations
and
risks
of
native
containers
I?
Think.
C
Would
they
have
privileges
on
the
host
and
so
on?
Linux,
do
there's
been
a
set
of
practices
and
people
are,
you
know,
gradually
trying
to
build
processes
or
sorry
I'm
policies
around
that,
so
that
they
can
restrict
what
can
and
cannot
be
done
on
the
in
the
windows
case,
it's
a
little
bit
different,
because
each
container
actually
has
its
own
security
database
and
so
there's
no
equivalent
of
something
like
Etsy
groups
or
Etsy
password
that
are
shared
across
all
the
individual
containers.
C
So
the
users
are
always
separated
by
default,
and
so
it's
a
it's
a
little
bit
different
and
arguably
a
little
bit
more
secure,
because
the
users
aren't
inherently
shared
between
the
host
and
the
containers.
But
if
we've
got
customers
that
are
running
yo,
untrusted
code
and
they're,
you
know,
and
they
basically
want
two
layers
of
protection
against
breakout
attacks.
Then
that's
where
being
able
to
use
the
hyper-v
isolation
is
something
that
that
it's
something
that
you
may
want
to
do
there.
C
The
other
thing
that's
going
to
be
really
important
about
hyper-v.
Is
that
that's
also,
but
we're
going
to
be
using
to
build
support
for
forward
compatibility
and
what
I
mean
by
that
is.
If
you
build
a
container
that
runs
and
depends
on
Windows
Server
2000
19
today,
when
you
go
and
update
a
node
to
a
new
version
of
Windows
next
one
coming
out,
it's
going
to
be
night
1903,
although
I
think
that
might
be
it
miss
named.
C
But
then
one
of
the
differences
from
between
Windows
and
Linux
is
that
in
Windows
the
user
mode
needs
to
be
paired
with
the
same
kernel
mode
version,
and
so
in
order
to
get
that
back.
Compatibility
on
that
newer,
node
using
hyper-v
isolation
means
that
they
can
still
provide
that
container.
The
matching
kernel
version,
so
you
don't
have
any
compatibility
problems.
C
You
big
use
case
for
hyper-v
that
were
gonna
be
working
to
enable
and
probably
version
15,
and
it's
a
something
that
we're
discussing
right
now
with
cig
node
and
trying
to
get
some
alignment
around
runtime
classes
for
that.
So
that
way,
there's
a
very
clear
way
in
the
kubernetes
api
that
you
can
choose
what
level
of
isolation
you
want
and
when
you
actually
do
a
deployment.
So
that
way,
they'll
be
consistent.
We
know
with
what
people
are
doing
with
like
cada
and
some
of
the
other
efforts.
A
Okay,
Ben
I
hope
that
answers
your
question
feel
free
to
post
a
follow-up.
If
you'd
like
any
clarification
on
any
of
that
we're
about
halfway
through
those
of
you
that
have
joined
us,
midstream
feel
free
to
join
us
on
slack
below
and
ask
your
question.
The
next
question
comes
from
Carlos.
He
says:
what's
the
recommended
network
provider
plug-in
to
use
with
Windows
nodes
running
on
Azure.
C
Sure
I
could
that
one
so
as
you're
seeing
I
is
the
one
that
we're
doing
the
most
testing
with
today
and
like
the
tool
that
I
used
to
deploy
that
cluster
was
called
aks
engine
and
and
for
Windows.
It
should
be
using
that
by
default
and
so
that
that's
that's
the
one
that
would
recommend
using
their
that
also
lets
you.
Basically
it
the
way
it
allocates
all
the
IPs.
C
A
C
Okay,
so
I'm
trying
to
remember
what
Windows
sandbox
is
if
it's
the
one
that
that's
used
for
running
desktop
applications,
it
does
share
some
of
the
same
technology
that
we
use
underneath
for
for
the
docker
based
containers,
but
it's
something
that's
fundamentally
a
bit
different,
because
the
goal
of
Windows
sandbox
is
that
it's
supposed
to
be
able
to
isolate
the
application
from
the
rest
of
the
system,
but
things
like
the
version
and
some
of
the
stuff.
That's
on
your
system
is
supposed
to
bleed
through
and
be
visible
to
it,
whereas
in
the
containers
I'm.
C
Sorry,
when
we're
doing
docker
based
containers,
the
goal
is
that
you
can't
tell
what
host
you're
running
on
it
runs
the
same
everywhere,
and
so
it's
a
little
bit
of
a
different
goal.
The
Windows
sandbox
is
more
about
providing
desktop
level
isolation
and
there's
no
programmatic
interface
like
docker
around
it.
So
it's
it's
a,
although
it
may
share
some
of
the
same
technology
underneath
the
goal
is
not
to
use
kubernetes
deploy,
UI
based
apps.
The
goal
is
to
use
kubernetes
to
deploy
server
based
apps.
A
B
Allopatric
answer:
they
are
you
a
question,
I
guess,
from
the
Google
next
conference,
google
has
announced
a
private
preview
of
Windows
containers
in
UK,
so
you
can
assume
that
most
of
the
other
public
vendors
will
kind
of
follow
suit
within
their
own
timelines.
We
don't
have
anything
that
you
can
publicize,
but
public
you
aren't
about
as
a
result.
Yes,.
C
If,
for
a
sure,
we've
got
an
open
source
project
called
aks
engine,
that's
what
we're
actually
using
to
run
all
the
tests
on
the
kubernetes
master
branch,
and
so
you
can
use
that
today
and
build
up
your
own
cluster
with
whatever
kind
of
options
you
want
and
then
there's
also
a
sign-up
list
for
the
for
the
AKS
preview,
and
it's
so
that
that's
that's
gradually
rolling
out
right
now.
But
I
can't
like
you,
began
the
list,
but
I
can't
tell
you
exactly
when
you'll
be
able
to
start
using
it.
C
B
A
C
I
can
give
a
quick
intro
on
that,
so
it'd
be
great.
Khali
I
would
know
a
little
bit
more
on
that.
So
a
lot
of
the
pool
other
plugins
on
Linux
use,
IP
tables
to
basically
reroute
and
rewrite
traffic
and
Windows
has
a
similar
thing
called
the
virtual
filtering
platform,
and
that's
part
of
that.
The
team
that
Caleo
works
on,
but
basically
that
when
we
write
a
Windows,
CE
and
I
plug
in
VFP
provides
the
underlying
functionality
that
that's
able
to
do
that.
Do
you
want
to
elaborate
on
that
at
all
Kalia
yeah.
E
E
So
as
a
user
you're
not
really
concerned
about
the
rules,
you
just
need
to
know
which
H&S
objects
or
policies
to
configure
right
now.
Queue
proxy
is
mostly
responsible
for
those
types
of
things
and
then
other
network
plugins
like
calico
and
everything
they
program
each
nice
to
subsequently
program
VSP.
E
A
C
So,
like
I,
did
a
presentation
at
a
cube
Con
in
December
and
in
that
in
that
one
I
had
I,
don't
know,
I
think
it
was
something
like
40
people
in
a
room.
All
deploying
Windows,
apps
and
I
just
used
a
high
availability
and
genetics
cluster
there
running
on
the
linux
nodes,
and
then
that
worked
fine,
so
I
was
able
to
start
from
a
known
good
set
up
on
the
Linux
side
and
because
all
those
windows
nodes
could
you
know,
provide
services
using
normal
service.
C
Ips
I
could
still
route
all
that
traffic
in
there,
and
so
you
know
it
was
just
the
one
domain
name
and
public
IP
I
had
you
know,
I,
don't
know
40
50
different
services,
all
routing
through
that.
So
there's
there's
nothing
substantially
different
there.
But
if
you
wanted
to,
you
know,
try
running
something
directly
out
of
windows.
I
know
that
there
is
an
open
source
engine,
export
and
I.
C
B
A
B
Yeah
I
think
the
need
here
is
really
gonna
come
from
the
customers.
We
just
won
GA
right
now,
we're
gonna
hear
customer
feedback,
we're
gonna,
see
how
customers
and
users
are
deploying
windows
and
kubernetes,
how
they're,
using
it
and
kind
of
use
that
feedback
to
prioritize
our
next
set
of
features
and
and
I
mean
this
becomes
a
high
priority
for
many
users
and
it
becomes
a
need.
Then
we
as
a
community
are
gonna,
invest
in
it
and
make
that
a
reality,
but
right
now
no
specific
direct
needs.
A
And
with
that
we're
caught
up
on
questions,
Nick
would
like
to
add
that
traffic
is
working
for
him
thanks
for
that
feedback,
while
we
wait
for
more
questions,
this
gives
me
a
chance
because
we're
starting
to
run
out
of
time
here.
What
are
the
plans
for
the
next
cycle
and
beyond
what?
What
current
things
have
you
heard
so
far
that
your
Road
mapping,
you
know
we
don't
need
the
details,
just
like
the
general.
You
know,
yeah.
B
Those
are
super
important
things
for
us,
because
you
wouldn't
need
one
other
class
of
apps
that
can
run
on
kubernetes
on
Windows.
So
those
are
super
important.
The
group
managed
service
accounts
that
deep
mentioned
earlier
is
something
that
they
want
to
continue
graduating
to
the
next
stage
in
the
kubernetes
evolution
so
going
from
bed
to
eventually
GA
at
some
point,
so
we'll
continuously
invest
into
that
work.
B
So
our
work
is
not
done,
but
those
are
some
of
our
high-value
targets.
The
last
one
is
looks
like
Cuba
GM
is
a
chosen
Orchestrator
for
for
creating
clusters
in
the
community
and
from
users
everywhere.
So
our
goal
here
is
to
provide
full
tube
ATM
support
for
Windows
nodes
with
1.15
our
party
relative
to
our
door,
deep
yeah.
H
Like
increased
storage
support,
so
that's
one
of
the
things
we're
working
on
yeah,
making
sure
that
you
know
maybe,
through
a
privileged
proxy,
get
CSI
plugins
working
so
that
if
they're
based
on
Windows
and
adapt
to
the
API
exposed
by
the
proxy,
they
can
do
the
operations
that
are
gated
and
still
be
packages.
Containers
yeah.
C
B
A
B
Absolutely
so
so
not
just
sick
meeting
notes,
it's
actually
posted
it's
paint
on
the
slide
channel
as
well
already
posted
it's.
Basically,
a
getting
started
guides
for
for
Windows
includes
everything,
documentation
on
contributor
guides
or
meeting
notes,
meeting
schedule,
I'll
post
it
right
now,
and
it's
already
clean
folks,
yeah.
A
It
looks
like
you,
folks,
have
15
pinned
items,
so
that's
good!
Those
of
you
that
are
joining
new.
You
know
we're
expecting
a
bunch
of
neat.
That's
why
we're
having
this
a
bunch
of
new
users
now
that
this
is
a
major
new
feature
that
people
have
been
looking
forward
to
just
want
to
make
sure
that
those
of
you
on
the
stream
and
listening
know
how
to
find
the
information
I'm.
A
How
often
do
you
all
me
every
week,
every
other
week,
every
week
at
12:30
done,
okay
and,
like
all
the
other
SIG's,
these
meetings
are
open
to
the
public.
The
notes
are
published
and
all
that
good
stuff,
so
check
out
the
pinned
items
in
the
slack.
If
you
want
to
know
how
to
join
the
slack
just
put
slack
kubernetes
io
in
your
browser,
follow
the
instructions
and
join
the
sig
windows
channel
with
that,
Michael
would
like
to
ask
any
impact
to
windows
with
the
cryo
announcements
from
Red
Hat.
C
C
You
know
the
way
that
the
cubelet
could
be
configured.
You
know
you
could
point
to
any
any
API
endpoint
you
want
that
implements
cry
and
so
like
today
we're
using
docker
shim,
which
was
built
in
the
cubelet,
but
you
know
with
just
a
command-line
switch.
We
could
switch
over
to
cry
container
D,
and
so
you
know
cryo
would
definitely
be
be
viable
as
well.
C
C
Then
you
could
map
that
into
a
container
and
then
run
that
there
likewise,
you
know,
Windows
does
have
a
remote
management
protocol
called
win
RM
that
you
can
use
to
do
things
like
storage
management,
other
tasks,
and
so,
if
you
gave
a
container
a
certificate
or
a
user
name
and
password
and
the
IP
address
of
the
host,
then
it
could.
You
know,
connect
around
that
way
into
management
actions
on
the
host.
Much
like
you
would
do
with
something
like
SSH
promoting.
Of
course,
SSH
is
also
available
as
an
optional
component
on
Windows
Server.
C
If
you
want
to
run
stuff
there,
so
you
know
if
your
goal
is
to
you
know,
use
something
like
a
daemon
set
to
install
software
across
a
bunch
of
machines.
Then
you
could
do
that
by
basically
doing
a
loop
loop
back
and
gain
privilege
through
you
know,
basically,
over
the
network
using
an
network
based
login,
okay,.
A
But
I
hope
that
answers
your
question.
You
feel
free
to
ask
a
follow-up,
we'll
keep
it
open
for
questions
for
a
few
more
minutes,
but
as
we
as
we
get
into
the
outro
here,
there
are
any
major
features
or
anything
that
we
haven't
talked
about.
Yet
that
you
feel
should
get
some
attention
talk
a
little
bit
about
networking
a
little
bit
about
storage,
I.
B
They
also
thank
you
to
everyone
that
has
completed
the
poll.
That's
giving
us
good
insight
into
both
use
cases
for
any
windows
containers
what's
important
to
you,
so
so
this
is
a
really
good
feedback
that
we
can
use
to
help
us
prioritize.
Some
of
our
feature
requests-
and
you
know
from
the
looks
of
it
the
folks
that
have
completed
the
poll
are.
The
ones
are
more
passionate
about
Windows
and
it
looks
that
it's
both
urgent
and
important
to
your
organization
to
have
windows
containers.
A
It
looks
like
a
lot
of
people
showed
up
as
well
today,
so
this
is
something
that
we
could
do.
We
could
run
on
a
regular
basis
to
for
people
to
ask
questions
and
give
your
team
feedback
there.
So
if
you
think
this
is
pretty
good,
I
would
love
to
hear
it
or
any
other
feedback
that
you
have
on
running
these
office
hours
like
this.
We
also
have
general
kubernetes
office
hours
or
third
ones.
They
have
every
month,
if
you're
interested
in
that,
so
it
looks
like
some
people
are
typing.
A
A
B
Well
basically,
say
thank
you
for
using
thank
you
for
the
support.
If
you
guys
are
interested
in
contributing
or
last
to
have,
you
accept
all
levels
of
contributions
from
try
things
out
and
poliwag,
or
look
at
our
documentation
and
find
an
area
that
you
can
improve
or
or
make
sure
that
you
provide
us
feedback
in
an
area
that
you
want
us
to
improve
or
or
if
your
goal
developer,
and
you
want
to
try
honing
your
development
skills
and
get
started
in
the
kubernetes
community.
B
A
Right
and
we'll
wrap
this
up
will
likely
do
another.
One
of
these
so
pay
attention
to
the
listen
to
the
channel
and
the
usual
social
places,
and
we
will
do
announcements
and
with
that's
a
panel,
stick
around
for
a
little
bit
and
those
of
you
on
the
stream.
Thank
you
for
joining
us
and
we'll
see
you
next
time.