►
From YouTube: Kubernetes SIG Windows 20180327
Description
Kubernetes SIG Windows 20180327
A
I
heard
hello,
everybody
and
welcome
to
another
meeting
for
sick
windows.
Thank
you
all
for
attending.
It's
probably
gonna
be
a
short
meeting.
Today
we
don't
have
a
lot
of
updates
there.
In
the
last
week,
myself,
Patrick
Adelina
and
Alessandro
all
met
twice
with
the
cig
testing
and
the
toxic
testing
Commons
group
to
outline
the
plan
that
Microsoft
and
cloud-based
have
been
putting
together
around
creating
an
automated
the
CIC,
the
infrastructure
for
testing
and
validating
the
kubernetes
on
Windows.
A
That
includes
updates
to
test
cases,
modifications
to
existing
test
cases,
so
that
can
be
adapted
and
run
on
Windows
and
a
variety
of
other
things
to
kind
of
increase.
The
stabilization
of
our
feature:
we've
gotten
some
feedback
from
the
teams
and
a
lot
Delina
provide
more
deep
update
in
a
second.
But
overall,
this
is,
you
know,
great
response
on
the
features.
So
that's
good.
The
other
update,
I'm,
aware
of
bob,
is
gonna,
be
working
on.
B
B
B
A
For
some
of
these
tickets,
because
tickets
can
be
lost,
we
have
a
pretty
big
pool.
Is
it
possible?
You
can
create
a
single
page
that
you
kind
of
track
some
of
well
I,
don't
know.
Maybe
Patrick
might
have
a
better
idea.
I
just
want
to
have
some
form
of
tracking
of
the
tickets
that
we
find
our
high-priority
versions.
The
ones
are,
just
you
know,
hey
nice,
to
haves
and
we
can
go
through
them.
Maybe
next
week
you
can
actually
go
through
all
those
tickets.
A
C
Sure
so,
in
the
meeting
notes,
I've
got
a
link
to
to
the
Trello
board.
That's
been
tracking
a
test
issues
and
white,
and
what
I
hadn't
proposed
was
having
a
column
in
there
which
I
I
already
added
that
basically
says
blocked
by
bugs,
and
so
that
that
that
was
one
idea
I
had
for
tracking
the
stuff
that
was
going
to
block
progress
there
and
I
put
that
card
there.
Although
we
still
need
to
link
it
github
issue
to
it
your
for
any
of
these
things
that
we
need
to
get
a
fix
for.
A
A
C
I
know
that
Peter
had
put
some
feedback
in
there
already
and
I
respond
made
some
updates
and
responded
with
that
in
line,
but
basically
I
want
to
go
ahead
and
move
this
from
this
hack
MD
site
into
an
actual
feature
proposal
over
on
the
kubernetes
future
repo
and
then
discuss
it
with
cig
node
in
two
weeks,
I'd
like
to
do
next
week,
but
I'm
not
actually
going
to
be
in
town,
so
I
think
I'll.
Probably
do
it
two
weeks
from
now,
but
I
want
to
push
this
for
1.11.
C
C
Okay
turn
at
workflow
basic,
rather
than
using
a
secret
to
store
the
active
directory
config.
That
was
not
the
active
directory
config,
but
to
store
the
data
about
two
Active
Directory
user.
He
had
said.
Maybe
we
should
just
put
it
directly
into
the
API,
and
so
that's
something
that
I'd
likes
to
get
sick
notes
feedback
on,
because
if
you
look
at
the
OCI
spec,
we
just
pass
a
JSON
object
in
as
a
string,
and
so
we
could
do
that
in
the
kubernetes
api
or
we
could
store
it
in
a
secret.
C
Both
ways
are
feasible
and
both
of
them
would
be
pretty
easy
for
the
user
to
do.
We
just
need
to
decide
whether
or
not
there's
it's
better
to
separate
it
into
two
steps
where
you
put
that
data
in
a
secret
and
then
reference
it
or
if
it
should
just
be
part
of
the
deployment.
So
if
anyone
else
has
feedback
on
that
or
other
topics,
please
let
me
know
and
then
I'll
make
sure
to
get
that
incorporated
when
I
get
this
into
the
formal
proposal
on
their
agenda.
I
looked.
A
A
A
C
A
So
there
was
a
let
me
actually
find
a
ticket
right
now.
There's
a
github
II
should
too
eight
eight
eight,
that's
part
of
a
bigger
PR
that
and
I'm
putting
it
here
on
the
on
the
message
as
well.
It's
part
of
a
bigger
PR
that
basically
were
commanded.
Xe
is
not
used
in
Windows
on
these
exact
and
bash
and
that's
basically
failing
certain
commands.
So
what
was
gonna
Bob
was
gonna,
look
at
that
and
fix
that,
and
possibly
contribute
to
the
bigger
PR.
That's
PR
2029
and
also
in
the
comments.