►
Description
In the pre-OpenShift world, backup and disaster recovery solutions were generally implemented at the virtual machine (VM) level. This system works for traditional applications when an application runs on a single VM, but when applications are containerized and managed via OpenShift, this system falls apart. Because of this, effective backup and disaster recovery solutions for OpenShift must be designed for containerized architectures and natively understand the way OpenShift functions in order to work.
In this OpenShift Commons briefing, we will:
– Explain key backup and disaster recovery concepts including zero recovery point objective (RPO) and near-zero recovery time objective (RTO) and how they apply to OpenShift
– Explain why backing up entire applications, including application configuration and data, is critical to data protection on OpenShift
– Discuss how an effective Backup and Disaster Recovery program includes data protection and availability within a cluster, between clusters, and between clouds depending on the use case
– Demonstrate real-world solution for OpenShift DR using Portworx the Kubernetes Storage Platform
A
B
A
B
B
So
you
know,
I
think,
the
way
that
I
spend
my
time
is
a
combination
of
you
know
talking
to
customers,
understanding.
You
know
how
they're
approaching
digital
transformation
within
their
organization.
Broadly,
you
know
how
we
translate
that
into
you
know,
requirements
and
solutions
for
solving
the
data
problem
that
comes
along
with
application,
development
and
application
operations
and
then
making
sure
that
when
someone
comes
to
you
know
our
website
or
visits,
that's
at
a
trade
show
or
attends
one
of
our
webinars.
B
A
B
No,
no,
unfortunately,
not
so
I'm
not
batting
100
on
this
one,
but
you
know
I
it's
you
know.
If,
if
you
don't
mind,
I
can
kind
of
take
a
little
bit
of
detour,
because
I
think
it'll
put
a
lot
of
the
conversation
in
context
so
yeah.
So
I
was
at
another
startup
prior
to
footworks.
I
was
a
company
by
the
name
of
cluster
hq
and
I
spent
about
three
years
at
that
company
as
well.
In
fact,
kind
of
as
part
of
the
acquisition
by
pure.
B
I
recently
wrote
kind
of
a
a
blog
post
reflection
on
the
last
six
years
in
that
journey
and
kind
of
what
I
learned
along
the
way
and
to
give
the
kind
of
the
the
high
level
of
review.
I
would
say
that,
first
of
all,
when
I
joined
the
previous
company
cluster
hq,
I
had
been
working
in
kind
of
a
you
know:
publicly
traded
company
for
the
last
five
years
and
really
enjoyed
it
but
kind
of
got
the
itch
to
join
a
startup.
I
mean
for
me
joining
a
startup.
B
It's
really
about
building
something
from
scratch,
right,
not
just
being
on
it
on
a
winning
team,
but
but
helping
kind
of
get
the
team
going
so
that
it
can
win
and
really
build
things
from
scratch,
and,
as
I
was
looking
around
at
kind
of
what
startup
to
to
join,
you
know,
do
I
want
to
do
something
around?
You
know
a
sas
company,
or
do
I
want
to
do
something
around
you
know?
I
don't
know
you
know
neural
networks
that
were
calling
at
the
time
now.
B
If,
if
the
data
center,
and
even
the
public
cloud
becomes
predominantly
containerized,
what
does
that
mean
for
the
other
parts
of
the
application
stack?
What
does
it
mean
for
infrastructure?
What
does
it
mean
for
security,
and
I
realized
that
you
know
kind
of
storage
and
data
management
writ
large
would
need
to
be
completely
re.
Redone
reimagined
rebuilt
if
containerization
was
going
to
become
the
primary
operating
model
and.
A
I
was
just
going
to
say
something:
you
know
you
brought
up
docker
and
you
know
I've
been
here
at
red
hat
for
19
years
now
and
pretty
happy
about
that
and
a
great
company
to
work
for,
but
it
seems
like
every
three
years,
there's
a
new
there's,
a
new
golden
child
out.
There
remember
when
openstack
first
came
out
and
it
was
openstack
openstack
openstack
and
then
there
was
then
there
was
the
whole
docker
craze
and
then
there
was
what
was
it.
You
know.
A
Dockercon
was
the
new
you
know
place
to
be
at
and
then
that
kind
of
dwindled
and
then
there
was
containers
and
containers
containers
containers
now
kubernetes
kubernetes
is
now
the
you
know,
orchestration
of
containers.
So
how?
How
have
you
you
know
seen
those
changes
as
it
relates
to
storage
over
the
last.
You
know
x,
number
of
years.
B
Yeah
yeah
excellent
question,
and
you
know
I
so
not
to
make
this
all
about
kind
of.
You
know
my
my
recent
past,
but
you
know
six
years
ago
when
I
joined
the
startup,
I
I
believe
that
if
containers
were
going
to
continue
to
be
important,
you
someone
would
have
to
figure
out
storage
and
data
management,
and
it
turns
out
that
maybe
like
five
or
six
people
agreed
with
me
and
everybody
else
said
you
know
what
you
know
michael.
B
B
When
I,
when
I
say
that
it's
really
a
game
changer
when
you
have
a
team
that
used
to
take
six
months
to
get
a
new
application
into
into
production
and
now
with
openshift,
they
can
squeeze
that
down
to
you
know,
weeks
or
days
or
in
sometimes
hours.
That's
such
a
big
change
that
you
say
how
can
we
apply
this
to
our
entire
infrastructure
and
if,
if
there's
a
limiting
factor,
which
is
to
say
you
can
get
that
goodness
as
long
as
there's
no
data
involved,
then
it
it
it's.
B
It's
really
a
deal
breaker,
because
how
many
enterprise
applications
don't
have
don't
have
data
and
customers
began
to
realize
that
then
the
vendors,
you
know
big
and
small,
realized
that
they
needed
a
solution
there,
and
you
know
I
was
lucky
enough
to
to
work
for
two
companies
that
were
there
kind
of
six
years
ago.
Portworx
was
founded
in
parallel
with
this
other
company,
but
you
know
not.
You
know
the
emc's
of
the
world
were
among
the
first,
but
it
probably
took
them.
B
You
know
a
good,
maybe
18,
to
24
months,
to
really
understand
that
containers
was
something
that
could
challenge
their
business.
Netapp
was
even
longer,
and
now
we
kind
of
come
full
circle,
and
you
know
the
biggest
companies
in
the
world
who
are
using
containers
are
also
running
analytics.
Ai.
You
know
big
data
workloads
on
on
containers
in
production.
B
B
Now
could
just
be
software
in
order
to
automate
the
deployment
of
other
software,
but
in
some
cases
it's
you
know
it's
everything
from
kind
of
lightweight
coding
to
very,
very
heavy
coding
when
you're
building
large-scale
kind
of
platforms
and
that
cultural
change
for
how
do
you
operate
in
a
company?
That's
you
know,
you
know
one
of
our
customers,
I'm
just
going
to
pick
on
them
because
it,
I
think
it
illustrates
the
point
here,
they're
one
of
the
largest
retailers
in
the
united
states.
B
You
know
they've
been
in
business,
for
you
know
over
100
years,
and
how
do
you
take
a
company?
That's
been
around
for
so
long
kind
of
started
out,
not
as
a
digital
business,
really
as
a
brick
and
mortar
and
then
transform
that
into
a
company
capable
of
delivering
software
to
compete
with
true
digital
native
companies
when
you're
also
transforming
your
culture,
I
think
you're
exactly
right.
Lots
of
questions
get
posed
and.
A
To
you,
you
know,
as
as
customers
are
starting
to
adopt
multi-cloud
and
moving
everything
out
of
the
data
center,
we
see.
I
I
think
we
tend
to
see
a
lot
of
customers
aren't
necessarily
moving
their
workloads
into
production
right
away,
and
I
think
probably
a
lot
of
that
is
about
concerns
around
you
know:
data
protection,
so
you
know
how
you
know
how
how
do
you
see
protecting
applications?
The
way
we
used
to
do
with
like
say,
virtual
machines
now
that
everything's
running
in
containers.
B
Yeah,
that's
a
good
question.
I
mean
I,
I
agree
with
you
that
you
know
the
you
know
if
you're
adopting
containers
or
kubernetes
or
cloud
native
or
whatever
you
want
to
call
it.
You
know
it
there's
a
there's
a
learning
period
before
those
applications
move
into
production
as
there
would
be
with
any
any
technology
stack,
and
I
think
if
you
look
at
the
industry
overall
lots
of
organization
organization
is
on
on
kind
of
an
escalator
and
everybody
gets
on
at
the
same
spot,
but
some
people
get
on
before
other
people.
B
So
you
know
at
any
given
point
in
time.
Even
within
the
same
organization,
you
have
some
some
customers,
or
some
teams
that
are
are
in
production,
where
you
have
other
teams
that
are
starting
the
beginning
of
the
journey,
and
so
that's
kind
of
one
of
the
things
you
have
to
deal
with
as
well,
which
is
that
there's
different
levels
of
maturity,
even
within
the
same
organization.
B
That
said,
I
think
when
we
talk
to
customers
about
data
protection,
we
you
know
a
lot
of
a
lot
of
things
are
new,
but
a
lot
of
things
are
not
new
and
so
customers
understand
concepts
like
you
know,
rpo
and
rto.
When
it
comes
to
data
protection,
then
just
for
you
know
clarity's
sake.
Rpo
stands
for
recovery.
B
Point
objective:
that's
you
know
how
much
data
loss
are
you
willing
to
accept
in
the
case
of
a
disaster
right
does
if,
if,
if
a
right
just
happened
in
one
data
center,
does
that
right
need
to
be
available
in
your
in
your
disaster
site
or
are
you
say
you
know
it's?
Okay?
If
we
have
a
backup
from
an
hour
ago,
that's
okay,
that's
acceptable
amount
of
data
loss
and
different
types
of
applications
have
different
requirements.
B
B
So
we
start
with
the
understand
a
customer's
understanding
right.
They
they
have
their
rpo
and
their
rto
for
applications
defined
and
they've
done.
That
for
vms
and,
like
you
know
the
chief
security
officer,
the
chief
compliance
officer,
you
know
head
of
I.t,
like
all
of
these
things
have
been
debated
endlessly
by
the
organization,
and
none
of
that
needs
to
change
just
because
you're
moving
to
containers.
B
Where
we
would
say
we
would
back
up
our
vm
right.
We
would
you
know
we
would
use,
I
don't
know
veeam,
and
that
would
back
up
all
of
our
all
of
our
vmware
instances
and
because
we
ran
one
application
per
vm.
If
we
had
a
backup
of
the
vm,
we
also
had
a
backup
of
the
application
that
model
completely
breaks
down
when
it
comes
to
containerization,
because
now
my
openshift
application
is
actually
running
across
many
vms
or
in
the
case
of
bare
metal.
B
It's
running
across
many
bare
metal
instances,
I'm
running
distributed
applications
and
because
openshift
enables
us
to
have
kind
of
radical
multi-tenancy
right
to
get
those
efficiency
gains.
Not
only
is
a
single
application
running
across
multiple
hosts,
but
each
of
those
hosts
is
hosting
multiple
applications,
so
I've
kind
of
got
this.
A
Now
you,
you
folks,
have
a
red
hat
certified
operator
right.
Yes,
so
we've
been
working
with
you
folks
around
you
know
getting
a
container
up
and
running
available
for
customers,
so
they
know
that
you
know
the
internal
components
of
that
container.
Are
you
know
red
hat
blessed
code
as
well?
As
you
know,
supportable
code?
From
from
your
side,
how
does
the
operator
help
people
manage
their
data
in
this
cloud-native
distributed
environment.
B
Yeah,
so
the
the
operator
concept
is
basically
software
for
managing
other
software,
and
so
there
are
a
lot
of
things
that
you
need
to
do
in
order
to
kind
of
execute
these
these
operations.
So,
for
instance,
if
I
want
to
take
a
backup,
I
might
need
to
snapshot
a
distributed
database.
Maybe
it's
cassandra
and
I
have
10
cassandra
nodes
and
I
need
to
snapshot
them,
but
I
need
to
do
it
in
a
way
that
actually
runs
a
command
within
the
cassandra
container.
B
B
B
B
Yeah,
it's
you
know,
they're
a
bunch
and
unfortunately
the
kind
of
you
know
the
whole
covid
thing
has
really
put
into
stark
contrast.
Kind
of
you
know,
companies
that
have
been
able
to
cope
with
just
the
unprecedented
demand
and
those
that
have
that
have
struggled
and
we're
lucky
to
work
with
some
very
kind
of
forward-thinking
customers
that
have
been
down
this
path
for
a
while,
and
it
just
you
know,
proved
to
be
the
prescient
decision.
When
kind
of
the
you.
C
B
With
when,
basically
the
world
changed
starting
in
february
or
march,
so
a
couple
of
examples
come
to
mind.
One
is
a
platform
called
roblox,
so
it's
a
gaming
platform.
I
think
they
have
like
150
million
monthly
active
users,
mainly
kind
of
teens
and
preteens,
and
so
you
can
build
your
own
games.
It's
a
community.
B
You
know,
kids
in
the
house
where
parents
are
working
on
all
those
types
of
things,
and
so
you
know
they
really
had
to
grow
what
they
call
their
points
of
presence,
which
is
where
they
stamp
out
these
infrastructures
all
around
the
world
in
order
to
meet
the
demand.
That's
popping
up,
and
so
that's
a
really
cool
use
case,
being
able
to
support
that
another
customer
that
comes
to
mind
is
called
esri.
So
they're
one
of
these
companies
that,
like
you
know,
we
all
rely
on
every
day,
but
we've
never
heard
of.
B
Mapping
data
right
exactly
and
they're
they're
becoming
more
of
a
household
name,
because
some
of
their
maps
around
covet
tracking
are
kind
of
you
know,
often
used
by
you
know
new
york
times,
washington,
post
et
cetera,
it's
just
to
keep
track
of
infection
rates
and
testing
and
things
like
that
using
their
arc
gis
platform,
so
you've
probably
been
to
websites
where
it's
arcgis.esri.com
and
they're
running.
All
of
that
in
the
public
cloud
on-
and
you
know,
data
is
a
huge
part
of
what
they
do
so
it
has
to
be
reliable.
B
B
We
recently
did
a
webinar
with
with
them
and
say
how
do
you
both
meet
your
kind
of
regulatory
requirements
of
just
being
you
know,
financial
services
institution
and
be
as
agile
as
you
know,
silicon
valley
startup
when
it
comes
to
getting
to
market
quickly,
like
that's
a
hard
needle
to
thread
and
so
being
able
to
help
their
you
know,
solving
things
like
disaster
recovery,
multi-site,
dr
for
them
is,
is
really
exciting.
It
kind
of
points
to
the
future,
I
think
of
yoga.
B
A
A
There
were
40
different
flavors
of
linux
out
there
everybody
was
in
the
linux
space,
there
was
blue
dog
linux
and
miracle
linux
and
china
had
red
flag
linux,
and
you
know
red
hat
was
the
company
that
got
it
right
right.
We
figured
out
how
to
slow
down
the
release
cycles
of
the
kernel
releases
so
that
customers
could
actually
standardize
on
one
distribution
of
linux,
and
then
software
vendors
could
certify
their
software
on
a
target
that
wasn't
moving
all
the
time.
A
So
we
we
went
from
red
hat
linux,
which
was
you
know,
version
six
version,
seven
version,
eight
version,
nine,
you
know,
and
we
came
out
then,
with
you
know,
a
version
of
linux
that
was
released
every
three
years
before
the
abi
or
kabi
would
change
now
with
kubernetes.
It's
kind
of
a
similar
thing
like
everybody's
in
the
kubernetes
space
everybody's
got
a
different
story
around
kubernetes,
especially
like
the
major
cloud
providers.
A
B
B
Anyway.
Amazon
was
the
running
runaway
winner
in
the
in
the
cloud
1.0
award.
At
the
same
time,
vmware,
I
think,
is
still
smarting
from
their
business
being
sucked
away
because
of
cloud,
and
so
you
have
a
market
now,
where
the
google
and
azure
and
to
it
to
a
lesser
extent
ibm.
But,
but
I
would
you
know,
call
ibm.
The
fourth
big
cloud,
where
they're
trying
to
figure
out
how
do
we
prevent
amazon
from
running
our
way
with
cloud
2.0?
B
And
that's
where
you
see
you
know:
microsoft
with
arc
google
with
anthos
ibm
with
red
hat
openshift
as
a
infrastructure,
agnostic
management
layer
on
top
of
public
cloud
infrastructure.
So
if
you're
google
you're
thinking
about
how
do
we
make
it
so
that
amazon's
strength,
their
infrastructure
play
actually
not
a
liability?
B
Infrastructure
storage,
network
and
compute
from
the
cloud
provider,
but
then
your
kind
of
your
ela
is
with
tanzo
and
I
think
red
hat
can
offer
something
similar.
So
I
think
there
is
not
going
to
be
only
one
winner
in
this
market.
The
way
that
there
was
a
very
predominant
winner
in
the
public
cloud.
B
A
What's
next
meaning,
like
you
know,
there
was
open,
there
was
the
openstack
shiny
object,
docker
sheen
already
talked
about
that.
Is
there
going
to
be
another
shiny
object,
24
months
from
now,
or
do
you
think
we're
kind
of
settled
into
you
know
kubernetes
and
container
orchestration
for
the
foreseeable
future.
B
Well,
you
know,
I
think,
there's
all
there's
always
a
shiny
object,
you
know
and
that
that's
a
good
thing,
because
you
know
you
know:
smart
people
are
getting
born
every
day
and
they
figure
out
how
to
do
you
solve
problems
differently?
I
I
don't
think
that
yo
at
a
high.
Well,
let
me
let
me
let
me
say
that
I
don't
think
there's
going
to
be
something
in
the
next
couple
years
that
fundamentally
changes
application
delivery.
The
way
kubernetes,
slash
containers
have
changed
application
delivery
over
the
next
five
years.
B
I
think
the
next
big
thing,
though,
is
going
to
be
kubernetes
as
the
control
plane
for
the
entire
data
center,
not
just
for
containers,
and
I
because
I
think
that
that's
been
one
of
the
things
that's
been
holding
back.
Adoption
of
kubernetes,
which
is
that,
like
you
have
to
buy
into
containerization
or
you
have
to
commit,
is
probably
a
better
word
to
containerization
if
you
want
to
get
those
benefits.
B
But
if
you
look
at
someone
like
netflix,
you
know
they
made
microservices
popular
before
docker
was
popular
and
all
of
that,
for
the
most
part,
was
on
amazon
and
all
of
that,
for
the
most
part,
was
running
in
ec2
instances
and
they're,
a
highly
agile
organization,
lots
and
lots
of
microservices,
and
yet
they
weren't
a
containerized
business.
So
if,
if
the
idea
behind
kubernetes
is
often
said,
how
can
we
make
any
business
like
netflix
or
like
google?
Well,
why
are
we
still
saying
kubernetes
hashtag?
B
It
can
only
manage
container
and
we're
starting
to
see
things
like
openshift
virtualization.
We
actually
just
did
a
blog
on
our
website
about
how
you
can
use
openshift
to
manage
vms
in
the
same
agile
manner,
and
I
think
once
that
happens,
coovert
is
a
project,
that's
being
popularized.
A
lot
of
people
are
looking
at
ways
to
kind
of
get
vmware
out
of
their
infrastructure,
because
it's
not
that
we
don't
want
virtualization,
it's
that
we
don't
necessarily
need
people,
call
it
the
vmware
tax,
like
I
think,
that's
you.
C
C
B
Yeah,
I
think
they
have.
They
absolutely
would,
and
you
know
it's
it's
their
their
argument
to
lose.
But
you
know
customers,
you
know
customers
vote
with
their
with
their
checkbooks
and
you
can't
take
your
customers
for
granted.
Not
that
that's
what
vmware
is
doing,
but
I
think
some
customers
say:
hey
you
know.
B
A
I,
I've
been
living
here,
my
at
my
my
summer
house
now
since
march
20th
and
and
when
when
I
first
got
here,
I
left
massachusetts
because
of
the
challenging
times-
and
I
was
snowmobiling
into
my
cabin
here,
because
the
road's
not
maintained
or
anything
for
me,
my
business
of
partner
marketing
here
at
red
hat,
has
just
absolutely
exploded
like
through
the
like.
We
are
so
busy.
B
Yeah,
it's
I
I
I
joke
with
my
wife.
All
the
time
is,
like
you
know,
whoever
you
think
of
being
quarantined
as
like.
This
is
like.
How
are
you
going
to
make
the
time
pass?
It's
going
to
be
so
boring.
You
can't
do
anything
and
as
a
family,
we've
never
been
busier
between.
You
know
two
kids
in
school,
both
of
my
my
wife
and
I
working
virtually
and
you
just
you
multiply
that
by
every
port
works
employee
each
poor
works.
B
Employee
interacts
with
you,
know,
100
different
customers,
and
you
just
you,
keep
multiplying
it
out
and
everybody's
busier.
And
if
you
look
at
like
the
the
things
that
are
making
modern
life
livable
in
this
very
unusual
times,
it
all
comes
back
to
software,
and
so,
if
you
kind
of
say
well,
what
does
it
mean
for
software
businesses?
It
means
that
there
are
a
lot
more
customers,
they're
buying
a
lot
more
they're
they're
running
at
scale,
a
lot
faster,
there's,
a
kind
of
a
I
saw
it
on.
B
I
think
it
was
on
twitter,
maybe
some
other
social
media
platform,
but
it
was
or
maybe
it
was
linkedin.
It
doesn't
matter
like
a
little
kind
of
mock
survey
and
it
said
who,
in
your
organization,
has
been
responsible
for
digital
driving
digital
transformation
and
like
choice,
a
cto
choice,
b,
cio
choice,
c,
covet
19
and
like
that
one's
checked,
because
the
reality
is
like
kovid
it
just.
B
It
was
an
adapter
by
moment,
and
so
you
know,
customers
like
like
esri,
like
roblox,
experiencing
growth
that
they
hadn't
planned
for
and
yet
they
had,
they
had
to
adapt
to,
or
just
you
know
be
surpassed.
Zoom
is
another
example:
I'm
not
not
a
portworx
customer
but
a
clear
example
of
a
company.
That's
just
unprecedented
and
I
think
all.
A
B
A
B
That
doesn't
mean
that
we
can't
get
together
anymore,
but
that
your
things
that
we
used
to
do
with
paper
you
know
face-to-face
are
increasingly
going
to
go
online
and
all
that
infrastructure
needs
to
run
somewhere.
It
needs
to
be
managed,
it
needs
to
be
secure
and
you
know
to
bring
it
back
to
your
earlier
question.
You
know
who
wins?
I
think
it's
the
companies
that
can
make
that
easy
and
reliable
for
their
customers,
because
that's
ultimately
what
what
the
end
user
needs
is.
B
They
need
it
to
work
right
at
any
level
of
scale
and
you
it's
too
complicated.
Even
for
people
like
you
and
me,
we
do
this
for
a
living.
It
still
can
be
really
really
complicated
to
understand
how
all
the
pieces
fit
together,
and
so
you
take
a
customer
that
also
has
a
day
job.
You
know
doing
banking
or
doing
gaming
or
whatever
their
their
specific
area
of
expertise.
Is
they
can't
understand?
A
Well,
I'm
looking
at
the
clock
we're
coming
up
here
at
the
end
of
at
the
end
of
our
our
content
period.
Here
we
don't
want
you
to
go
back
after
being
here
today
and
have
your
boss
or
your
ceo,
say,
michael
you
were
there.
You
were
streaming
on
the
openshift
commons.
You
know
briefing
show
addressing
you
know
people
all
over
the
world.
Why
didn't
you?
A
B
Yeah,
it's
a
good
question.
I
mean
I,
I
would
say
the
the
thing
that
I'm
really
excited
about.
Is
you
know
by
joining
pure
storage?
I
don't
know
if
the
you
know
the
audience
knows
anything
about
pure
I'm
not
gonna
do
justice
to
their
to
their
story,
history,
but
I
think
the
opportunity
that
your
import
works
have
in
the
context
that
we've
just
described
is
that
applications
are
more
important
than
ever.
B
B
Layer,
the
data
management
layer
to
go
to
live
alongside
kind
of
the
the
application
management
layer
provided
by
openshift,
or
you
know
whatever
container
platform
you're
using,
and
I
I
think
the
best
solution
on
the
market
for
that
is,
is
pure
and
and
poor
works,
and
you
know,
ultimately,
you
know
the
people
listening
get
to
decide,
but
we
believe
that
you
know
if
you
are
running
serious
applications
on
openshift
and
you
care
about
data
protection.
You
care
about
performance
and
you
care
about.
You
know.
B
Multi-Cloud
operations
that
you
know
fort
works
is
the
the
most
complete
platform
for
kubernetes
data
management
services,
and
I
I
think
you
know
getting
a
chance
to
work
with
innovative
customers
is
what
really
makes
us
tick,
really
really
passionate
passionate
about
it,
and
so
you
know
looking
forward
to
the
next
six
years
to
complement
the
previous
six.
I
think
there's
a
lot
of
cool
things
in
store.
A
Going
on
to
the
resources
tab,
we
took
the
liberty
of
putting
up
a
resources
link
here,
michael
on
how
to
get
started
with
portworx.
You
know
the
the
operator
that
you
folks
have
that
you
built
with
us,
is
made
available
and
published
and
distributed
via
the
red
hat
catalog.
We
have
the
link
up
there
and,
of
course,
openshift
commons,
probably
one
of
the
one
of
the
the
most
exciting
things
that
I've
had
an
opportunity
to
work
with
here
at
red
hat.
We
also
have
a
link
to
it
there.