►
From YouTube: OpenShift Coffee Break: Red Hat Hackfest Office Hours
Description
Get your espresso ready for the EMEA OpenShift Coffee Break as we kick-off the Red Hat Hackfest Office Hours! Join the monthly meeting with Red Hat and Red Hat Partners experts around Edge, RHEL and OpenShift as part of the Red Hat Hackfest.
A
Hey
welcome
back
to
the
openshift
tv
coffee
break
our
after
our
summer
break.
We
are
back
here,
live
on
openshift
tv
every
wednesday
morning.
10
a.m
set
time
here
in
emea.
Today,
I'm
very
happy
to
have
our
special
guest
in
the
show
for
the
red
dot
act,
fest
office
hour
there.
There
is
the
our
you
know:
permanent
djs
like
andrea
and
matthia
andrem,
I
am
matia.
Are
you.
B
D
First
of
all,
I
think
so
it's
our
fourth
session
today
and
I
wanted
to
invite
mike
because
miquela
is
one
of
the
esteemed
members
of
the
global
team
that
covers
the
validated
patterns
for
edge,
and
this
is
a
fantastic
opportunity
to
start
our
collaboration,
so
whatever
the
hackfest
team
produces
is
validated
and
then
promoted
at
the
global
level
through
michele's
team.
So
miguel,
if
you
would
like
to
say
a
few
words
about
you,
that
is
yours,.
E
A
Great
thank
you
for
the
the
introduction.
As
andre
will
say,
this
is
the
fourth
red
attack
fest
office
hour,
andre,
but
is
worth
because
maybe
people
come
back
from
the
holidays
or
maybe
people
just
join
from
twitch
or
youtube.
It's
worth
to
remind
people
what
is
the
red
at
hackfest
office
hour
and
I
want
to
say
to
all
the
people.
If
you
have
any
question
about
the
topic
we
talked
today
and
it's
all
about
openshift
edge
computing,
open
source
and
streaming,
please
send
questions
to
the
chat,
I'm
putting.
A
D
Thanks
natalie,
so
the
hackfest
office
tower
is
a
kind
offering
from
the
from
our
friends
of
the
openshift
coffee
break,
hosted
by
openshifttv
to
spread
news
around
what
the
hackfest
technical
team,
so
that
happens,
technical
team
and
the
community
are
working
on.
So
the
red
of
hackfest
is
an
event.
You
know
that
as
an
event
behind
the
red
attack
quest
event.
D
B
A
B
D
D
Will
this
would
talk
to
us
about
the
lighting
talks
and
will
give
us
an
overview
of
how
what
they
are
and
how
to
use
them,
and
then
we'll
have
miguel
giving
us
an
overview
technical
overview
of
what
the
validated
patterns
are
and
what's
the
value
of
collaborating
with
them
or
using
them
adopting
them
for
a
customer
project?
For
example,
the
call
to
action
for
today
is
quite
interesting
in
collaboration
with
microsoft,
potentially
and
intel
and
other
technology
vendors.
We
are
trying.
D
We
are
thinking
of
an
fsi
edge,
related
business
case,
so
we
are
we're
starting
the
implementation
of
a
potential
fsi
prototype
that
could
solve
financial
services
prototype
that
could
be
used
in
several
and
several
business
cases.
So
that's
gonna
include,
as
usual,
all
the
edge
related
portfolio
from
red
hat,
but
also
cloud
but
also
hardware
with
medium
and
small
footprint.
So
we
will,
as
usual,.
D
Will
adopt
reference,
but
also
we
are
discussing
the
adoption
of
microshift.
We
will
work
on
on
signal
openshift
and
several
technologies
that
stay
on
top
of
our
extended
platform,
an
additional
discussion
we
are
having
today
in
the
community
and
by
the
way,
thanks
to
the
links
natalie
shared
with
you,
you
can
go
the
qat
project
website.
B
D
Is
actually
the
community
version
of
our
red
and
harvest
event?
You
can
connect
to
our
and
join
for
free,
our
slack
channel
and
also
join
our
weekly
meetings,
community
meetings
that
happen
every
thursday
4
p.m,
central
european
summer
time
so
another
another
potential.
Adoption
is
related
to
the
edge
management
software
as
a
service
from
redhat,
which
is
something
a
lot
of
customers
and
partners
they
are
asking
for
and
with
the
edge
management
that
we'll
probably
discuss
in
the
next
session.
D
We
have
a
great
software
as
a
service
tool
to
manage
patches
and
updates
on
our
remote
web
forage
instances.
So
that's
something
that
is
really
interesting,
that
is
a
no-brainer
for
each
and
every
technical,
devops
depths
option
manager.
Who
is
keen
to
understand
the
technology
and
not
that.
So
I
kindly
encourage
all
of
you
to
join
our
community
meetings.
D
B
C
Perfect
so,
as
andrea
mentioned,
we
are
going
to
have
or
talk
about
more
a
soft
topic
today
and
not
really
a
deep
technical
topic.
So
we
are
going
to
talk
about
why
lightning
talks
can
be
a
really
good
enablement
format
and
how
we
have
used
them
in
a
very
concrete
scenario.
With
a
with
an
organization
we've
been
working
with
so
approximately
two
years
ago,
next
slide
material.
C
Approximately
two
years
ago,
when
working
with
a
really
large
organization,
we
faced
a
pretty
typical
situation.
Openshift,
as
a
container
platform
has
been
established,
so
has
been
in
place.
The
first
set
of
applications
has
been
onboarded
onto
the
platform
running
in
production,
and
then
the
organization
decided
they
want
to
leverage
and
utilize
the
benefits
of
containers
and
kubernetes
for
far
broader
set
of
their
applications.
C
So
we
are
talking
about
an
organization
with
with
hundreds
of
applications
with
thousands
of
software
developers
and
with
a
certain
complexity
associated.
So
it's
a
global
organization
globally
distributed
people
are
sitting
in
different
geos,
different
time
zones,
talking
different
languages
and
as
well
a
very
heterogeneous
set
of
technologies
used
within
the
company.
So
it's
from
really
legacy
to
top-notch
modern
cloud
native
applications.
C
Even
if
people
are
coming
from
a
completely
different
background
and
we
have
been
discussing
different
formats
and
things,
we
could
do
next
to
the
usual
trainings
and
we
chose
to
do
a
series
of
lightning
talks
and
we
want
to
basically
wanted
to
achieve.
A
certain
set
of
objectives
was
with
these
lightning
talks.
So
in
the
end,
it
should
be
a
series
of
enablement
for
for
the
people,
so
technical
enablement
on
technical
topics
and
educate
them
and
also
generate
awareness
about
the
new
topics.
C
C
So
it's
not
just
an
enablement
thing,
but
also
trying
to
introduce
a
feedback
loop
between
consumers
and
producers
of
of
such
new
technologies
and
platforms,
and
in
the
end
we
wanted
as
well
it's
with
large
organizations
pretty
much
always
the
same.
So
it's
sometimes
it's
hard
to
get
started
with
new
stuff.
There
is
a
lot
of
boundaries
and
we
wanted
to
prove
it
can
really
be
easy
to
get
started
and
can
also
be
quick
to
get
started
with
new
stuff.
C
C
So
we
formed
a
small
kind
of
steering
committee
consisting
of
people
from
red
hat,
as
well
as
from
from
the
organization
we
were
working
with,
and
these
were
basically
the
agreement
which
was
overseeing
the
topics
which
we're
presenting
and
as
well
the
content.
So
we
had
basically
if
ways
how
people
could
formulate
requests
or
proposed
topics.
We
should
take
up
in
the
lightning
talks,
and
then
we
were
discussing
them,
selecting
based
on
number
of
requests.
C
We
were
selecting
topics
and
then
preparing
the
respective
session
always
from
from
red
hat
side,
so
we
were
always
providing
parts
of
the
session,
but
always
contextualized
into
this
business.
Specifics
of
that
organization,
because
out
of
the
box,
sometimes
it
just
doesn't
work
in
each
and
every
organization
right.
Therefore,
we
always
make
sure
we
have
it
working
and
in
the
associated
context
of
the
of
the
organization,
and
then
basically,
it
was
up
to
the
organization
to
internally
communicate
about
these.
C
These
sessions
and
lightning
talks
so
to
promote
them
and
make
sure
we
have
the
right
audience
on
on
the
sessions,
and
then
we
also
make
these
things
available
in
internal
learning,
centers,
so
as
replays
and
and
everything
so
that
people
also
who
are
joining
the
party
later,
they
can
still
make
use
of
all
the
materials
we
produced
throughout
these
lightning
talk
sessions,
the
concrete
permit
of
such
a
session.
How
we
shaped
it
I
think
mattia.
Can
you
take
us
through
that.
B
Yes,
thanks
chris,
so
the
format
I
think
it
was
the
key
of
this
lightning
talk
we
devised
in
three
parts.
The
first
part
was
about
the
introduction
of
the
session
and
overview
or
what
we're
going
to
shown
and
how?
Technically
you
could
achieve
it
right
with,
for
instance,
talking
about
design
pattern,
how
you
architecture,
how
you
can
solve
that
problem,
and
the
second
part
is
really
showing
the
demo
about
how
you
can
implement
such
pattern
or
architecture
or
integration,
with
a
specific
ecosystem
of
the
customer
in
the
current
platform.
B
Last
but
not
least,
of
course,
q
and
a
where
you
ask
questions
where
they
ask
questions
about
this
solution
that
we
propose
or
architecture
that
we
propose
and
then
the
last
piece
of
this
10
minutes
queen
is
about
server,
because
we
want
to
gather
feedback
about.
How
was
the
talk,
how
we
can
improve
footer
around
this
light.
Clean
talk,
series.
B
So,
just
to
give
you
an
example
of
which
talk
to
be
present
on
the
customer
and
as
you
see
as
a
first
topic,
is
about
really
basic
functionality,
because
you're,
starting
with
this
platform,
so
you're
going
to
start
from
the
basic.
Because
if
you
understand
the
basic,
then
it
will
be
easier
on
the
footer
talks
to
understand
that
technology,
how
you
can
work
with
the
technology
itself,
and
so
so
basic
introduction
with
container
kubernetes
12
factor
then
go
deep
dive
with
java
containers
reason.
B
We
like
to
create
a
real
package
for
kubernetes,
and
then
we
go
even
further.
With
this
complex
topic
like
how
we
can
start
moving
from
a
legacy
application
based
on
monolithic
approach
to
microservices
how
you
what's
the
approach,
what
tool
you
can
use
to
migrate
right
and
and
then
you
are
in
the
platform
itself
and
then
how
you
make
sure
your
amplification
is
held
in
production,
how
you
can
protect
from
disaster
recovery
and
then
even
further
talking
about
difficult
topic
like
distributed
transaction,
because
now
you
are
not
anymore
on
a
monolithic.
B
And
of
course
you
have
several
thousand
services,
and
then
you
want
to
have
zero
trust
between
these
services.
So
you
introduce
a
certificate
management
on
top
of
the
flatmoon,
so
how
you
can
achieve
that
right?
So
you
you
prepared
this
lightning
talk
to
enable
the
developer
about
several
topics
from
basic
to
advanced,
and
then
you
prepare
example
where
they
can
start
working
on
and
make
it
reproductive,
and
just
talking
about
numbers
and
people
attended.
This
session
were
around
150
in
average
and
as
well
offline.
B
They
were
even
more,
and
so
it's
very
nice
to
see
how
this
grow
on
the
viewing
and
see
how
help
people
to
use
the
platform
and
work
in
a
better
way
yeah.
So
the
storyline,
you
start
from
the
scratch,
and
then
you
increasingly
use
leverage
the
platform
and
the
talks
and
help
them
to
integrate
this
platform
to
the
existing
ecosystem
of
the
customer,
because
the
ecosystem
of
the
customer
can
be
wide
broad.
B
B
It's
based
on
the
feedback,
so
you
the
flow
all
we
have
to
do
from
basic
to
advanced
it's
better,
to
have
a
specific
session
for
a
specific
topic
and
as
well
is
the
obvious
must
be
important
because
you
need
to
identify
which
audience
will
be
attending
meeting,
because
if
you
go
to
deep
dive,
but
then
the
session
is
attended
by
management
or
people
that
are
not
really
working
day
by
day
on
the
code.
So
maybe
it
doesn't
make
any
sense.
B
And
of
course
you,
if
you
do
such
a
three
that
you
need
to
promote,
because
if
you
do
this,
you
don't
promote
it,
the
audience
will
be
low
and
then
this
it
will
not
work
and
more.
I
think
this.
The
most
important
things
is
about
showcase
functionalities
that
are
currently
available
on
the
on
the
platform
itself,
because
if
because,
if
you
prepare
the
demo,
you
prepare
the
lighting
talk
and
then
the
developer
or
the
application
owner
cannot
use.
It
is
kind
of
useless
because,
yes,
it's
it's
cool,
really
fancy,
I
love
it.
B
But
then
what
can?
I
do
right
and
of
course,
the
one
important
topic
you
want
to
provide
on
when
you
work
in
a
microservices
or
on
a
container
platform.
You
want
to
provide
a
simple
way:
how
to
transform
your
application
and
keep
it
always
up
to
date.
So
you
want
to
show
migration
process
how
you
can
implement
as
well
new
green
application,
application
with
third
party
provider
and
so
on
and
so
forth,
and,
of
course,
as
well.
A
No,
we
don't
have
a
yet
question
from
the
chat
if
you
have
any
questions
from
what
chris
and
andre
and
matthias
said,
please
send
in
the
chat.
No,
it
looks
to
me
very
interesting.
I'm
interested
in
the
modernization
part
you
you
mentioned
the
java
modernization
for,
for
that
part,
are
you
using
any
framework
any
any
any
tool
or
is
just
following
the
patterns.
B
Well,
we
are
leveraging
the
tool
from
coveria
taco,
okay,
but
this
to
create
an
assessment
of
the
application
on
wherever
they
are
right,
so
to
define,
if
it's
the
status,
if
it's
ready
to
be
containerized
or
known,
if
you
follow,
for
instance,
the
right
pattern
already
or
is
completely
unknown
status
and
based
on
this,
we
can
in
the
define
how
difficult
or
how
it
takes
to
transform
this
application.
On
on
the
to
move
on
the
platform
itself,.
C
A
A
Thank
you,
and
I
like
also
the
light
in
talks
format.
Chris
we've
been
together
in
some
of
those
some
of
those
I
think
they
are
very
effective,
successful
and
I'm
happy
to
see
the
same
approach
also
here.
This
is
my
opinion,
of
course,
but
I
think
the
it's
a
very
good
format
to
for,
for
you
know
managing
some
of
these
topics.
Yeah.
Those
are
the
questions
that
that
I
had.
E
E
E
At
this
point
in
time,
we're
mainly
doing
ci
over
release
stuff.
So
when
there's
a
new
open
shift,
we
test
it
with
that
version,
a
new
operator
version,
that's
officially
released.
We
test
it
with
those
version,
and
the
bonus
is
that
we
do
the
testing
as
a
whole.
So
all
the
operators,
all
the
ocp
versions,
are
tested
as
a
whole
unit
with
the
whole
pattern.
Our
next
step
there
is
we're
striving
to
do
ci
on
unreleased
stuff
as
well,
so
next
version
of
an
upcoming
operator.
E
E
E
Yeah,
the
the
other
benefits
are
it's
it's
possible
to
show
customers
and
folks
to
what
is
what
is
possible.
It's.
The
way
we
can
see
validate
patterns
is
that
there
are
a
bunch
of
lego
bricks
and,
and
you
can
build
things
we
just
give
you
a
way
to
to
make
things
simpler,
to
start
off,
to
be
faster
to
to
to
play
with
stuff
and
and
try
things
out
the
feedback
that
we
get
back
from
people
from
customers.
E
Then
flows
back
to
the
pattern,
and
then
we
improve
on
it
and
change
it
over
time
to
make
it
better.
I
said
we
tested
in
ci,
so
we
get
on
a
daily
basis.
We
see
what
breaks
and
what
doesn't
and
we
provide
any
feedback
that
we
get
back
to
the
to
the
units
that
that
are
in
to
the
teams
that
are
in
charge
of
the
different
components.
E
E
E
D
D
A
question
please,
as
we
are
talking
about
life
cycle-
and
you
mentioned
architecture
here,
I
would
love
to
a
lot
to
underline
to
our
audience
that
reference
architectures.
They
of
course,
are
based
on
our
platform,
but
they
use
different
products
from
our
portfolio
and
third
parties
like
we
are
doing
together
with
the
hackfest
pocs.
But
what
about
maintaining
these?
These
validated
patterns
now
an
example
that
jumped
into
my
mind
and
that's
the
reason
actually
why
I'm
asking
this
question.
D
We
worked
one
year
ago
in
a
manufacturing
use
case
that
has
been
formalized
in
a
white
paper
that
has
been
is
under
under
validation,
thanks
to
you
and
your
team,
but
we
started
working
on
that
with
openshift
and
matia.
Correct
me
in
front
wrong.
That
was
open
sheet,
4.8
or
4.9,
which
means
we
had
to
use
specific
operator
versions.
We
had
to
use
specific
functionalities
from
the
opposite
platform.
What
if
I
would
like
to
have
an
updated
version
of
that,
once
it's
been
adopted
by.
D
E
E
E
E
Those
might
progress
to
the
status
of
validated
patterns
once
they
fit
certain
requirements.
So
far
we
have
industrial
edge,
which
is
a
distributed
architecture.
Maybe
it's
the
one
you
were
mentioning
before
there
that
does
monitoring
of
production
line
it's
distributed
across
clusters
has
a
certain
eye
model
to
detect
anomalies
and
report
back.
It
has
some
visualizations
and
it's
all
running
in
githubs.
E
E
Do
the
analysis,
the
scanning
and
report
back
and
then
we
have
multi-cloud
git
ops,
which
is
a
pattern
that
showcases
a
few
things
I'll
talk
about
I'll
talk
a
bit
more
about
this
today
and
I'll
show
how
to
deploy
it.
It's
basically
how
to
do
a
get
ups,
how
to
run
get
ups
across
multiple
clusters
or
multiple
clouds.
E
E
In
the
hub
cluster,
we
have
hashicorp
vault
that
acts
as
a
storage
for
secrets.
We
configure
it
on
the
hub
in
the
pattern
and
we
load
the
secrets
into
the
vault
out
of
band
I'll.
Show
you
a
bit
how
it's
done.
We
do
it
with
ansible.
It
can
be
done
in
a
number
of
ways,
but
we
do
it
out
of
band
because
we
want
to
make
sure
this
no
secrets
end
up
in
git,
which,
which
is
a
large
problem.
E
E
E
E
E
E
That
are
common
across
all
of
our
patterns,
then
all
the
the
charts
folder
you
have
all
the
the
helm
charts
that
you're
gonna
use
in
your
in
your
different
clusters
and
I'll
show
you
later
in
the
values
files.
You
have
a
values
global
which
gets
applied
to
all
of
all
clusters,
be
it
the
hub
or
regional
clusters,
and
then
you
have
the
other
values
file,
one
for
the
hub
one
for
the
regional
clusters,
and
you
can
split
up
the
imported
clusters
in
multiple
regions.
E
E
E
That
will
show
you
the
secret
that
you
loaded
in
the
vault,
and
it
runs
both
on
the
hub
and
on
the
regional
cluster,
with
the
same
sim
code
and
the
regional
cluster,
you
import
it
into
acm,
and
it
basically
just
has
a
the
git
ups
instances
that
make
sure
that
the
applications
for
that
cluster
are
installed
all
right
now,
we'll
quickly
go
through
a
demo,
let's
see
if
the
demo
gods
are
on
my
side,
so
I
cloned,
can
you
see?
Is
it
big
enough?
Should
I
make
it
bigger.
E
E
E
E
E
E
The
run
with
a
specific
interval
of
10
minutes
by
default,
which
can
be
changed
and
they're
just
ansibles
that
get
run
in
a
in
a
container
inside
the
cluster,
and
you
can
do
whatever
you
you
want
with
it.
So
once
you've
copied
the
secrets,
template
edited
it.
It's
really
just
make
install
away,
and
a
couple
of
checks
will
be
run,
making
sure
that
your
repo
exists
with
the
branch
that
you're
on
and
then
it
just
starts
installing
the
entry
point
and
take
care
of
everything
else.
E
E
And
if
you
go
on
the
hub,
it's
config
demo-
and
this
is
the
secret
that
I
I
configured
before-
and
it's
test
one
two
three:
if
you
change
the
secret,
it
will
obviously
be
reflected.
This
is
probably
it
will
be
reflected
on
the
hub
and
on
the
regional
cluster
later
on.
It's
every.
I
think
the
sync
is
every
few
minutes
and
yeah
and
all
the
applications
are
managed
via
via
our
go.
E
E
A
D
A
A
Demo,
because
there
are,
there
are
lots
of
components
involved,
for
this
is
the
music
cloud.
You
know
key
tops
validate
and
pattern.
There
are
many
pieces,
I
think
it's
very.
It
was
a
powerful
demo.
Thank
you
give
an
idea
of
how
you
can
manage
those.
You
know
complex
use
case,
but
at
ease
with
a
pattern,
so
there's
a
there's
a
way
to
make
it
reproducible
and
make
it
stable,
and
I
think
this
is
the
overall
idea
around
validated
pattern.
D
No,
I
know
actually
miguel,
they
are
implementing
this
patterns
overall
in
the
regional
india
region,
which
is
the
one
we
we
belong
to.
Also
chris
matthew
and
myself.
I
wanted
to
ask
you
actually
mathia
if
there
is
already
a
current
adoption
of
project
of
these
buttons
for
any
of
your
customers,
without
mentioning
the
customers,
of
course,
but
you're
already
working
on.
B
Yeah,
let's
say
this:
pattern
is
coming
on
the
customer
side
with
acm
to
manage
a
multi-book
cluster,
because
customers
want
to
have
the
functionality
of
this
platform
worldwide.
So
it's
a
distributor
customer,
so
they
need
a
way
to
manage
all
the
other
clustering
in
an
easy
way
as
well.
It's
in
secure
ways
with
as
well,
they
use
external
operator
they
have
volt,
but
also
they
have
elder
secret
provider.
That's
why
external
external
stick
operator
is
nice
feature
about
that,
but
yes
is
coming
on
the
on
the
customer
side.
B
A
Oh
yeah,
folks,
it
was
a
really
great
session,
thank
you,
chris
and
and
michelle
for
joining
us
today.
It
was
a
pleasure
to
hear
from
you
and
thank
you,
andrea
and
mattia,
to
coming
back
for
the
act.
Fest
office
hour
always
great
to
hear
from
you
and
the
news
from
the
hackfest
appointment.
Openshift
tv
coffee
break
come
back
next
wednesday
10
a.m,
with
young
lawson,
talking
about
serverless
and
kafka
out,
to
combine
those
two
pattern
together:
data
streaming
and
serverless
and
other
than
that
folks.