►
Description
Join us for a little one-on-one time with a Red Hat Product Manager - each session will feature a Product Manager focused on a specific product or project. We’ll start with an overview & discussion of the topic, then have time for Q&A.
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
episode
of
ask
the
product
manager
today
we're
a
little.
You
know
a
little
different
format.
Today
we
have
some
some
some
fun
fun
windows,
community
operator,
things
to
go
through
and
I'm
gonna
introduce
the
host
of
characters.
I
have
here
in
a
second,
but
some
very
sad
news
happened
in
the
cloud
native
community
over
the
weekend.
The
former
general
director
president.
I
forget
that
is
exactly
dan.
B
A
He
was
leading
up
the
efforts
for
covet
19
response
from
linux
foundation.
He
passed.
A
Weekend
after
some
complications
with
colon
cancer
so
to
dan's
family
and
his
kids,
we
are
very
sorry
for
your
loss.
Our
condolences
go
out
to
you
on
behalf
of
the
cloud
native
community
and
red
hat.
We
are
very
sorry
and
we're
here
to
let
you
know
if
you
need
us
we
are
here.
Please
do
not
hesitate
to
retouch
reach
out
to
me
if
you
need
anything
at
all.
A
With
that
I'd
like
to
introduce
our
bevy
of
guest
today,
anand,
arvind
and
gabriel,
I
said
that
in
the
order
that
it
was
just
in
my
screen,
I'm
not
sure
who
is
speaking
first
but
please
feel
free
to
let's
start
with
an
ond
since
you're
on
my
top
left
feel
free
to
introduce
yourself
tell
us
what
you
do
here
at
red
hat.
Thank
you.
C
Sure,
thanks
good
morning,
everybody,
my
name
is
anand
product
manager.
With
red
hat.
I
work
very
closely
with
gaben
alvin
driving
the
windows
community
windows
operator
to
our
customers.
E
Hi,
I'm
marvin,
I'm
the
team
lead
for
windows
containers
in
the
openshift
arg
and
I
also
lead
the
architectural
work
there
back.
A
C
Yeah,
it
is
chris
and
if
you
remember,
I
think
it
was
sometime
back
in
july
when
we,
you
know,
did
a
demo
of
the
windows
operator,
the
windows
in
ansible,
playbook.
Sorry-
and
we
showed
you
how
you
know
you
could
you
know
bootstrap
a
windows
note
into
an
openshift
cluster.
C
Now
since
then,
you
know
arvind,
gabe
and
the
rest
of
the
engineering
team
have
done
an
awesome
job
and
taking
that
playbook
that
was
built
and
transitioning
that
to
an
operator-based
model
and
the
operator-based
model,
you
know,
lends
itself
a
lot
of
good
things
over
the
playbook
model,
and
you
know
I'll
talk
about
a
lot
of
those
things.
But
what
has
essentially
happened
is
over
those
last
few
months.
You
know,
since
we
did
the
last
windows
demo
is
we
built
out
the
operator,
and
we
have
you
know,
like
everything.
C
Is
red
hat
we've
open
sourced
a
community
version
of
the
operator
for
customers
to
kick
their
tires
with
and
start.
You
know
giving
us
feedback
as
to
how
they
would
like
to
see
the
operator
improve
small
and
server
and
yeah
I
mean,
like
you
said
I
mean
you
know,
for
the
windows
community
who
want
to
get
onto
containers
for
the
kubernetes
community
that
want
to
bring
their
windows
workloads.
I
mean
this,
is
you
know
a
big
deal
right
and
you
know
we've
had
you
know
regular.
C
You
know
requests
from
numerous
customers
over
the
years.
You
know,
windows
server
enjoys
a
huge,
you
know,
presence
in
the
data
center
operating
system
market.
You
know,
applications
like
asp.net,
you
know,
vb.net,
are
you
know
still,
you
know
very
popular
in
a
lot
of
communities
and
we
really
want
to
help
those
communities.
You
know
accelerate
their
adoption.
C
You
know
of
containers
and
bring
you
know
some
of
those
windows
server
applications
to
public
cloud,
and
we
believe
this
operator
will,
you
know,
serve
as
a
essential
bridge.
You
know
from
windows.
Applications
running
on-prem
to
you,
know,
containerized
applications.
You
know
running
in
the
public
cloud
and
yeah.
C
So
we
announced
a
developer
preview
of
this
sometime
in
april
during
the
red
hat
virtual
summit,
and
that
was
like
I
said
you
know,
based
on
a
ansible
playbook
and
the
architecture
was
around.
You
know
letting
you
run
windows
nodes
in
an
openshift
cluster
alongside
regular
rel
and
rel
core
os.
You
know
containers
with
open
shift,
you
know
orchestrating
all
the
building
blocks
and
you
know
serving
as
the
the
universal
control
plane
for
a
hybrid
cluster.
You
know
comprising
of
windows
and
linux
nodes.
C
That
is
right,
and
today
we
are,
you
know,
pleased
to
announce
the
first
community
release
of
the
windows
machine
config
operator,
that
will
let
you
run
windows
server,
workloads
on
openshift
4.6.
C
To
begin
with,
we
are,
you
know,
taking
a
cloud
first
approach
and
this
optical
will
be
available
on
aws
and
azure,
with
support
for
more
platforms.
You
know
coming
in
the
future,
yeah
specifically
things
like
vsphere
and
bare
metal.
A
C
The
next
coming
months
and
chris,
as
you
might
appreciate
you
know,
vsphere,
is
you
know
very
critical.
You
know
platform
for
openshift
customers.
So
again
you
know
we're
working
very
hard
to
make
sure
that
happens
pretty
soon.
A
Absolutely
right,
like
I
think,
vsphere
is
one
of
the
largest
install
bases
we
have
so
making
it
a
priority.
Is
our
priority
but
oftentimes
it's
easier
to
kind
of
spin
things
out
on
the
cloud
providers
than
get
into
the
guts
of
vmware,
because
sometimes
we
have
to
like
work
with
them
together.
So
I'm
curious
how
that's
been
going?
You
know
just
the
whole.
The
whole
process,
like
it's
fascinating
to
me
from
you
know,
stem
to
stern
right,
like
windows
and
linux
containers
living
in
harmony,
cats
and
dogs.
A
C
Yeah-
and
this
is,
you
know,
really
enabled,
because
we
have
a
very
tight
engineering
collaboration
with
microsoft,
so
I
called
it
out
that
this
is
a
solution
that
will
eventually
be
you
know,
jointly
supported
by
red
hat
and
microsoft,
and
you
know
you
know
once
this
gets
on
to
you
know
ga
and
it
gets
into
the
marketplace.
Customers
can
call
red
hat,
and
if
there
is
an
issue
with
you
know,
windows
and
microsoft,
you
know
we
call
microsoft
up,
we
fix
it
for
you
and
then
it
looks
back
to
you
right.
C
So
I
want
to
call
out
a
very
tight
partnership
with
microsoft
in
this
process
and
they
have
been.
You
know,
awesome
partners
in
helping
us.
You
know
get
this,
you
know
delivered
to
customers.
C
You
know,
I'm
gonna,
you
know,
you
know,
pass
the
ball
to
you
and
you
know
show
us
the
most
awesome
demo
from
those
containers.
D
All
right
here
we
go.
Can
everybody
seen
this?
Yes
all
right,
so
this
is
a
open
shift.
Container
platform
cluster
that's
been
set
up
with
ovn
hybrid
enabled
it
is
the
minimum
requirements
is
a
four
six
cluster.
With
this
functionality
enabled
once
this
functionality
is
enabled
the
ability
to
bring
the
operator
in
is
as
simple
as
going
to
the
operator
hub
and
typing
in
windows.
D
I've
currently
already
installed
this
on
the
system,
but,
as
you
can
see,
we
highlight
out
specifically
what
the
prerequisites
are
and
some
of
the
more
detailed
information
on
how
to
do
the
initial
setup.
One
of
the
key
usages
is
that
the
operator
creates
its
own
generic
cloud,
private
key
to
be
able
to
ssh
into
the
windows
notes
and
do
its
configuration
of
them.
D
This
information
is
here
it's
also
in
the
blog
that
I
think
was
posted
in
chat,
and
it's
all
linked
from
the
windows
machine,
machine,
config
operator,
github
space
as
well.
We
give
examples
of
machine
sets,
so
we
are
using
machine
sets
for
both
aws
azure
and
our
future
platforms
to
roll
and
deploy
new
machines.
D
We
can
do
is
we
can
go
into
a
workload.
Actually,
let's
go
down
to
compute
and
let's
look
at
a
machine
set.
I've
enabled
a
machine
set
here
and
have
already
enabled
two
windows
machines
on
as
part
of
this
machine
set.
This
is
a
very
similar
yaml
set
that
you
would
find
for
other
machine
sets.
It
highlights
out
a
few
specific
things
that
are
called
out
easily
in
the
documentation
but
in
essence,
we're
pointing
to
our
our
windows,
image
that
needs
to
have
containers
and
docker
enabled
on
it.
D
Both
azure
and
aws
provide
these,
and
so
those
machine
sets
are
part
of
the
examples.
As
far
as
those
are
concerned,
you
can
see
once
working
with
a
machine
set
though
say,
for
instance,
you
wanted
three
nodes
instead
of
two.
We
can
actually
do
this
and
we
will
see
we
start
provisioning.
Another
third
windows
working
node,
oh
snap,
so
as
this
is
sweet
yeah,
this
is
the
part
that
is
is
a
little
slow
here.
So
I'm
going
to
kind
of
diverge
in
the
demo
and
then
come.
D
Yeah
yeah
yeah,
okay,
so
exactly
so,
this
part
will
cook
and
as
it
cooks,
what
is
happening
in
the
in
the
back
end
is:
is
our
operator
which
windows
machine
config
operator
is
actually
it's
running
on
the
linux
based
nodes
and
it
is
actually
looking
for
those
windows
machines
to
come
up
as
they
come
up.
It
will
reach
in
and
do
configuration
on
those
devices
as
as
they
become
configured
now
because
of
the
initial
startup
time
and
configuration
of
some
of
the
windows
nodes.
D
It
does
take
a
little
bit
of
time,
so
we
will
let
that
bake
as
it
goes
on.
But,
as
you
can
see,
initial
consistency
gave
us
our
current
two
windows
worker
notes
that
we
can
work
off
of
right
now
for
a
small
demo,
I
used
a
work
deployment.
I
created
its
own
namespace
for
it,
which
was
the
windows
workload,
and
this
is
just
a
very
simple
powershell
based
web
url,
so
it
returns
html
back
based
upon
connecting
to
it.
As
you
can
see.
D
Currently
we
have
one
pod,
that's
up
and
running
but
say
for
instance,
you
want
to
go
from
one
to
say
six.
We
can
scale
up
the
six
as
these
get
deployed
out.
We
will
see
that
they
then
get
deployed
onto
the
two
existing
windows
nodes
that
are
currently
ready
for
scheduling
and
deployment,
and
they
will
come
up
and
their
their
time
as
well,
so
we've
got
three
of
them
now
and
now
we
have.
A
D
So
those
all
come
up
and
if
we
want
to
switch
over
to
more
of
the
developers
perspective
on
this,
we
can
see
that
we've
created
a
windows
web
service
that
points
to
this
and
I've
got
a
load
balancer
here
that
I
can
go
to,
and
I
can
now
reach
my
web
service
that
is
running
on
those
six
spots
on
the
windows.
Very
nice.
A
Can
you
have
windows
and
linux
workloads
in
the
same
project?
I'm
assuming
yes,
because
they're
just
pods
at
that
point,
correct,
yeah,
okay
and
then
bare
metal
support
coming,
hopefully,
first
half
of
2021.
A
C
I
can
talk
through
some
of
this
so,
like
I
said
you
know
initially,
we
are
going
to
ga
with
the
cloud
first
approach,
which
means
try
this
on
aws
azure,
you
know,
will
get
their
hands
we'll.
You
know
we'll
get
their
hands
dirty.
You
know
first
followed
by
vsphere
vsphere
again,
you
know
like
we
spoke,
you
know
of
our
install
base.
That's
probably
the
most.
You
know
dominant
platform
on
which
you
know,
customers
try
openshift
and
the
other
angle
is
you
know
it
also
enjoys
a
huge.
C
A
C
Right
so,
given
you
know
it
enjoys
such
a
dominant,
you
know
presence
in
that
market
as
well.
So
that
is
the
number
one.
You
know
platform
of
choice.
You
know
after
vga.
C
A
And
that's
kind
of
a
bear
in
and
of
itself.
I
feel
like
as
the
definition
of
bare
metal
kind
of
feels,
like
it's
morphed
over
the
ears
say
what
you
want
like
bare
metal
virtualized
bare
metal
on
demand
is
the
thing
right,
like
so
bare
metal
question
mark
when
you
say
bare
metal.
What
exactly
do
you
mean
like
spinning
up
windows
hosts
on
you
know
actual
like
iron
and
then
incorporating
those
into
your
node
or
some
quasi
definition
of
that.
C
C
C
You
know
all
these
platforms,
because
there
can
be
things
where
let's
say,
logging
driver
is
not
supported
on
windows
or,
let's
say
a
storage
solution.
Doesn't
work
on.
You
know
alibaba
cloud
right
so
that.
B
C
Be
you
could
run
into
some
flavor
of
an
untested
path?
That
might
you
know,
make
the
solution
not
that
appealing
to
you,
so
I
would
say:
wait
till
we.
You
know
test
and
certify
some
of
these
things,
and
then
you
can
go.
You
know
play
around
with
this
as
much
as
you
like.
A
Yeah
and
the
whole
I
mean
you
can
go
to
tride.openshift.org
openshift.com,
try,
sorry
try.openshift.com
also
works,
and
you
can
kick
the
tires
on
these
platforms.
You
know
relatively
quickly
and
easily
and
kind
kind
of
cheaply.
I
feel
like
to
an
extent
right
like
if
you
really
want
to
kick
the
tires
on
the
the
windows
machine,
config
operator
right
now,
and
you
know
thinking
in
the
future,
you
could
totally
take
it.
A
I
would
encourage
folks
to
do
that
if
they're,
looking
at
seriously
considering
doing
this
in
the
future
right
like
there
is
some
testing
that
kind
of
needs
to
happen
like
to
get
yourself
familiar
with
it,
but
definitely
don't
take
this
as
like
concrete
guidance,
as
this
exact
same
experience,
you're
going
to
get
in
vsphere
because
there'll
be
differences,
correct.
C
So
one
other
thing
I
want
to
point
out
is
as
you're
spinning
up
the
4.6
cluster.
There
is
a
hard
requirement
on
ovn
hybrid.
C
The
cluster
needs
to
be
set
up
with
ob
and
hybrid
for
the
solution
to
work.
Okay,
so
you
know
remember
that
as
you're
spinning
up
the
cluster,
you
know
set
it
up
with
ob
hybrid
and
for
instructions
of
doing
that
we
will,
you
know,
send
you
links
to
our
docs
and
our
blogs
at
the
end
of
this
twitch
session,
but.
A
So
this
is
awesome
and
groundbreaking
and
all
kind
of
like
happening
all
at
once.
Right
like
the
what
are
some
of
the.
What
is
the
demand
from
customers
like?
What
are
we
seeing
as
far
as
like
this
is
use
cases
that
they
want
to
do
right?
Like
I
get
it,
they
have
a
lot
of
windows
install
base
and
they
want
to
utilize
that.
But
what
is
the
use
case
here
right
like
running
dot
net
apps
in
openshift
running
full-blown?
A
C
Yeah
we
do
get
a
lot
of.
You
know:
customers
interested
in
the
solution,
specifically
from
healthcare
and
manufacturing,
where
there
is
a
huge
you
know,
windows
presence.
So
I
can
give
you
a
couple
of
examples
from
the
healthcare
industry
right
they
want
to
run.
You
know,
back-end,
you
know,
windows
applications.
You
know
back-end
web
applications.
So
if
there
is
a
you
know,
provider
or
a
you
know:
patient
who's
logging
into
a
website.
You
know
that's
probably
written
in
asp.net,
and
so
they
need
a
login
page.
C
That's
you
know
running
on
windows
containers
and
that
login
page
needs
to
authenticate
with
something
like
you
know,
group
managed
service
accounts
in
windows
for
doing
you
know,
or
the
authentication
authorization
of
the
account.
So
essentially
you
know
web
applications
back-end
applications.
Is
you
know?
What
is
you
know
often
requested
for
by
customers?
C
C
So
at
this
time
your
customers
are
really
you
know
what
should
I
say,
very
eager
to
lay
their
hands
on
any
solution
that
will
help
them.
Take
them
from
you
know:
a
legacy
windows,
application
running
on-prem
to
a
more
modern
application,
that's
containerized
and
running
in
the
public
cloud,
and
they
need
that.
You
know
that
essential
bridge
to
go
from
a
to
b
right
and
those
you
know.
C
Playable
applications
in,
like
I
said,
includes
web
applications,
applications
that
need
authentication
with
external
gnsa
backend
applications,
bad
jobs,
not
even
windows,
web
server
applications.
So
these
are
you
know
some
of
the
combination
of
applications
that
we
hear
that
they
are.
You
know
highly
interested
in
running.
A
Yeah
so
there's
a
question
in
chat
here
and
I
kind
of
responded
to
it.
Will
red
hat
share
a
comparison
table
between
windows,
containers
and
linux
containers
in
the
future,
and
my
response
is
kind
of
like
they're
all
oci
compliant,
so
there
isn't
that
big
of
a
difference,
but
what
you
can
actually
do
with
windows
and
for
essentially
there's
a
hard
requirement
on
docker
right
now,
I'm
assuming
so
like
sky
is
kind
of
the
limit
there.
A
I
feel
like
right
like
if
you
can
run
it
on
windows
in
your
docker
hosts
like
locally.
It
will
probably
run
on
your
server
okay,
you
know
assuming
you've
applied
the
right
security
practices
and
so
forth.
So
on.
You
can
almost
just
point
your
cicd
pipeline
over
to
the
ocp
cluster
running
those
windows
hosts,
as
opposed
to
the
current
host
you're,
pointing
at
right
so
replicate
that
environment
inside
openshift
and
you
can
kind
of
just
kick
the
tires
and
light
the
fire
is
right
there
right,
there's
not
much,
there's
not
much
difference.
C
Yeah
there
is
not
much
of
a
difference
in
the
sense
that,
like
you
said
you
know,
openshift
with
windows,
is
you
know
yet
another
deployment
target?
For
you
know
customers,
and
you
know
they
can
point
their
cd
pipelines.
You
know
once
they
build
their
app
and
visual
studios
and
studio
code.
They
can
take
it
through
any
supply
chain.
They
want,
you
know,
push
any
registry
of
their
choice.
You
know
bring
it
down
to
an
openshift
cluster
with
windows,
notes
and
you
know,
run
things
so
from
that
sense,
the
supply
chain.
C
You
know,
anatomy,
isn't
really.
You
know
too
different
from
a
linux
in
our
supply
chain.
Right
right.
But
but
you
know
the
thing
is
you
know
the
linux
supply
chain
is
way
more.
You
know
advanced
with
so
much
of
other
contribution
from
other
you
know,
vendors
and
other.
You
know
startups
and
other
players-
and
you
know
windows
containers
is,
you
know,
still
catching
up
to
a
lot
of
those
things.
Right,
read
and
storage,
read
and
monitoring.
Even
logging
beat
and
tracing
be
it.
A
C
These
are
things
that
just
you
know,
work
so
seamlessly
on
the
linux
side,
but
for
these
kind
of
things
to
come
on
the
windows
side,
it
is
going
to
take
time
right,
and
all
of
this
is
going
to.
You
know,
require
work
not
just
from
red
hat,
but
for
the
the
larger
upstream
community
come
collaborate
and
you
know
get
some
of
these
things
out
of
the
way.
So,
yes,
it
is
the
journey.
The
containerization
is
similar,
but
the
linux
ecosystem
is.
A
It's
almost
like
a
flywheel
right
like
the
linux
wheel,
has
started
and
stops
and
or
not
started
to
stop,
but
it
started
and
going
and
now
the
windows
wheel
has
started
and
going
and
it
there
will
be
progressions
and
you
know,
logging,
and
that
cloud
native,
like
landscape
for
windows,
has
to
kind
of
spread
its
wings
as
well
right
like
if
you
go
to
l.c
and
cf.I
o
right
now.
A
It's
this
huge
smattering
of
all
these
tools
that
you
can
use
for
any
various
function,
but
I
like
to
say:
go
to
the
cloud
native
trail
map
and
look
at
that
and
say:
okay,
do
these
things
work
in
your
windows,
environment
right
like
will
prometheus,
and
you
know
all
your
alerting
and
everything.
Logging
wise,
still
work
with
windows
host
and
sometimes
that
answers.
No.
A
You
know
right
like
you
might
have
something
that
requires,
or
is
you
know,
proprietary
to
windows,
environments
that
you're
using
currently-
and
you
know
you
might
have
to
enable
some
kind
of
connector
there
or
you
know
to
give
you
an
idea
like
I
don't.
I
don't
have
any
ideas
around
like
windows.
Containers
inside
service
meshes
right,
like
I
haven't,
even
thought
about
that
yet
or
or
or
the
serverless
side
of
it
with
k-native
right
like
I
haven't
even
gone
down
that
road.
A
That
far,
which
kind
of
brings
a
good
question
that
matt
asked
in
chat
here.
Is
there
something
that
is
clearly
not
recommended
at
the
moment
to
do
with
windows?
Containers
right,
like
don't,
do
this
with
windows
containers
right
now
it
just
won't
work.
C
Yeah,
I
would
say,
be
very
cautious
if
you're
trying
to
run
this
on
vsphere
a
lot
of
gotchas-
and
you
know,
arvind
and
gabe-
are
working
very
hard
with
microsoft,
with
vmware
to
get
in
a
lot
of
these
issues
fixed.
So
that
is
a
work
in
progress
and
that
story
will
get
better
and
you
know
trust
us
when
we
say
you
know
we
will.
You
know,
support,
and
you
know
fully
test
the
solution
before
we
go
ga.
C
So
I
would
say
that
is
the
path
of
say,
most
interest
and
a
few
you
know
gotchas
or
you
know,
landmines
along
the
way
that
we're
trying
to
resolve.
So
I
would
say
that
is
the
you
know
thing
that
you
got
to
be
most
cautious
about,
but
every
other
thing,
like
you
know,
setting
up
like
you
know,
networking
into
the
windows
notes.
You
know,
windows,
notes
talking
to
linux,
nodes
windows,
notes
talking
to
other
windows
notes,
so
all
kinds
of
ingress,
egress,
east
west.
C
Not
so
those
things
you
know
should
be
working
so
so
go
ahead
and
you
know
play
with
those
kind
of
things
when
it
comes
to
new
platform.
Support
like
vmware
or
bare
metal,
I
would
say
that's
the
path.
That's
that's
got
a
lot
of
uncertainties
right
now,
right.
D
I
was
just
going
to
hop
in
and
say
that
you're
also
going
to
see
from
our
team
of
a
consistent
release
into
the
community
operator
showing
new
functionality
regularly,
so
we
we
will
be
regularly
updating
it.
My
guess
would
be
about
once
a
month
with
functionality
that
will
be
coming
in
the
future
to
the
ga
version.
So
if
you
want
an
early
insight
and
to
really
you
know,
kick
the
tires
so
to
speak
as
it's
coming
down
the
road.
That
is
definitely
the
place
to
do
that.
A
Awesome,
where
would
be
the
best
place
to
get
updates
on
that
blog,
the
repo,
probably
both
yeah,
okay
cool?
I
will
replace
those
for
everybody
if
they
missed
that
earlier,
go
to
our
blog,
openshift.com,
blog
and
that'll.
A
Take
you
just
just
subscribe
to
it
if
you're
an
openshift
user
just
subscribe
to
that
blog
right
like
there's,
there's
no
better
blog
for
you
to
subscribe
to
than
that
one,
and
then
the
machine
config
operator,
github
repo,
where
you
can
watch
for
releases
and
just
you
can
watch
everything
if
you
want
right
like
you,
can
monitor.
A
Makes
being
creepy
in
code
very
easy,
you
can
watch
all
the
ones
and
zeros
change
if
you
want
so
there's
a
github
repo
for
everybody.
A
What
last
week
last
monday,
I
feel
like
last
tuesday
or
something
so.
What
have
you
seen
in
the
past
week
as
far
as
like?
Oh
didn't,
think
about
that
or
you
know
something
new
that
after
you
know
the
announcement
of
it
anything
of
interest
come
across
your
desk.
Lately.
C
Yeah
before
that,
chris
one
other
thing
I
want
to
point
out
in
terms
of
staying,
you
know
in
tune
with
updates
on
our
site.
Is
there
is
a
mailing
list?
Openshift
hyphen
windows,
redhat.com,
oh
cool,
feel
free
to
subscribe
to
that
mailing
list.
We
will
be
sending
you
periodic.
You
know
regular
updates
through
their
mailing
list.
You
know
new
content,
new
videos,
new
updates
to
the
community
operator,
and
you
know
so
on
and
so
forth.
So
that's
another
channel
where
you
can
go
get
updates.
Besides
the
blog
and
the
github
marketplace,.
C
And
yeah
to
back
your
question
in
terms
of
what
kind
of
interest
we
are
receiving,
I
think
it's,
you
know
a
lot
of
the
things
that
we've
talked
about
right
support
for
new
platforms
like
you.
C
Bare
metal,
you
know,
ibm
z,
ibmp,
believe
it
or
not.
You
know,
hosted
offerings
like
a
lot
of
customers.
You
know
came
to
us
and
said
hey.
This
is
support
on
azure.
Is
this
going
to
be
supported
on
you
know,
azure
red
hat,
open
shift
right.
A
C
Yeah
azure,
red
hat,
open
shift
or
aro
you
know
is
the
acronym,
for
it
is
the
hosted
and
the
fully
managed
version
of
open
share
from
azure
a
lot
of
customers
like
it
because
it's
you
know
fully
autonomous.
You
know
version
of
openshift
on
azure
and
a
lot
of
our
hybrid
cloud
customers.
You
know
really
lap
it
up
right
and
we've
had
a
lot
of
customers
who
have
come
and
asked
us
hey,
you're
supporting
this
in
azure.
Does
it
mean
it
will
work
on?
C
You
know
azure
ad,
open
ship
right,
and
that
is
a
great
question
and
I
think
the
answer
is
yes,
but
that's
something
that
again,
you
know
we
have
not
tested.
We
have
not
validated,
we
have
not
supported.
C
So
if
you
want
to
go
ahead
and
you
know
take
it
for
a
test
drive,
I'm
cautiously
optimistic
that
things
could
work,
but
you
know
things
may
break
as
well,
but
again
again
in
terms
of
the
hosted
offerings
next
year.
You
know
I
think
azure
red
hat
openshift
is
going
to
be,
I
would
say
the
most,
if
not
the
most
topical,
hosted
platform
that
we
want
to
add
support
for.
A
Awesome,
so
what
is
the
key
reason
to
use
the
ovn
cni?
If
a
customer
chooses
a
third-party
cni
like
aci?
Is
there
anything
they
should
consider?
That's
this
is
coming
in
from
chat
so
take
that
with
a
grain
of
salt,
in
the
sense
that
like
what
are
the
network
requirements
for
windows
boxes
here
like,
why
is
there
this
requirement.
C
A
C
Having
said
that,
you
know,
technically
things
should
work
with
the
calico
framework.
That's
you
know
another
option,
but
again
the
does
not
use
calico.
There
is
a
blog
out
there
that
shows
how
to
set
up
a
openshift
cluster
with
calico
for
windows,
and
I
can
point
you
to
that
blog.
There
was
even
a
recording
by
the
tiger
guys
on
this
topic,
but
again,
that's
not
something
we
support
through
the
operator.
That's
just
another
option.
C
E
Yeah,
so
mainly
what
what's
happening
behind
the
scenes?
Is
that
not
only
are
we
using
ov
and
hybrid,
where
we're
setting
up
this
hybrid
option
for
ovn
kubernetes
itself,
where
part
of
the
network
is
actually
carved
out
for
most
of
the
windows,
node
and
windows,
pod
communication-
and
that's
again
like
anand
mentioned,
is,
is
what
rsdn
team
when
working
with
microsoft
came
up
with,
so
the
operator
is
sort
of
opinionated
about
about
that.
It
knows
that
if
it's
a
ovn
kubernetes
cluster
with
hybrid
networking,
it
knows
what
to
do
on
the
windows
node.
E
So
our
plan
is
to
keep
adding
more
and
more
networking
third-party
networking
support
as
and
when
you
know,
customer
demand
asks
for
it.
So,
for
example,
like
anand
was
mentioning.
Caligo
might
be
the
next
argument
so
that
the
operator
can
detect.
Oh
okay,
I'm
on
a
cluster,
that's
using
caligo,
and
this
is
what
I
need
to
configure
on
the
windows
node
to
get
it
working
with
the
calico
networking.
A
And
I
think
the
the
biggest
thing
to
consider
is
that,
like
cloud
native
infrastructure
in
general
is
like
picking
from
the
things
that
work
best
for
you
so
yeah
whenever
these
hard
requirements
exist,
it's
usually
because
right
like
this,
is
the
happy
path.
A
First,
you
know
and
then
then
we
add
on
as
we
go
and
start
bolting
on
other
bits
and
pieces,
because
we
do
understand
that
people
are
like
making
decisions
around
their
cni's
for
various
reasons:
policy
security,
whatever
it
may
be-
and
you
know
adding
more
to
that-
I
think,
is
very
important
here,
because
there
will
be
these
bespoke
use.
Cases
of
I
want
to
use
calico
and
windows,
and
you
know
everything
else
that
comes
along
with
that.
C
Yeah
I'll,
let
gabe
you
know,
handle
some
of
these
things
but
gabe.
Maybe
we
speak
about.
You
know
the
monitoring
piece
since
you
know
prometheus,
you
know
was
mentioned
saying.
D
Yeah,
so
that's
one
that
we're
really
excited
about
we're,
really
hoping
to
pull
it
in
for
rga,
but
at
this
point
it's
not
slated
for
that,
but
you
should
see
it
in
the
community
operator
shortly.
What
we're
doing
is
we've
run
a
windows
exporter
service
on
the
windows
machine
to
export
metrics,
in
the
way
that
you
know,
you'd
be
able
to
use
with
prometheus
and
grafana
to
draw
your
your
dashboards
and
see
all
of
those
within
the
actual
cluster
metrics
themselves,
so
we're
in
the
process
of
moving
that
forward.
D
A
And
what
kind
of
problems
did
you
have
with
prometheus?
I
guess
you
know
just
being
curious
in
general
right
and
a
prometheus
user
right
like
what
differences
are
there
I
mean.
Obviously
I
know
the
difference
between
windows
and
linux,
but
from
a
prometheus
perspective
I
mean
getting
that
exporter
running.
How
hard
was
that.
D
There
are
some
subtleties,
you
know
the
way
that
windows
and
linux
reports,
like
the
emphasis
metrics
so
to
speak,
is
sometimes
slightly
off.
What
is
a
core
on
this
version
versus
a
thread
on
that
version
so
on
and
so
forth
got
it
so
we
had.
We
had
to
work
through
a
lot
of
those
networking
tools,
a
similar
constraint,
they're
yeah
you're,
not
they're,
not
apples
to
apples
comparisons.
It's
definitely
an
apples
to
orange
and
we're
trying
to
find
the
happy
path
down.
The
middle.
A
D
so
yeah,
like
those
kind
of
bring
up
there,
was
a
rumor
a
few
weeks
ago
that,
like
windows,
was
gonna
rebase
on
linux
or
something
right,
but
it
it
does
make
you
wonder
that
like
would
that
just
be
easier
at
this
point
right,
like
I
don't
know,
I
don't
know,
there's
such
a
massive
windows
install
base,
I
don't
think
that'll
ever
happen,
but
like
the
the
idea
of
like
a
consistent
standard
for
like
systems,
metrics
reporting,
like
I
feel
like
that,
is
like
needed
almost
to
an
extent.
You
know,
I'm
I'm.
A
Because
there's
so
many
metrics
to
pull
and
and
everybody
cares
about
golden
signals-
there's
all
kinds
of
things
to
watch
out
for
in
the
sre
world
right
like
to
keep
an
eye
on
and
and
like
getting
those
consistent
right.
Like
that's
hard,
that's
very
hard
in
the
in
a
you
know,
kind
of
a
multi-os
environment,
even
when
it
is
like
multiple
different
versions
of
linux.
Yes,
it
is
still
the
linux
kernel
and
those
stats
are
easy
to
get,
but
sometimes
there's
subtle
differences
even
in
the
performance
of
applications
between
you
know,
cloud
vendors
right.
B
A
On
top
of
what
your
you
know,
your
hardware
is
at
that
point
and
your
hardware
is
virtualized.
It
makes
it
even
more
interesting
right
so
yeah,
there's
various
subtleties
that
you
have
to
look
out
for
everywhere.
You
go,
I
feel
like,
and
adding
the
windows
part
to
the
mix
makes
it
even
more
muddied
waters
right,
like
does
this
threat
actually
mean
like
a
whole
processor
is
being
taken,
or
does
it
mean
something
different
right
like.
D
So
those
are
the
things
that
we
really
hope
to.
You
know
identify
and
work
with
the
customers.
I
I'm
really
excited
to
work
with
the
community
on
this.
You
know.
B
D
Please
open
up
issues
on
github
like
give
us
feedback
point
us
to.
You
know
improving
everything
as
a
whole.
As
a
group,
I
think
we
can
push
the
community
to
find
something.
That's
a
little
more
standardized
in
the
process.
A
Yeah,
I
would
like
to
see
just
metrics
reporting
in
general,
get
a
little
bit
more
standardized
right
like
prometheus
drove
the
cloud
native
world.
That
way,
I
feel
like.
I
almost
hope
that
there's,
like
some,
you
know
industry-wide
initiative
to
kind
of
make
you
know
like
when
I
open
top.
I
understand
what
I'm
seeing
when
I
open.
A
You
know:
windows
systems
manager
monitor
whatever
it's
called
like.
I
understand
what
I'm
seeing
but
they're,
not
one-to-one
at
all
and
then
like
having
to
compare
the
two
right
like
does
this
linux
application
perform
better
on
our
windows
nodes?
Who
knows
right,
like
the
internet.
D
That's
what
I
think
we're
gonna
get
it
pans
out
yeah
as
we
as
we
said.
As
you
said
earlier,
you
know
right
now
we're
attacking
the
happy
path,
but
as
we
diverge
from
that,
I'm
really
interested
to
see
like
you
know
where
some
of
that
stuff
goes
so
arvin.
I
don't
know
if
you
have
anything,
you
want
to
weigh
in
that
you're
excited
about
too.
E
Yeah,
I
think
what
I'm
really
excited
about
is
getting
vmware
vsphere
ipi
support.
Enabled
at
this
point
that's
what
I'm
really
looking
forward
to
there's
a
lot.
B
A
Yeah,
I
think,
vmware
being
such
a
large
install
base
of
openshift
and
red
hat
in
general.
Right
like
that
next
checkbox,
I
think,
will
be
the
most
fun
part.
What
are
the
like?
The
biggest
challenges
jump
like
making
that
leap
from
the
cloud
vendors
to
vmware
like
what
are
the
kind
of
gotchas
here
right
now
that
you're
sort
of
working
through
that
you
can
talk
about.
E
There
were
not
that
many
huge
gotchas
I
would,
I
would
say
we
did
run
into
some
issues
with
a
a
bug
with
vm
tools
that
you
know
was
already
fixed
by
vmware,
but
was.
A
B
E
E
Are
just
one
or
two
steps
that
we're
doing
different,
interesting
vmware.
E
D
There's
also
some
work
that
needs
to
be
done
on
a
golden
image
ahead
of
time
to
where,
when
you're
working
in
the
cloud
environment
such
as
aws
and
azure
that
we've
facilitated,
you
know,
though
those
images
are
all
prepared
and
ready
for
you,
yeah
they're,
getting
baked
and
tested,
and
vmware
you're
going
to
need
to.
You
know,
configure
your
golden
template
in
essence,
and
you
know
and
use
that
for
your
cloned
images.
D
A
Right
yeah,
like
I
mean
for
my
windows
days,
right,
like
the
idea
of
or
not
windows
days,
were
from
my
operational
days
right,
like
the
idea
of
a
windows
golden
image,
like
scares
me
a
little
right,
because
I
know
how
quickly
those
things
can
get
at
a
date
right
like
so
having
that
golden
image
kind
of,
like
with
some
strong
suggestions
around
automating.
The
production
of
that
golden
image
I
feel,
like
is
vitally
important.
A
C
Yeah
one
more
thing
I
would
like
to
point
out
on
the
v-strip
side
is
the
support,
for
you
know:
persistent
storage.
So
far,
you
know
we
have
entry
volumes.
You
know,
that's
like
a
separated.
You
know
persistent
storage
solution
vsphere,
but
the
upstream
community
is
in
the
process
of
you,
know,
moving
csi
proxy,
which
is
an
alpha
right
now
to
ga
1.20,
which
should
happen
by
the
end
of
this
year.
Yep
once
dga
the
csi
proxy
in
cube,
we
will
get
added.
We.
B
C
Get
you
know,
support
for
you
know
the
csi.
You
know
proxy
support
right,
which
includes
things
like
you
know,
snapshotting,
you
know
provisioning
visioning
and
all
the
goodness
that
csi
brings
should
be
once
that
gs.
Csi
procedure.
That's
you
know
another.
You
know
I
would
say
goodie
we're
waiting
for
from
upstream
before
we
you
know,
can
harden
the
solution.
A
You
know
all
these
people,
or
you
know
all
these
different
organizations
that
have
their
own
priorities
and
their
own
kind
of,
like
you
know,
kpis
for,
like
a
better
term
okrs
and
kpis
we're
all
kind
of
moving
at
speed
in
our
own
directions
and
we're
all
kind
of
hammering
on
the
same
pieces
of
wood
right
like
we're
all
working
on
these
things
together
and
it's
it's.
It
is
a
lot
to
bring
together
just
a
kubernetes
release.
A
I
need
windows,
gpu
node
right
and
we're
going
to
be
like
all
right
here.
You
go.
You
know,
because
we
will
have
done
all
this
work
in
the
past
and
we
can
kind
of
glue
it
together
in
the
future.
Now
right,
like
it's,
it's
kind
of
amazing
how
I
feel
like
that's
going
to
come
to
light
eventually
someday.
A
There
will
be
like
this
massive
gpu
instance
of
windows
boxes,
doing
modeling
for
something
who
knows,
but
because
it
was
written
for
windows
and
it's
running
on
openshift
now,
because
of
all
this
work,
you
guys
are
doing
so,
I'm
very
very
happy
to
even
think
that
that's
a
possibility
right,
let
alone
right
like
to
be
sitting
where
we
are
with
the
ability
to
add
windows,
notes
to
ocp
or
openshift
in
general
is
just
amazing
to
me.
Yes,
you're.
D
Absolutely
right
about
the
complexity,
it
kind
of
goes
back
to
that
earlier
statement.
You
had
said
about
the
flywheel
and,
like
you
know,
we've
we've
gotten
a
lot
of
the
complexity
together
and
we've
started
to
get
them
the
wheel
of
momentum,
but
you
know
I
would
I
would
keep.
I
would
beg
everybody
to
remember
that
this
is
the
beginning
of
this
journey,
yes,
and
that
we
will
be
adding
lots
of
things
as
we
go
along.
A
And
I
would
imagine
it
would
come
at
a
very
rapid
clip
right,
like
you're
not
going
to
be
arrested
on
your
laurels.
I
don't
think
no,
no
awesome,
chat's
pretty
quiet
right
now.
Any
other
questions
from
the
audience
want
to
give
everybody
a
moment
to
fire
them
off
before
you
know
anybody
before
I
ask
if
there's
any
final
thoughts
or
anything
right
like
I
feel
like
we
got
everything
covered.
Thank
you
both
arvind
and
anand.
So
much
for
chiming
in
thank
you
matt
for
the
the
not
recommended
question
at
this
moment.
A
That's
that
was
kind
of
nice
to
never
thought
about.
You
know
what
shouldn't
you
do
with
this
tool.
It's
always
good
to
know
there
any
other
links
or
anything
that
I
need
to
share
with
folks.
I
got
the
blog
post
from
last
week.
I
got
the
repo
you
did
the
tiger
thing.
Oh,
you
got
a
slide
for
the
road
map.
That's
right!
Yes,
let's
share
that
real
quick.
C
I
just
wanted
to
you
know,
point
out
a
couple
of
you
know
things.
Let
me
see
if
I
can
go
full
string
on
this.
Yes,
okay,
most
of
these
questions,
in
terms
of
you
know
what
platforms
you're
going
to
be
supporting
in
the
near
term
in
the
long
term.
So
obviously
you
know
vsphere
is
a
big
one
for
us
in
the
midterm,
which
is
you
know,
I
would
say,
six
to
nine
months,
openshift
you
know
and
beyond.
C
We
want
to
have
you
know
more
environments
like
you
know,
openstack,
maybe
you
know
bare
metal
and
things
like
that,
and
you
know,
as
we
spoke
about,
we
want
to
have
a
more
hardened
solution
for
storage,
monitoring,
logging
and
so
on
and
so
forth.
C
Support
for
things
like
gmsa
right
again,
healthcare
industry
gms
is,
you
know
very
they
want
to,
like.
You
know,
authenticate
their
windows,
application
with
things
like
microsoft,
ide
or
with
octagon
those
kind
of
things
right.
We
want
to
get
some
samples
for
gmsa
and
then
in
the
long
term.
Obviously,
we
want
to
support
more
hosted
platforms
like
aro
azure,
openshift
amazon
laid
out
openshift
openshift
dedicated,
and
then
you
know
we
really
haven't
spent
much
time
on
the
developer
journey
right.
C
So
far,
gabe
and
irwin
have
you
know,
been
really
doing
an
awesome
job
of
building
a
really
secure,
hotend
cluster.
But
at
some
point
we
need
to
start
talking
about
the
developer
journey.
How
are
you
know
developers
making
apps?
How
are
they
going
to
connect
it
to
a
build
pipeline?
Is
that
going
to
be
techton
or
a
third-party
like
octopus,
ci
cd
or
you
know,
azure
devops,
you
know
whatever
it
is
right
and
how
are
they
going
to
deliver
the
app
through
the
supply
chain?
C
You
know
on
the
openshift
deployment
target,
so
we
need
to
talk
through
those
journeys
and
what
we
can
do
to
improve
the
developer.
Experience
for
that
part
of
the
process-
and
you
know
we
again-
we
spoke
about
things
like
k-native
and
service
mesh.
But
again
those
are
you
know
things
in
the
far
horizon.
You
know
good,
not
stars
that
we
want
to
shoot
towards,
but
that's
going
to
take
a
lot
of
time.
C
You
know
by
the
time
we
get
to
k
native
and
service
match
and
again,
a
lot
of
that
is
going
to
be
driven
by
customer
demand
and
just
want
to.
You
know
really
point
out
that
this
is
evolving
priorities
and,
as
we
launch
this
to
the
marketplace,
as
you
know,
customers
give
us
feedback.
We
will
be
prioritizing
based
on
where
the
demand
is
and
where
customers
you
know
specifically
ask
us
to
go.
So
that's
how
we'll
be
you
know
prioritizing.
You
know
the
roadmap
as
we
go
forward.
C
We
get
more
customer
feedback
and
it's
kind
of
like
this.
You
know
auto
collecting
google
search
right
and
it
gives
you
more
efficient
search
results.
So
that's
our
product
roadmap
and.
B
A
Yeah
the
feedback
loop
is
vitally
important
right
like
if
we're
going
in
the
right
direction,
that's
great,
but
we
need
feedback
and
if
it
is
the
right
direction,
but
there's
little
tweaks
we
can
make.
Let
us
know
question
we
don't
support
on
red
hat
virtualization.
C
Of
my
head,
that
is
a
good
question.
We
do
not
supported
virtualization
and
I'm
sorry
if
it's
not
one
of
those
items
here,
but
it
is
definitely
an
item
on
our
roadmap,
because
customers
have
asked
us
for
support
on
rhv.
So
that
is
that's
a
very
legit.
Ask.
A
Yeah,
okay,
cool
awesome,
trying
to
think
what
else
platform
wise
right
like
could
I
run
so?
Here's
off
the
wall
question.
Could
I
run
openshift
virtualization
windows,
nodes
and
use.
A
Operator,
maybe
maybe
not
that's
a
good
question.
A
C
All
you
know
scheduled
managed
by
the
same
ocp
control
plan
right
you
can
get
traffic
from
one
to
the
other.
You
can
get
traffic
into
the
cluster.
You
know
out
of
the
cluster.
So
all
these
three
different
elements,
which
is
linux,
containers,
windows,
containers
and
you
know,
windows.
Virtual
machines
can
be
a
part
of
the
same.
You
know:
cluster
beautiful,
okay,
cool.
A
Awesome
thank
you
that
that
was
just
a
question
that
popped
in
my
head.
I
didn't
even
think
about
that
before
the
show
came
on,
but
yeah.
That's
awesome
that
we're
doing
that
see
no
other
questions
from
chat.
Anything
else
before
we
part
ways.
C
Least,
this
is
an
announcement
blog
that
went
out
last
week.
So
so
I
would,
you
know,
encourage
customers
to
you
know
read
this
yeah
try
this,
you
know,
give
us
more
feedback
again,
you
can
open
your
shoes
or
I'm
gonna,
put
a
link
below
here.
A
No
thank
you
all
for
coming
on
right
like
this.
I
think
the
fastest
turnaround
between
announcing
and
show
we've
might
have
had
in
a
while.
So
thank
you
all
for
thinking
of
me
and
thinking
of
everybody
else.
That's
watching
out
there.
If
there's
nothing
else,
y'all,
I
I
think
we
call
it
here
and
yeah,
okay
cool.
So
up
next
on
the
show
noon:
eastern
1700
utc.
A
We
have
an
open
shift
comments,
briefing
about
backing
up
your
clusters
with
no
I'm
sorry
not
backing
up
your
clusters,
introduction
to
contour
with
steve
sloca
and
nick
young
from
vmware,
so
yeah
that'll
be
awesome,
and
if
you
have
any
questions
about
the
windows,
machine
config
operator
feel
free
to.
Let
me
know
at
chrisshort
on
twitter
and
see
short
redhat.com.
I
can
get
those
questions
answered
for
you
jp
day.
A
Don't
worry,
I
will
send
you
the
slide
that
you
asked
for
the
romance
slide
and
we'll
see
you
next
time
here
on
openshift
tv,
everybody
thank
you
anand,
arvin
and
gabriel,
the
easiest
name
to
say
that
I
forgot
thank
you
for
joining
me
this
morning
and
y'all
have
a
great
day
wherever
you're
at.
Thank
you
thanks.