►
From YouTube: The Windows Operational Readiness Specification - Amim Moises Salum Knabben & Xinqi Li, VMware
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
The Windows Operational Readiness Specification - Amim Moises Salum Knabben & Xinqi Li, VMware
Speakers: Amim Knabben, Xinqi Li
Windows nodes have been a bit of an enigma in the Kubernetes community for some time. What do they support? How are they different from Linux nodes? And what “Conformance” standards should they adhere to in an enterprise environment? In this talk, we’ll introduce the Sig-Windows operational readiness specification which does for Windows what the Kubernetes Conformance tests have provided for Linux clusters: A standard for defining a fully functional Kubernetes environment. We’ll go through the 6 categories of Enterprise Windows use cases that we’ve identified as part of our Operational Readiness tests for windows, how each one is tested and how this framework works under the hood. We’ll also demonstrate how we use it to verify advanced “realistic” Windows scenarios, such as GMSA and Windows NetworkPolicy support.
A
And
finally,
this
project
is
still
a
working
progress,
so
we
want
to
bring
a
framework
attention
from
the
community
and
we
will
like
to
see
the
most
our
collaboration
on
this.
The
goal.
The
goal
of
this
talk
is
to
the
golf
resort
is
to
introduce
the
windows,
the
idea
of
Windows
operational
Readiness
and
attract
more
people
like
we're
very
well
very
well
going
to
Upward,
and
anyone
else
was
interested
in
this
project
started
their
contribution
to
the
uptrend.
A
So
the
first
question
here
is:
what
is
performance
test,
so
imagine
you
as
a
kubernetes
vendor
and
let's
say
you
have
to
ship
a
product
to
your
customer
that
helps
customers
to
create
kubernetes
one
certified
clusters.
So
how
do
you
verify
the
project
for
the
cluster
created
by
your
product
to
support
all
the
required
apis
in
Google
next
155?
A
That's
the
protocol
connection
work,
can
user
amount
of
volume
to
their
cost
and
also,
if
you
imagine
yourself
as
a
kubernetes
developer,
how
do
you
know
that
the
feature
you
are
about
to
add
to
one
to
125
or
works?
Well,
all
the
works
well,
with
all
the
existing
features
there
and
if
you
are
like
troubleshoot
the
cluster,
how
do
you
know
about
how
to
systematically
figure
out
what
works
and
what
doesn't
work?
So
the
answers
to
all
the
questions
here
is
that
if
we
have
a
suite.
A
A
A
There's
one
thing
that
actually
is
still
not
an
official
cncf
testing,
but
here's
come.
The
first
question
is:
what
is
the
windows
kubernetes
cluster?
It
means
its
support,
running
containers
in
a
class
in
running
containers
on
its
Windows
OS.
Let's
see
if
we
have
a
cluster
and
you
can
use
Linux
OS
as
the
control
plane,
node
OS
and
use
Windows
OS
in
the
like
the
rest,
part
of
your
worker,
node
or
all
of
your
worker
nodes.
A
A
A
A
You
need
to
like
set
up
your
ad
server
first
and
then
create
the
domain,
create
a
group,
managed
service
account
and
join
the
node
to
domain
or
set
up
the
security
context
for
the
node
for
the
part
to
access
the
resources
in
the
domain.
So
so,
after
all
this
setup,
you
can
run
this
test
to
see.
If
you
said
you
do
that
correctly,
but
this
kind
of
setup
is
not
required
for
all
the
Clusters.
So
it's.
A
And
windows,
operational
readiness,
the
playlist
conformance,
is
defined.
Bacteria
is
official,
but
the
when
we
find
that
cap
2578,
which
is
not
the
official
one
and
the
implementation
of
all
the
tasks
listed
by
both
tests,
lives
in
the
Upstream
kubernetes
Ripple
and
the
official
way
to
run
the
learner's
conformance
is
Byron
way
to
run.
A
A
So
the
tool
can
automatically
detect
what
version
of
kubernetes
you
are
using
and
download
the
pre-compiled
test
free
compiled
binary
from
Upstream,
but
you
can
also
set
up
an
environment
variable
called
kubernetes
hash
points
to
any
Upstream
Community
chart
you
want
to
use.
So
by
doing
this,
the
tool
will
first
pull
down
the
Upstream
kubernetes
triple
and
check
out
your
commit
and
build
this
E3
test
binary
from
there.
A
A
Messages
all
the
functionalities
we
want
to
add
here
and
for
each
task
as
it
belongs
to
one
of
the
nine
categories
I
mentioned
before.
So
the
description
here
tells
us
what
functionality
we
want
to
test
for
this
test
case
and
the
focus
and
Skip
are
the
same
with
strengco
focus
and
gentle
skip.
So
here
we
match
the
functionality
with
its
Upstream
implementation.
So
let's
take
the
first
test
case,
for
example,
if
we
want
to
test
the
ability
to
access
Windows
container
IP
by
part
IP,
we
want
to
run
the
Upstream
jinkle
test.
A
It
should
have
stable
Network
for
Linux
and
windows
pod
and
also
here
we
can
find
the
existing
implementation
of
the
functionality,
but
sometimes
the
test
is
missing
in
the
Upstream.
So
if
that
happens,
we
add
new
tweak
tasks
to
the
Upstream
kubernetes
folder
directly
and
in
the
top
of
this
file,
there's
a
kubernetes
version
which
tells
us
which
version
of
which
kubernetes
version
are
we
testing.
So
let's
say,
if
you,
you
want
to
run
the
active
directory
test
and
it
started
support
by
kubernetes
since
118.
A
A
So
this
is
an
example
of
running
the
operating
binary
directly.
The
categories
here
is,
though,
like
you
can
Define
one
or
more
categories.
You
want
to
run
so,
for
example,
here
we
Define
categories
equals
to
core
Network
and
extend
active
directory
so
that
all
the
test
cases
from
these
two
categories
will
be
triggered.
A
So
here
this
is
that
the
utility
test
binary
is
called
internally
and
the
windows
parameters
are
set
by
default.
So
we
know
that
you
are
running
on
a
Windows
cluster
and
here's
the
code
base
of
how
we
generated
the
command
to
trigger
the
E3
test
binary,
and
this
is
what
the
result
looks
like.
So,
if
you
define
the
report
there
or
the
artifacts
environment
variable,
the
result
will
be
stored
in
those
folders
and
it
can
be
passed
by
the
Dashboard.
C
C
For
those
who
don't
know,
Sona
boy
is
the
standard
tool
for
running
and
submitting
the
conformance
test
for
Linux.
So
it
totally
makes
sense
to
bring
these
to
our
project
and
make
this
a
default
for
the
windows
operational
brightness
as
well.
Besides
running
this
in
the
cluster,
you
can
have
tools
for
run
for
parsing
and
extracting
the
results
and
give
you
the
summary
of
the
results
you
you
just
run
your
closer
we're
gonna
sing,
the
next
slides
so
to
run
the
operational
redness
via
Sona
boy.
It's
super
simple.
C
We
have
a
solo
by
plugging
ammo
file
where
you
can
net
it.
You
can
Define
the
specification
for
all
the
specification
for
a
son
of
boy
plugin,
so
you
can
do
the
same
way
as
you
do
running
this
in
the
CLI
you
pass
like
the
e2e
binary
the
path
you
pass,
the
core
Network,
the
category
that
you
want.
Whatever
you
want,
if
you
don't
want,
you
want
to
run
a
particular
category.
You
just
remove
all
the
categories
in
this
one
of
them.
C
So
one
thing
that
was
super
cool
that
Mark
help
us
to
to
do
is
publish
these
on
the
GCR
bucket
Upstream.
So
every
time
you
merge
these
on
on
Master
on
Main,
you
can
have
one
version
of
the
latest
Socia
oci
image
of
the
project.
So
you
can
use
these
on
a
solo,
Sono
boy
on
your
own
path
or
any
anywhere.
You
want
to
run
the
image
of
the
project.
The
docker
file
is
in
the
root
as
well
super
simple
to
use
and
and
start
and
getting
started.
C
So
we
have
a
few
make
Targets
in
the
project
that
will
help
help
you
and
simplify
the
the
streamlined
experience
you
have
with
the
with
the
system.
So
you
can
run
make
solo
by
plugging
this
will
start
the
Sono
boy
I.
Think
at
this
point
this
will
wait
for
the
results.
You
have
dash
dash
weight,
zero,
so
it
it
will
wait
to
run
the
the
job.
The
conformance
plugins
extract
the
results
and
and
dump
this
inside
the
Sono
boy,
so
you
can
run
make
sort
of
boy
results.
C
This
will
read
the
results
and
output
it
for
you.
So
in
the
example
here,
one
of
the
network
policies
tests
fail.
It
will
print
out
what
tests
for
you
in
the
in
the
screenshot
the
bottom
and
give
you
like
some
percentages,
some
information
of
the
state
of
your
closer
at
the
time
it
was
running,
it's
super
simple,
super
easy
to
run
and-
and
we
have
a
few
Market
Target-
make
file
targets
to
help
you
on
that
yeah.
So
we
start
to
explore
the
few
usages
of
this
project.
C
Already,
some
good
stuff
are
going
on
the
first
one,
and
this
is
like
in
the
developer
side,
you
can
use
the
windows
Dev
tools
to
bootstrap
your
own
closer.
It's
super
easy
to
bootstrap
it
you,
you
don't
need
a
cloud.
You
just
run
this
locally.
You
need
a
good
machine
to
to
run
that,
but
that's
fine!
You
just
need
virtualbox
vagrant.
Everything
is
open
source
everything.
C
Everything
is
fine
for
a
personal
use
in
the
project
you
just
run
make
and
you
can
run
the
windows
operational
redness
to
inside
your
own
local
virtual
system.
You
know
you
you
Windows
closer,
so
advancing
a
little
bit
in
the
use
cases.
We
have
like
a
integration
of
the
pro
jobs
you
can.
When
you
do
a
comment
in
the
project,
you
can
run
slash
tests,
operational
test
cap
Z.
C
This
will
bring
up
a
cap,
Z
closer
for
you
with
Windows
2000
2019,
and
we
run
all
the
tests
in
the
system
and
you
we
would
put
this
for
real.
So
we
integrated
the
pro
jobs
with
our
project
and
we
can
run
our
project
as
a
custom
job
of
pro,
and
this
will
bring
up
the
results
of
the
of
our
changes
of
what
you
are
developing
at
the
moment
for
you
in
Pro.
C
C
So
one
way
to
use
that,
like
you
it
it
brings
you
a
brain
or
Master
closer
that
we
call
management
cluster
and
this
management
cluster
will
bootstrap
new
workload
clusters
for
you,
so
you
can
have
hybrid
Os
or
you
can
have
a
Linux
zone
or
Windows
only,
and
this
is
like
a
production
ready
way
to
run
your
your
closer
in
the
cloud
or
on-prem
one
of
the
features.
There
are
a
good
sessions
about
this.
C
This
runtime
extensions
cluster
class
and
things
like
that
around
cubecon
this
year,
but
one
of
the
features
that
we
started
to
explore
for
this
project
was
the
usage
of
closer
class
and
runtimes
extensions.
So
you
can
have
like
these
hooks
inside
the
life
cycle
of
your
closer
and
in
the
middle
of
one
of
these
phases
of
her
cluster.
You
can
execute
a
command
or
do
some
operation
called
like
this
web
hooks
that
you
just
created
so
in
the
folder
exp
is
possible
to
explore
one
of
these
systems
that
we
developed.
C
One
of
these
hooks
that
we
develop,
and
this
will
call
solo
boy
as
soon
as
their
control
plane
is
ready.
So
we
are
going
to
control
plan,
gets
ready
and
it
it
will
automatically
run
the
operational
test
for
you.
So
this
is
super
cool
because
you
can
validate
your
new
closers
as
soon
as
they
are
created
with
new
extensions,
a
new
bootstrap
of
of
this
test
at
each
creation.
C
Yeah,
so
to
wrap
up
here,
I
have
some
special
shootouts.
First
is
Jay
files
from
VMware
from
my
team
for
all
the
mentoring
leadership
on
on
all
these
projects
and
and
Sig
Windows
Mark,
Jose
and
James
Stewart,
here
mentoring
and
the
guidance
on
Windows
and
kubernetes.
They
help
us
allotting
all
these
parts
of
the
project
and
understanding
how
Windows
works
on
kubernetes,
aravine,
Claudio,
Lutheran
and
Douglas
for
working
on
new
Windows
features
and
always
ready
to
help
the
community.
C
So
there
are
more
folks
inside
the
secret
windows
and
all
of
them
help
it
to
create
the
cap
to
bring
out
review
and
and
our
outers
of
the
this
cap
as
well
Adelina
in
Bend
the
Elder
for
the
early
discussions
in
this
topic.
They
started
the
conversations.
It
was
a
Delino
that
started
the
thread
and
everything
started
to
to
move
on
and
finally,
Antonio
o'jaya
for
the
networking
we
test
review
and
moving
forward
with
that.
C
Also
how
to
contribute
to
the
project.
So,
if
you
are
interested
in
help
move
Windows
forward
test,
Windows,
that's
super
cool.
That's
there
is
a
lot
of
challenges,
a
lot
of
work
to
do
in
this
area.
So
right
now
we
have
40
percent
of
the
test
is
implemented
on
the
list
that
we
Define
it
in
the
cab
around
of
that
I
hope,
I
open
one
one
ticket
for
each
one
of
the
missing
tests.
If
you
are
interested,
go
ahead
check
the
project,
this
is
the
kubernetes
six
Windows
operational
redness.
C
You
can
get
one
area
that
you
are
interested,
get
Windows
Dev
tools
to
bootstrap
your
first
closer
go
to
wager,
go
to
way
double
s,
go
to
vsphere
and
bring
your
your
closer
that
check
test
your
stuff.
We
are
here
to
help.
You
are
here
to
help
anyone
Newton
board
and
start
to
code
with
us
on
the
project.
Join
us
on
Sig
Windows
kubernetes
is
black
as
well.