►
From YouTube: Kubernetes SIG Windows 20200512
Description
Kubernetes SIG Windows 20200512
A
Everybody
welcome
to
another
sick
windows,
meetup,
it's
the
12th
of
May
today.
Hopefully,
everybody
is
having
a
good
day
good
week.
As
always,
this
is
a
recorded
conversation.
So
please
adhere
to
the
seam
CF
code
of
conduct
and
let's
get
started
kind
of
looking
their
agenda
for
today,
not
not
a
lot
of
not
a
lot
of
items,
but
let's,
let's
go
through
them
share
my
screen,
I
mean
if
you
can
all
see
my
screen.
A
Excellent,
thank
you
so
so
the
first
order
of
business
is
a
Kubik
on
you
updates.
So
we
actually
have
two
sessions
for
cubic
on
a
high-level
session
to
talk
about
in
throat
windows
as
well
as
a
deep
dive
and
now
from
the
looks
of
things
we
were
supposed
to
have
Taylor
and
I
believe
Ben
moss
do
the
first
session.
But
you
know
kind
of
looking
at
the
Kubik
on
schedule
looks
like
Mars.
Right
now
is
the
the
new
owner
of
the
session.
A
B
A
I'm,
assuming
since
there's
no
travel,
maybe
Taylor
can
come
back
into
the
schedule
right,
I'm,
assuming
you
know
that
this
was
kind
of
shuffled
a
little
bit
due
to
travel,
so
maybe
Taylor
and
muss
can
come
back
and
do
their
session,
and
the
second
window
session
that
you
have
is
the
one
that
mark
and
I
are
doing,
and
we
will
you
know
the
the
dates
are
not
ideal
for
neither
me
nor
mark,
but
we'll
figure
out
a
way
to
do
this.
It's
only
35
minute
sessions.
A
So
it's
not
a
lot
we'll
give
everybody
an
update
on
sick
windows
where
we
are
in
all
the
new
changes.
Oddities
specifically,
you
know
GMS
aong,
a
CSI
and
and
and
the
work
that's
happening
there
and
cubicles
gonna
happen
at
the
tail
end
of
119.
So
if
we
have
made
significant
progress
in
continuity
or
other
technologies,
we'll
be
able
to
kind
of
talk
about
that
at
all.
So
we'll
keep
the
two
sessions
we'll
see
what
what
mas
can
do
and
and
and
go
from
there
any
questions
on
that.
A
All
right.
Second
thing
is
really
quickly
mark
myself
and
Craig
and
I.
Think
Craig
and
I
haven't
done
much
work
on
this,
but
we
need
to
I've
been
working
on
a
set
of
interview,
questions
that
would
be
used
to
produce
a
piece
around.
You
know
how
secundus
is
working
with.
Are
we
focusing
on
and
help
folks
get
some
insight
into
our
seek
and
potentially
excite
some
new
contributors
to
come
in
and
develop
an
RC
I'm
gonna
put
the
document
here.
A
A
All
right,
cool!
The
next
item
is
PRS
for
build
instructions,
so
so
these
are
the
ones
that
Patrick
added.
We
actually
have
a
new
community
six
repo
called
seek
Windows
samples,
so
there's
two
pairs
of
Patrick
created
here.
We
actually
open
them
up,
and
you
know
that's
a
result
of
the
work
that
he
mentioned
last
week
right.
So
he
has
a
whole
bunch
of
samples
in
other
work
and
as
well
as
old
content.
That
was
in
his
report
that
he
doesn't
have
time
or
resources
to
keep
maintaining
so
he's
asking
to.
A
A
B
C
A
Right
closing
in
on
the
OS
version,
support
so
I
think
we'll
have
consensus,
but
let's,
let's,
let's
see
if
anybody
disagree.
So
what
do
you
had
agreed
was
one
long-term
servicing
channel
several
2019?
That's
not
gonna
change
for
the
foreseeable
future
and
then
the
last
two
si
si
is
the
semi-annual
channel
that
Microsoft
is
pushing
releases
twice
a
year.
Any
questions
or
concerns
on
that.
D
A
That's
that's
basically
I'm
the
one
that
wanted
to
so
it's
for
one
release,
it's
great,
but
you
know
it
comes
to
a
point
that
we're
always
gonna
have
to
choose
hey.
Is
there
a
sac
release
that
just
came
out
recently
right
before
the
kubernetes
release,
or
is
it
gonna
come
right
after
one
it
introduces
complexity
and-
and
given
that
you
know,
if
we
do
it's
not
a
huge
burden
on
us,
it
allows
us
to
kind
of
open
up
a
much
bigger
gap
of
support
and
and
that's
what
we
want
right.
A
I
mean
we're
a
small
Sikh.
We
don't
have
a
ton
of
customers
who
don't
have
a
ton
of
users,
so
not
limiting
them
on
the
versions
of
Windows.
Other
support
is
gonna,
be
idea
right,
like,
let's
not
add,
more
restrictions
and
more
barriers
to
adoption
and
entry
here.
So
let's
be
open,
let's
have
to
and
it
becomes
a
little
more
support
burden
for
us
a
little
bit
more
test
burden.
But
given
the
day
that
we
heard
the
I
believe
it
was
last
week
from
Adelina
and
mark,
it
didn't
seem
like
he
was
an
impossible
feat.
A
I
mean
I,
don't
think
we
do
that
anywhere
in
the
company's
community.
Well,
I
mean
that's
more
around
the
question,
so
they're
old,
kubernetes
versions,
I
think
that's
more
of
a
problem
for
some
of
the
distributions,
like
the
public
clouds
that
are
like
even
have
1.14
out
and
1.14
is
no
longer
supported.
Is
that
kind
of
your
question
the
Frank
so
I
mean
that's,
been
a
problem
across
the
board
like,
for
example,
contoured.
That's
another
project
I
ran
and
we
tend
to
incubate
it
into
C
and
C.
A
A
Tests
on
the
things
that
kubernetes
it
on
its
own
officially
support,
but
should
someone
find
an
issue,
let's
say
Google
or
as
your
AWS?
Obviously,
when
I
look
at
that
issue
and
its
merits
and
if
it
makes
sense
and
there's
a
significant
customer
base
on
a
version
of
kubernetes
and
you
need
to
figure
out
how
to
fix
it,
the
reason
why
I
don't
run
that
is
because
aging
goes
right.
So,
let's
say
kubernetes
1.14
is
not
actively
maintained.
What
is
making
bug
fixes,
so,
ideally,
nothing
should
break
correct.
A
B
We
currently
we
do
have
test
passes
for
at
least
on
Windows
Server
2000
1840,
actively
supported
ones
to
test
all
of
the
optics
branches
as
they
are
generated.
So
we'll
probably
maintain
that
I
think
we'll
have
to
decide
if
we
want
to
run
that
matrix
on
just
possibly
the
LTS
C
version
of
Windows
or
all
the
supported
versions
of
Windows
as
well.
D
To
be
honest,
I'm
not
totally
convinced,
but
I
thought
I'd
laid
out
a
proposal
in
that
bug,
but
it
sounds
like
no
one
else:
yeah
I,
don't
know
I,
guess
I'm.
If
complexity
is
our
concern,
then
for
this
for
us
here
in
the
city,
then
just
having
one
to
one
mapping
makes
sense
to
me
to
reduce
that
complexity,
and
it
feels
like
for
users
who
are
concerned
about
the
cadence.
That's
why
LTS
C
is
for
but
again
I
know,
I.
Think
I
laid
out
my
thoughts
there,
but
if
yeah.
A
A
By
the
way,
like
this
plan
is
not
etched
in
stone,
right,
they're
not
gonna,
create
the
support
for
this
anywhere
publicly
right
I
mean
with
every
kubernetes
version.
We
get
to
say
what
is
a
port
and
what
we
don't
support,
and
if
this
model
doesn't
work
for
us
and
it
proving
to
either
be
expensive
from
a
time
and
resources
perspective
or
complicated,
then
we
could
always
drop
it
to
one
on
one.
A
So
I
want
to
actually
bring
up
one
more
point:
I
has
come
to
my
attention,
there's
a
couple
of
PRS
for
signal
that
are
just
waiting
and
having
made
much
progress,
I'm
wondering
if,
if
any
of
you
have
anything,
that's
waiting
for
sig
note,
please
feel
free
to
ping
me
and
I'll
bundle
them
all
together
into
a
comprehensive
ask
for
them
to
spend
some
time
with
us.
You
know
we'll
ask
you
you
and
Don
and
see
if
they
can
add
some
time,
I've
gotten
one
of
those
PRS.
A
If
there's
more,
please
send
them,
and
that
kind
of
also
reminds
me:
do
you
remember
that
PR
from
from
the
team
that
was
pushed
out
of
118
right
at
the
last
minute,
because
he
didn't
have
Windows
tests,
I
wonder
if
that
the
driver
support
I,
wonder
if
that
that
person
went
back
and
wrote
the
test,
because
up
here
I
will
not
go
anywhere.
If
it
he
doesn't
do
that.
C
A
Nothing
else
all
right:
everybody
give
back
their
15
minutes.
I
will.
Thank
you
all
everybody
stay
safe,
hopefully
we'll
get
to
see
a
lot
of
you
guys
either
attending
late
at
night
or
early
in
the
morning,
on
some
of
the
Cuba
contacts
and
and
and
please,
if
you,
if
you
have
some
minutes
and
you're,
not
some
more
questions
on
that
say,
windows
interview,
please
go
ahead
and
add
it
cool
thank
you're,
a
great
resume.