►
From YouTube: APAC Hybrid Cloud Kopi Hour (S0E3) | Live Demo! Red Hat Connect APAC Technical Keynote.
Description
Join Kopi Hour co-host Steve Ellis fresh off presenting at Red Hat Connect in Jakarta, Sydney, and Melbourne! You'll get a front row seat to the conference's Technology Keynote: "Open Hybrid Cloud: The Foundation for a Robust Digital Transformation". See the demo and hear stories about its creation, motivation, goals, and if we're lucky, some interesting backstage (mis)adventures associated with producing a large-scale APAC-focussed demo!
00:00 Intros
07:30 Demo presentation kicks off
48:50 Demo concludes and we discuss!
A
A
A
Hello
and
welcome
everyone
to
our
third
exciting
beta
edition
of
the
APAC
hybrid
cloud
copy
hour.
So
again,
I
put
the
the
title
up
there
because
I'm
not
saying
coffee,
I
gotta
tell
you
this
I'm
saying
copy
or
copy
traditional
coffee
beverage
that
you
find
in
Singapore
that
we
we
wanted
to
Brand
the
show
with
so
this
week.
We
have
kind
of
an
exciting
thing:
I'm
not
joining
you
from
Qatar,
but
I
am
joining
you
in
my
Belgian
Red
Devils
football
jersey.
A
It's
devil
time,
I
become
the
the
best
fair
weather
fan
for
football
this
time
of
year
and
and
stay
up
all
night
and
watch
matches.
I
barely
understand
so
I
figured
I'd
do
that,
but
in
a
more
exciting
way,
we've
got
our
regular
contributors
this
week
and
we
have
Deb
Schoenberg
Dev.
Why
don't
you
go
ahead
and
put
the
wrong
thing
up,
but
go
ahead
and
introduce
yourself
say
hello.
B
C
Hey
thanks,
August
yeah,
so
I'm
part
of
our
APAC
officer
technology,
team
and
and
we've
recently
spent
quite
a
bit
of
time
on
the
road
talking
about
redact
technology
and
actually
showing
it
in
action
at
some
of
our
Customer
Events
here
across
Asia.
So
you
know,
I
was
lucky
enough
to
attend
events
in
Jakarta
and
over
in
Australia,
and
some
of
my
colleagues
covered
also
our
events
in
Mumbai
Tokyo
and
we
had
a
team
in
Korea
running
it
and
we
of
course
had
an
event
in
Singapore.
C
It's
been
a
busy
period
and
it's
been
really
nice
to
actually
get
out
in
front
of
the
customers
and
hear
what
they
want
to
what
they
want
to
see
from
red
hat,
but
actually
be
able
to
show
our.
You
know:
hybrid
Cloud,
Technologies
in
action,
and
that
seemed
like
the
most
the
really
cool
part
about
this
and.
A
That's
what's
so
cool
is
so
Steve
talking
about
is
talking
about
the
red
hat
Summit,
connect
events
that
we've
done
across
the
world,
they're
sort
of
a
spin-off
that
came
I
think
during
covert
times
of
a
way
of
bringing
the
excitement
of
red
hat
Summit
to
each
region.
I
think
there's
been
different
versions
in
APAC.
What
did
we
have
before
that?
You
guys
did.
C
We
used
to
run
a
red
hat,
Forum
event
similar
model,
but
now
they've,
like
shifted
The
Branding,
to
kind
of
piggyback
off
our
Global
Red
Hat
Summit
event-
and
it
really
is
I-
think
connects
a
great
term
for
this,
because
it
really
is
an
opportunity
to
connect
with
our
customers
and
partners
and
allow
them
to
connect
with
each
other.
So
a
big
focus
of
it
is
our
customer
stories
and
we
we
use
it
as
a
way
to
recognize
customers.
Who've
done
really
exciting
things.
Yeah.
C
I
really
loved
attending
the
one
in
Jakarta,
because
we
hear
we
heard
similar
themes
to
what
I'm
hearing
say
in
the
ANZ
region.
It
was
really
impressive
to
see
how
they
used
a
chunk
of
our
Technologies,
to
build
the
platform,
to
track
vaccinations
and
to
track
you
know,
covert
infections
and
to
deal
with
an
awful
are
those
you
know:
Health
Care,
impacts
of
the
pandemic,
and
you
imagine
trying
to
do
that
at
the
scale
of
a
country
like
Indonesia.
It
really
was
quite
impressive.
A
Yeah
I
was
lucky
enough
actually
to
attend
the
the
ones
in
Sydney
and
Melbourne,
and
the
partner
side
of
it
was
was
also
fascinating
too,
because
our
partners
are
doing
so
much
for
us
and
to
actually
get
to
connect
with
them
directly.
You
know
face
to
face
the
the
partner
event.
The
ecosystem
event
was
held
just
before
the
connect
event,
so
it
really
joined
the
two
in
a
great
in
a
great
way.
B
Yeah
I
didn't
get
to
go,
but
they
were
live
as
well
online,
so
that
was
a
good
thing
travels
back,
so
that
must
be
really
exciting.
You
know
we
did
a
couple
of
customer
engagements
in
Sydney
and
other
places.
I'm
sure
you
know
you
guys
must
have
enjoyed
traveling
and
you
know
meeting
with
the
customers
connecting
with
me.
A
Yeah,
it's
so
much
more
real
when
you're
able
to
to
have
those
conversations-
and
you
know,
standing
in
the
hallway
or
to
watch
the
session
and
then
with
all
that
energy
after
the
Applause
to
speak
to
the
speakers
and
find
out
how
it
really
went
and-
and
so
I
agree
with
you
Steve
calling
them
connected.
It
just
suits
it
perfectly,
especially
in
a
post-pandemic
world,
because
we
all
got
so
disconnected
and
it
allowed
us
to
really
come
back
together
and
plug
back
in.
C
And
a
big
part
of
our
conversation
at
the
moment
is
this
pitch.
We
have
about
an
open,
hybrid
cloud
and
to
actually
show
that
in
action
and
I'm,
never
a
fan
of
can
demo
I
want
a
live
environment
and
and
so
to
actually
stand
on
stage
and
run
openshift
at
scale
and
show
workloads
how
it
impacts
or
changes.
C
A
Out
there,
yeah
and
Steve
and
I
have
been
talking
about
the
demos
he
was
putting
it
together
and
and
weeks
before
we
even
had
the
copy
hour
and
he's
like
you
know
we
could
do
this,
there's
a
live
stream
and
I'm
going.
Oh,
can
you
can
you
so
I'm
so
excited,
because
I
got
to
go
and
watch
Steve?
Do
it
twice,
along
with
all
the
other
great
presentations
and
I'm
sitting
here?
A
It's
the
keynote
Tech
demo
yeah
done
live,
but
with
a
little
bit
of
a
behind
the
scenes,
and-
and
you
know
folks,
like
Dev
he's
not
had
the
chance
to-
he
wasn't
there
to
see
it
so
he's
going
to
get
to
see
it
live,
and
we
can
hear
a
bit
about
the
stories
about
how
how
it
went
and
what
it
was
like
at
these
venues
and
and
all
that
kind
of
stuff.
So
I
I
just
so
glad
to
have
this
opportunity.
C
Yeah
and
if
you're
on
the
stream,
please
feel
free
to
jump
in
and
ask
some
questions
yeah
and
also
realize
this
is
a
real
thing.
It's
a
real
demo
that
my
peers
here
in
in
the
region
now
have
access
to.
So
if
you
want
to
actually
see
this
in
action
reach
out
from
the
red
hat
team
and
they
can
actually
come
in
and
rerun
this
with
you
yeah.
A
I
definitely
encourage
that
as
well.
You've
got
folks
here
on
the
stream,
who
are
you
know
in
Sydney,
Melbourne
and
New
Zealand,
so
here
in
Auckland
Auckland,
but
you
know,
we've
got
people
in
Singapore
and
everything
we
we
can.
We
can
do
this
demo
for
your
customers
for
yourself,
if
you're
a
customer,
we
can
we'd
really
like
to
share
it,
but
it's
really
nice
that
it's
kind
of
captured
here
so
that's
exciting.
C
And
yeah
so
I'm
just
going
to
start
with
a
quick
photo.
This
is
actually
the
venue
in
Jakarta
and
the
great
that
this
was
an
awesome
venue.
It
was
a
really
good
event
team
and
the
great
thing
about
this
environment
was
that
we
could
go
to
a
split
screen,
so
we
could
have
a
combination
of
the
technical
demo
on
the
slides
up.
At
the
same
time,
it
made
for
a
very
kind
of
engaging
format.
C
Now
it's
actually
a
bit
harder
to
do
this
on
a
web
stream,
so
I'm
just
going
to
kind
of
alternate
between
a
bit
of
slight
content,
which
is
about
setting
the
context,
but
most
the
time
I
actually
want
to
be
inside
the
technology
and
showing
it
off.
So
this
was
just
to
give
you
a
little
bit
of
a
flavor
of
that
before.
A
C
And
this
leads
into
our
own
Vision,
the.
Why
why
we
think
open
hybrid
Cloud's,
important
so
I've
just
borrowed
a
slide
from
like
the
opener
just
to
kind
of
set
some
of
the
scene,
because
when
we
talk
about
open
hybrid
cloud,
we
do
truly
mean
hybrid
for
us
our
hybrid
stories,
much
more
than
you
know,
a
bunch
of
hyperscaler
environments,
it's
everything
from
the
public
Cloud
through
to
your
on-premise
infrastructure.
Through
to
your
you
know,
Edge
devices,
wherever
you
need
to
run
your
business.
C
That's
our
view
that
a
true,
hybrid
Cloud
needs
to
be
and
open.
That's
red,
Hat's
DNA-
and
you
know
we
say
here
about
being
an
open
source
leader.
Our
open
hybrid
cloud
is
fundamentally
built
on
open
source
technology
and
under
the
hood,
one
of
the
core
components
of
that,
of
course,
is
Red
Hat
Enterprise
Linux,
and
that
brings
us
that
security
layer,
we
kind
of
need
which
again,
is
very
very
critical
to
this
conversation.
It
you
know
we
hear
about
all
of
these.
You
know
new
security
vulnerabilities.
C
When
your
bills,
on
a
secure
platform,
you
get
a
higher
degree
of
assurity
and
and
we
kind
of
live
and
breathe
security
here
at
Red
Hat
every
day,
and
then
on
top
of
that
we
know
we
acknowledge.
Customers
aren't
just
running
in-house
applications,
they're
running,
what's
known
as
cots
off
the
shelf
common
off
the
shelf,
they
might
be
where
you
know
using
things
develop
for
them
by
custom
Partners.
You
know
custom
Tech
by
Partners,
so
our
partner
ecosystem
is
incredibly
important
and
we've
literally
got
thousands
I.
C
Think
it's
about
49
000,
certified,
isvs
and
Global
sis
delivering
Solutions
today
on
Red
Hats
platforms,
as
I
mentioned
this
being
agnostic.
That's
a
key
component
of
our
open,
hybrid
Cloud
story.
So
we
can
run
this
where
you
want
to
run,
and
that
means
it's
much
easier
to
then
reduce
that
cognitive
load.
You
do
things
once
and
repeat
them
everywhere
and
on
top
of
this,
your
developer
doesn't
want
to
care
about
the
infrastructure
and
where
they're
deploying
code
or
optimizing
it
for
Amazon
versus
Azure
versus
running
on
an
on-premise
hypervisor.
C
They
just
want
to
deliver
the
code.
Your
organization
needs.
So
these
are
some
of
the
themes
we
dig
into
as
we
go
through
the
story
and
we're
gonna.
Do
it
in
the
context
or
through
the
lens
of
a
virtual
customer
and
something
we're
all
really
familiar
with.
So
our
virtual
kind
of
customer
story
here
is
about
a
web
retailer
cool
stuff
store
inc,
who
are
like
a
North
American
Web
retailer.
You.
B
C
We've
all
done
far
too
much
shopping
in
the
last
few
years
online,
because
that
kind
of
became
the
norm
and
you
think
how
those
organizations
had
to
adapt
and
change
yeah
and
then
you
think
about
the
big
shopping
events
we're
on
top
of
a
Black
Friday
Type
window.
Now,
if
you're
running
a
traditional
kind
of
storefront,
how
do
you
scale
that?
How
do
you
scale
something?
C
That's
a
very
old-school,
traditional
storefront
when
you're
dealing
with
a
huge
bump
in
customers
in
a
huge
increase
in
load
and
many
organizations
struggle
at
those
windows
and
many
organizations
struggled
with
you
know
the
increase
in
traffic
during
you
know
the
pandemic,
so
we're
using
that
as
a
kind
of
context
to
set
the
story.
I.
A
Really
love
that
because
it
really
gives
that
I,
don't
know
it's
that
that
kind
of,
especially
with
Black
Friday
just
a
week
away
and
all
the
sales
I
mean
I'm,
getting
the
emails
already,
but
I
love
how
you
how
you
guys
do
that
you
always
have
these
very
real
world
demos
I
can
just
let
let
someone
just
get
right
inside
it.
It's
really
cool
yeah,
I,.
C
Mean
right
now
I'm
getting
similar
things
for
like
singles
day,
which
was
never
a
thing
in
New
Zealand
a
few
years
ago,
and
we've
done
a
lot
of
Demos.
In
the
past,
we've
took
we've
been
across
a
range
of
Industries.
Ultimately,
a
large
range
of
Industries
have
some
kind
of
storefront.
If
you're
a
bank,
you
have
a
customer
facing
application.
If
you're
in
telecommunications,
you
have
some
kind
of
customer
facing
platform.
If
you're
a
government
Department
you've
usually
got
some
customer
facing
service,
you
have
a
web
portal
of
some
kind.
C
C
Yeah
and
we're
going
to
start
the
story
where
the
north
american-centric
they
want
to
expand
geographically.
They
can't
do
that
because
it's
a
big
traditional
monolithic
application,
so
we're
going
to
take
you
through
their
transformation
story
where
their
developer
wants
to
cut
code.
Luckily
they're
using
some
kind
of
source
code
management,
but
they're
deploying
on
Legacy
infrastructure
and
if
they're
lucky,
you
know
sorry,
we
I
mean
most
organizations
have
been
there
before
operations
kind
of
becomes
a
bottleneck.
C
Now,
as
these
customers
transform,
they
need
to
start
bringing
in
some
kind
of
CI
CD,
and
you
know
this
could
be
using
openshifts
Technologies.
It
could
be
some
external
solution
integrated
with
openshift.
It
could
be.
You
know
many
organizations
already
going
down
a
CI,
CD
Journey,
that's
fairly
critical,
because
that
gives
you
that
consistency.
You
need
and
means
that
the
developers
are
just
worried
on
cutting
code.
C
Then
you
need
a
consistent
platform,
and
this
is
where
we
try
to
bring
an
open
shift.
You
know,
openshift
is
a
consistent
platform
means
you
have
the
same
platform,
whether
you're
on
on
premises,
Legacy
or
bare
metal
infrastructure
or,
if
you're
running
on
the
hyperscalers,
and
then
operations
is
going
through
this
change
as
well.
C
We
go
on
about
devops
devsecops,
but
platform
engineering
is
becoming
quite
an
important
term
and
around
that
has
to
be
changing
the
way
we
actually
manage
the
environments
and
we've
pushed
the
management
approach
for
a
long
time
at
red
hat
with
our
satellite
technology
for
traditional
Linux
workloads
in
the
openshift
ecosystem.
This
really,
where
Advanced
cluster
management
comes
in,
so
that
we
now
start
to
be
able
to
offer
a
better
pane
of
glass,
not
a
single
paneer
glass,
but
it's
an
overarching
view
a
way
to
manage
our
openshift
environments
at
scale.
C
Multiple
clusters
geographically
dispersed
and,
as
I
said
earlier,
security
can't
be
an
afterthought,
so
our
security
product
integrates
into
this
whole
journey,
both
from
an
operational
infrastructure
perspective
and
into
the
developers
part
of
the
journey.
So
this
is
where
we
kind
of
go.
When
we
went
through
the
story,
there
was
a
lot
of
elements
we
wanted
to
include
here,
and
we
kind
of
just
use
the
slides
to
give
her
the
the
audience
like
a
keystone
to
know
where
we
are
in
the
journey
as
we
go
through
it.
A
And
that
that
bit
above
the
infrastructures,
I
just
love
it
right,
we
always
talk
about
the
openshift
part
being
there,
but
I
love
that
ACM
that
either
you've
got
ACS
in
there.
So
these
two,
the
security
product,
the
management
product,
because
it
is
that
that's
the
same
that
can
be
normalized
across
all
that
infrastructure.
Yes,.
C
And
this
is
part
of
what
we
call
openership
platform
plus
and
the
plus
really
is
kind
of
key
here.
There's
some
other
parts
in
here.
We
don't
really
dig
into
because
we're
trying
to
deliver
this
in
about
25
minutes
yeah
on
stage
so
there's
a
lot
of
things
are
going
to
go
through
fairly
fast
and
we're
covering
kind
of
Three
core
pillars
here,
we're
talking
about
the
benefits
of
adopting
a
proper
open,
hybrid
Cloud
infrastructure.
C
How
that
changes
and
can
really
accelerate
application
development,
as
you
start
to
look
at
Cloud
native
development
approaches
and
then
really,
if
you're
going
to
do
this,
you
need
to
bring
in
it
Automation
and
management
practices,
because
you've
got
to
do
this
at
scale
without
sacrificing
stability
and
without
sacrificing
security.
So
that's
kind
of
core
to
the
the
steps
we
kind
of
go
through,
so
the
first
pillar
really
is
going
back
to
where
we
begin
like
where's
the
customer
starting
from-
and
this
might
be
familiar
to
a
bunch
of
you.
C
C
You
think
about
the
impact
on
your
time
to
Value
how
long
it
would
actually
take
you
to
get
that
change
out
through
your
organization,
which
is
why
a
lot
of
organizations
where
pushing
out
production
changes,
weekly
or
monthly
or
even
quarterly,
because
you
know
things
might
get
as
far
as
tests
be
rolled
back
new
iterations
each
time,
there's
a
lot
of
hand-holding
involved
and
even
worse,
all
too
often
in
some
cases,
even
the
push
to
Dev
required
operations,
so
developer
would
package
something
up.
Send
it
with
some
install
notes.
C
Operations
would
install
it
and
that
really
does
kind
of
impact
your
delivery
times,
and
we
go
now
about
you
know
time
to
value,
and
you
know
developers
are
so
important
to
organizations.
How
do
we
change
this
and
one
way
we
can
change
this
is
through
this
hybrid
Cloud
infrastructure
adoption
you
might
think.
Well,
how
does
that
change
things
for
just
for
the
developers
as
well
as
operations?
C
Well,
in
our
story
here
we
say:
well,
let's
leverage
some
more
existing
infrastructure
or
bring
in
our
Advanced
cluster
management
for
kubernetes
and
we'll
run
that
on
our
hypervisor
platform
will
continue
to
leverage
the
value
the
money
we've
spent
on
our
bare
metal
infrastructure.
Well,
and
we
we
know
that
our
application
needs
a
bit
of
grunt
to
run
in
production,
so
we'll
run
openshift
on
that
at
scale.
C
But
where
do
we
run
our
developer
workloads?
How
do
we
get
developers,
agility
and
scaling
your
developer
footprint
can
be
quite
difficult
because
all
too
often
you've
had
one
development
environment.
That's
shared
across
a
range
of
development
teams.
Maybe
you've
got
half
a
dozen
environments
shared
across
30
development
teams.
Why
not
host
your
development
environment
on
an
open
shift
service?
We
have
a
cloud
service
called
Azure
red
hat
openshift
that
we
jointly
manage
in
conjunction
with
Microsoft,
because
it's
a
managed
service.
C
You
can
elastically
scale
it
as
you
need
to
meet
the
number
of
development
workloads.
You
have
at
any
point
in
time
and
openshift
here
is
acting
as
the
normalizer,
so
that
all
the
team,
all
the
environments,
are
running
the
same
kubernetes
platform
and
if
I
just
jump
into
our
ACM
console
here,
we
can
see
our
infrastructure,
so
I
can
see
how
many
nodes,
how
many
clusters
I'm
operating,
how
many
pods
are
running
if
I
just
want
to
look
at
this
cluster
I
can
see
its
scale
and.
A
C
And
here
I
can
see
the
workloads
of
introspected
and,
unlike
the
the
kind
of
joke
to
the
audience
during
the
demo,
is
oh,
my
God.
My
developers
must
be
running
Pac-Man
in
their
downtime
because
the
Pac-Man
application
has
been
deployed,
and
this
is
quite
a
familiar
little.
You
know
container
app
a
lot
of
people
use
for
demos,
so
it's
quite
a
nice
one
to
to
include.
But
if
I
I
kind
of
look
through
here,
I've
got,
you
know,
normalized
environment
across
my
range
of
infrastructure
I
can
create
new
clusters.
C
C
I
also
now
need
to
just
cut
code.
I
need
to
be
hands
off
in
the
rest
of
the
experience.
So
this
is
where
we
start
to
bring
in
CI
CD.
This
is
fairly
critical.
We
need
consistent
way
to
deploy
whether
it's
into
Dev
or
production,
regardless
of
of
the
environment,
but
we
said
earlier,
we
need
more
than
just
consistency.
We
need
co-quality,
we
need
security.
So
for
the
story
we
bring
in
advanced
customer
security
because
that
can
actually
be
used
as
part
of
our
pipeline.
C
We
can
analyze
our
container
images
as
they're
being
built,
not
just
as
they're
being
deployed,
so
we
can
actually
prevent
potential
new
conflict
security
compromises
early
on
in
the
development
cycle.
We
shift
the
problem
left
and
then
Sona
cube
is
one
of
the
many
tools
out
there
for
doing
things
like
code,
quality
checks
and
unit
testing.
So
that's
the
one
we
used
as
part
of
this
Argo
CD
is
really
well
known
in
the
industry
and
that's
actually
part
of
openshift
get
Ops.
C
So
when
you
actually
deploy
openshift,
you
get
openshift
pipelines
and
get
ups
and
a
bunch
of
other
tools
out
of
the
box.
So
everything
we're
showing
here
isn't
just
about
driving
the
experience.
It's
all
runs
on
openshift
we're
hosting
the
tools
we
need
on
the
environment
that
we're
using
for
the
demo.
A
C
Just
amazing-
and
this
is
where
we
then
move
into
the
the
couple
of
the
key
developer
eccentric
parts
of
this.
You
know
the
inner
loop
is
a
concept
where
the
we
have
these
two
things:
the
inner
loop
and
the
outer
loop,
the
inner
Loops.
Where
the
developer
lives.
The
developer
is
King.
The
developer
is
driving
those
outcomes.
The
organization
needs
the
new
enhancements,
the
business
needs
and
all
they
really
want
to
do
is
cut
code
and
and
make
sure
that
gets
built
and
deployed,
and
they
may
need
to
debug
the
code
during
that
process.
C
But
most
of
the
time
should
be
focused
on
the
code
not
on
where
it
lives
or
how
it
runs.
The
outer
loop
is
where
we
want
to
make
sure
we
have
software
supply
chain
security.
We
want
to
make
sure
we
have
consistency,
we
want
to
make
sure
we
meet
our
compliance
requirements.
We
want
to
do
our
test
automated
tests.
This
is
really
really
crucial.
C
C
Openshift
has
a
developer
perspective,
so
I
can
immediately
see
how
my
application
is
behaving.
I
can
see
based
on
the
work.
The
project
I'm
associated
with
I
can
see.
Meta
data
that
previously
I'd
have
asked
to
ask
for
permission
from
operations
to
get
access
to.
I
can
dig
into
things
like
the
logs
on
the
applications.
I'm
running
I
can
look
at
my
build
pipelines,
which
is
critical
in
the
kind
of
the
next
part
of
our
story,
and
I
can
look
at
our
the
topology
of
the
application.
C
I've
got
deployed,
so
here
we've
now
taken
our
Legacy
app
and
we
actually
deployed
as
microservices.
We've
got
a
catalog
service,
an
inventory
service,
there's
a
pricing
service
and
we
actually
have
our
web
user
interface.
So,
if
I
just
pull
that
up,
let
that
load
fresh.
So
now
we
have
so
as
a
developer.
I
can
get
into
there
and
through
this,
I
can
go
and
look
at
other
details,
including
the
logs
and
observe
the
environment,
and
see
how
it's
behaving
without
put
calling
on
Ops
with
able
to
raise
a
ticket.
C
A
C
C
Yeah
because
the
the
overall
shopping
experience
I
mean
this
is
why
this
is
quite
a
good
useful.
App
to
use,
isn't
great,
it
doesn't
have
a
good
UI,
it
doesn't
have
good
end
user
feedback
and
so
imagine
as
a
business
you
go.
Oh,
we
want
an
enhancement,
we're
not
good
customer
retention.
How
can
we
change
this
so
that
we
can
see
our
shopping
cart?
We
get
better
feedback.
I
know
you
know
where
I'm
buying
other
than
I
have
8.99
in
the
card.
I've
got
very
little
information.
C
So
what
we've
got
is
a
developer
view
on
this.
Let's
look
at
this
in
a
loop
outer
loop
story,
let's
write
some
code
and
then
see
what
happens
so
I'm
going
to
jump
in
and
change
some
code
now
in
this
case,
because
we're
just
using
like
a
normals
kind
of
source
code
management
system
based
on
git
I
can
just
go
and
write
code
in
pretty
much
any
IDE.
I
want
now
we're
using
vs
code
web
here,
because
again,
I
can
host
this
on
top
of
the
openshift
environment.
C
But
this
could
be
your
favorite
idea
of
choice
on
on
your
developer's
local
desktop.
So
I'm
just
going
to
bring
in
a
floating
shopping
panel
change
and
I'm
also
going
to
bring
in
second
change,
which
is
some
unit
tests,
some
additional
unit
tests,
because
again
we're
going
about
code
quality.
We
want
to
make
sure
we've
got
solid
tests.
So
let's
commit
that
change.
C
So
let's
take
a
look
at
what's
really
happening
behind
the
scenes
from
the
moment.
I
kind
of
commit
my
code
as
a
developer.
I
can
go
and
have
a
look
at
our
build
pipeline
so
because
we've
built
these
pipelines
using
openshift
pipelines.
The
moment
I
committed
that
code.
My
pipeline
run
kicked
in
so
we're
now
performing
the
initial
code,
quality
checks
and
unit
tests,
and
then
we
go
through
the
rest
of
the
pipeline.
C
The
great
thing
is:
I
can
jump
in
and
immediately
see
the
logs
for
everything
that's
happening
again
without
requiring
that
interaction
with
operations
and
our
pipeline
fails.
So
this
is
a
good
little
bit
of
the
story
we
go.
Oh
no.
My
release
has
failed
because
of
a
unit
test
issue,
so
we
actually
show
we've
caught
a
problem
and
it
requires
a
second
code.
Change
I
actually
need
to
go
and
remove
this.
A
And
I'll
just
I'll
just
interrupt
during
the
demo
when
Steve
does
this
he's
so
good
at
it
right
and
I'm
sitting
there
and
he
goes?
Oh,
it's
failed
and
I
spoke
to
people
after
it
and
they
all
believed
you
they
thought.
Oh
you
had
that
moment
of.
Oh
no
live
Demo's
gone
wrong,
and
so
it's
create
such
empathy,
both
with
the
customers
in
the
audience
who
have
lived
this
in
in
production,
environments
and
people
who
are
interested
in
Tech
and
demos
who
have
lived
that
failure
in
real
reality.
C
A
C
This
isn't
a
real
environment,
it
wouldn't
the
developer,
wouldn't
be
sitting
here
waiting
for
it
to
fail.
You'd
have
this
hooked
into
page
of
Judy
or
teams,
or
slack
or
Google
chat
or
whatever
platform
you're
using
for
your.
You
know,
developer
conversation
and
the
development
team
would
just
be
alerted.
Oh
your
bill
failed
debugging
that
then
well
you
can
have
the
the
log
data
just
pushed
into
the
channel.
C
They
may
not
even
need
to
come
and
check
anything
inside
openshift,
but
if
they
want
to,
they
don't
need
to
ask
permission
so
I've
made
that
change
and
got
the
pipelines
kicked
off
again.
The
moment
I
made
that
change
and
we're
now
going
through
the
rest
of
the
pipeline.
So
we've
now
done
the
scans
quality
checks
were
moved
into
the
build,
and
you
know
what
we're
moving
into
here
is
the
outer
loop.
But
this
is
where
we're
actually
guaranteeing
that
we've
got
a
secure
software
supply
chain,
and
this
looks
a
little
bit
like
this.
C
The
developer
Cuts
code
and
they're
done.
That's
where
they
value
that's
what
they
do.
They
don't
want
to
worry
about.
Is
it
going
to
Dev?
Is
it
going
to
prob?
Where
is
it
being
deployed?
Is
it
on
premises,
I,
don't
care,
but
that
then
triggers
the
openshift
pipeline,
and
the
first
part
is
that
initial
code
scan
and
unit
test-
and
here
we
use
sonar
Cube-
which
again
in
this
case
is-
is
running
on
top
of
openshift.
C
C
It
also
looks
for
potential
bugs
and
issues,
so
we've
got
a
couple
of
books
highlighted
which
is
just
common
HTML
formatting
issues,
the
sort
of
thing
that
you
just
hand
over
to
your
web
team
and
they
go,
and
you
know,
push
a
quick
change
to
go
and
tidy
up
your
HTML
tags
and
make
sure
things
are.
You
know
compliant
with
modern
HTML
standards,
but
you
can
control
how
this
is
gated.
B
C
C
So
at
this
point
in
the
in
the
process,
we
are
performing
a
real
build
and
then
we
pass
it
off
to
Advanced
cluster
security-
and
this
is
the
thing
I
said
earlier
is
ACS
is
great
because
it
can
perform
image,
scans
and
image
analysis
and
other
tests
on
components
within
your
application
during
your
build
process,
and
it
can
also
do
cluster-wide
security
and
look
at
your
overall
cluster
health
and
and
including
looking
at
the
health
of
third-party
components.
You've
got
deployed,
but
it's
really
important.
C
So
if
we
jump
into,
let's
see
our
pipelines
going
right,
we're
still
running
we're
getting
most
of
the
way
through
it.
So
here's
our
ACS
dashboard.
So
this
lets
us
do
things
like
Define
custom
security
policies
around
you
know
the
age
of
of
packages
or
libraries.
We
constantly
we're
we're
pushing
policies
out
to
our
customers
all
the
time
as
new
vulnerabilities
come
become
available.
You
can
import
custom
policies
if
you
want
to
set
particular.
You
know,
standards
for
your
organization.
C
We
actually
have
a
critical
vulnerability
raised
here
and
it's
actually
in
the
sonar.
Cube
version
we've
got
deployed,
which
basically
means
we
need
to
go
to
our
you
know,
platform
operation.
You
know
our
platform
team
and
say
you
know
they
need
to
go
and
update
this,
because
it's
a
third-party
component,
we're
actually
introspecting
those
third-party
containers
to
look
for
vulnerabilities,
I.
A
Think
there's
overall
health.
This
is
almost
like
a
meta
moment
in
your
demo
in
your
presentation,
because
you're
sitting
there
going
I
have
to
look
after
my
code
and
my
developers
will
be
happy
and
then
you
go
hang
on
a
sec.
I
can
look
after
my
environment
too
I'm,
not
just
here
to
say
developers.
You
know
you
got
to
get
your
stuff
right
and
you
got
to
get
yours
it's
this
moment
where
everybody
kind
of
goes.
A
That's
right
and
you
bring
you
bring
your
audience,
and
so
you
bring
us
on
that
Journey.
So
we
get
that
we
get
that
realization
on
our
own
and
the
buzzwordy
devsecops,
which
is
great.
We
kind
of
go
right,
so
it
there.
It
is
that's
it
happening
right
there
and
for
me
this
was
that
kind
of
moment
where
I
did
I
settled
back
when
the
chair
went
boom
I,
don't
say
that.
But
you
know
what
I
mean
like.
C
C
Luckily,
we
didn't
have
that
crop
up
during
this,
so
we
now
move
back
through
our
pipeline,
and
this
is
where
we
tag
a
release.
This
is
really
important.
You
don't
just
really
push
latest
or
something
when
you're
releasing
containers
in
an
Enterprise
environment.
You
need
to
know
what
version
you're
running
where
we
then
push
that
tag
release
into
our
local
container
registry.
That
could
be
the
openshift
one.
It
could
be
our
Quay
Enterprise
grade
registry
and
then
we
push
a
update
into
our
configuration
repository,
so
we
actually
run
two
git
repositories.
C
First,
the
configuration
repository
is
very
important
when
you're
looking
at
things
like
get
Ops,
because
this
is
where
we
start
triggering
the
next
part
of
the
pipeline.
This
is
where
Argo
CD
comes
in,
where
we
guarantee
consistent
deployment
or
delivery
of
the
app
out
onto
in
this
case,
a
development
environment.
We
can
gate
our
releases.
We
can
know
that
we're
running
you
know
version
one
two
three
in
Dev
and
we're
only
one
two
two
in
prod,
because
we're
running
explicitly
tagged
versions.
C
C
C
There
we
go
now,
it's
sinking
now
it's
pushing
that
update
out,
so
that
takes
a
few
minutes
to
run
so
normally
I'd
be
spending
a
bit
longer
inside
our
inside
ACS.
Talking
about
its
features,
we'd
be
spending
a
little
bit
of
time
here,
because
this
is
a
live
thing.
You
know
we're
going
to
wait
for
the
code
to
actually
get
deployed.
It
takes
a
few
minutes
and.
A
C
C
They've
been
told
that
there's
been
a
problem,
they've
come
back
and
they've
fixed
the
code
and
everything
else
is
automated
and
then
once
we're
happy,
we
can,
you
know,
make
use
whatever
our
change,
release,
processes
and
say
that
we're
now
going
to
tell
Argo
to
push
that
change
into
test
or
into
production,
and
it
will
take
care
of
all
the
heavy
lifting
for
us.
So
let
me
go
and
see
if
the
application
has
refreshed.
Now.
C
Yes,
that's
looking
good
and
we
now
have
our
floating
shopping
cart
and
you
notice
it
still
has
my
drink
bottle
in
the
car.
So,
even
though
that's
a
refreshed
the
application,
it
hasn't
changed
any
of
my
data,
so
if
you're
managing
this
properly,
the
idea
is
that
you
can
try
and
do
these
like
non-customer,
impacting
changes
and
do
a
b
releases.
Canary
releases,
whatever
kind
of
release
model,
suits
your
organization
when
you're
actually
pushing
this
out
to
production.
C
So
we've
shown
a
little
bit
of
that
kind
of
developer
view.
So
the
developer
right
now
is
just
focused
on
what's
important
to
them
and
the
organization's
getting
that
security
and
we've
shown
a
bit
of
the
benefits
around
Automation
and
management,
because
we're
automating
that
deployment
process
we're
implementing
that
devops
or
devsecops
or
githubs
or
whichever
Ops
your
organization
wants
to
do,
and
one
thing
that
comes
up
as
a
question
is
well
who
owns
Which
bit
because
in
some
organizations
a
team
will
own
the
pipelines
in
some
organizations
the
developers
own
the
pipelines.
C
C
C
So
now,
we'll
now
move
on
to
the
last
bit
of
the
story.
Remember
when
we
started
this,
we
talked
about
North
American
Retailer,
wanting
to
expand
geographically,
so
if
they
want
to
expand
into
Asia,
why
not
do
it
again
using
an
open
shift
cloud
service
in
this
case
we're
going
to
use
red
openshift
on
AWS
or
rows
or
as
our
example,
but
this
could
be
any
openshift
environment
running
somewhere
in
in
the
region.
We
we
want
to
run
as
close
as
possible
to
our
customers.
C
C
Putting
it
close
to
your
customers
is
critical,
but
if
you're
expanding
into
a
new
region,
you
don't
know
what
your
customer
demand
is
going
to
be.
So
you
maybe
want
to
manage
your
costs.
You
don't
want
to
buy
new
hardware.
You
want
to
deal
with
things
elastically
so
and
using
openshift
as
the
platform
means
we
have
this
common
platform
for
Dev
test
uat
prod,
with
a
common
platform
in
North
America
and
in
Asia
Pacific.
C
We
want
to
expand
into
emea
into
Europe
again
we
can
have
a
common
platform
and
we're
still
leveraging
Our
Kind
Of
release
management
process,
our
CI
CD
back
end,
our
git
Ops
based
environment.
So
where
do
we
benefit
with
red
Hat's
approach,
so
here
through
ACM
I
can
actually
go
and
create
clusters
from
scratch,
and
it's
fairly
quick
about
30
minutes
for
most
infrastructure
providers,
but
for
the
demo
we're
running
low
on
time,
so
I'm
going
to
import
one.
C
We
built
a
few
minutes
ago,
I'm
actually
going
to
grab
the
credential
from
here,
so
I'm
going
to
grab
a
token
quickly
now.
This
is
a
limited
time
token.
So,
if
any
of
you
want
to
go
and
grab
this
after
the
session
and
try
and
borrow
my
environment,
it's
tough
because
it
won't
exist,
so
we're
going
to
grab
that
token.
C
C
So
we'll
jump
back
to
my
overview
there
we
go
so
that's
important
in
the
background,
but
if
it's
going
to
create
this
from
scratch,
I
can
go
through
here.
We
support
quite
a
range
of
infrastructure
providers.
Today,
our
bare
metal
approach
to
this
has
now
been
deprecated
because
we
have
this
new
assisted
installer,
and
this
is
awesome
because
we
know
customers
have
interesting
networks,
unique
Hardware.
C
In
some
cases
they
may
be
deploying
insecure
environments
where
they
need
to
do
it
offline.
So
our
new
assistant,
installer,
is
really
good
because
you
can
manage
offline
installs
and
you
know
highly
secure
environment
type
deployments.
So
it
does
give
us
a
lot
more
flexibility
in
terms
of
supporting
other
infrastructure
platforms.
C
If
I
was
deploying
on
Amazon
I'd
just
provide
a
credential,
you
can
actually
pre-cache
credentials
inside
this
you'd
give
it
a
name,
maybe
I'm
gonna,
deploy
now
into
Europe
and
I
can
actually
select
where
in
the
world
we
currently
support
deployment
for
openshift
on
Amazon.
So
I
can
do
all
that
through
the
interface
you
might
say.
Well,
that's
not
very
kind
of
get
opsy.
It's
a
bit
kind
of
clicky
clicky
Hands-On.
C
Well,
when
you've
defined
it,
you
can
actually
go
and
Export
the
yaml
definition
and
then
use
that
via
your
command
line,
tooling
import
it
into
your
source
code
management
and
customize
it.
So
it's
a
great
way
to
actually
build
the
configuration
you
want
to
use
as
well,
so
fingers
crossed
yeah,
it's
imported
right,
which
is
always
fun
yeah.
B
A
C
Yeah,
let
me
log
in
so
that's
how
fresh
this
environment
is
because
I
only
got
the
credentials
today.
Fingers
crossed
it's
actually
all
up
and
working,
so
the
this
will
bring
me
in
with
a
normal
kind
of
open
shift
admin
interface
already
over.
Here,
though,
in
the
overview
we
now
have
four
providers
more
pods,
more
nodes,
more
clusters,
so
already
got
a
lot
more
information
already
being
introspected
off
our
our
footprint,
and
this
is,
of
course,
where
things
decide
to
get
a
little
cranky
come
on.
C
Here
we
go
now,
it's
loading,
great
okay
and
then
what
I'm
going
to
do
is
quickly
try
and
see
if
our
application's
been
deployed.
So
if
I
go
to
routes
and
choose
the
call
Store
app
I
should
have
a
version
of
our
app
deployed.
Then
this
should
be
the
production
version
of
the
app,
not
the
new
version
we've
got
in
Dev,
so
there's
the
app
as
we
saw
at
the
beginning
of
the
conversation.
C
Here's
the
other
version.
With
my
shopping
cart.
You
know
it's
here,
my
shopping
carts
empty.
This
is
a
clean
environment.
I
haven't
used
it.
Yet
this
is
the
version.
We've
got
improv.
Meanwhile,
you
know
if
you
were
a
you
know,
any
decent
retailer,
you're,
probably
going.
No,
that's
still
a
bit
ugly,
we're
going
to
like
refine
the
user
interface.
We
might
go
through
a
few
more
changes
before
we're
ready
to
actually
go
and
push
that
out.
A
Yeah
and
I
love
that
some
of
the
dev
you
have
the
dev
environment.
That
has
the
updated
cart
and
then
you
go
I'm
going
to
add
this
stuff
and
don't
worry,
I
haven't
messed
with
that.
We're
still
trying
to
get
it
right
because,
as
you
just
said,
it's
not
pretty
enough
or
whatever,
but
you've
literally
just
done
it
in
front
of
all
of
us
and
that
I
think
it
just
it
just
kicks.
It
really
works.
Yeah.
C
And
I'm
I
am
honestly
running
for
openshift
clusters
right
now.
In
order
to
show
this
off,
yeah
I
can
actually
bring
up
the
workload
on
the
other
cluster,
the
n,
a
prod
one
cluster
as
well.
It's
deployed
there.
We
just
don't
really
have
the
time,
and
then
you
know
to
kind
of
close.
The
conversation
offers,
as
we've
said,
our
hybrid
story
or
open,
hybrid
Cloud
stories
just
a
lot
more
than
just
where
you
do
Cloud
native
development
and
and
do
two
things
with
containers.
C
We
know
our
love,
our
customers
are
still
deploying
on
premises,
often
in
a
traditional
way
using
red,
Enterprise,
Linux
or
maybe
they're
deploying
onto
you
know
a
hyperscaler
environment.
It's
one
of
the
cloud
providers
again
they
may
be
still
deploying
traditional
workloads,
but
hopefully
many
of
them
are
now
starting
to
approach
things
like
Cloud
native
development
microservices.
C
And
then
your
organization
wants
to
run
it
on
eks
or
gks,
or
the
the
thing
the
developers
running
on
their
desktop
actually
is
very,
very
different
from
what
they're
running
out
in
production
and
we're
hearing
the
same
thing
again
and
red
Hat's
been
there
every
time.
We've
helped
customers
through
this
journey.
Many
many
times,
and
let's
and
and
you
hear
some
of
our
success
stories
with
customers
who
are
saying
we're
going
to
normalize
on
openshift,
it's
open
and
it's
hybrid.
A
C
A
Say
and
then,
and
then
we
do,
that
I
mean
it's
it
and
and
it
flows
Beauty.
Obviously
I
interrupted
you
during
this,
and
and
you
know
you
were
fiddling
with
this,
but
that
was
the
point,
but
it
really
flows
beautifully
across
across
this
whole
thing
and
takes
you
along
the
journey
and
for
Deb
for
someone
who's
just
seen
it
I,
don't
know
if
you
saw
it
in
the
live
stream.
Let's
pretend
you
didn't.
If
you
did,
you
know
what
do
you
think
like?
B
I
was
totally
blown
away,
I
mean
Steve.
That
was
an
awesome
presentation
or
you
know
just
moving
between
slides
and
demos.
Some
really
good
things
that
you
know
you
brought
in
and
I
was
listening
intently.
It
did
not
want
to
bother
because
there's
so
much
that
was
going
on
in
my
mind
you
know
the
inner
loop
and
outer
loop.
That
was
a
great
concept,
I
loved
that
and
you
were
right
right.
You
know
developers,
you
know
they
just
want
to
write
code
and
you
know
want
to
have
a
consistent
one
and.
C
B
Yeah
I
mean,
if
you
think
of
it
from
a
developer's
perspective,
I
mean
they
look
at
this
and
they're
like
wow,
because
you
know,
then
they
get
to
focus
on
what
they
do
and
what
they
love
to
do
best
because
the
right
code,
it
certainly
makes
their
lives
easy,
and
you
know
that's
how
you
know
you
bring
in
that
consistency.
I
love
that
you
know
the
way
you
kind
of
brought
in
you
know.
You
know
you
had
a
lot
of
nuggets
in
there.
B
In
terms
of
you
know
all
these
12
Factor
at
methodology,
you
know,
like
you,
have
a
consistent
code
base.
You
know,
write
everything
deploy
everywhere.
You
have
concurrency,
you
know,
that's
what
everyone
wants
right,
I
mean
if
you
think
about
it.
You
know
the
example
that
you
gave
you
know
deploy
this
in
North
America.
If
you
want
to
scale
it
to
different
regions,
that's
what
customers
want
right.
I
mean
they
want.
You
know
save
time.
B
C
C
So
we
could
have
gone
down
that
pathway
for
this,
but
we
didn't
have
the
UI.
We
wanted.
We
couldn't
kind
of
position,
the
story
where
we
wanted.
So
you
know
if
you
want
to
dig
into
this
with
some
other
themes
again:
I
I
recommend
you
go
and
talk
to
your
red
hat,
account,
teams
and
say:
hey
look.
This
is
kind
of
neat,
but
the
problem
we're
trying
to
solve
is
this
and
and
if
we
haven't
heard
of
it
before
it'll
be
surprising
and
if
we
haven't
heard
of
it
before
well,
there's
a
good
chance.
A
That's
what
I
love
about
the
demo
is.
It
gives
ourselves
as
red
hat
folks
and
our
customers
who
see
it
a
common
starting
point.
So
we
sit
down
at
the
table
and
go
right.
We
see
these
things
and
what
it
can
do
and
we
understand
it
and
Dev
I
mean
Dev
is
a
a
red,
Hatter
and
very
smart,
but
instantly
just
got
the
story,
got
the
value
and
then
you,
you
all
sit
down
and
just
build
on
that.
A
C
C
But
it's
not
the
right
way
if
you're
not
actually
delivering
the
business
outcomes,
if
it's
not
delivering
the
developer
agility,
if
it's
not
allowing
you
to
deliver
the
services
close
to
your
customers,
yeah,
and
if
it's
got
a
high
overhead,
so
maybe
we
can
help
you
tune
it
to
suit
the
other
needs
of
your
organization.
Yeah.
A
C
We
we
based
this
on
a
much
bigger
demo
solution.
We
have.
That
has
a
lot
of
the
moving
parts.
So
if
you
really
want
to
dig
into
things
like
raml
strategy
or
some
of
our
Edge
strategy,
we
have
other
demo
components
running
on
openshift,
for
that
we
kind
of
stripped
it
down
into
something.
We
could
have
go
out
quite
repeatably
and
it
was
a
collaborative
effort
globally.
C
We
had
a
bunch
of
people
from
Red
Hat
come
in
and
and
help
deliver
this
consistently,
which
means
that
our
field
teams
can
just
go
and
request
this
and
spin
it
up.
We
are
going
to
try
and
get
most
of
these
artifacts
in
an
external
repository
if
someone
wants
to
try
it
out
on
site
with
their
own
infrastructure,
but
things
like
the
cool
store
application.
We
use
that's
readily
available.
There's
several
repositories
online,
I
I
think
one
of
the
problems
right
now
is
there's
too
many
versions
of
it
available.
C
A
C
C
Because
the
subsequent
sessions
in
the
day
kind
of
expand
on
many
of
the
themes
we've
covered
here,
yeah
so
and
again,
it's
that
realization
that
not
everybody
has
gone
as
far
as
this
virtual
customer
of
ours
has
gone
by
the
end
of
their
Journey
they're,
all
at
different
points
in
this
journey.
So
wherever
you
are,
how
can
we
help
you?
How
can
we
help
you?
You
know
achieve
your
business
outcomes,
yeah.
C
A
Well-
and
it
shows
that
where
it
can
go
and-
and
you
know
this-
this
is
one
piece
but,
like
you
said
you
get
you
get
more
in
the
other
sessions,
you
can
build
this
out.
You
can
go
a
lot
of
places
with
it.
Yeah.
That's
nice
cool!
Well,
we
are
hitting
the
end.
I
guess
any
final
words
as
to
how
people
should
find
out
more
about
this
I
mean
we've
kind
of
covered
that
but
Steve
you
know
if
you
want
to
just.
C
C
B
A
Thrilled
to
do
it
and,
as
I
said,
I
mean,
as
you
know,
this
will
be
on
the
on
the
openshift
YouTube
page
for
you
to
watch
at
your
own
speed
or
one
and
a
half.
If
you
like
us
to
talk
a
lot
faster,
we
can
do
that
too,
depending
on
your
time
always
check
out
the
latest.
The
red
hat
live
streaming.
Calendar
like
And,
subscribe
to
the
stuff
below
I've,
always
wanted
to
say
that
that's.
C
A
And
finally,
you
know
World
Cup
kicks
off
on
Monday
quite
excited,
so
I
look
forward
to
sharing
some
of
that
with
you
all.
We
have
upcoming
sessions
in
for
the
live
streaming,
Channel
and
I
look
forward
to
seeing
people
there,
but
for
now
we're
done.
Thank
you,
everybody
and
we
will
catch
you
next
time.
Bye.