►
From YouTube: OKD Working Group 2021 05 25 Full Meeting Recording
Description
OKD Working Group 2021 05 25 Full Meeting Recording
A
A
This
is
my
role
in
the
world
these
days,
I
am
trying
to
replace
myself
everywhere.
I
can
so,
especially
if
we
can
get
external
non-red
hatters
too.
So
that
would
be
wonderful.
So
with
that
said,
I'm
just
going
to
share
my
screen
for
a
minute.
So
if
people
don't
have
the
details,
I'm
going
to
put
the
the
screen
here
for
where
things
are
and
the
github
openshift
community
projects
thing
here,
planning
page
in
in
github.
C
A
C
E
C
D
Right
so
last
weekend
we
released
another
stable
cut
from
four
seven.
The
most
notable
about
this
release
is
that
it
has
a
new
signature,
gpg
keys.
Unfortunately,
our
previous
ones
have
expired.
So
if
you
want
to
update
this
version,
you
would
have
to
force,
update
and
skip
the
verification
of
the
keys,
but
from
now
on
for
the
next
two
years,
we
should
be
covered
in
this
situation,
along
with
four
seven
stable
release.
D
There
is
also
a
new
release
candidate
for
okay
for
eight,
I
encourage
everyone
to
have
a
look
and
we're
waiting
for
feedback
on
that.
The
most
notable
change
from
four
seven
is
a
new
way.
We
build
machine
os
content,
so
no
longer
you're
required
to
use
a
specific
federal
res
version
and
os
extensions
are
no
longer
used.
All
of
the
rpms
are
already
baked
in
the
us
content.
D
D
A
D
D
Ideally,
we
would
convince
the
software
collections
org
to
mirror
all
the
images
to
clay,
update
all
the
image
streams
in
there
in
their
repos
and
there's
like
20
of
them,
and
then
it
would
be
picked
up
by
samples
operator,
and
we
would
have
this
updated.
The
short
term
fix
is
that
we
could
probably
install
some
kind
of
a
proxy
or
a
mirror
with
those
releases,
but
that
would
complicate
ci
a
bit.
D
We
would
be
working
with
our
infra
team
to
fix
it
up,
but
I
don't
think
it's
easy
to
achieve,
so
we
would
have
to
live
with
that
for
some
time.
The
most
problematic
issue
I
see
right
now
in
48
is
that
upgrade
has
before
mysteriously
broken,
we'll
also
be
looking
into
that.
But
in
my
manual
tests
things
have
been
working
fine,
so
I'd
be
very
interested
for
some
results
from
the
field.
C
E
C
E
E
The
podman
issues
have
been
resolved
as
far
as
I
understood
so,
which
should
be
good,
so
rather
smooth
move
to
federal
34
for
now
this
this
one.
So
this
one
does
not
come
with
the
c
groups.
V2
change
right!
Now.
It's
coming
up
this
one.
The
this
specific
change
is
coming
in
the
next
testing
release.
E
That
will
happen
approximately
in
two
weeks
and
yeah,
but
this
one,
I
think,
is
covered
too
by
the
changes
in
okg,
so
that
should
be
fairly
transparent
by
now,
because
I
don't
think,
okay
we'll
be
switching
to
secret
v2
right
now,
but
that's
different
issue.
So
yeah!
That's,
I
guess
that's
it
from
me.
On
the
retro
chorus
side,
the
counting
work
has
been
fully
announced
everywhere.
G
Yep
it's
about
about
to
land,
so
it'll
be
in
testing
next
week
and
then
stable
two
weeks
after
for
existing
nodes,
they're
not
migrated,
but
there
will
be
a
nice
little
banner
that
says:
hey
you're
on
c
groups
b1.
You
might
want
to
run
this
command
to
switch
up
the
the
problem
there
is
like
you
know.
G
If
there
are
any
compatibility
issues
with
people's
applications,
we
don't
want
an
automated
automated
upgrade
to
break
them,
so
we're
trying
to
balance
things
there,
but
for
newly
deployed
nodes
they
will
be
on
c
group
speed
2
by
default.
If
you
would
like
to
stay
on
c
groups,
b1
you'll
have
to
basically
add
a
kernel
argument
to
keep
your
system
that
way.
G
Ignition
just
did
land
support
for
actually
changing
kernel
arguments,
which
is
nice,
so
you'll,
be
able
to
soon
enough
you'll
be
able
to
write
a
butane
config
that
says
hey
this
kernel
argument
should
exist
on
the
command
line
and
ignition
will
apply
that
for
you.
So
that's
kind
of
a
nice
recent
change.
I
don't
know
if
it
really
helps
okd
much,
but
it
you
know
might
be
able
to
be
leveraged
by
okd
at
some
point.
If
that's
something
that's
needed.
C
All
right,
then,
let's
move
on
to
the
discussion
section
reviewing
the
discussion
section.
There
was
a
discussion
item
put
in
12
days
ago
and
for
folks
I'll
put
this
in
the
link
for
folks.
That
don't
know
where
this
is.
This
is
the
new
discussion
section
and
folks
have
been
using
this
for
ideas
and
also
for
bugs
or
issues
that
they
come
across
diane.
Did
you
have
something
sorry
yeah.
C
A
C
On
my
scripting
and
stuff
like
that,
and
so
the
question
here
was:
would
it
be
convenient
to
or
improve
the
user
experience
if
all
of
the
resources
which
were
created
were
fetchable
via
that
yeah?
I
don't
know
the
team,
did
you
ever
find
out
or
do
you
know
if
there
was
like
a
list
of
resources
that
get
created
or
if
there's
an
available
list
in
regards
to
the
installer.
D
D
Applications
which
are
cleaning
up
after
our
ci
if
it
fails
in
the
middle
or
we
are
actually
making
a
bug
and
leaking
something.
So,
ideally,
you
would
be
able
to
list
all
of
them
by
tag
if
some
resources
are
missing,
it's
a
bug
in
the
installer
and
it
needs
to
be
fixed
because
it's
well.
It's
flagging
all
of
our
systems
and
it's
pretty
severe.
C
Does
anyone
want
to
join
me
in
doing
some
installs
and
querying
on
items
created
looking
for
items
created
and
making
sure
that
they're
all
properly
tagged?
Are
there
any
other
vsphere
folks
on
here
that
like
to
join
me
in
that
task?
That
actually
sounds
like
a
worthy
project,
because
then
we
could
put
in
bug
reports
on
anything.
That's
not
getting
tagged.
Anyone
else
well
go
ahead
and
put
your
name
in
the
chat.
If
you
are
interested,
because
I
think
I'm
going
to
do
that.
H
I
was
jamie,
I
was
talking
with
this
person
when
they
were
asking
in
chat
about
this,
listing
the
resources
with
gov
c,
and
my
I
seem
to
have
the
impression
that
they,
what
they
were
trying
to
do
was
like
have
a
way
to
like
audit
what
had
been
created
or
like
during
a
failed
creation.
They
wanted
to
go
back
through
the
v
center
or
something
like
that
and
find
everything.
H
So
I
think
I
think
you're
absolutely
right
and
what
vadim's
saying
is
is
great
like
we,
we
should
just
enable
you
to
be
able
to
use
oc
to
see
like
what
what
was
created.
What
was
not,
you
know
just
pull
the
tags
that
way.
That
would
be
a
lot
better.
This
also
feeds
into
kind
of
some
other
things
we
have
going
on
about.
You
know
tagging
all
resources
that
get
created
and
whatnot,
but
I
think
your
instinct
was
great
there
yeah
if
people
wanted
to
like
just
confirm
what's
created.
That
would
be
amazing.
C
Excellent
and
mike,
if
you
find
that
if
you
can
scroll
back
when
you
get
a
chance,
not
necessarily
right
now,
but
find
that
discussion
in
the
chat
and
link
us
to
it,
that
might
be
helpful.
Maybe
just
put
it
in
the
actual
discussion
item
on
the
repo
that'd
be
awesome,
cool
all
right
and
other
discussion
item
was
upgrade
failed
4.6
to
4.7.
C
C
This
is
the
most
recent
discussion
item,
so
my
time
is
limited
at
the
moment
in
terms
of
the
vmware
stuff,
the
next
couple
days
anyway.
Now,
let's
bounce
over
to
the
issues
section
of
the
repo
so
yeah
just
to
the
left
there
you
go
perfect.
Thank
you,
diane
and
anything
you
want
to
draw
to
our
attention
here
or
anything
that
vadim
that
you
think
that
folks
could
help
out
in
troubleshooting
or
any
other
way
that
you
could
leverage
the
group
to
address
some
of
these.
D
D
So
we
were
kicking
the
scan
down
the
road
and
our
stable
build
has
expired
because
the
cubelets
certificates
are
valid
for
six
months,
only
meaning
we
have
to
rebuild
the
46
image
every
six
months,
at
least
so
I'm
thinking,
if
I
remember
correctly,
charo,
has
documented
how
to
build
crc
fully.
So
it
would
be
a
great
exercise
for
the
community
how
to
build
a
crc
from
4,
6
or
ideally
for
7.
D
A
D
A
C
A
A
There's
a
group
of
new
red
hatters
on
boarding
who
are
going
to
be
coming
through
the
okd
working
group
as
part
of
their
onboarding
process
in
the
engineering
team
and
mustafa
is
the
first
guinea
pig
of
that
group
and
he's
been
on
most
of
the
calls
except
this
week.
So
I'm
not
quite
sure
where
he
is
today,
but
we
had
a
conversation
about
doing
some
pair,
reviewing
our
pair
programming
approach
to
reviewing
the
docs
so
taking
one
person
in
this
instance.
A
We
we're
thinking,
bruce,
link
and
mustapha
who's
new
to
it
hasn't
really
done
a
lot
of
deploying
of
okd
and
reviewing
the
okay,
docs.okd.io
and
testing
out
the
workflow
of
how
that
pair
programming
would
work-
and
I
say
pair
programming
pair
reviewing
and
then
how
we
interact
with
the
docs
team.
So
we
have
one
red
hatter
in
each
of
the
pair,
which
would
be
mustafa
in
this
instance
and
work
out
that
workflow
and
then
once
they
did.
A
You
know
I'm
not
sure
they're
going
to
do
all
of
the
docs.okd.o,
but
like
a
section
and
figure
out
what
that
is,
is
to
replicate
that
in
like
we
did
for
the
hackathon
on
testing
and
deploying
and
having
taking
each
of
the
section
of
the
docs
and
basically
pair
programming
with
a
red
hatter
and
an
external
person.
Who's
got
some
experience
in
it
and
reviewing
the
docs
and
doing
using
link
hub,
not
linkedin,
hop
in
again
to
do
something
similar
to
that.
A
So
that
could
help
us,
like
with
the
crc
docs
that
charo
has
done
getting
those
up
to
speed,
because
what
we've
all
seen
in
the
docs.ok
section
is
that
it
is
just
a
a
rebuild
from
the
ocp
archives
stuff
and
often
there
are
little
things
that
are
tweaks
for
what
we're
doing
that
aren't
getting
integrated
into
that
flow.
So
part
of
that
is
one
of
the
things
that
that
I'd
like
to
see
if
we
can't
get
moving
forward
and
and
mustafa,
I
did
talk
to
him
bruce
his
game.
A
H
I
have
a
question
about
this.
This
may
be
better
for
the
docs
meeting,
but
I'm
just
curious
because,
like
I
would
imagine
that
the
okd
docs
were
going
to
keep
updating
them
every
time.
A
new
release
comes
out
in
the
same
way
that
the
ocp
docks
are,
but
I'm
curious
was
there
any
thought
about.
Like
should
do
the
okd
docks
exist
as
a
change
set
on
top
of
the
ocp
docs
yeah
because,
like
it
seems
like
it's
going
to
be
a
ton
of
material
to
go
through
every
time.
Ocp
docs
get
updated.
A
G
A
I
am
all
right,
so
I
would
love
it
if
next
tuesday,
you
could
come
to
the
docs
meeting,
which
is
the
same
time
same
place
as
this,
and
we
can
kind
of
figure
out
what
the
work,
how
how
you
want
to
be
informed
of
the
things
that
they
want
to
change
those
kinds
of
little
details,
and
that
would
be
really
helpful
for
us,
because
we
we
have
resources
and
larry
just
stepped
up
on
and
said
yeah
I'll.
Do
the
vsphere
stuff
everybody.
A
You
know
at
just
each
of
these
things
and
that
way
I
think,
once
we
know
what
the
overlay
is
just
for
the
docs.okd.ios
part
of
the
documentation
set,
then
hopefully,
each
time
we
rebuild
a
new
release,
those
patches
get
applied
properly,
so
michael
doesn't
have
to
go
in
and
hand
hold
them
and
all
that.
So
that's
that's
my
thought
process,
but
michael
chime
in
now
or
next
week
and
what
it
would
be.
A
A
H
Well,
I
you
know,
I
don't
want
to
speculate
at
your
business
or
my
busyness,
but
no
I
kind
of
backed
off,
because
I
thought
I
thought
you
were
going
to
take
a
look
at
it.
But
if
you're
not
having
time
like
you
know,
we
got
a
long
weekend
coming
up.
I
can
I
can
take
another
look
at
making
a
pr
there.
H
A
H
I
have
yeah,
I
mean
I
just
didn't.
I
just
didn't
go
through
with
it,
because
I
thought
at
last
you
and
I
talked.
I
thought
you
were
going
to
take
a
look
at
it,
so
I
just
didn't
get
any
deeper
into
understanding
that,
like
jekyll-ish
blogging
platform,
that's
there.
I
forget,
I
forget
what
it's
called.
A
Yeah,
I
I
think
in
the
person
who
can
the
community
person
who
can
help
out
with
that
who
understands
the
back
back
end
is
joseph
meyer
from
rodian
schwartz
who's.
Not
on
this
call.
So
I'm
going
to
volunteer
him
to
help
you
with
that
so
reach
out
to
him
because
he
didn't
show
so
he
gets
volunteered.
H
A
We'll
see
yeah,
it's
not
bad
and
there
are
a
couple
new
blogs
and
that
went
out
very
quick
ones
about
one
with
joseph's
video
from
the
last
kubecon
that
he
did
a
nice
talk
on
and
the
other
one
with
the
office
hours,
and
I
think
I
did
them
right.
They're
public
and
the
other
thing
that
I
have
is
if
anyone's
interested
in
it,
the
video
will
go
up
later
today.
Hopefully,
the
cross
plane
operator
needs
to
be
tested
on
okd
and
that's
just
been
released
and
just
prior
to
this
meeting.
A
I
just
did
a
review
a
briefing
on
that,
and
there
is
a
blog
post
on
openshift.com
that
chris
choudry
wrote.
That's
a
you
know
it
might
be
on
developer.com
I'll,
find
the
link
and
post
it
to
the
group.
But
if
anybody
would
like
to
they
they're
looking
for
some
feedback
on
that
crossplane
operator
and
making
sure
that
it
works
with
okd
and
vanilla,
kubernetes
or
any
other
kind
of
kubernetes
as
well.
A
C
So
the
link
that
I
just
posted
in
the
channel
is
to
an
older
discussion.
That's
ongoing.
We
talked
about
this
last
week.
This
will
be
something
that
the
docs
group
is
going
to
tackle,
which
is
clarifying
the
community
support
model
like
what
that
actually
means
and,
in
essence,
I'm
going
to
move
a
little
bit
because
there's
some
construction
happening
near
me.
C
So
the
docs
group
will
be
talking
about
this.
What
we
will
need
from
the
community
at
large
is
any
place
where
you
think
that
this
language
would
be
appropriate
to
to
put
any
type
of
communications.
The
website
blog
in
any
of
the
repositories
any
place
where
you
think
that
this
language
would
be
helpful.
C
Please
let
us
know
like
put
a
comment
in
the
discussion
thread
there.
That
would
be
super
helpful.
We're
going
to
come
up
with
the
language
within
the
docs
group,
I
think,
and
if
anyone
wants
to
chip
in
on
that,
we'll
probably
be
doing
that
like
adding
to
this
thread
with
that
language,
any
questions
or
comments
on
that
any
thoughts.
I
I
Yeah,
I
was
thinking
specifically
in
the
case
of
the
slack
channels
like
maybe
it
would
be
possible
to
have
slackbot
say
something
to
people
when
they
first
join,
like
hey,
if
you're
using
okd,
maybe
pain,
and
we
set
up
a
group
with
you-
know,
community
members
who
want
to
be
involved
with
it,
just
like
an
okd
or
something
so
that
they
can
ping
that
instead
of
ping,
a
red
hat
employee
directly
or
someone
that
they
have
seen
in
a
github
issue,
which
I
think
is
more
often
what's
happening.
Right.
Yeah.
C
A
The
kubernetes
channel,
we
don't
have
control
too
much.
I
can
reach
out
and
see
if
we
can
slightly
modify
the
openshift
dev
one
with
a
you
know,
a
reference
to
okd,
I
I
know
amy
and
the
other
managers
there.
So
maybe
we
can
get
something
out
of
there
I'll
see.
Let
me
add
add
that
to
my
to-do
list
today,.
H
That
would
be
fantastic.
I
think
sheree
had
a
nice
idea
in
there
too,
like
in
addition
to
the
cluster
bot
like
having
having
an
alias
for
like
a
group
of
people
who
want
to
volunteer
to
be
the
okd
support,
team
or
whatever
like.
If
there
was.
If
there
was
a
group
of
community
members,
you
know,
but
I
mean
if
there
were
a
group
of
community
members
who
are
willing
to
volunteer
for
that
kind
of
stuff
say
like
well.
H
I
H
C
Excellent
anyone
else
have
comments
or
questions
on
this
topic,
all
right
and
then
the
other
one
which
sort
of
ties
into
this
is.
We
had
talked
with
vadim
at
the
last
meeting
about
coming
up
with,
like
a
list
of
like
the
group,
the
community,
coming
up
with
a
a
sort
of
a
quick
little
guide
to
how
to
troubleshoot
yourself
an
okd
install.
C
You
know,
in
addition
to
the
little
bit
of
stuff.
That's
that's
in
the
official
okd
docks,
and
I
know
vadim
was
gonna,
come
up
with
a
list
of
things
that
he
thought
we
should
sort
of
fill
out,
provide
more
details
on
in
terms
of
install
stuff
based
on
sort
of
common
issues
that
he
sees
and
whatnot
vadim.
Did
you
have
anything
you
wanted
to
to
chime
in
on
that.
D
I
don't
think
I
had
any
progress
on
actual
implementation,
but
I'm
thinking
we
could
start
with
a
markdown
in
the
repo
get
it
reviewed
and
slowly
iterate
from
here,
maybe
making
a
video
or
a
full
blown
blog
post.
I
could
take
a
look
into
this
this
week.
Hopefully,
if
I
forget,
please
do
remind
me
to
do
that.
That's
very
important
actually.
C
H
I
D
How
do
they
work
together
because
well,
this
thing
changes
every
release
and
I
don't
think
we
can
keep
it
updated
every
single
time,
but
just
to
give
you
an
idea
of
what
can
possibly
go
wrong,
it
could
be
networking,
it
could
be
monitoring
it's,
it
could
be
useful
and
it
also
points
you
to
a
particular
comet.
It
was
built
from
so
you
can
find
out
which
repo
is
it
built
from,
and
hopefully
this
ripple
would
have
a
troubleshooting
guide
or
some
developer
documentation.
H
From
a
more
architectural
standpoint,
not
just
from
the
component
like
operator
standpoint,
because
I
totally
like
sri
what
you're
talking
about
makes
complete
sense
like
I've,
I've
actually
gone
through
like
every
operator
and
tried
to
put
pieces
together
for
myself,
and
it
is
not.
It
is
not
an
easy
task,
but
I
had
been
talking
with
another
red
hatter
internally
fabiano
franz
for
the
other
red
hitters
here
when
we
had
first
set
up
that
guides
and
deployment
repo.
He
and
I
had
kind
of
talked
about.
H
He
was
working
on
a
project
to
generate
architecture
diagrams
of
openshift
clusters
based
on,
like
I
think,
terraform
or
something
so
like
he
was
generating
these
really
cool
diagrams.
That
would
show
you,
like
topologically
how
your
cluster
was
laid
out
and
where
each
component
was
and
like
you
know
how
these
things
fit
together,
we
never
got
to
the
point.
He
was
talking
about
generating
some
documents
that
he
was
going
to
contribute
to
that
okd.
You
know
deployment
guides
repo,
but
we
never
got
to
the
point
where
he
was
generating
them.
H
I
I
Six
words:
that's
unfortunate.
Come
here
microphone,
no,
it's
just
saying
it
just
to
help
on
board
people
who
are
perhaps
new
to
okd
in
particular,
who
might
even
have
experience
with
kubernetes,
because
very
few
like
there
are
maybe
three
things
on
this
list
that
could
conceivably
call
it
be
called
like.
Oh
yeah,
I
recognize
that
from
a
vanilla
kubernetes,
you
know
cube
proxy
woohoo.
I
know
I
know
what
that
is,
and
then
everything
else
on
top
of
it
is
just
like
who
knows.
H
I
All
the
more
reason
to
maybe
start
now,
maybe
I
don't
know,
I'm
I'd-
be
totally
willing
to
contribute
at
least
write
down
what
I
have
figured
out
about.
What's,
on
top
all
the
sort
of
open,
okd
or
openshift
specific
value,
add
stuff,
but
I'm
sure
I've
gotten
about
half
of
it
wrong.
Simply
because
I
don't
know.
A
How
about
if
sri,
if
you,
if
you
took
a
stab
at
that
and
because
I'm
just
sort
of
listening
in
the
background,
but
I'm
also
thinking
the
work
that
that
bruce
did
around
the
taxonomy
for
things
to
watch
out
for
when
you're,
installing
that
this
diagram
or
this
piece
all
of
the
things
in
his
taxonomy,
should
have
a
an
entry
point
in
this
diagram
or
this
list
at
some
point.
So
that
kind
of
is
this
to
me.
It's
the
same
work
effort.
A
D
E
A
A
You'd
think
you'd,
think
and-
and
I
asked
there
there
is-
there-
is
some
marketees
around
that
on
the
openshift.com
site
in
different
places.
It's
not
really
explicitly
clear,
often
even
in
my
humble
opinion
and
I'm
inside
the
inside
the
beast.
I
think
I
think
it
is
something
that
we
need
to
clarify
in
the
docs
a
little
bit
better
beyond
just
you
know,
this
is
community
supported
and
it
runs
on
fedora
core
os.
I
mean
there's
there's
some
other
things
that
are
are
a
little
bit
different.
F
F
H
H
Well,
yeah
and
then
there's
the
truth
right,
but
like
so
for
a
while,
the
messaging
was
yeah.
Openshift
is
kubernetes
because,
like
from
a
marketing
perspective,
you
know
we
didn't
want
to
scare
people
who
were
like
well.
Openshift
is
like
you
know
you
get
locked
into
this
specific
type
of
kubernetes
right
so
that
that
was
a
message
for
a
while,
but
like
now
it's
like
well.
How
do
we
differentiate
openshift
from
what
is
what
does
openshift
add?
H
How
do
we
enumerate
that,
and
I
see
sales
people
struggle
internally
to
figure
out
like
the
best
way
to
talk
about
this
messaging.
So,
like
I,
I
agree
with
your
with
your
what
you're
saying
like
we
should
own
that
message
and
have
it
somewhere
on
the
okd
site.
So
people
don't
have
to
rely
on.
You
know
the
propaganda
and
the
fun
and
whatever
else
is
out
there.
But
it's
like
a
difficult
question
to
answer
something
right.
Well,
maybe
everybody's
expecting.
I
I
A
A
I
You
have
microlist,
that's
the
susa
distribution
and
then
you
have
okd
and
openshift.
That's
the
red
hat,
rel
distribution.
You
know
it's
red,
hat's
opinions,
it's
zeus's
opinions,
it's
red,
hat's,
tooling,
it's
seuss's!
Tooling!
It's
you
know.
Whoever
else
is
vanilla.
Kubernetes
is
basically
the
arch
linux
or
slackware
of
kubernetes.
C
C
D
D
D
It
builds
the
release
and
runs
a
conformance
end-to-end
test,
and
if
this
change
is
acceptable,
it
will
merge
it
build
a
new
image
and
push
it
to
the
image
stream
and
from
this
image
stream,
we
are
building
an
official
release
on
our
release,
controller
page,
which
is
like
a
release
page
for
all
of
out.
There,
and
if
this
so-called
nightly
build,
is
stable
enough,
we
declare
it
stable
and
move
it,
mirror
it
to
quay
and
move
it
to
for
stable
length.
D
C
That'd
be
fantastic:
okay,
we
have
four
minutes
left,
and
so
are
there
any
last
questions
or
comments
about
anything,
okd
related
that
we
can
deal
with
in
the
next
three
minutes.
I
want
to
be
mindful
of
people's
time.
Always
any
other
questions
comments.
Anything
you
want
to
bring
to
the
table
before
we
adjourn.
C
All
right
sounds
like
we've
got
everything
we
need,
and
you
know
in
terms
of
that
discussion
that
was
going
in
terms
of
you
know
communicating
what
okd
is
that's
a
great
discussion.
I
think
that
you
know
I
wanted
to
pull
back
to
make
sure
we
had
enough
time,
but
that
can
be
carried
on.
I
think
for
sure.
So
please
don't
feel
like
that.
Was
cutting
it
off
in
any
way.
Yeah,
not
intentional,
intended
to
do
that.
Yeah
diane
did
you
have
anything
no.
A
A
A
It's
you
can't.
You
can't
use
kubernetes
in
the
name
of
a
product
or
an
open
source
project.
You
that's,
why
you
see
all
the
k8
s's
and
the
eks's
and
the
gk
okays
and
the
you
know
everything
that
is
just
the
way
the
the
world
bounces
when
google
donated
it
to
the
linux
foundation
and
set
up
cncf,
they
donated
the
trademark
and
cncf
owns
that
brand.
So
yeah,
it's
an
interesting
world,
but
it
also
keeps
us
honest.
A
It
just
makes
it
hard
to
message
stuff.
So,
hence
why
okd
has
that
you
know
the
kubernetes
distribution
that
powers.
You
know
red,
hat's,
open
shift
and
it's
it's
tough
internally
and
I'm
just
and
I'm
gonna
take
the
last
one
minute.
If
you
think
about
how
many
different
flavors
of
open
shift
there
are
it's
not
just
ocp
anymore,
so
you
know
it's
it's
crazy,
so
anyways.
Thank
you
for
a
wonderful
meeting
jamie,
I'm
so
happy
that
you're
willing
to
do
this
and
I
love
your
backyard.