►
From YouTube: Kubernetes SIG Windows 20190924
Description
Kubernetes SIG Windows 20190924
A
Hello,
everybody
and
welcome
to
another
see
windows
meetup,
it's
the
24th
of
September
and
thank
you
all
for
attending.
As
always,
please
adhere
to
the
CN
CF
code
of
conduct
all
right.
Let's
dive.
In
last
week
we
talked
about
the
contributor
summit
I'm,
hoping
that
a
lot
of
you
guys
got
a
chance
to
sign
up.
They
always
have
some
goodies.
A
A
There
were
a
couple
of
other
events
at
Kubik
on
there's
one
that
me
and
deep
will
attend
and
there's
also
I,
don't
know
what
the
right
term
for
it,
but
is
a
meet
the
maintainer
z'
area
that
that
they
will
actually
host
I'm
gonna
sign
up
for
a
few
hours
there,
if
any
of
you
guys
are
interested
in
in
they're,
going
to
Cuba
con
and
I'm
interested
in
contributing
more
in
terms
of
being
the
face
of
sig
windows.
Just
let
me
know
by
giving
in
to
the
different
events
are
happening
now.
A
A
The
event
that
deep
and
I
are
going
is
added
to
the
contributor
summit
and
that's
where
new
contributors
are
looking
for
areas
to
come
in
and
and
lend
their
expertise
now,
I,
don't
know
how
many
of
those
guys
are
gonna
have
windows,
expertise
or
interested
in
Windows,
but
being
there
is
you
know
it's,
you
know
it's
at
least
presenting
or
seek,
and
if
folks
wanna
tent,
you
know
that's
overall
good.
It's.
A
Sig
meet
and
greet,
and
then
there's
also
they
meet
the
maintainer.
You
know
will
continuously
attend
these
things.
Now
we're
not
only
sick
that
doesn't
have
people
there,
but
you
know
if
folks
don't
have
questions
for
us.
It
is
what
it
is
all
right.
Let's
get
into
our
agenda,
so
Patrick
on
the
announcements
from
the
release
team.
B
Yeah,
yes,
I
was
pulling
this
back
up.
Yes,
so
the
release
team
has
been
formed
and
they've
got
the
preliminary
dates
in
there.
October
15th
is
enhancements
freeze,
and
so
that's
when
we
need
to
have
all
the
caps
reviewed
I
did
you
know
one
minor
update
to
the
cap
already,
and
that
was
just
fixing
them.
Basically
the
milestones
to
say
we're
working
on
it
in
17,
as
opposed
to
I.
Think
it's
at
15
or
16
before
that,
then
I've
got
another
one.
B
We
can
discuss
a
little
bit
later,
but
the
main
thing
is:
that's
only
21
days
to
get
those
merged.
So
if,
if
anybody
else
has
kept
so
I
need
updates,
let
us
know
so
we
can
make
sure
that
we
get
time
for
them
on
the
and
the
weekly
meeting
agendas
here,
I,
don't
are
there
any
updates
needed
for,
like
the
GMS,
a
kept
deep
know.
C
I
I
think
besides
Jeremy
I
still
have
not
received
any
feedback
of
like
actual
enterprise
customers
using
it
so
I
think.
Typically,
what
I've
seen
in
some
of
the
other
signal
is
then
look
for
real
deployment
data
to
go
to
GA
so
and
I
think
we
explained
that
in
the
cap
as
well,
they
will
look
for
at
least.
A
B
A
A
B
B
F
E
B
G
E
B
Some
PRS
that
that
claudia
has
open
that
update
the
scripts
that
build
the
test
images
to
be
able
to
use
a
remote
docker
host
to
build
Windows
images,
and
so
the
idea
is
at
the
same,
proud
job
that
built
sees
on.
Linux
could
then
go
ahead
and
build
them
on
Windows,
using
that
remote
host
and
then
still
be
able
to
do
things
like
the
docker
login
needed
to
push
them
into
the
same
registry.
So
then
they
can
be.
F
I've
added
a
couple
of
extra
things:
the
beers
one
issue
that
you
jus
had
was
the
fact
that
we
were
using
isolation
hyper-v
when
building
the
windows
images.
So
we
can
actually
build
multiple,
most
versions
for
those
images
in
this
before
the
earth
years
and
semi-annual
channel
images
and
the
party
they
do
not
put
hyper-v
in
the
Google
Cloud,
and
this
was
blocking
the
progress.
F
F
C
So,
basically,
in
this
option,
I
don't
have
a
lot
of
background.
I
took
a
brief
look
through
the
pr,
but
so
just
to
clarify
it.
So
here
the
prowl
job
kicks
off
and
then
their
hosts
in
the
windows
host
in
Azure
pre
provision
that
builds
the
image
and
sort
of
knows
where
to
push
it
so
that
it
gets
appropriately
staged.
B
Well
well,
today,
Claudia
is
pushing
them
to
a
private
registry,
and
then
we
passed
that
and
they're
in
the
manifest
list
to
cube
tests.
So
that
way
the
images
are
pulled
from
that
that
private
reg.
Well,
it's
not
private
registry.
It's
on
docker
hub,
but
it's
pulled
from
a
non-default
registry
as
opposed
to
the
default
one,
and
what
we're
trying
to
do
is
get
something
hooked
up
to
the
prowl
process
so
that
the
bots
can
go
ahead
and
promote
these
images
and
put
them
in
the
public
GCR
repository.
B
B
B
C
F
B
B
B
That
need
to
be
tracked
on
this
board,
and
so
you
know
one
the
most
interesting
ones
right
now
is
that,
like
that
single
file,
mappings
are
not
working
quite
as
expected.
If
there's
an
existing
file
there-
and
so
this
means
that
things
like
the
termination
files,
you
know
work
because
that
file
doesn't
already
exist,
but
let's
see
hope,
but
the
hosts
file
already
exists
on
the
windows
container
and
so
populating.
That
is
still
failing,
because
it
can't
be
superseded
with
the
version
that
is
created
by
the
cubelet
today.
B
B
B
Actually,
link
there
from
that
from
that
dashboard,
and
so
occasionally
I
always
see
something
where
something
doesn't
get
set
up
correctly
or
there's
a
time
out,
but
most
of
the
time
things
are
starting
to
get
a
little
more
consistent,
so
we're
working
on
driving
those
failures
out
so
I
think
that's
all
I
have
for
today.
I'm
good
anybody
have
other
topics
you
want
to
bring
up.
A
A
B
C
A
B
B
And
so
I've
got
the
name
of
someone
that
runs
that
program
and
I'll
talk
to
them
and
see
what
they
want
to
do
about
next
steps,
because
I
don't
know
if
that's
a
the
dealer
needs
to
be
done
on
a
per
hypervisor
vendor
basis
or
how
they,
how
they
run
that.
So
you
know,
I've
got
a
name
and
I'll
see.
Well,
we
probably
need
to
do
next
to
get
those
discussions
going
and
and.
A
B
I,
don't
think
it's
necessarily
I
mean
because,
because
docker
doesn't
run
a
hypervisor,
it's
good
more
about
you
know
like
if
the
customer
is
running.
You
know
hyper-v,
while
they're
fine
today,
if
they're
running,
VMware
or
or
if
they're
running
on
you
know
like
AWS
or
GCP,
as
you
mentioned,
and
yeah.