►
From YouTube: OpenShift Coffee Break: KubeCon NA 22 Recap!
Description
Get your espresso ready for the OpenShift.TV Coffee Break as we go through all big announcements made at KubeCon NA 22 in Detroit to discuss latest news about the great Kubernetes community and ecosystem!
A
A
B
Good
mate:
how
are
you,
how
are
you
mate,
all
good
I
hope
you
had
your
coffee
shop.
We
come
back
to
the
openshift
TV
coffee
break
with
this
session
great
Orient,
about
a
recap
of
what
happened
at
that
cubecon.
So
we
need
some
coffee
right
to
start
the
journey
in
the
in
the
right
mode,
because
lots
of
stuff
happen.
So
we
we
were
thinking.
B
Okay,
let's
do
a
a
show
where
we
just
go
through
the
PR
announcement
of
what
happened
on
kubecon,
North,
America,
Detroit,
disclaimer
warning
we
nobody
of
us
any
one
of
us
were
present
on
North
America
Detroit.
But
if
anyone
in
the
chat
were
there
or
assisted
virtually,
please
join
the
discussion,
ask
question
and
tell
us:
what
do
you
think
about?
We
have
some.
You
know
news
some
some
blog
posts
to
share,
but
if
anyone
was
really
there,
please
join
the
discussion.
C
C
A
B
And
yeah
anyone
in
the
chat,
please
feel
free
to
so
any
question.
What
we
were
planning
today
is
a
quick
round
of
a
wrap-up
discussion
heard
it
one
thing
of
cool
of
cubecon
is
that
there
are
the
co-located
events
right.
So
there's
one
particular
one
that
you
might
be
interested
in.
You
want
to
talk
us
about
a
little
more
about.
What
is
the
key
tops
con,
and
why
is
on?
What
do
you
think?
It's
a
next
Cube
code.
C
Yeah
totally
I'm
very
biased,
I'm,
the
PM
for
openshift
get
up
so
I'm
very
keen
on
get
Ops
con.
So
you
know
it's
kind
of
happens
just
over
one
day,
co-located
with
kubecon
and
all
about
different
types
of
get
Ops
workflows,
different,
get
Ops
projects
that
are
out
there,
the
main
ones
being
Argo
and
flux,
and
there
were
so
many
cool
talks
this
year.
C
It
was
really
awesome
lots
of
stuff
about
bringing
in
different
elements
into
githubs,
like
policies
as
code
I,
think
there
were
at
least
three
different
talks
about
that
which
was
really
awesome.
Oh
yes,
there
we
go.
That's
the
link
to
what
happened
at
gearboxcon,
North
America,
thanks
for
popping
that
in.
C
Yes,
obviously
we
we
were
there
and
not
me
personally,
but
red
hat
had
a
presence
there
and
I
think
get
UPS
is
getting
bigger
and
bigger.
Every
year
there
were
a
bunch
of
Talks
by
companies
that
I
hadn't
I
wasn't
familiar
with
before
good
Ops
gone
I
know,
we've
worked
had
a
big
presence
there.
They
were
the
kind
of
Originators
of
the
word
get
Ops
and
they
always
have
some
really
great
talks.
C
C
Side,
folks,
who
are
like
managing
their
clusters,
they
want
to
make
sure
that
people
aren't
going
and
changing
them
manually
and
making
weird
changes.
They
want
to
do
things
automatically.
They
want
to
be
automating
their
workflows.
They
want
to
be
providing
automated
deployments
for
their
teams.
They
they
want
to
like
set
stuff
up
for
their
development
teams,
but
I
know
like
individual
developers,
are
interested
in
good
Ops
as
well.
C
A
C
B
That's
super
cool
because,
as
you
say,
it
is
any
kubecon
has
its
own
gitopscon
I
remember
it
started
also
virtually,
but
now
it's
only
in
person,
if
I
recall
correctly
right
right
so
yeah
when
it
was
also
virtual.
There
were.
Maybe
more
people
can
attend
worldwide,
but
this
yo,
the
the
real
sense
of
those
co-located
event,
is
that
okay,
you
go
to
cube
code
and
you
can
also
join
in
person
those
event
vertical
to
a
specific
topic
or
technology.
There's
also
a
service
mesh
con
and
a
six
star.
B
C
B
And
opposite
of
Commons
is
another
very
cool
event,
which
is
for
the
people
not
aware
of
opposite
comments.
Is
the
community
of
openshift
gathering
and
meeting
on
on
typically
on
event
close
to
cubecon,
but
not
only
there
was
the
commons
Gather
in
London
I,
don't
know
if
you
were
also
there
attending.
B
A
A
A
A
So
in
those
cases,
if
you
remember,
we
would
address
that
with
our
red
for
Edge
and
if
you
think
about
it,
there
are
obviously
a
number
of
of
capabilities
that
you
need
in
that
case,
and
we
can
talk
about
you
know
the
way
you
have
to
the
way
you
update
the
the
software
components,
looks
at
the
operating
system.
Anything
that's
running
on
it.
A
The
way
you
do
you
do,
the
the
first
installation,
the
creation
of
the
images
and
all
that,
if
you
remember
our,
we
tended
to
to
use
well
for
Edge
and
if
you
want
to
containerize
something
on
it
running
in
containers,
that
would
be
the
perfect
fit
for
Portland.
But
there
are
other
cases
where
you
may
want
to
have
a
way
of
running
executing
and
distributing
the
containers
and
orchestrating
them
the
same
way
to
the
far
Edge
and
all
the
other.
A
Let's
say:
Edge
Edge
materials
that
you
want
to
have
so
openshift
already
comes
in
different
form
factors.
It
comes,
as
you
know,
as
a
three
note
configuration
it's,
a
one,
node
signal
configuration
and
now
trying
to
push
to
the
edge
and
sort
of
have
a
merge
between
certainly
the
capabilities
of
open
shift
and
well
for
Edge,
and
now
we
have
Edge
device
where
the
capabilities-
let's
say
they
strip
down
small
form,
factor,
capabilities
and
small
footprint
of
open
shifts,
are
actually
provided
by
a
project
that
we
talked
about
in
the
past
microshift.
So.
A
We
could
get
into
details
by
essentially
microshift
is
open
shift,
but
it's
just
one
single
executable
that
the
cards
actually
from
the
same
code
Base
is
located,
and
at
that
point
you
can
run
your
containers
not
just
important
but
directly
on
a
very
small
footprint
version
of
openshift.
It's
not
I
need
it's.
If
you
wish
you
could
yeah,
it
only
has
the
capabilities
that
openshift
will
need
in
this
single
load
single
node
device.
A
But
who
knows
if
you're
in
the
future
that
may
even
be
clustered?
Who
knows
I,
don't
I,
don't
think
we
have
yet
a
requirement
for
that,
but
maybe
some
Asian
capabilities
that
I'm
eating
in
the
future,
so
that
that
would
be
pretty
more
or
less
the
announcement
we
can
get
into
into
the
details,
but
I
think.
Actually
we
should
have.
Maybe
our
PM
for
Edge
device
come
and
talk
to
us
about
it.
Yeah.
A
Yeah
we
could
do
that
again
get
into
the
into
the
various
the
virus
capabilities,
and
but
it's
obvious
you
think
about
it.
It's
like,
if
you
have
a
usual
Venn
diagram.
On
the
one
hand
you
have
the
capabilities
of
open
shift
and
on
the
other
you
have
you
have
the
use
cases
for
for
red
for
Edge.
There
is
an
intersection
there
and
that's
where
microchipped
and
that's
where,
when
I
July
sits.
C
A
I
have
my
own
notes
so
think
of
microchip
as
the
equivalent
of
k3s,
with
the
difference
it's
actually
running
at
CD,
so
it
runs
a
subset
of
the
components
of
openshift,
but
they
all
are
exactly
from
the
same
code
base
with
the
same
behavior.
So
you
will
not
have
all
the
build
capabilities
that
openshift
provides
because
you
do
the
build
somewhere
else.
A
It's
only
the
what
you
need
to
run
and
orchestrate
the
containers
update
them,
monitor
them.
Okay,
so
it's
just
a
stripped
down
version
that
is
actually
distributed
in
a
different
way,
because
it's
distributed
via
RPM,
os3
and
and
and
the
beauty
of
that
is
that
you
can
actually
build
the
even
the
US
image
that
contains
the
call
that
the
bootstrap
images,
the
number
of
images
that
you
already
want
to
have
when
you
produce
that
edge
device.
A
A
B
And
I
have
a
question:
I
heard
it
about
this.
So
if
we
have
read
that
device
Edge,
imagine
a
level
1000
or
you
know
million
of
devices
connected
right.
How
do
you
see
openshift
key
tops
supporting
such
capabilities?
Like
you
know,
it's
a
difficult
question,
because
we
have
different
architectural
pattern.
You
can
have
a
mega
big
giant,
openshifted
Ops
cluster,
controlling
everything
or
you
can
have
a
multiple
opportunity,
tops
right.
How
do
you
see
in
the
future
a
possible?
You
know,
architecture.
C
B
B
Right
right,
I
think
the
this
this
approach
is
extended.
You
know
it's
a
big
windows,
it's
not
only
and
for
the
data
center
or
cloud
or
even
at
the
edge
the
same
approach,
but
for
many
infrastructure
or
how
you
want
to
call
clouds
Edge
infrastructure
that
that
layer
that
the
fundamental
layer
it
looks
like
holistic
in
this
way
cool
that
read
that
device
Edge.
We
shared
the
link
in
the
chat
because
it
contains
also
a
good
recap
of
what
Andrea
said
right.
A
So,
underneath
you
have
well
for
us
not
colorless,
that's
one
of
the
other
main
differences,
which
also
gives
you
the
so
you
have
full
control
of
that
OS
and
what
you
install
it,
because
you
need
to
be
able
to
install
special
device
drivers,
Hardware,
dependent,
Hardware,
dependent
software.
That
may
come
from
an
ISB
which
couldn't
do,
but
you
could
do
that.
But
that's
not
as
open
in
case
of
for
us
for
us
only
comes
with
openshift.
If
you
remember
right.
B
B
So
thank
you
for
organizing
the
quesadilla
I
will
we
will
really
want
would
like
to
invite
you
to
share
Insight
about
this
event
close
to
jidex,
which
is
a
really
big
event
in
the
in
the
area
so
great
to
have
you
here
and
if
you
have
any
feedback.
Please
share
in
the
chat
about
kubecon
announcement
and
any
co-located
event.
You
think
are
interesting
yeah.
B
So,
as
you
can
see,
there's
cubecon
there
are
the
co-located
event
and
then
there
are
also
those
community
events:
the
kubernetes
Community
Day
for
your
importers,
one
in
Milano
in
November
that
happening
virtually
because
we
had
some
issue,
but
we're
gonna
do
it
in
person
in
next
year,
but,
as
you
can
see,
any
city
has
its
own
kubernetes
Community
Day,
it's
a
kind.
It's
like
having
a
small
cubecon,
really
small
right,
Community
tall
Community,
but
it's
the
same
concept,
so
really
cool
yeah.
A
A
The
device
at
that
point
is
offline
and
you
won't
be
able
to
accommodate.
So
you
need
to
have
a
way
to
do
to
roll
back.
Whatever
updates
you
get
to
the
last
known,
workable
state
of
the
device,
and
that's
something
that's
already
part
of
of
the
bundle,
if
you
wish
with
a
relative
device,
because
there
is
an
intelligent
rollback
mechanism
that
you
can
customize
for
green
boot,
that
will
go
and
check
do
all
the
checks.
A
B
A
B
Well,
this
is
super
cool
I
think
this
was
the
major
announcement
from
Red
Dot,
together
with
the
partnership
with
looking
Martin
right,
always
on
Red
Dot
device
Edge,
we
had
another
very
good
announcement,
which
is
a
red.
The
one
telling
that
redact
is
joining
the
backstage.
Community
I'm
really
excited
about
it.
Andre
I
heard
it
because
backstage
it's
a
popular
open
source
software
made
originally
by
Spotify
for
creating
project
inside
you
know
in
your
company.
B
You
add,
you
have
to
fold
a
new
project
with
a
git
repository
with
some,
you
know
permission
or
connected
to
some
cluster
somewhere.
So
backstage
is
this
software
and
and
we
announced
that
we're
joining
the
backstage
IO
Community,
so
it's
gonna
be
part
of
a
Reddit
offering
and
the
idea
is
that
nicely
connecting
the
backstage
ux
to
to
openshift.
So
you
you
want
to
start
a
new
project.
You
just
create
this
project
using
backstage
and
then
it's
connect
to
openshift.
B
This
is
this
will
be
really
nicely
connected,
so
I'm
excited
about
it
because
the
backstage
is
being
very
popular
and
if
you
think
about
when
you
have
to
create
a
new
project
on
kubernetes,
it's
not
that
trivial
right.
You
have
to
manage
user
permission.
Okay
heard
it,
you
can
say
it
could
be
infrastructure
as
a
code.
The
policy
as
a
code
security
is
a
code.
Whatever
else
they
call
right.
Everything
gets
a
code
yeah
yeah.
B
B
We
we
don't
have
the
roadmap
again
shared,
but
it
looks
like
yes,
it's
gonna
be
a
part
of
the
developer
experience.
Definitely
the
developer
experience
in
openshift,
so
the
web
console
will
be
nicely
connected
like
for
other
ship
detox
right.
If
you
see
Argo
CD,
it's
on
the
application
path,
top
top
right,
you
click
it
and
you
join
it's
another
software
Argo
CD.
Well,
it's
openshift
key
top,
which
contains
argosity
in
a
certain
version
right.
But
it's
nicely
connected
to
the
openshift
authentication.
The
openshift
weapon,
Zone
I,
think
we're
gonna.
B
Oh,
while
it's
saying
many
golden
platform
use
it
for
their
user,
Port
Cloud
I'm
wondering
if
the
UI
RCP
would
be
more
acceptable.
It's
there
since
2016..
Yes,
it's
true!
Well,
it
is
it's
a
project
started
from
one
time,
but
now
already
decided
it's
time
to
to
make
it
part
of
the
family,
or
at
least
you
contribute
actively
to
it
and
I
think.
It's
really
really
good
idea.
A
B
Oh
yes,
and,
to
be
honest,
we
did
a
lab
a
workshop
around
this,
so
I
can
share
with
you
this
Workshop
made
by
my
colleague,
Ryan
Josh
Evan,
everyone
in
the
team,
the
Cedric
collaborated.
It's
it's
basically
a
tutorial
that
drive
you
on
how
to
extend
the
web
console
because
the
web
option
web
console
can
be
extended.
There
are
some
API
or
custom
razors
that
allow
you
to
Define
how
to
extend
the
console.
A
B
Based
on,
if
I
I
don't
know,
I
don't
know,
to
be
honest,
so
I
found
the
the
workshop
coming
back
to
magnific
I
find
the
workshop
valid
if
you
are
interested
on
how
to
customize
operation
weapon.
So
we
did
this
workshop
at
Summit,
North
America,
semicolon
North
America
in
September.
This
is
a
way
around.
You
can
customize
the
console
extend
it.
B
This
is
one
thing.
The
UI
thing
Andrea
is
pattern
flight
valid
share.
Oh
you
share
in
the
chat
the
link.
This
is
the
the
part
all
that
products
are
using
pattern
fly,
although
that,
if
you,
if
you
look
at
openshift
web
console
or
cockpit
in
Rel
or
any
other
like
the
hybrid
Cloud
console,
you
go
to
console
reddit.com,
it's
still
pattern
fly.
It's
a
consistent
user
experience.
B
Definitely
we
did,
we
did
it
for
recently.
So
it's
it's
called.
Let
us
know
what
do
you
think
about.
So
if
you
go
through
it,
it's
a
really
cool
showing
how
to
customize
the
the
console.
The
UI,
for
instance,
openshift
key
tops
right,
has
one
icon
to
the
application
pad.
This
is
something
you
can
customize.
You
can
change
the
logo
or
change
the
the
URL
for
your
items
right.
You
can
also
add
your
apps.
There.
B
Super
cool,
so
thanks
for
the
question
valid,
if
you
I
wanted
to
ask
to
the
audience,
attend
any
one
of
us
using
backstage
already
or
what
do
you
think
about
backstage
because
as
police
say
2016,
so
it's
it's
a
mature
open
source
project,
probably,
but
now
we're.
We
hope
we
give
some
boost
with
this
adoption
from
from
Red
Dot,
so
just
wondering
if
anyone
in
the
chat
want
to
share
any
story
around
backstage
their
integration
with
the
kubernetes.
B
Yes,
I
think
you'll.
Already
you
get
you
you,
you
catch
a
really
good
point
now
that
there's
the
Wally
to
your
question.
Why
now
and
on
2016.,
now
there
there
is
that
platform.
Engineering
momentum
backstage
is
coming
back,
strong,
Harriet
I
know
you
work
it
with
platform.
Engineer:
do
you?
Can
you
explain
to
us
what
the
heck
is
a
platform
engineer
please,
because
in
Cuba
North
America
Detroit
there
was
lots
of
Platforms
in
the
platforms
so
yeah
and
inside.
C
Yeah
so
my
pre-red
hat
time,
I
was
the
PM
on
a
platform
team.
So
it
was.
We
had
an
internal
team
that
managed
our
like
the
services
for
the
other
teams,
so
not
just
like
things
that
the
other
teams
would
use
internally
but
also
kind
of
cross-cutting
concerns
that
they
would
use
externally
as
well.
So
like
we
managed
our
SSO
offering
across
the
multiple
products
that
we
offered
so
that
each
individual
team
didn't
have
to
do
it
so
yeah
that
post
that
you've
popped
in
from
Gartner.
C
That
was
a
really
good
one.
If
you're
unfamiliar
with
platform
engineering
covers
like
the
high
level
of
like
what
even
is
this
thing?
Why?
Why
would
we
want
to
do
it,
but
I
think
it's
a
nice
way
of
kind
of
consolidating
a
bunch
of
like
it
would
be.
Rework
you'd
be
like
copying
and
pasting
stuff
across
teams
and
consolidating
that
into
one
team
to
manage
it
all
in
one
place
and
using
something
like
backstage
to
help
you
do.
That
makes
it
like
really
Schmick.
B
B
C
B
B
C
C
B
C
A
Speaking
about
buzzwords,
we
just
talk
about
the
devops,
but
the
other
buzzword
is
death
setups
and
there
was
actually
an
announcement
at
cubecon
about
advanced
classes,
security
for
kubernetes.
That
is
now
also
going
to
be
delivered
as
a
cloud
service,
I
think
initially
on
AWS,
and
so
people
won't
have
to
normally
now
you
would
install
it
on
your
own
yourself
cluster
and
that's
requirement
to
bang
it.
However,
kubernetes
clusters
not
necessarily
appreciate
from
security
perspectives
to
security
for
the
whole
left
circles.
A
C
B
And
if
we
look
at
the
story
of
it
all
right,
this
was
an
acquisition
from
stack
rocks.
Stack
rocks
already
have
their
SAS
so
red
that
both
stack
for
open,
searched,
stack,
rocks
and
now
it's
advanced
class
security
for
kubernetes
and
then
offered
the
on-prem
and
now
back
to
Cloud
right
back
to
SAS.
But
there
was
the
open
socialization
in
the
in
the
in
the
middle,
so
I
don't
know
how
many
Company
open
source
their
acquisition.
A
Yeah-
and
he
said
it,
it
is
causing
easy
process
in
some
cases,
so
so
that
that's
why
there
is
a
little
bit
of
a
Gap
in
terms
of
time
before
between
the
acquisition
and
when
we
actually
manage
to
open
source
it,
and
but
it
is
part
of
of
how
we
build
software.
So
we
have
to
have
an
upstream
community,
and
this
is
this
is
how
we
we
manage
our
software
delivery.
So
so
that's
that
I
think
that's
interesting,
but
also
the
fact
that
it
kind
of
lowers
the
entry.
B
C
We
are
exploring
it
as
an
option.
Obviously,
we've
got
a
lot
of
interesting
get
ups
and
like
some
some
folks,
just
don't
want
to
do
that
all
themselves,
but
it's
such
a
useful
workflow
that
we
want
to
make
it
available
to
people
if,
even
if
they
don't
want
to
have
to
like
manage
everything,
everything
and
so
yeah
we're
looking
at
ways
that
we
can
provide
like
Automation
in
deployment
from
configuration
to
folks
as
a
service,
so
yeah
keep
your
eyes
peeled.
Okay,
that
may
be
something
maybe.
B
Something
can
happen,
really
really
cool
like
we're
going
more
in
this
cloud
services,
where
we
can
connect
everything
like
red
dot
device,
Edge
security,
SAS,
any
anything
SAS.
Also
in
the
GitHub
site.
Super
cool,
yeah
I
was
looking
also
at
the
chat.
There's
my
friend
Didier
saying:
devops
is
a
culture
and
practice?
Yes,
we
definitely
it's
a.
We
cannot
refactor
a
culture
right.
C
C
It's
more
kind
of
adding
on
to
it,
where
we're
looking
more
at
so
there's
like
the
four
get
Ops
principles
and
about
the
the
one
that
I
always
think
is
the
main
one
is
having
the
the
controller
that
watches
and
continuously
reconciles,
and
so
it's
just
like
another
another
thing
to
add
on
to
devops.
It's
a
nice
evolution
of
the
concept.
B
Right
right,
yeah,
I,
agree
with
you
and
it's
super
exciting
to
to
see
the
evolution
right.
We
have
devops
key
tops
and
then
platform
engineering,
so
for
people
wondering
it
to
change
their
job.
Title
from
devops
engineer
to
platform.j
wet
a
bit
because
it's
like
a
little
bit
different,
but
it's
still
valid
devops
super
valid
because,
as
CDF
said,
it's
a
it's
a
culture
and
practice
yeah.
So
I
just
wanted
to
go
through.
Also
the
session
that
read
that
hat
at
kubecon,
North,
America
Detroit.
B
First
of
all,
I
want
to
say
that
everyone
would
say:
oh
Detroit,
blah
blah
blah
I
see
some
picture
from
Detroit
looks
wonderful,
I,
don't
know
all
the
people
posting
some
nice
picture
from
Detroit,
so
first
I
I,
have
to
admit,
Detroit
looks
a
really
nice
city
and
and
then
I
I
wanted
to
share
with
you
the
list
of
the
the
session
that
that
I
read
that
head.
You
can
see.
B
B
Let
me
let
me
share
the
screen
so
because
I
have
the
tab
on
this
right,
you
can
see
it
yeah.
We
can
yes
yeah.
If
you
are
curious,
so
what
red
that
did?
Cubecon
North
America
2022
in
person
in
Detroit,
we
had
the
keynote
session
from
our
colleague,
edit
cicd,
isn't
reservable
for
software,
then,
as
we
say,
co-located
event
lots
of
cool
stuff
github's
con.
We
had
two
additional
talks.
B
B
C
Oh
so
cool
I
believe
that
talk
in
particular
had
a
really
interesting
demo,
not
just
using
istio
but
also
using
Argo
rollouts.
So
that's
the
latest
and
greatest
in
Argo
CD
Progressive
delivery,
enabling
you
to
do
things
like
Canary
deploys
or
blue
green
deploys
doing
like
a
b
testing
that
kind
of
stuff
and
hooking
that
in
with
istio,
you
get
like
a
really
nice.
A
C
A
C
A
That's
why
so
I
thought,
as
always
as
it
happens,
because
it
has
happened
in
the
past.
We
come
up
with
some
new
Solutions
and
then
we
tend
to
push
them
down
the
stack
towards
towards
the.
So
it's
a
couple
sources
of
adding
new
capability.
It
has
happened
to
cover
dentists
several
times,
so
that's
that
was
one
so
steal.
Our
service
mesh.
B
A
B
Like
you're
gonna,
you
know,
try
to
control
something
from
the
GitHub
site
and
then
service
mesh
is
gonna
control,
something
from
the
upper
layer,
but
they
actually
they
they
work
together
nicely
and
you
can
have
really
layer
really
good
multi-cluster
again
to
the
Red
Dot
device.
Edge.
Imagine
thousands
of
devices
you
want
to
deploy
your
app,
it's
openshift
key
tops
and
it
also
can
be
openshift.
Serverless
I,
don't
know
if
it
is
not
supported.
Yet
this
is
a
topology,
but
I
think
it
could
be
a
really
good
blueprint.
Yeah.
C
Yeah,
be
pretty
cool.
You
imagine
have
like
oh
you're,
thousands
of
edge
devices
and
doing
like
Progressive
deployments
just
to
like
some
of
them
to
like
test
how
it
goes
and
then
being
able
to
get
reports
back
on
how
it
went
and
then
progressively
deploy
it
out
to
other
things
or
roll
them
back
as
you
need
to
be
so
cool.
My.
C
B
We
gave
the
stage
a
little
bit
more
github's
gone
just
because
Harriet
is
here
with
us.
Thank
you
for
joining
us.
It
is
always
a
pleasure,
but
we
have
also
other
co-located
Evan
this.
This
is
cool
I
like
this.
This
is
cloud
native
reject.
If
you
are
not
accepted
to
cfp
of
cubecon,
you
can
apply
to
the
cloud
native
rejects.
It's
a
and
the
the
session
are
super
cool,
because
there
are
lots
of
good
sessions.
You
can
go
to
the
website
and
see
how
it
works.
B
Cloud
native
rejects,
if
you
see
the
shadow
I,
it's
always
a
super
super
interesting.
So
don't
worry
if
you
are
not
accepted
to
to
cubecon
there's
the
cloud
native
project,
which
is
a
even
cooler
yeah
but,
as
we
mentioned
security
con
K
native
con.
This
is
for
serverless
right.
Our
colleague
doing
a
talk,
content
container
food
serverless,
also
super
cool
right,
yeah.
B
B
Oh
yes
right!
So
you,
if
you're
curious
what
grid
that
did
like
a
cubecon
Beyond,
just
sponsoring
we,
we
we
contributed
a
lot
with
talks
and
the
round
table
and
panels,
because
there
are,
of
course,
a
contributor
to
the
kubernetes
community.
The
and
the
community
at
kubecon
meets
and
talk
about.
You
know
update.
You
can
see
the
see
groups
seek
apps
update
like
something
also
like
this.
You
you
see
many
companies
right.
They
work
together
in
the
same
open
source
project
and
then
they
have
their
product.
B
B
So
if
people
couldn't
attend,
they
can
join
the
session
virtually
or
deliver
the
session
virtually
but
again,
there's
lots
of
stuff
here:
operators,
smart
grain,
Computing,
so
again,
kubernetes
communities
talk
and
the
openshift
commons
Gathering,
which
is
happening
in
the
in
the
in
the
day
before
kubecon,
with
other
talks
other
people
attending.
If
you
want
to
have
a
look
of
what
is
opposition
common?
What
what?
Where
the
talk
is
from
organized
by
our
awesome
colleague
Diane.
B
B
B
A
You
guys
so
I
I
think
there
was
something
else.
I
think
it
was
a
bit
on
the
side,
but
and
if
you
guys
are
familiar
with
our
validated
patterns
there
are
they
keep
coming
out
and
and
they
they
are,
let's
say
so-
the
Upstream
version
of
the
the
patterns
and
then
they
get
validated
and
they
get
published.
A
Some
were
announced
during
the
qcom
and
it
goes
from
like
secure
supply
chain.
That's
a
cops
are
also
ansible,
Edge,
detox
and
I.
Think
I
can
actually
share
the
the
link
to
that
one
which
is
a
nice
one,
but
I
actually
encourage
you
guys
to
look
at
all
the
validated
patterns
they're
actually
quite
useful.
C
A
A
C
B
A
B
Customize,
it
yeah
that
that
is
the
right
link.
You
can
join
our
openshift
community
Channel.
We
talk
about
openshift
and
okt,
which
is
the
Upstream
version
of
openshift,
so
there
are,
almost
hundreds
of
people
feel
free
to
join.
We
we
share
also
the
link
of
these
shows
and
share
insight
about
openshift
openshift
architecture.
There
are
there:
are
people
really
passionate
about
about
the
cloud
native
evolution,
yeah,
so
I
think
it
was
a
great
recap.
B
I
just
wanted
to
to
mention
something
I've
seen
from
a
another
blog
post
from
the
Ambassador
Labs
I've,
seen
a
nice,
a
nice
talk,
a
nice
tweet
mentioning
in
the
Friday
keynote
that
the
future
is
built
on
Open
Standards.
So
this
is
a
nice
message.
I
think
I
can
copy
the
link
of
this
tweet
from
Daniel,
which
was
there
and
the
confidence
it
was
reporting
this.
Oh,
this
link
is
really.
B
C
B
You
are
able
to
click
this,
the
super
giant
link.
It
should
go
through
Daniel
treat
showing
that
the
the
future
depends
of
the
evolution
of
Open
Standards.
This
is
really
important.
If
we
don't
have
an
open
standard,
we
cannot
start
implementing
anything
in
open
source
right.
Also,
if
you
look
at
containers,
containers
are
these
oci
standard
for
creating
container
image
and
anyone
can
Implement
its
version.
Docker
podman
anyone
can
go
and
implement
this
version,
but
if
the
standard
is
on
not
open,
there's
nothing
really.
We
can.
C
And
in
the
keynote
by
the
from
Priya
Sharma
who's,
the
director
of
the
cncf
was
also
tracking
about
the
importance
of
community
and
maintainers.
So
as
part
of
Open
Standards,
we
need
people.
We
need
everyone
working
together
and
figuring
this
out
as
a
group,
because,
if
we're
not
having
lots
of
different
voices,
then
it's
going
to
be
like
too
specific.
So
we've
got
to
have
the
Open
Standards
and
we've
got
to
have
lots
of
contributors.
B
Right
right
and
I
think
cubecon
is
a
really
nice
Community.
They
organize
the
participation
in
a
nice
way.
Also
joining
this
conference
person
is
a
good
opportunity
to
meet
the
community
to
join
this
community.
There's
the
sake
groups.
There
are
the
you
know,
working
group.
Everything
is
really
open,
but
I
agree.
We
need
to
work
on
more
on
how
to
involve
those
people,
because
maybe
it's
not
easy
at
the
beginning
right
or
they
feel
intimidated
right.
Like
oh
I'm,
not
the
super
mega
engineer.
B
How
can
I
join
this
community,
but
actually
anyone
can
join
doing
anything
right,
documentation,
software
testing
or
just
being
there
and
and
being
part
of
this
awesome
community
I
want
to
close
this
I'm
going
to
leave
you
the
link
of
Daniel
block,
because
he
was
doing
a
recap
of
everything
because
it
was
there.
So
thanks
Daniel
for
this
blog.