►
Description
Welcome to the Red Hat OpenShift Product Management Team's What's Next Livestream!
Here we unveil our highly anticipated product roadmap, showcasing the future of OpenShift and the exciting features and updates we have in store. Our talented product management team will walk you through the roadmap, highlighting the key milestones, advancements, and innovations planned for OpenShift.
👇Grab the downloadable copy of the slide deck here! 🚀
https://speakerdeck.com/redhatlivestreaming/whats-next-in-openshift-q2-cy2023
And, as always, please engage with the team, ask questions, and get a better understanding of the future direction of OpenShift.
00:00 Live Stream begins
01:50 Introduction
09:00 Software supply chain security
20:31 Multicluster management, governance, and security
28:14 Red Hat Cloud Services
34:10 Workloads and developer experience
47:47 Core platform
01:11:20 OpenStack Services coming to OpenShift
01:13:08 Telco & Edge
01:16:22 Networking and Observability
01:22:56 Closing
A
A
Hello,
everyone
welcome
to
the
what's
next
in
openshift
for
Quarter
Two.
We
do
this
kind
of
sessions
once
every
quarter
or
so
every
other
session
is
about
a
roadmap
update
and
the
other
one
about
what's
new
in
a
specific
version
of
openshift
today's
session.
What's
next
offers
you
a
glimpse
of
what
we've
been
working
in
different
aspects
of
the
products
and
we
are
aiming
to
do
over
the
next
six
to
18
months?
A
That
will
be
helping
me
to
walk
you
through
these
details
and
there
are
filter
details
Beyond,
whether
they
speak
throughout
the
session
that
will
be
available
in
the
appendix
of
this
slide
deck
both
display
deck
and
the
recording
will
be
shared
with
you
after
the
session
during
this
session.
If
you
have
questions,
please
drop
it
in
in
the
Q
a
section
of
fun
time,
and
my
colleagues
are
on
the
on
the
live
stream.
A
But
let
me
set
the
context
a
little
bit
before
we
get
into
the
details
of
the
roadmap
updates,
and
this
is
really
all
centered
around
the
open,
hybrid
Cloud
strategy
and
message
that
we
have
at
red
hat
and
openshift.
For
the
past
10
years
we
have
been
making
the
case
for
opencube
cloud
and
our
customers
have
been
innovating
competing
and
succeeding
really
through
the
application
that
they
build
for
the
hybrid
Cloud.
These
applications
might
be
traditional
logic,
applications
that
they
have
been
building
for
for
many
years
or
more
modern
Cloud
native
applications.
A
There
are
sometimes
apps
that
customers
are
building
in-house
themselves
through
their
developers
or
application
that
they
purchase
from
the
isps
or
Si
deliver
those
applications
and
to
them,
and
our
customers
have
been
deploying
these
applications
across
a
range
of
footprints
as
well
from
physical
data,
centers
all
the
way
to
the
public
clouds
and
also
more
and
more
cases
we're
seeing
that
they
are
deploying
these
applications
at
and
openshift
builds
on.
Top
of
Rel
has
been
the
foundation
of
this
journey
for
our
customers.
B
A
A
Configuring
this
cluster
is
in
a
consistent
manner,
has
a
challenge
having
an
overview
of
compliance,
how
we
can
Define
the
security
boundaries
and
security
rules,
that
consistency
are
applied
to
all
these
clusters.
That
becomes
a
pain
for
for
the
customer,
and
it's
not
even
just
about
infrastructure.
If
you
look
at
any
of
our
customers
and
the
infrastructure
is
obviously
heterogeneous
with
customers
having
a
combination
of
physical
slope,
servers,
virtualization
and
one
or
two
public
clouds,
combined
with
possibly
private
cloud
and
now
moving
to
the
edge
to
edge
deployments.
C
A
More
recently,
we
are
seeing
a
watch
from
a
lot
of
our
customers
and
vendors
to
bring
more
intelligence
to
these
applications
incorporating
more
AI
ml
data
analytics
in
these
apps
and
those
apps
also
need
to
be
managed
alongside
the
rest
of
the
app
portfolio
that
customers
have,
combining
that
with
a
combination
of
waterfall
and
agile
methodology
that
we
see
our
customers
have
different
ways
of
cicd
for
delivering
this
application.
Different
release,
policies
and
skill
sets
really
you've
been
able
to
lose
organizations,
and
these
are
a
lot
of
challenges.
A
Complicit
is
that
almost
every
customer
will
look
at
is
dealing
with,
and
it's
it's
specific.
It
becomes
particularly
becomes
a
problem
for
them.
Then
this
is
not
really
the
core
of
their
visitors.
This
is
not
where
they
should
be
spending
their
time
and
within
openshift
have
a
cloud
platform.
These
are
the
challenges
that
we
are
trying
to
add
a
little
bit
from
the
bottom,
the
lowest
player
with
kubernetes
cluster
services
and
platform
services
that
help
the
customers
run.
A
Their
hybrid
Cloud
applications
to
developer,
tooling
and
capabilities
that
make
their
developers
and
application
developers
more
productive
and
to
keep
looking
around
management,
Fleet,
Management
and
security,
so
that
they
can
consistently
manage
a
fluid
of
cost.
The
Clusters
apply
policies
to
them
and
ensure
security
across
the
entire
field
of
custom,
regardless
of
where
these
clusters
are
running
on
any
type
of
footprint
that
they
have
openshift
exists
in
in
two
distinct
flavors.
A
It
exists
as
a
managed
service,
and
we,
and
also
as
a
self-managed,
offering
managed
Services
we
partner
with
the
cloud
providers
co-engineer
operate
and
manage
these
Services
together
with
the
cloud
provider,
so
our
customers
can
start
up
and
use
these
Services
quickly.
Examples
of
that
is
often
ship
dedicated
on
AWS
and
Google.
Cloud
you'll
have
openshift
on
IBM
Cloud
Microsoft
Azure
ran
out
openshift
Android
hat
openshift
service
on
AWS.
Our
cell
service
offerings
includes
openshift
pattern
plus
container
platform
and
kubernetes
energy.
A
These
are
designed
for
customers
who
want
to
take
a
platform
running
on
premises,
infrastructure
that
being
a
physical
data
center
or
public
cloud
or
even
image,
but
customers
themselves
they
operate.
The
platform
competitive
is
designed
to
be
able
to
run
anywhere
that
customer
needs
in
any
shape
with
any
mode
any
type
of
infrastructure.
C
My
name
is
Maria
I'm,
one
of
the
parents
of
the
secure
like
pillar
of
openshift.
We
handle
security
and
I'm
gonna
talk
about
the
supply
chain
security
here
supply
chain
security
has
increased
its
importance.
Now,
it's
more
important
than
ever.
We
see
that
you
can.
You
can
go
to
the
next
slide.
Cmac.
C
Yeah
we
we
see
that
attacks
have
increased
more
than
700
over
the
last
three
years,
and
also
we
envisioned
that
by
2025
half
of
the
organizations
worldwide
will
be
affected
by
one
of
these
attacks.
It's
not
only
one
of
the
main
causes
of
data
breaches,
but
also
it
incurs
high
costs
for
the
companies.
We
are
talking
about.
Downtime
cost
data,
breach
costs,
and
you
know
in
many
cases
run
run
some
that
it
needs
to
be
paid
as
well.
C
So
by
now,
I'm
sure
that
we
are
all
very
familiar
with
the
executive
order
that
the
U.S
signed
two
years
ago
to
improve
the
nation's
cyber
security.
So
this
this
came
to
for
to
drive
the
need
across
companies
to
invest
in
supply
chain
and
supply
chain
actually
is
includes
two
key
elements.
One
of
them
is
to
secure
the
tools
and
processes
that
compromise
the
supply
chain
itself
and
also
evaluating
the
security
of
the
software
produced
by
the
supply
chain,
so
the
silver
bill
of
materials
sometimes
commonly
refer
as
S1.
C
C
So
in
red
heart,
we
are
invested
in
tools
that
are
already
available
in
openshift.
To
achieve
this,
there
are
two
specific
tools
that
are
important
to
mention.
We
have
the
openshift
pipelines
and
openshift
getups,
so
openshift
pipelines
is
a
serverless
cicd
system.
Your
customers
can
use
tecton
to
define
an
automate
application,
Pipelines
and
also
open.
Zip
githubs
is
a
continuous
deployment
tool
based
on
github's
workflows.
C
The
customers
can
use
igocd
and
get
as
a
single
source
of
Truth
to
manage
infrastructure
and
application
configuration.
Now.
Let's
look
what's
coming
in
openshift
pipelines
in
the
roadmap.
Enterprise
contract
is
a
set
of
tools
to
maintain
the
software
supply
chain
security.
It
also
Define
and
enforce
policies
like,
for
instance,
artifact,
provenance
and
policy
validation.
C
This
functionality
will
be
integrated
in
pipelines
as
code.
This
will
help
developers
visualize
and
take
action
on
Pipeline
Branch
triggers
by,
for
instance,
pull
and
merge
requests
Etc
and
also
an
additional
support
to
the
developers
in
pipelines.
As
code,
we
will
have
the
option
to
validate
PRS
with
the
user
provided
gpdp.
C
Red
hub
will
also
release
its
own
tecton
catalog,
with
a
verified
and
trusted
task
pipeline
bundle
which
includes
tasks
like,
for
instance,
vulnerability
scanning
code
scanning
that
are
coming,
for
instance,
from
ACS
or
any
of
the
partner
ecosystem
that
we
have.
Openshift
pipelines
also
focuses
on
mitigating
running
bills,
with
elevating
privileges
by
leveraging
leveraging
kubernetes
username
spaces.
C
C
We
will
also
be
investing
on
how
github's
operator
manages
Trust.
We
are
planning
to
make
improvements
in
certificate
management
within
Ardo
City,
but
also
the
github's
interaction
with
certificates
in
openshift
in
the
area
of
secret
management
integration,
rather
than
investing
in
integrating
on
a
specific
secret
manager
individually.
We
are
evaluating
external
sequence
operator
and
also
Secrets
store,
CSI
driver
so
that
the
customers
can
choose
which
secret
manager
they
want
to
use,
and
they
can
already
use
the
ones
that
they
are
using
in
your
particulars
also
to
support
their
requirement
for
end-to-end
auditability
of
supply
chain.
C
.Io,
which
is
our
hosted
registry
service,
we
are
investing
heavily
in
supply
chain
security
to
Claire,
which
is
the
static,
vulnerability
analysis
solution
for
containers.
It's
going
to
cover
more
application
dependencies
like,
for
instance,
node.js
libraries,
ruby,
gems
or
online
modules
by
adopting
the
open
source
vulnerability
database
project.
C
C
C
Let's
go
to
the
next
and
talk
about
red
hat
trusted
application
pipeline
for
a
bit.
This
was
big
news
in
the
red
hat
Summit
and
what
is
it?
It's
a
multi-tenant
service
available
in
preview
online
at
Red,
hat.ht
trusted,
which
is
the
link
that
appears
right
there
on
the
slides
and
it
helps
to
you
to
create
secure
content
or
cicd
pipelines
in
minutes
without
the
complexity
of
having
different
tools.
C
Previous
slide,
please!
Yes!
So
let's
look
at
what's
coming
in
the
near
term,
so
we
are
going
to
invest,
to
allow
users
to
create
additional
workspaces.
Their
workspaces
or
manage
users
are
back
in
their
workspaces,
which
is
currently
not
available.
At
this
moment.
This
will
come
soon.
We
will
also
add
a
specific
capabilities
for
operator
Developers,
so
this
is
mostly
targeted
for
red
heart
productization,
but
it's
available
for
anyone.
C
The
long-term
vision
includes
exploring
single
tenant
deployments
as
well,
as
you
know,
expanded
their
metric
support
available
today.
Currently,
we
support
Python
and
golang,
but
Java
and
npm
will
be
added
soon
and
possibly
we
are
planning
to
invest
in
John
and
Ross
after
we're
also
exploring
integration
of
advanced
roller
strategies
based
on
Argo
rollouts.
C
So
if
we
go
next,
let's
talk
a
bit
like
how
this
whole
ecosystem
that
we
are
building
in
red
hat
like
goes
together
with
the
other
products.
So
we
already
talked
about
a
couple
of
different
tools.
Now,
let's
talk
about
how
ACS
is
able
to
work
with
our
staff?
So
if
you
are
a
user
of
red
hand,
Advanced
faster
security-
and
you
are
also
going
to
use
red
hat
trusted
application
pipelines-
you
can
rely
on
the
features
that
are
already
available
in
advanced
cluster
security
cloud
service,
for
you,
like.
C
Some
of
the
features
that
you
can
benefit
from
are,
for
instance,
scanning
images
for
vulnerabilities
at
build
time
with
openshift
Python's
tasks.
You
can
also
monitor
system
level
events
with
containers
to
detect
anomalous
activities,
also
being
able
to
automatically
respond
with
kubernetes
Native
controls.
C
You
can
use
the
pre-built
policies
to
the
tech,
for
instance,
privilege
escalation,
also,
crypto
mining
different
types
of
exploits
assess
compliance.
There
are
hundreds
of
consoles,
for
example,
PCI
DSS.
We
have
HIPAA,
we
have
the
CIS
benchmarks
and
also
we
are
able
to
Baseline
the
network
activity
to
visualize
allowed
versus
active
traffic
directed
to
the
network
graph,
and
with
this
I'm
going
to
hand
it
off
to
Warren.
D
Hello,
my
name
is
Brad
weidenbenner
I'm,
a
product
manager
on
Advanced
cluster
management
for
kubernetes
and
Oren
will
be
coming
up
next.
So
today,
I'm
excited
to
share
with
you
some
updates
regarding
management,
security
from
the
left
to
the
right
and
from
Day
Zero
onward
near
kubernetes.
Journey
next
slide,
please
cymac.
D
All
right,
customers
across
all
verticals
are
deploying
kubernetes
and
abundance
and
the
red
hat
Advanced
cluster
management
for
kubernetes
product
management
team
is
a
meeting
with
you
and
listening.
We've.
You've
consistently
relayed
your
concerns
and
needs
in
the
area
of
fleet
observability,
Fleet
governance
and
requirements
for
scale
to
accommodate
Edge
devices.
In
your
your
new
philosophy,
around
cattle
clusters
respond
to
your
needs
by
focusing
our
roadmap
efforts
around
observability
governance
and
scale,
ensuring
that,
as
you,
evolve,
we're
ready
and
prepared
to
deliver
in
these
times
of
economic,
intense
economic
challenge.
D
Further
scrutiny
on
every
dollar
spent
has
platform
teams
focusing
on
underutilization
like
never
before.
We
intend
to
bring
those
tools
to
your
team
to
help
in
this
effort
and
all
while
maintaining
strict
governance
controls
across
our
growing
Fleet
and
expanding
Integrations
and
the
risk
and
compliance,
so
we
need
to
ensure
you're
covered.
Providing
all
these
features
from
the
central
Data,
Center
and
out
to
the
edge
has
always
been
core
to
our
mission
will
continue
to
evolve
areas
of
the
Global
Hub
offering
to
ensure
you
have
a
seamless,
end-to-end
experience.
D
We're
going
to
highlight
a
few
examples
of
this
commitment.
In
the
following
slides
next
slide,
please
slide
Mac
all
right.
Advanced
cluster
management
continues
to
focus
on
features
across
the
five
key
pillars,
including
cluster
life
cycle
application,
life
cycle,
multi-cluster,
networking,
observability
and
governance.
D
These
ladder
to
compromise
the
top
usage
areas
for
Red
Hat
customers
that
are
well
long
in
their
kubernetes
usage
and
growing
rapidly
rapidly
we're
going
to
zoom
in
on
a
few
highlights
there
and
the
fleet
observability
customers
do
continue
to
stress
the
need
for
Clear
signals
of
their
platform,
performance
and
overall
health
of
the
business
by
viewing
application.
Level
metrics
additionally
they're
under
increasing
pressure
to
reduce
cost
and
provide
a
more
efficient
experience
both
for
operations
and
app
Dev
scenarios.
D
The
end
result
is
increased
needs
for
fine-grained.
Our
back
capacity
management
and
ensuring
Fleet
alerts
are
less
noisy
and
more
actionable
and,
of
course,
keeping
our
eye
on
growth
and
scale
needs
all
the.
While
we
will
continue
to
evolve
our
architecture
and
capabilities
to
ensure
we
stay
a
step
ahead
of
new
verticals
and
environments
where
kubernetes
is
being
used
and
then
within
Fleet
governance.
The
common
refrain
from
customers
that
they
need
additional
compliances
or
to
meet
the
needs
from
audit
and
secops
control
teams.
D
This
is
to
provide
an
easier
onboarding
and
life
cycle
experience
around
kubernetes
operator
deployments
across
your
Fleet,
as
always
we're
appreciative
of
the
appreciative
of
the
customer
feedback
and
looking
forward
to
hearing
from
you,
so
that
we
can
shape
our
product
and
plan
our
future
capabilities
together.
So
please
reach
out,
and
really
the
best
way
to
reach
out
is
to
your
account
teams
and
they
can
get
you
in
touch
with
the
appropriate
product
managers,
but,
yes,
we're
very
happy
to
meet
with
customers.
D
D
Yes
from
Advanced
cluster
security.
This
is
part
of
our
unified
experience.
We
keep
investing
in
the
portfolio,
we'll
be
delivering
vulnerability.
Scanning
support
for
images
stored
in
Mirror
Registries
to
support
openshift
customers
using
these
type
of
Registries,
mainly
in
air-gapped
environments.
Those
disconnected
scenarios
is
where
we'll
see
that
we
will
consolidate
the
scanner
to
clear
version
4,
which
is
the
one
that
Quay
uses.
D
This
ensures
accurate
and
consistent
results
across
products
now
also
as
well
to
help
open
shift
in
kubernetes
cluster
admins
quickly,
adopt
Advanced
cluster
security
and
add
devsecops
users
into
the
ACs
console.
That's
Advanced
cluster
security,
the
ACs
acronym.
We
are
looking
to
provide
a
direct
mapping
of
our
back
from
the
the
secured
clusters
into
ACS.
D
Lastly,
on
the
unified
experience,
we
recently
introduced
the
concept
of
the
ACs
deployment
collections,
allowing
users
to
define
a
role-based
scope
for
repeatable
use.
We
plan
to
expand
the
collection
implementations
across
the
products
View
and
the
filters
Define
once
used
anywhere
next
slide.
Please
cymac
yeah
yeah
again
we're
we're
continuing
on
the
unified
experience
and
for
advanced
cluster
security.
We
keep
investing
in
delivering
vulnerability,
scanning
support.
D
We'll
consolidate
the
scanner
to
clear
version,
four
and
and
similar
to
the
the
last
and
and
we're
also
introducing
the
concept
of
deployment
collections
slide.
Three,
please
cymac
next
slide
and
then
under
security
everywhere,
to
make
it
easier
for
users
to
consume
and
share
vulnerability
information
with
other
stakeholders
which
may
not
have
access
to
tools
to
the
tool.
A
downloadable,
on-demand
image
vulnerability
report
will
be
accessible,
that's
pretty
powerful
when
you
can
download
that
and
provide
it
to
who's
requesting
it
or
archive
it.
D
In
the
area
of
policies,
we
plan
to
support
ACS
policies
as
code
to
support
a
get
Ops
approach
and
to
use
ACS
an
environment
where
an
Opa
gatekeeper,
our
our
kyvernois
used
new
system
policies
will
be
at
an
area
of
networking
similar
to
kubernetes
admin.
Network
policies
to
allow
admin
users
to
ensure
certain
guard
rails
are
being
followed
without
the
need
to
audit
HTML
file.
D
Many
next
many
customers
have
requested
that
users
that
have
namespace
scoped
access
and
kubernetes
or
project
access
and
openshift
be
allowed
to
only
view
update
those
ACS
resources
for
their
designated
namespaces.
This
effort
will
be
to
provide
scope,
permissions
to
resources
and
workflows
commonly
used
by
namespace
admins,
such
as
policy
management
or
network
graph
views.
D
Next,
we
have
heat
maps
in
the
network.
Graph
will
allow
the
users
to
Overlay
vulnerabilities
of
policy
violations
on
the
graph
for
a
visual
representation.
This
can
help
users
identify
and
prioritize
problem
areas
for
the
remediation
next
slide.
Cymac,
please,
yes,
platform,
consistency.
We
are
investing
in
allowing
our
customers
to
run
ACs
on
a
wider
set
of
secured
clusters.
For
this
reason,
we'll
deliver
the
new
go
re,
BPF,
collection
method.
This
allows
our
customers
to
run
their
secured
clusters
on
top
different
Linux
kernel
versions,
as
well
as
running
ACs
on
IBM
Rock.
D
In
addition,
easier
management
platform,
we
include
Auto
renewal
of
internal
certificates
to
ensure
compliance
and
security
requirements
are
always
met
without
the
need
of
customer
interaction.
That's
pretty
powerful
not
having
to
time
had
counten
resources
to
those
certificate.
Renewals
we're
working
to
deliver
a
new
compliance
experience
in
ACS,
using
compliance
operators,
a
main
source
of
information
while
improving
the
capabilities
to
schedule.
Compliance
scans
as
well
build
a
tailored,
build
tailored
profiles
and
analyze.
Historical
information
I'd
like
to
now
hand
it
off
to
orenkashi.
E
Hey
Brad,
thank
you
very
much
for
taking
us
through
that.
We're
going
to
talk
a
little
bit
about
red
hat
cloud
services
and
I
think
that
before
kind
of
getting
started,
it's
also
important
to
understand
a
little
bit
about
why
many
of
our
customers
decide
to
use
Redi
cloud
services
and
in
specific
managed
openshift
when
they
kind
of
get
started.
E
So
when
our
customers
decide
to
utilize
their
services
and
manage
open
shift
in
specific
the
reasons
for
doing
so,
usually
fall
into
a
few
different
areas,
some
of
which
you
see
here
on
the
screen
so
kind
of
starting
with
you
know,
quick
time
to
value,
and
what
this
is
really
about
is
that
when,
when
we
talk
to
customers,
we
ask
them,
you
know
how
long
does
it
take
for
them
to
get
Hands-On
keyboard?
And
you
know
when
they're
really
able
to
do
the
things
that
they
want
to
do.
E
They
want
to
start
to
focus
on
on
that
activity.
We
usually
hear
something
in
the
days
to
weeks.
Time
frame
we've
had
a
rarer
few
that
are
in
the
months
time
frame,
but
when
you
contrast
that,
with
what
you
get
with
Reddit
openshift
cloud
services
of
being
up
and
running
in
as
little
as
10
minutes,
they're
really
delivers
a
very
high
value
to
them.
To
be
able
to.
You
know,
start
on
the
on
that
Innovation
on
the
stuff.
That's
really
important
to
them.
E
So
because
of
that,
and
because
we
take
on
a
lot
of
that
day,
one
and
day
two
activities
they're
able
to
operate
a
lot
more
efficiently
and
what
I
mean
by
that
is
that
you
know.
Instead
of
having
you
know
the
folks
on
their
team
kind
of
focusing
on
the
plumbing,
putting
the
environment
together.
Getting
that
Hardware.
Getting
the
you
know,
cluster
built
out
going
through
the
securitization
process
of
everything
and
then,
and
only
then
really
getting
Hands-On
keywords
to
do
the
thing
that
they
wanted
to
do.
E
They're
able
to
start
with
that
in
you
know
as
little
as
10
minutes
and
they're
able
to
utilize
those
folks
to
focus
on
those
higher
level
and
those
higher
value
activities.
So
they
get
that
they
get
that,
coupled
with
24x7
support,
we
do
proactive
monitoring,
so
you
know
we
keep
our
eyes
on
the
cluster,
making
sure
that
everything
is
operating
as
it
should
be,
and
should
it
not
it'll
be
our
folks
that
end
up
getting
paid.
E
You
know
just
for
one
hour
whether
you
want
to
consume
it,
for
you
know
a
day
a
week,
a
month
a
year
three
years.
Really
the
choice
is
yours.
We
have
customers
that
are
really
going
through
the
gamut
of
this,
some
that
are
used
really
using
it
in
the
true
Cloud
native
sense
of
spitting
up
a
large
number
of
clusters
to
do
the
testing
that
they
need
to
do
and
couple
of
hours
later,
putting
it
back
down
to
those
that
commit
for
the
long
term
and
to
realize
the
greatest
amount
of
discounting.
E
So
on
the
roadmap
front
and
on
the
things
that
are
coming
down,
the
pipe
starting
with
the
Azure
Red
Hat
openshift,
there
are
two
major
pieces
of
work
that
will
be
coming
down
in
the
next
couple
of
months
and
into
next
year,
and
this
is
enabling
Arrow
to
work
with
managed
identities
and
workloaded
entities
for
short-term
credentials.
We'll
also
be
working
on
implementing
hosted
control
plans,
as
well
as
expanding
Regional
availability
instance
type
supported,
as
well
as
the
maximum
cluster
sizes.
E
We're
also
improving
the
customer
experience
with
integration
of
signals
with
Azure
Monitor,
and
also
supporting
custom
nsgs
on
the
Rosa
side
or
red
hat
openshift
service
on
AWS
we're
actively
working
with
the
fedramp
pmo
on
a
fedramp
high,
offering
we're
also
expanding
features
with
terraform
new
regions
and
the
new
instance
type
Support
also
hosted
control.
Planes
was
released
as
a
a
tech
preview
feature
over
Summit
and
we
will
be
moving
that
to
GA
later
this
year.
Next
slide.
E
On
the
openshift
dedicated
side
from
the
gcp
front,
we've
been
making
significant
Investments
here,
such
as
adding
the
available
the
ability
to
purchase
from
the
gcp
marketplace
as
well
as
shared
vpcs.
We
are
expanding
the
offering
to
include
new
instance
types
and
regions
and
also
working
on
bringing
support
for
short-term
credentials
with
workload,
identity
Federation.
E
On
the
AWS
front,
we
are
expanding
the
capabilities
of
managing
Ingress
to
more
closely
align
with
self-managed
ocp,
as
well
as
expanding
the
service
log,
to
include
more
notifications
and
more
customizability
next
slide,
please,
and
with
the
ACs
right
so
in
May,
2023
ACS
cloud
service
was
released
with
limited
availability
in
North,
America
and
Europe.
This
is
available
on
the
AWS
Marketplace
and
it
comes
with
full
support
by
red
hat,
with
a
99.95,
SLA
and
also
connectivity
for
a
local
registry.
E
In
the
later
part
of
this
year
we
will
announce
General
availability
of
the
service,
and
it
includes
a
60-day
trial
of
the
service
and
also
capabilities
within
the
platform
to
send
notifications
without
configuring,
a
Notifier
in
the
beginning
of
next
year.
So
2024
we
plan
to
expand
to
APAC
regions
as
well
as
to
Azure.
We
are
also
actively
working
on
compliance,
certifications
with
industry
standards
such
as
ISO
and
PCI
DSS,
and
with
that
I'll
turn
it
off
to
cool
stuff.
F
Hi
everyone
in
this
section
I
will
focus
on
what's
coming
next
for
some
of
the
code
developer
and
workload
experience
in
in
openshift,
starting
with
next
slide,
please
yeah,
starting
with
openshift
serverless,
which
is
a
comprehensive
Enterprise
grade,
serverless
solution
built
on
top
of
K
native
project.
So
we
have
identified
three
key
themes
that
we
will
be
focusing
to
shape
the
future
of
openshift
serverless.
The
first
thing
is
enhancing
the
user
experience.
F
To
achieve
this,
we
are
working
on
improving
the
debt
console
CLI
and
the
ID
functionalities
for
microservices
and
functions.
Additionally,
we
are
also
exploring
integration
with
kubernetes
Native
effectments,
enabling
developers
to
build
Cloud
native
applications
with
effortless
event-driven
communication.
Moreover,
we
are
also
focusing
on
the
orchestration
and
choreography
of
microservices
and
functions,
facilitating
the
development
and
the
deployment
of
event-driven
business
logic
in
a
serverless
manner.
The
second
thing
is
around
security.
Obviously,
we
understand
the
importance
of
building
Cloud
native
applications
that
comply
with
industry
security
standard.
F
As
part
of
our
effort,
we
are
prioritizing
end-to-end
encryption
for
both
internal
and
external
services
within
the
serverless
environment.
We
are
also
working
on
enhancing
security
through
broker
and
channel
authentication
and
authorization.
Furthermore,
on
the
security
front,
multi-tenancy
is
a
crucial
feature
for
a
serverless
platform
and
we
will
be
developing
a
solution
using
service
mesh
for
both
Eventing
and
surveying
purpose.
The
third
thing
which
you
will
be
focusing
for
our
friendship
surveillance
is
around
platform
enablement,
so
we
will
be
committed
to
serving
various
needs
and
expanding
capabilities
of
openshift
serverless
with
openshift
AI.
F
Additionally,
we
also
aim
to
extend
the
capabilities
to,
for
example,
a
single
node,
openshift
or
microchip,
and
we
are
also
exploring
the
integration
of
custom
automatic
scalar
for
scaling
even
sources
along
with
a
site
operator
and
Gateway
API
next
slide,
yeah
coming
to
the
next
set
of
tools
which
is
basically
used
to
build
test,
deploy
your
applications
and
infrastructure.
Openshift
provides
two
layer
products,
openshift
pipelines
built
on
tecton
and
official
databs
built
on
top
of
on
the
city.
So.
C
F
Openshift
pipelines,
many
of
you
might
have
already
noticed
in
1.11,
we
introduced
effect
on
results
as
a
tech
preview.
Techtron
results
address
the
challenge
of
retaining
pipeline
logs
and
metadata
for
an
extended
period.
We
have
some
exciting
plans
to
further
enhance
the
user
experience
and
also
extend
the
support
for
various
storage
providers.
Etc
with
electron
results.
One
other
extension
of
detect
on
results
will
be
providing
an
CI
oriented
dashboard
inside
the
openshift
console.
F
Another
significant
area
of
focus
for
openshift
pipelines
is
pipeline
as
code,
which
is
basically
an
open,
YouTube
CL
solution
built
on
top
of
tecton.
This
approach
follows
the
getoff's
kind
of
methodology
and,
as
pipeliner's
code
gains
more
traction,
we
aim
to
strengthen
its
native
integration
with
Git
providers,
particularly
in
terms
of
repository
permission
policies.
We
also
plan
to
integrate
pipeline
as
code
with
electron
chains
and
but
then
we
we
are
actively
working
on
automating,
Pipeline,
templating,
based
on
repository
content
within
pipeline
S4,
other
area
or
Focus
for
openshift
pipelines.
F
We
are
committed
to
improving
workflow
customization
in
openshift
pipeline,
specifically
focusing
on
caching,
nested
pipelines,
manual
approval
and
considering
the
growing
adoption
of
Techron
and
its
usage
in
production
in
the
environment.
We
are
conscious
of
the
performance
consideration
to
address
this.
We
will
be
introducing
pipeline
resource
quotas
and
advanced
concurrency
controls,
enabling
customers
to
fine
tune.
The
Techron
footprint
more
within
their
cluster
come
into
openshift
githubs.
In
the
most
recent
GitHub
versions.
1.9,
we
introduced
a
tech
preview
of
Arco
rollouts
for
Progressive
delivery.
F
We
will
be
working
closely
with
our
users
to
design
and
Implement
UI
integration
points
in
both
openshift
Dev
console
as
well
as
other
City.
We
have
also
got
a
lot
planned
for
automation
this
year,
with
a
lot
of
work
in
our
Upstream
Community
already
underway,
highlight
from
this
area
will
be
a
proposal
to
support
Dynamic
value
income,
not
only
through
Health,
but
for
any
other
user
who
needs
to
flash
cluster
data
at
runtime.
Finally,
as
our
customers
scale
up
and
expand
their
use
of
bitops,
we
will
be
iterating
alongside
them
and
most
excitingly.
F
F
Another
important
significant
area
for
developers
is
openshift.com
if
you
have
not
already
started
building
your
own
native
integration
into
openshift
console
now
is
an
excellent
opportunity
to
do
so.
We,
the
introduction
of
dynamic
plugins,
enables
users
to
create
Advanced
integration
that
seamlessly
integrate
within
the
openshift
drive
console
Dynamic
plugins.
It
got
G8
in
one
4.12
and
post
4.12.
We
expect
lot
of
great
Improvement
based
on
feedback
from
partners
and
customers
like
support
for
react
tools
and
more
lupus
documentation
and
examples.
F
Look
out
for
new
extensions,
like
project
creation
model
and
new
components
like
charting
that
that
will
be
supported.
We
will
also
make
sure
that
the
template
info
stays
up
to
date,
since
it
is
actually
a
great
starting
point
for
creating
awesome,
plugins
and
we
will
add
examples
of
using
apps
testing
framework,
so
users
can
keep
them
plugin
508
compliant.
Finally,
we
will
be
supporting
pf5
and
react
Route
6
in
the
future.
F
We
see
the
value
in
enabling
customers
and
partners
to
be
able
to
customize
the
openshift
console
and
I'm
dedicated
to
building
a
plus
plus
screen
on
the
next
slide
yeah.
So
migration
toolkit
for
application
6.2
will
be
released
in
August
14..
In
this
release,
we
are
introducing
a
new
module
specifically
designed
to
manage
migration
waves.
Additionally,
we
will
also
enrich
our
integration
with
atlasm
jira,
which
will
bring
powerful
planning
capabilities
to
empty
it.
We
also
along
with
6.2.
F
We
have
identified
three
key
themes
that
we
will
be
focusing
to
shape
the
future
of
migration
toolkit.
The
first
of
them
is
migration
guidance.
We
firmly
believe
that
bringing
Legacy
application
to
openshift
can
significantly
allow
software
delivery
performance
without
the
need
of
complete
the
architecture
or
rewriting
under
the
theme
of
gather
inside
MK,
plays
a
pivotal
role
in
identifying
Trends
and
providing
insights
across
pipe
application
portfolio
at
scale
and
lastly,
under
NTA
has
traditionally
focused
on
static
analysis
of
application,
binaries
and
source
code.
F
F
F
So
our
operator
framework
is
evolving
and
we
are
preparing
for
the
much
anticipated
release
of
operator
life
cycle
manager
or
olm
version.
1.0
on
1.0
basically
represents
a
culmination
of
all
the
learnings
that
are
gathered
from
openshift
releases
over
the
years
and
it
brings
a
redesigned
lifecycle
model
to
the
table.
Let
me
highlight
some
of
the
key
features
that
you
can
expect,
so.
Firstly,
olm1.0
will
introduce
a
fully
declarative
and
detox
20
workflows
for
managing
the
life
cycle
of
operators.
F
This
will
streamline
the
process
and
provide
a
seamless
experience
for
administration
and
srets.
Furthermore,
olm
1.2
empowers
admins
and
SRE
teams
with
more
control
over
granting
access
to
the
apis
provided
by
an
open
shift
to
the
cluster
users.
This
granular
control
ensures
enhanced
security
and
governance
within
the
operated
ecosystem.
One
exciting
addition
is
basically
the
final
control
for
operated.
Upgrades
admins
will
be
able
to
select
a
specific
Target
version
for
updates
or
set
updates,
who
are
automatic
but
limited
to
jet
stream
Updates.
F
This
flexibility
will
allow
addressing
critical
vulnerabilities
promptly
while
minimizing
the
risk
of
breaking
changes.
We
have
also
focused
on
simplifying
the
onboarding
process
for
new
operators.
Olm
1.0
expands
its
support
to
operators
packaged
with
plain
kubernetes
manifest
and
even
Health
jobs.
This
means
that
you
can
ship
any
Resource
as
part
of
the
lifecycle
management,
making
it
easier
for
openshift
customers
and
certified
Partners
to
manage
their
in-house
built
operators
and
join
our
ecosystem
with
operator
framework
next
slide.
F
We
have
announced
the
death
preview
of
red
hat
developer
Hub
in
direct
Summit
and
by
the
end
of
this
month
you
will
have
the
opportunity
to
try
it
out
today.
So,
let's
focus
on
what
lies
ahead
in
redirect
developer
heart.
Firstly,
we
are
addressing
one
of
the
biggest
challenges
reported
by
the
platform.
Engineers
plugin,
that
is
plugin
installation
and
configuration
currently
adding
a
new
plugin
to
Backstage
requires
a
rebuild
and
redeployment.
However,
we
are
making
significant
contribution
to
the
Upstream
backstage
project.
To
enhance
this
aspect.
F
Redhead
developer
Hub
will
feature
a
mark,
plugin
Marketplace,
simplifying
plug-in
management
and
reducing
the
time
and
effort
to
require
to
add
plugins.
Secondly,
we
are
placing
an
emphasis
on
improving
authorization
and
the
admin
user
interface
experience.
Authorization
has
been
a
major
concern
with
backstage,
but
in
an
upcoming
release,
data
developer
Hub
will
introduce
a
default
permission
framework.
Additionally,
we
will
introduce
our
admin
role
with
its
own
dedicated
UI.
F
Next
slide,
we
did
announce
podman
desktop
1.0
in
redirect
Summit
supporting
Mac
windows
and
Linux
platforms.
So
what
we
will
be
focusing
next
with
fortnite
desktop
1.0,
is
in
the
container
tool
in
real.
We
aim
to
define
the
onboarding
experience,
simplifying
environment
and
Docker
compatibility
control
positions.
Podman
will
support
provider
support
for
Native,
hypervisors
specific
to
each
platform
like
VF
gift
for
Mac
or
hyper-v
for
Windows,
firstly,
and
secondly,
we
are
committed
to
empowering
developers
to
transition
containers
into
kubernetes
seamlessly
through
modify
or
qv5
flows.
F
We
enable
the
smooth
movement
of
applications
from
containers
to
kubernetes.
We
will
continue
to
improve
on
this
close,
making
transition
even
more
efficient.
Additionally,
we
will
expand
the
UI
capabilities
to
handle
more
kubernetes
objects
facility
in
easier
testing
and
debugging
of
application.
Lastly,
for
Developers,
working
with
openshift
to
VR
streamlining
the
process
of
leveraging
openshift
devs
and
works
for
quick
application
testing
next
slide.
F
Sandbox
is
designed
to
empower
developers
like
you
to
unleash
your
creativity
and
explore
the
Limitless
possibilities
of
your
projects.
So
we
are
working
to
move
sandbox
experience
to
hybrid
Cloud
console
the
first
part
of
it
that
it
will
be
enabling
users
to
signif
sign
up
from
within
hybrid
Cloud,
console
to
developer
sandbox
page
another.
C
F
Focus
is
enabling
users
to
create
their
own
instance
of
radar
developer
Hub.
This
will
be
first
done
with
a
hem
shop.
Then,
with
an
operator,
the
operator
will
enable
a
single
click
to
start
the
developer,
Hub
we'll
also
be
creating
a
dashboard
that
lets
users
see
how
some
high
level
metrics
about
their
sandbox.
They
can
see
how
much
time
they
have
left
in
the
sandbox,
how
much
of
the
resources
they
have
used
and
what
is
actually
consuming
those
resources.
F
And,
lastly,
we
will
enable
users
to
invite
others
into
the
side
moves,
and
this
will
obviously
unlock
developers
to
cover
it
on
the
work
that
they
are
doing.
So
thank
you
for
for
the
support
and
Trust
in
your
platform.
We
are
excited
to
embark
on
this
journey
with
you
and
we
look
forward
to
delivering
those
features
that
will
transform
your
software
development
experience
over
to
you.
William.
B
We
are
focusing
on
the
life
cycle
part.
We
are
focusing
on
three
main
areas:
installation
updates
and
provider
Integrations.
We
continue
to
expand
our
support
for
new
Cloud
providers,
new
platforms,
onboarding
new
regions
and
enabling
third-party
Integrations
with
the
introduction
of
hosted
Contour
planes
on
red
hat
openshift
on
AWS
or
rosam.
We
continue
to
enhance
the
installation,
experience
and
add
new
capabilities
across
the
hybrid
cloud.
B
B
On
external
DNS,
so
on
on
cloud
providers
today,
when
using
openshift,
full
stack,
automated
installation
or
API
to
deploy
to
public
Cloud
thiseller
uses
each
cloud
provider
DNS
service
there,
the
installer
configures
the
DNS
entries
for
the
openshift
API
and
Ingress
services
on
highly
regulated
environments
where
organizations
need
to
provide
their
own
manage
DNS
solution.
This
is
not
an
option,
so
we'll
be
adding
support
to
external
DNS
when
using
IPI
for
deployments
on
public
cloud.
B
B
Continuing
on
the
efforts
that
we
started
with
openshift
412,
where
we
extended
the
life
cycle
of
our
EOS
releases
from
18
months
to
24
months
in
two
four
years
for
the
x86
architecture.
We
are
expanding
this
to
include
arm
IBM
power
and
IBM
Z.
With
this
we
are
bringing
new
24-month
life
cycle,
support
to
all
our
supported
architectures.
B
B
It's
really
different
from
our
current
platform
type
as
it
allow
infrastructure
Partners
to
clearly
identify
when
their
openshift
deployments
contain
certain
components,
replacing
openshift
for
brand
High
components.
An
example
of
this
is
a
partner
can
specify
the
presence
of
their
own
custom,
Cloud
controller
manager
or
their
own
CSI
driver
next
slide.
B
Out
of
three
CCM
originally
kubernetes
started
by
implementing
all
the
cloud
provider:
specific
functionalities
natively
within
the
main
kubernetes
tree
as
an
entry
model.
However,
the
old
method
has
become
impractical
to
maintain
and
is
no
longer
advice.
New
providers
must
follow
the
out
of
three
model
for
enabling
cloud
provider
specific
functionalities.
This
in
mind,
starting
in
openshift
414,
will
be
switching
openshift
deployments
that
are
using
the
current
Legacy
entry
CCM
to
the
new
external
CCM.
B
B
It's
like
opens
you
from
the
Oracle
cloud.
We
keep
expanding
and
supported
and
are
supported
providers
and
this
time
to
include
Oracle
cloud
recently
we
enabled
Oracle
Cloud
VMware
solution
and
now
we're
working
to
enable
openshift
4
on
cloud
interest
on
Oracle
Cloud
infrastructure
on
VMS
and
bare
metal
instances.
B
B
For
the
IBM
power
and
ibmc
architectures,
we
are
enabling
systems
specific
advantages
like
share
memory,
communication
allowing
openshift
users
to
take
advantage
of
some
of
the
IBM
architecture,
more
powerful
features.
We
continue
working
on
improving,
also
the
experience
for
disconnected
multi-architecture
cluster.
This
time,
making
awesome
mirror,
for
example,
better
interact
with
multiple
architecture.
B
Payloads
next
slide,
openshift
from
Very
Metal.
We
are
improving
agent
based
installer
to
include
use
cases
often
only
possible
with
the
UPI
such
as
this
partition.
This
encryption
and
other
host
level
configurations
we're
adding
support
to
extend
cluster
running
on
AWS,
Azure
and
Google
cloud
with
bare
metal
nodes
running
on
premise.
B
Finally,
we
are
making
enhancement
to
openshift,
make
administrator's
life
easier,
like,
for
example,
we
are
making
rollout
updates
more
resilient
and
flexible,
especially
when
they
are
blocked
by
workloads
that
are
not
terminating
properly
or
by
drains
blocked.
By
other
reasons,
like
all
disruption,
budgets
we're
providing
more
options
there
next
slide,
Hardware
salaters,
Dynamic
resource
allocation
or
the
array
is
the
new
generation
of
device.
Plugin
dri
VRA
provide
a
new
API
for
device
initialization
and
cleanup
its
Support
over
the
fabric
devices,
among
other
things,
features
with
Nvidia
gpus.
B
B
B
Support
customers
running
Ai
and
ml
application
jobs
on
openshift.
We
are
enhancing
the
job
management,
with
capabilities
like
job
queuing,
job
priority
and
job
quota
management.
There's
a
few
Upstream
projects
we
are
exploring
to
solve
these
use
cases,
among
them,
q
and
the
multi-cluster
app
dispatcher
MCAT
next
slide.
B
What
about?
Well?
It's
a
scaling.
Well
part
Auto
scaling
is
a
fundamental
feature
on
openshift
and
it's
critical
for
auto
scaling
applications.
We
are
listening
to
our
customers
and
their
need
for
new
ways
to
scale
their
applications.
With
that
in
mind,
we're
working
on
new
and
exciting
upcoming
Auto
scaling
feature,
including
In-Place,
update
of
part
resources.
This
allows
customers
to
change
the
resource
specification
on
the
Pod
definition
and
the
shames
will
be
applied
without
restarting
the
pod
in
place.
Update
of
vpa.
B
Windows
containers
for
the
future
of
Windows
containers,
we're
focusing
on
several
areas
to
highlight.
One
of
them
is
bring
in
better
visibility.
These
include
conversion
of
Windows,
specific
metrics
into
openshift,
consumable
values,
also
the
ability
to
connect
to
storage
via
CSI
plugin
and
to
use
proxies
in
your
windows
environment.
B
At
the
same
time,
we
are
bringing
support
for
Windows
node
into
more
Cloud
providers
next
slide
in
the
Improvement
and
the
identity
and
access
management
stack
in
openshift
414,
we'll
introduce
Port
security
admission
control
in
enforcement
mode.
This
will
help
provide
Upstream
compatibility,
while
maintaining
a
security
hardened
openshift
platform
by
default
also
bring
your
own
oidc.
B
As
more
and
more
customers
look
into
multi-cloud
solutions.
They
need
oidc
idps
with
direct
access
to
openshift
and
kubernetes
API.
With
this,
we
are
working
to
integrate
with
standards.
Oidc
idps
providers
such
as
big
clock
and
Azure
ad
degrees
store,
CSI
driver.
We
are
productizing,
this
driver
that
mounts
secrets
from
external
secret
providers
directly
into
the
applications.
B
This
way,
Secrets
do
not
persist
when
the
part
is
deleted
and
they
are
never
poor
on
its
CD
with
the
new
certain
namespaces.
This
provides
the
ability
to
map
the
route
on
the
container
to
a
non-root
user
on
the
host
file
system.
This
has
been
a
requests
or
compliance
requirement
for
Telco
and
FSI,
so
we
are
working
on
that
as
well.
B
No
Auto
creation
of
certain
secrets
that
we
still
have
so
by
default
secrets
are
not
auto-generated.
However,
in
openshift
there
are
still
two
Legacy
secrets
that
are
still
created.
We
plan
to
remove
this
in
upcoming
releases
and
users
will
need
to
use
their
token
request.
Api
requires
token
or
create
secrets
to
populate
the
sa
token.
B
B
B
B
With
this
new
feature,
we
create
an
API
that
allow
a
cluster
administrator
to
select
from
a
validated
set
of
profiles
to
adjust
the
hard
disk
intervals
and
elections.
Timeouts
of
E3
Hit
List
hit
list,
hcd,
defragmentation
and
rotation
is
also
part
of
the
work
we
are
working
for.
The
coming
releases
next
slide.
B
B
B
B
Self-Manage
posted
console
planes,
we
are
focusing
on
development
of
cell
management,
posted
console
plane
as
a
cost-effective,
multi-cluster
openshift
form
factor.
We
intend
to
roll
out
new
providers
on
various
platforms,
starting
with
agent
provider,
openshift,
virtualization
and
AWS,
bring
in
flexibility
and
adaptability
to
hosted
control.
Plane
deployment
is
a
significant
part
of
our
plan.
This
involves
rollout
of
multi-architecture
control
planes
and
notebooks
on
AWS
will
have
support
for
two
architecture:
types
or
control,
planes,
x86
and
arm
on
bare
metal
using
agent
provider.
B
B
We
have
an
ecosystem
Partners
like
Fort
Worth
saving,
proilio
that
have
announced
support
and
that
they
support
VMS
and
operations
and
we'll
set
this
to
continue,
and
we
are
extending
that
with
the
ga
of
odf
Disaster,
Recovery
and
onboarding.
New
vendors
will
enhance
openshift
virtualization
secondary
networks,
security
capabilities
with
capabilities
like
micro
segmentation,
when
using
ovn
kubernetes
over
the
next
year.
You
will
see
the
addition
of
network
and
CPU
hot
plugs
and
support
for
memory
over
commit
on
multi-cluster
scaling
with
hosted,
console
plane
now
supporting
running
on
openshift
virtualization.
B
You
can
now
deploy
multiple
openshift
clusters
on
top
of
a
bare
metal
openshift
cluster.
So
there's
no
need
for
an
external
hypervisolator
to
improve
the
density
of
your
bare
metal
nodes,
but
this
users
can
also
deploy
and
manage
VMS
using
ACM
when
they
have
multiple
clusters
VM.
As
code,
we
are
providing
more
examples
for
VMS
code
such
that
you
can
use
that
to
deploy
using
githubs
or
using
tecton
and
argosity
Pipelines
on
the
public
cloud.
Today
we
support
openshift
virtualization
on
AWS
barmerum
as
I
take
review
and
we're
moving
that
towards
RGA.
B
B
B
on
the
core
side
of
the
openshift
storage
non-graceful,
for
example,
no
shutdowns
moving
into
GA.
This
allowed
volumes
attachment
to
be
released
if
a
node
is
shut
down.
Ungracefully
a
retroactive
storage
classes
assignment
is
also
coming
to
openshift,
and
this
will
allow
like,
for
example,
if
you
create
a
storage,
a
PVC
without
a
storage
class,
it
will
go
into
pending
State.
This
feature
allow
for
the
modification
or
update
of
that
with
the
storage
class.
B
Before
this
feature,
basically,
you
will
have
to
recreate
that
PVC
next
openshift
update
service
here.
Finally,
we
have
ocadm
Upstate
update
status.
This
is
a
new
single
command.
This
show
the
status
of
openshift
updates,
along
with
the
current
update
status
of
all
the
operators
and
nodes
Etc.
This
single
command
also
monitors
the
updates
and
troubleshoot
issues
without
having
to
search
for
logs.
G
Yeah
thanks
William
in
Reddit,
openstack
18
we'll
introduce
a
new
architecture,
the
deployment
and
hosting
of
the
openstack
control
plane
based
on
openshift
and
a
subset
of
the
openshift
core
Technologies.
This
is
a
major
milestone
for
red
hat
openstack.
That
gives
us
the
opportunity
to
approve
on
a
number
of
aspects
of
the
product,
such
as
the
deployment
and
upgrade
user
experiences,
monitoring
and
observability
scale,
and
better
alignment
between
infrastructure
platforms,
such
as
the
ability
to
move
bare
metal
resources
from
OSP
to
ocp,
and
vice
versa.
G
The
ability
to
use
core
openshift
capabilities
like
ACM,
to
deploy
multiple
ocp
clusters
on
the
openstack
compute
nodes,
the
ability
to
use
ocp
pipelines
to
automate
OSP
lifecycle
procedures
and
to
utilize
git
Ops
for
cluster
configuration
changes
next
slide.
Please,
on
this
slide,
we
can
see
at
a
high
level
how
openstack
18
will
look
like
openshift
is
hosting
the
control
plane
in
pods
and
governing
deployment
and
lifecycle
via
its
service
operators.
G
It's
important
to
note
that
the
data
plane
for
openstack
will
be
kept
separate
from
the
hosting
ocp
cluster.
For
several
reasons.
One
customers
are
accustomed
to
Long
product
support
life
cycles
with
openstack,
and
we
want
to
continue
to
provide
this
two.
We
want
to
have
a
minimal
impact
to
running
workloads
in
the
case
of
an
openshift
upgrade
and
three.
We
want
customers
to
adopt
the
new
architecture
without
having
to
migrate
or
interfere
with
the
running
workloads.
G
Talk
about
core
and
Edge
next
or
excuse
me,
Telco
and
Edge.
Next,
we're
focused
on
sharpening
our
Edge
capabilities
for
new
domains,
for
example
industrial,
retail
and
public
sector
use
cases.
A
Cornerstone
of
that
strategy
is
Red,
Hat
device
edge
with
microshift,
which
we
have
which
we
announced
last
year.
Microshift
is
a
small
form
factor.
Kubernetes
distribution,
targeting
field
deployed
Edge
devices
with
as
little
as
two
cores
and
two
gigs
of
RAM
microshift
is
currently
in
developer
preview.
The
next
big
milestone
is
General
availability,
which
we
will
Target
to
achieve
in
the
next
release.
G
G
G
Besides
microshift,
we
will
continue
to
improve
the
edge
experience
for
core
openshift
Technologies.
We
will
extend
single
node
openshift
to
Azure
and
Google
Cloud
as
supported
providers.
In
the
past,
we've
been
on
a
constant
trajectory
to
reduce
our
resource
footprint.
We
will
continue
this
work
by
making
more
cluster
capabilities
optional
and
we
intend
to
minimize
the
cluster
deployment
Time
by
making
Sno
relocatable
to
allow
for
faster
rollouts
at
far
Edge
locations.
G
G
G
Red
Hat
Strategic
investment
areas
for
Telco,
align
with
the
most
challenging
problems
that
telecommunications
providers
face
as
openshift
evolves.
Improving
operations
is
Paramount,
openshift
needs
to
utilize
the
capabilities
of
Next
Generation
Hardware
to
maximize
per
node
performance.
We
also
must
ensure
operations
at
scale
have
high
success
rates
and
easily
recover
from
failure.
G
Additionally,
we
must
provide
robust,
observability
and
other
operational
functionality
to
help
with
running
a
national
telecommunications.
Network
telecommunications
providers,
with
the
help
of
red
hat,
will
continue
to
reduce
openshift
and
workload
resource
consumption
to
lower
power
usage
and
improve
the
sustainability
of
our
Solutions.
G
G
I
will
cover
networking
and
observability.
Next,
let's
take
a
look
at
networking.
We
continue
to
invest
in
improving
networking
across
multiple
networking
layers,
all
with
the
goal
of
enabling
multi-cluster
networking
across
geographies
to
enable
Enterprises
to
innovate
without
limitation
in
their
digital
transformation.
G
Journey,
our
plans
for
networking
capabilities
are
expanding
to
include
single
node,
openshift
hypershift,
multi-cluster,
hybrid
cluster
and
globally,
unified
networking
we're
working
towards
unifying
how
we
handle
traffic
into
out
of
and
between
clusters,
so
that
Ingress
and
egress
are
configured
in
the
same
manner
regardless
of
protocol
and
platform,
and
we
want
to
align
on
how
layered
products
such
as
openshift
service,
mesh
and
openshift
virtualization
operate.
Not
only
will
this
make
operations
easier
through
unification,
but
this
will
extend
to
current
and
future
networking
protocols.
G
We
continue
to
work
on
Submariner
to
provide
enhanced
multi-cluster
networking
capabilities
with
layer,
3
and
layer
4
interconnect
by
enabling
You
by
enabling
direct
networking
between
pods
and
services
in
different
kubernetes
clusters,
either
on-premise
or
in
the
cloud
with
Submariner.
Your
application
Services
can
stand
multiple
Cloud
providers,
data,
centers
and
regions
next
slide.
Please.
G
G
Next
slide,
please,
service
mesh
helps
you
create
secure,
reliable
microservices
with
enforced
pod
to
pod
mtls
encryption,
zero
trust
policies
and
observability
with
metrics
and
traces.
Well,
we
have
made
incremental
updates
to
move
closer
to
Upstream
istio.
We
are
working
on
a
new
major
3.0
release
of
openshift
service
mesh
that
will
largely
converge
with
Upstream
istio.
G
This
will
enable
us
to
support
customers
on
the
latest
istio
features
such
as
Gateway
API
and
the
developing
ambient
mesh,
a
new
data
plane
that
avoids
the
need
for
sidecars
look
out
for
previews
later
this
year
on
the
theme
of
scale.
We
have
customers
that
run
meshes
with
hundreds
of
namespaces
and
thousands
of
services
across
multiple
clusters
and
Cloud
providers
with
complex
needs.
G
We
want
to
ensure
that
our
Enterprise
customers
are
able
to
secure,
observe
and
manage
traffic
at
scale.
Finally,
we
understand
that
service
mesh
is
only
one
component
of
a
larger
platform.
Providing
a
cohesive
experience
between
istio
and
openshift
is
is
our
primary
goal.
This
includes
Integrations
with
openshift
console
cert
manager,
openshift
monitoring,
git
Ops,
and
much
more
to
come
next
slide.
Please.
G
Openshift
observability
introduces
updates
across
three
key
themes:
theme
number
one
collect,
store
and
aggregate
near
term
from
a
monitoring
perspective,
the
Prometheus
operator
will
be
productized
from
a
logging
perspective.
Users
will
be
able
to
benefit
from
a
multi-cluster
log
collection,
experience
and
Loki
Zone,
aware
replication,
tracing
wise
Tempo
and
open
Telemetry
collector
operators
will
reach
GA,
providing
the
long-awaited
open
Telemetry
protocol
metrics
theme
two
visualize
near
term
improvements
to
the
openshift
web
console,
including
the
Loki
based
alerts
and
a
silences
tab
in
the
developer.
G
Console
users
will
also
be
able
to
bulk
expire
alert
manager
silences
long
term.
The
dashboard,
UI
and
web
console
will
also
be
displaying
Kepler
power
consumption
metrics.
Lastly,
with
red
hat
openshift
distributed
tracing
3.0
users
will
be
able
to
extract
red
metrics
from
distributed
traces
and
visualize
them
in
the
Jaeger
UI
monitoring
tab
theme:
three
analyze.
We
plan
to
release
a
correlation
operator
to
enable
users
to
visualize
correlated
observability
signals
in
the
web,
console
as
a
starting
point.
G
Users
will
be
able
to
correlate
alerts
to
logs
and
logs
to
metrics.
This
initiative
wants
to
reduce
the
time
spent
by
users
troubleshooting
individual
clusters.
Additionally,
enhanced
distributed
tracing
analysis
is
facilitated
with
the
support
of
traceql
in
tempo
next
slide.
Please,
let's
take
a
closer
look
at
Power
monitoring
for
red
hat
openshift
with
Kepler
a
Dev
preview
of
power
monitoring
will
be
available
within
the
next
six
months.
What
are
the
benefits
of
this
initiative?
Well,
making
energy
related
metrics
accessible
to
users
helps
them
Drive
energy
costs
down
and
contributes
to
achieving
their
sustainability
goals.
G
G
G
Red
Hat
insights
can
also
help
with
cost
management
by
providing
cost
visibility,
cost
mapping
and
effectively
communicating
cost
models.
We're
improving
insights
by
providing
recommendations
for
resource
optimization
and
by
automatically
Distributing
the
overhead
costs
of
kubernetes,
for
example,
the
cost
of
the
unallocated
capacity,
the
cost
of
the
control
plane
and
the
cost
of
any
Cross
services.
Your
applications
may
be
using
with
that
said,
I'll
hand
it
back
to
CMAC
to
close
out
our
presentation.
Thank
you.