►
Description
OpenShift 4.8 brings many feature to improve Developer Experience and to enable developers on Kubernetes at ease. Let's explore those with Markus Eisele, EMEA Developer Adoption Lead at Red Hat.
A
Good
morning,
everyone
thank
you
for
joining
us
today
for
another
episode
of
openshift
coffee
break.
So
today
we
will
be
joined
by
our
usual
suspects
attalevinto
and
hero
baonen
and,
of
course,
we
have
our
esteemed
guest,
marcus
eisel.
Who
is
our
developer?
Adoption
lead
joining
us
today,
so
thank
you.
Everyone
and
welcome
to
to
the
show.
B
A
B
C
Yeah
absolutely
good
morning,
everybody
so
marcus
is
based
out
of
north
east
of
munich.
So
that's
obviously
germany.
I
do
work
for
redhead
now
again
one
and
a
half
years.
I
think,
roughly
at
least
been
here
before
always
been
in
the
area
of
like
enterprise
java
developer
relations,
and
today
my
job
basically
is
to
help
our
customers
be
productive
on
openshift,
with
our
middleware,
creating
solutions
that
basically
make
developers
faster
and
help
them
deliver
value
faster.
That
sounds
awkward
but
basically
means
we
want
to
make
developers
better
and
faster
on
our
stuff
right.
C
B
D
C
A
D
D
The
full
engineering
power
is
more
on
running
the
applications
and
maintaining
and
the
like
getting
started
and
implementing
new
is
actually
it's
not
that
important
it's
to
how
to
run
efficiently,
how
to
monitor
how
to
do
support
developers
on
the
on
the
doing
updates
and
everything.
So
it
is.
It
has
been
like
I've
been
working
for
one
now
for
one
month
and
I
have
learned
a
lot
and
a
lot
of
new
stuff.
So
it's
a
different
error.
D
B
That's
cool,
that's
cool,
and
this
is
a
good
introduction
of
our
topic
today
to
tarot
mentioned
devops,
the
key
ops
developers
so
marcus.
We
have
some
nice
announcement
for
openshift4.8
what
openshift
bring
to
developer.
I'm
gonna
share
my
screen
because
I
want
to
first
I
wanna
share
the
the
announcement
blog
and
I
can
do
in
our
chat
and
it's
gonna
go
into
youtube
and
twitch
hello
to
everyone
and
following
us
on
twitch
on
youtube
bill.
Please
feel
free
to
use
the
chat
to
write
any
question.
B
B
Yeah
I
want
to,
I
shared
the
link
in
the
chat,
because
I
I
want
to
discuss
around
the
announcement
of
the
open
sheet
4.8.
This
is
the
announcement
new,
the
press
release
for
openshift4.8,
so
we
have
couple
of
news
and
today
we're
going
to
focus
on
the
developer
experience.
Moreover,
so,
for
instance,
we
have
a
nice
feature
for
developer
and
marcus.
We
can
discuss
about
it.
As
you
are
a
java
champion.
Also,
we
have
the
capability
for
java
developer
to
just
drag
and
drop
their
artifact.
B
Their
jar
file
into
the
openshift
web
console
developer
perspective.
So
you
there's
no
need
of
writing
yaml
file,
there's
no
need
or
no
link
kubernetes
under
the
hood,
just
produce
the
jar
upload
to
the
platform
or
there's
some
database
if
needed
and
boom.
It's
your
app
is
up
and
running
in
a
cloud
kubernetes
experience.
C
C
We've
seen
tools
like
swam
we've
seen
like
all
kinds
of
various
approaches
and
what
what
kind
of
was
missing
all
the
time
is
something
that
is
actively
starting
to
reduce
complexity
for
developers.
Because,
honestly,
like
I
in
one
of
my
talks,
I
had
a
slide
with
like
a
picture
of
me
and
a
big
quote,
so
I'm
not
really
interested
in
writing
any
yaml
like
at
all.
C
C
So
long
story
short,
I
think
this
year,
and
maybe
the
next
couple
of
years
will
have
a
common
theme,
and
this
will
be
to
make
all
of
these
distributed
stateless
infrastructures
easier
to
handle
for
developers,
so
you'll
see
a
lot
more
developer,
productivity
features
and
honestly,
like
this
jar
drop.
This
is
amazing.
One
of
my
personal
wishes
that
I've
probably
expressed
a
couple
of
times.
C
So
I
personally
consider
this
a
very
important
first
step
and
we're
we're
on
to
something
like
this
is
definitely
going
to
give
me
some
development
time
back,
because
I
don't
have
to
deal
with
like
everything
around
that
is
not
actively
putting
something
into
code
and
and
like
making
me
feel
good.
Yaml
doesn't
so
just
for
the
record.
B
A
A
C
Intelligent
defaults,
literally
just
coding
is
the
the
main
concept.
But
you
can
also
start
like
to
take
apart
and
look
under
the
hood
and
make
sure
you
can
tweak
every
single
thing
if
necessary,
but
thanks
to
intelligent
defaults,
this
shouldn't
be
at
all
right.
So
I
love
that
approach.
I
think
we're
we're
not
really
reinventing
the
wheel,
we're
applying
something
that
has
been
proven
to
be
super
valuable
to
something
that
is
pretty
new
and
here's
something
that
I
commonly
do
so.
C
I
don't
refer
to
openshift
as
a
container
platform
at
all
anymore,
because
to
me
it's
like
the
kubernetes
development
platform.
It's
actually
built
to
support,
not
only
ops
and
not
only
deaf
teams.
It
has
all
the
functionality
that
is
needed
to
to
even
involve
like
the
business
teams
in
a
different
way
of
working
and
terror
talked
about
devops
right.
So
this
this
is
even
a
different
way
of
scaling
projects
so
to
to
be
really
performant
on
on
a
real
good
platform.
C
You
also
need
to
tweak
your
methodologies
and
all
this
needs
to
be
one
package
and
needs
to
be
supported
by
a
product.
So
technology
itself
won't
solve
your
problems.
We
all
know
that,
but
we
can
invest
a
lot
to
make
your
life
easier
and
actually
support
these
new
approaches
so
thumbs
up
for
this,
and
I
can't
wait
for
natalia
to
show
us
this
magic
drag
and
drop
thingy,
because
you
won't
believe
how
easy
it
is.
B
Yeah
yeah
and
we
have
a
little
demo,
but
I
before
that
I
would
like
to
listen
also
to
the
devops
opinion.
Do
you
have
any?
What
do
you
think
about
developer
that
can
just
drag
and
drop
a
jar
in
in
kubernetes
and
have
your
their
application
up
and
running,
or
do
you
prefer?
Do
you
like
this
approach,
or
do
you
prefer
another
more?
You
know
formal
approach,
yaml
approach.
What
do
you
think
about
it.
D
Yeah
it's
I,
I
would
have
to
say
that
I
have
mixed
feelings.
The
I
remembered
I'm
so
old
that
I
remember
when
there
was
weblogic
chambers
and
they
had
a
web
ui
and
you
dropped
your
hr
file
in
there
and
it
deployed
now.
You
do
something
that
you
copy
your
file
into
deployments
directory
and
the
it
deploys.
So
now
the
level
is
going
just
higher
that
the
there
is
a
lot
of
yam
generation
and,
at
the
end
of
the
day
same
thing
happens.
D
The
artifact
goes
to
correct
directory.
I
would
say
that,
from
my
opinion,
the
most
important
tool
for
developers
is
kit
for
devops
for
everything.
So
it
is
awesome
that
there
are
different
tools,
because
there
are
different
type
of
developers
that
they
want
someone
to
write
for
jump
files,
not
many,
but
some
won't.
And
if
you
have
a
lot
of
different
ways
to
get
started
like
dropping
a
jar
file,
doing
source
to
image
or
just
giving
running
a
container,
it's
easier
to
step
into
the
goop
and
this
native
world.
D
And
then
you
can
just
write,
move
to
production
operator
that
basically
deploys
everything
to
production.
But
there
needs
to
be
like
tooling
in
place.
Let's
say
that
the
new
github
actions
that
thread
have
implemented
like
building
a
container
with
pilda
and
doing
a
deployment
and
open
system
so
that,
if
developer
want,
they
can
do
everything
with
kit
just
commenting,
and
then
there
is
this
devops
team
that
actually
do
the
magic
behind.
D
C
So
the
platform
as
a
service
idea
that
that
kind
of
sparked
the
first
ideas
around
different
work,
habits
and
ideas
so
and
and
honestly
speaking,
just
look
at
the
technology
stack
that
we
have
today.
So
we
have
like
the
operating
system,
some
kind
of
virtualization,
underneath
we
have
some
container
technologies.
That
is
basically
also
just
some
ch
root
environments
plus
magic.
We
have
our
vms,
whatever,
like
jvm
in
the
java
space
or
even
brawl
vm.
C
If
you
want
to
run
something
else
or
whatever
you
have
your
libraries
and
frameworks
on
top,
you
have
your
applications
on
top.
You
have
something
that
wires
all
the
individual
bits
and
pieces
together.
You
have
your
data
stores
so
like.
If,
if
you
are
a
student
today,
I
don't
envy
you,
because
you
really
have
to
learn
a
lot
and
like
folks
like
tara
and
me,
we
basically
grew
up
with
all
of
this
right.
So,
like
we've
been
swimming
in
the
ocean,
since
it
was
a
little
late,
but
it's
it's
really
getting
complicated.
C
So
having
different
approaches
to
reach
a
goal
and
be
productive
is
super
crucial
and
I
think
what
is
also
important
is
to
have
these
different
on-ramps
into
the
technology,
because
you
can't
just
get
people
started
with
the
cncf
landscape
right.
That
is
just
way
too
much
so
having
an
intelligent
definition
of
the
base,
technologies
and
intelligent
understanding
and
some
like
practical
ways
and
honestly
they're
different
requirements
when
it
comes
to
development
right.
So
there's
like
this
little
inner
development
loop
that
you
do
on
your
laptop,
literally
offline
in
a
plane
way.
C
That
was
a
couple
of
years
ago,
but
anyway,
like
when
you're
in
a
disconnected
environment.
You
still
want
to
be
productive
and
you
still
want
to
do
things
and
you
can't
just
have
your
like
company
cluster
available
to
deploy
stuff
all
the
time.
Maybe
you
can
so
yeah
different
ways
of
doing
things,
and
I
think
it's
super
crucial
to
support
this.
I'm
a
beginner
I
want
to
learn.
I
want
to
like
simple
defaults
and
I'm
an
expert.
I
can
do
literally
everything
myself
and
I
150
control
of
what's
going
on.
B
A
A
A
If
you
are
doing
feature
branch
development
or
something
like
that,
then
it's
going
to
automatically
trigger
the
pipeline
that
you
have
put
in
your
repository
code.
So
you
don't
have
to
figure
out
separately
how
to
first
build
your
application
and
then
how
to
create
a
pipeline
that
will
deploy
it
on
on
the
different
environments
or
or
such
things.
So
yeah,
that's
something
that
we
will
be
covering
in
another
episode
at
some
point.
It's
still
in
the
early
phases.
Now
it's
still
in
developer
preview,
but
yeah.
B
A
B
Having
the
same
git
lab
or
github
experience,
where
you
can
use
the
code
to
start
the
pipeline
start
the
test
very
powerful,
like
travis,
but
in
openshift,
very
cool,
yeah
and
lots
of
cool
feature.
Now
I
wanna,
I
wanna
show
you
a
little
bit
of
opportunity
for
that.
A
developer
experience
because
we
were
talking
about
it.
So
let
me
start
restart
sharing
my
screen,
so
this
is,
I
hope
you
can
see
it.
This
is
an
open
sheet.
4.8
cluster
brand
new.
B
If
you
see
if
you
are
familiar
with
openshift,
this
is
the
developer
perspective
in
a
topology
view,
what
change
between
the
4.7
and
for
the
8
is
that
when
you
try
to
add
some
workload
here?
Well,
you
have
some
option
like
you
can
pick
from
the
developer
catalog
as
usual,
you
can
go
from
git
repository
from
source
to
image
docker
file.
Even
then
file
version
two.
We
will
talk
about
it
and
also
container
image
samples
you
can
import
from
local
machine.
B
This
is
what
we
were
talking
about,
also
with
marcus
before
right
from
the
inner
loop.
From
my
my
my
local
machine,
I
can't
start
coding.
I
can
start
you
know
I
can
write
my
container,
but
also
I
can
also
upload
my
jar
file,
and
this
is
what
we
want
to
show
today
and
for
that
we
would
like
to
deploy
a
springboard
pet
clinic
application.
We
were
going
to
start
from
this
repository
here
yeah
and
I
put
it
in
the
chat.
So
what
we
need
is
a
clone.
B
This
repository
build
locally
and
then
we
can
have
also
the
two
tire
version.
Let's
say
we
start
coding
locally
on
visual
studio
code.
We
say
we're
gonna
produce
the
artifact,
the
jar
file
locally,
so
the
application
is
gonna,
be
started
in
my
laptop
and
when,
if
everything
is
fine,
I
can
just
upload
my
jar
and
let
the
jar
go
inside
the
open
sheet
locally.
It's
going
to
use
h2
right
there
in
memory
database,
but
this
application
is
also
supporting
with
the
jdbc
driver.
B
All
the
databases
like
mysql,
and
what
I
wanted
to
show
is
that
I
can
code
locally
use
h
to
verify
that
my
application,
it's
cool
and
when
it's
up
and
running,
I
can
just
verify
that
my
you,
you
see
there
is
h2
dialect
to
run.
My
application
is
up
and
running
listening
to
port
8080,
so
I
can
just
quickly
you
know
test
if
my
application
is
really
up
and
running.
B
B
Yeah
yeah
this
is
springboat,
is
using
a
tomcat.
You
know
an
embedded
server
and
yeah
and
quarkus
is
an
under
toy,
far
recall
correctly
marcus,
which
has
optimized
it
also
footprint
for
starting
the
application,
but
we
we
will
talk
about
that
in
a
few
seconds.
What
I
wanted
to
show
is
that,
okay,
my
application
is
up
and
running
now.
What
I
want
to
do
is
move
into
cloud
kubernetes
cloud
kubernetes.
Let's
say
this
is
a
close
to
the
production.
B
B
And
here,
if
you
see
we
can
just
follow
the
extraction
from
this
repository,
the
the
database
is
going
to
be
mysql
and
the
other
is
going
to
be
all
pet
cleaning.
So
let
me
create
my
database
in
this
brand
new
open
sheet
for
the
a
dashboard
all
right,
so
I'm
gonna
create
that
in
the
while
I
can
or
upload
my
jar
file
and
point
the
jar
file
to
the
database.
So
I'm
gonna
hit
this
upload
jr
file.
B
So
what
I
can
do
here
is
select
the
runtime
icon.
It's
java,
the
builder
image
I
can
go
into
ubi
a
for
instance,
open
jdk
11.,
the
name
of
the
app
is
going
to
call
springboots
spring
pet
clinics.
Clinic
resources
is
a
deployment
also.
I
can
decide
right
now
to
upload
some
environment
variable
to
just
connect
to
to
the
database,
or
I
can
do
later
on.
B
Let's
do
later
on,
so
we
can
just
demonstrate
that
the
jar
upload
is
working
with
the
with
the
with
the
drag
and
drop
so
jar
uploading
is
going
on.
I
uploaded
my
locally
produced
the
pet
clinic
springboard
application,
not
that
super
fast
into
the
web
console
now.
What
is
happening
under
the
hood
is
that
a
build
is
in
progress,
I'm
starting
from
my
artifact.
This
is
a
what
we
call
the
binary
build
source
to
image.
B
I
started
from
the
artifact
and
I'm
using
a
base
container
image,
which
is
which
is
open,
jdk
11,
to
create
a
container
from
the
artifact.
As
a
developer,
I
haven't
had
to
re
re
to
write
any
any
yammer
code,
no
any
kubernetes
knowledge.
You
know
what
I
can
also
play
with
the
topology
view,
and
you
know
just
logically
add
my
java
application
to
the
database
and
way
that
this
finish
and
one
is
finished.
I
can
really
point
the
database,
the
application
to
the
database.
B
How
can
I
do
that
if
we
follow
all
with
the
same
repo
I
was
sharing
with
you
know
we
can
just
enact
some
environment
variable
and
say:
hey
activate
the
mysql
profile
go
to
this
mysql
jdbc
url,
which
is
name
of
the
service,
local
port
name
of
the
database
that
we
just
created,
and
once
you
know
now,
our
application
is
up
and
running
at
the
moment
is
not
using
yet
the
the
the
mysql.
Let's
do
it.
B
A
If
we
install
like
the
binding
operator,
I
haven't,
I
haven't
checked
yet
if
it's
completely
implemented
but
yeah,
when
you
put
the
arrow
from
the
java
application
to
the
mysql,
if
you
had
some
annotations
appropriate
annotations,
then
it
would
say
whenever
I
pull
the
arrow
from
the
java
to
the
mysql,
then
you
inject
these
environment
variables
in
the
java
application
and
it
will
be
connected
to
the
mysql
server.
So
that's
also
one
of
the
like
cool
ui
improvements
that
are
happening
within
the
openshift
console.
D
B
Auto
connect,
I
don't
know,
I
don't
need
to
you,
know
inject.
The
environment
variable
take
care
as
a
developer.
I
can
just
drag
and
drop
my
line
and
it's
going
to
down
automatically
to
enable
it,
and
we
see
here,
you
know
my
sequel
has
been
loaded
and
my
pet
clinic
application
is
up
and
running
here
in
the
live
in
the
only
live.
B
Okay,
it's
not
ga,
but
when
you
install
this
operator
that
action
connecting
things
is
going
to
be
automatically
connecting
a
database
to
a
workload-
and
you
know
what
you
upload
the
jar
you
order,
the
database
you
connect
automatically
boom.
This
is
a
very
nice
developer
experience.
I
don't
know
what
what's
your
fault
about
it.
B
B
You
can
start
from
the
example
you
can
search
for
the
jar
file,
your
artifact,
you
can
start
from
a
any
of
this
n
chart,
for
instance,
if
you
want
to
deploy
for
it's
very
popular,
deploying
software
via
m
chart
like
a
state,
not
not
complex,
not
stateful
application.
For
that
you
have
an
operator
hub.
You
can
use
operator
hub
to
deploy
your
your
software.
B
C
It
assigns
your
application
threat
pools
and
all
the
resources
available
right
and
quackers
basically
takes
this
first
part
like
everything,
except
the
threat
pool
assignment,
and
does
that
at
build
time.
So
when
the
jvm
gets
the
jar
file
literally
injected,
it
just
has
nothing
left
to
do
just
start
up
and
be
ready,
and
if
you,
if
you
really
start
to
like
play
around,
go
to
caucus.io,
there's
actually
a
getting
started
guy
that
plenty
of
getting
started
guys.
C
But
you
can
like
witness
quackers
applications
of
pretty
much
the
same
size
firing
up
in
like
under
one
second
locally
on
a
normal
machine,
so
that
stuff's
really
neat
and
you
have
like
the
the
local
dev
mode,
which
is
my
personal
favorite.
So
quacker
starts
up
that
fast,
that
it
almost
looks
like
it's
a
hot
reload.
But
instead,
if
you
change
something
in
your
source
code,
it
gets
recompiled
and
quarkus
just
restarts,
which
is
possible
because
it's
so
lightning
fast.
C
So
yes,
if
you're
a
java
developer,
if
you're
looking
for
something
like
serverless
microservices
or
I
call
them
microlift,
then
quackers
might
actually
be
an
option
to
look
into
and
if
the
jvm
starter
improvements
aren't
enough,
for
you
there's
also
the
option
to
build
a
gravium
native
image
so
using
growl
substrate.
So
you
can
like
natively
fire
up
your
application,
which
is
insanely
fast
at
all.
Did
that.
A
Answer
your
question:
I
love
you.
I
I
think
that's
that's
very
amazing
what
you
just
shared,
but
if
I
wanted
to
to
make
a
very
like
down-to-earth
analogy,
please
let
me
know
if
that's
correct
so
say
you,
you
want
to
play
tennis
right.
So
I
love
tennis.
That's
why
I'm
I'm
bringing
her
here.
So
in
one
case,
you
are
going
to
the
tennis
club
with
your
golf
clubs,
with
your
basketball,
with
your
volleyball
with
your
swimming
suit,
and
then
you
finally
decide.
A
C
C
Decide
by
using
classes
and
and
putting
like
your
library
dependencies,
they
are
called
extensions
and
quarkus.
So
obviously,
there's
a
little
little
bit
more
magic
going
on
behind
the
scenes,
but
it's
not
dark
magic
and
pretty
similar
to
what
we've
seen
with
openshift.
You
have
like
intelligent
defaults.
C
You
can
still
dive
all
the
way
down
to
the
individual
settings
and
screws
and
tighten
them
if
you
want
to.
But
yes,
just
by
using
extensions,
the
capabilities
that
you
import
via
packages
and
everything
that's
needed
by
your
class,
that's
kind
of
your
packaging
list,
but
it's
implicit.
So
you
don't
have
to
make
an
active
choice.
But
I
love
that
comparison.
It's
really
spot-on.
D
And
also
remember
remember
this
that
even
even
that
containers
were
awesome
and
according
to
corpus
is
awesome,
but
if
you
write
pad
code
it
will
still
be
bad
code.
It
will
not
help.
Of
course
you
have
sensible
defaults
with
corkers,
like
you
don't
have
to
write.
Let's
compare
the
plain
old,
http
request.
You
have
to
write
your
parameter
parsing
and
everything,
so
you
have
defaults
that
do
stuff,
but
still
you
need
to
write
good
code
to
have
a
good
application.
C
B
B
And
sorry
is
now
that
you
mentioned
it
serverless
no
for
quarkus
in
the
announcement
that
we
haven't
afforded
8
there.
There
is
a
a
an
enhancement
for
serverless,
and
here
we
talk
about
openshift
server
function,
so
this
is.
I
think
this
is
a
tech
preview
is
tech
review,
but
this
is
the
function
as
a
service
on
openshift.
Very
close
to
you
know
pretty
popular
serverless
offering
like
lambda,
azure
function
or
cloud
run.
We're
gonna
bring
this
on.
C
Yeah,
I
I
think
that's
that's
kind
of
the
the
logical
next
step
right.
So
if,
if
you
have
a
really
suited
function,
that
needs
to
be
executed
at
various
times
various
instances
and
I've
seen
a
couple
of
really
good
examples.
So
what
one
function
that
I
love
the
most,
because
it
kind
of
explains
the
essence
of
a
function
from
a
design
perspective.
There
there's
a
function
out
there
as
an
example.
It's
not
even
java,
but
it
basically
takes
a
video
stream
as
input
and
adds
a
watermark
to
it
on
the
fly.
C
C
So
if
you
have
these
kind
of
scenarios
and
I'm
not
explicitly
picking
on
like
video,
editing
or
anything,
but
just
as
an
example,
so
the
next
logical
step
from
microservices,
which
are
like
bounded
contexts,
logical
functionality
around
these,
these
bounded
contexts
functions,
will
definitely
up
the
game
in
particular
when
it
comes
to
scaling
to
needs
right.
So
this
is
a
super
important
feature
and
I'm
pretty
sure
we'll
see
a
lot
more
of
of
it
being
used
in
the
next
couple
coming
years.
D
One
comment
is
that
also
that
now
that
the
the
startup
time
is
coming,
it's
going
low?
So
let's
say
that
you
don't
have
overhead
to
run
a
qrikers
in
a
serverless
function
to
do
something.
So
then
you
can
actually
still
removing
core
components.
Let's
say
that
your
web
application
registry
part
can
be
a
function
and
it
can
scale
basically
to
the
sky's
the
limit,
because
you
don't
actually
need
to
think
about
the
code
put
a
time
or
the
startup
time.
You.
C
Your
core:
this
is
something
that
is
super
important
to
java
developers,
because
they
are
kind
of
bound
to
the
jvm
and
the
jvm
itself
can
be
a
beast
in
terms
of
size,
so
not
only
disc,
but
also
memory,
consumption
right
and
there's
a
couple
of
non-cloud
friendly
behaviors
just
was
what
I
described
with
quackers
right.
So
everything
the
jvm
does
before
the
application
even
starts
up
kind
of
leads
to
a
little
bump
in
in
resource
consumption.
C
When
applications
get
started
up
right
so
having
a
native
image
as
a
compilation
result
coming
out
of
quakers,
you
get
rid
of
all
of
this.
You
have
like
a
super
small
footprint
in
memory
on
disk,
like
the
the
actual
images
on
disk,
also
comparably
small,
because
they
only
contain
what's
needed.
So
this
is
the
exact
right
approach
for
serverless
on
the
jvm
in
java,
so
yeah
give
it
a
try.
If
I
haven't
said
that
code.qracos.com.
B
And
I
want
to
show
I
want
to
show
also
that
there
is
a
nice
project
which
is
the
quarkus
for
iot
project
from
our
colleague,
andrea,
very
cool.
He
organized
an
act.
Fest
we've
read
that
partners
in
order
to
use
quarkus
both
on
the
embedded
device.
It's
a
raspberry
pi,
so
parkour's
minimal
footprint,
it's
very
good
also
for
such
low
memory
devices,
but
also,
and
moreover,
on
the
server
side,
part
with
serverless.
B
So
lots
of
data
that
is
coming
from
those
devices
years
is
an
example,
but
can
be
really
lots
of
data
pollution
that
in
this
case
it
can
come
to
an
openshift
server
and
with
serverless
can
really
scale
up
on
demand.
I'm
also
I
want
to
share
here
in
the
chat,
so
you
can
see.
Also.
This
project
is
a
very
good
example
on
how
to
use
quercus
technology,
either
for
the
edge
iot
use
case,
but
also
for
serverless
and
unfortunate.
Eight
is
bringing
function
so
it
looks
a
perfect
match
in
heaven.
C
Yeah
and
this
project
obviously
is
open
source,
so
pull
requests,
welcome,
just
take
it
play
around
with
it.
Everything
is
on
github
and
he
also
did
something
else,
because
this
is
the
first
example
of
quarkus
running
on
a
raspberry
pi
in
as
a
native
image,
so
take
a
deeper
look
at
how
he
did
that.
I
think
it's
not
even
officially
documented
at
the
very
moment,
but
even
that
is
possible.
So
yes,
plenty
plenty
of
good
things
in
this
project.
B
Yeah
there's
a
repository,
a
github
organizational
grouping,
all
the
repositories-
and
you
know
what
you
you
remember
me-
that
we're
gonna
have
the
parkours
for
iot
access
winner
on
openshift
tv,
we're
gonna,
announce
in
july,
so
we're
gonna
have
a
roundtable
with
the
winner.
They
can
share
their
thoughts
about
what
they
did
with
the
with
the
platform.
How
was
focus
for
either
client
and
server
side,
so
very,
very
cool
wow.
We
have
seen
a
lot
of
things
right,
so
this
is.
B
If
we
come
back
to
the
to
the
announcement
serverless,
we
have
pipelines,
pipelines
code
mentioned
by
jafar,
and
also
we
have
this
operation
sandbox
at
containers,
which
is
a
technology
preview
that
provide
light
weighted
virtual
machines.
Also,
we
are
extending
our
support
also
to
virtual
machine
with
cube,
feared,
but
also
cada
containers,
which
is
a
technology
for
lightweighted
virtual
machine.
B
But
for
our
developer
experience
I
think,
there's
a
huge
improvement
and
we've
seen
a
couple
of
things
that
developer
can
can
use
can
consume
other
software
from
the
operator
hub
with
permission
or
the
developer
catalog.
So
I
think
we
we've
seen
lots
of
cool
things,
and
this
is
the
the
quercus
app
we
were
deploying
before.
So
I
think
there's
a
we
have
a
night,
a
nice
round
table
of
options,
but
now
I
would
like
to
talk
about
microsoft
where
it
comes.
Okay,
I
have
obviously
4.8
it's
very
cool.
B
I'm
a
super
new
developer,
it's
very
cool!
What
about
bringing
workloads
to
openshift
for
the
age
migrating
workload?
What
about?
Because
I
don't
think
all
the
developer
super
cloud
native
from
from
day
zero!
No
jared
file
upload
is
very
cool.
It's
helping
a
lot,
but
is
there
any
process
to
help
enabling
the
developer
on
openshift
for
over
day.
C
Yeah,
I
think
tara
mentioned
this
in
the
very
beginning.
Right
so
I
mean
the
majority
of
workloads
is
not
going
to
be
green
field,
microservices
cloud
native
application
development.
We
have
large
investments
out
there.
Many
companies
have
like
all
their
back-end
processes,
supported
by
sometimes
really
large,
enterprise
java
applications
and
they
they're
built
in
a
technical
way
right.
So
back
in
the
days
three
tier
systems,
we
separated
presentation
from
the
business
logic.
C
We
have
a
little
bit
of
database
access
or
even
integration
layer
or
whatever
it's
been
called
back
in
the
days,
so
the
to
find
a
reason
to
throw
this
away
literally
and
rebuild
from
scratch.
It
has
to
be
a
pretty
good
business
case
right.
So
I
think
what
is
super
important
is
to
have
an
infrastructure
underlying
that
supports
all
kinds
of
approaches.
C
You
can
choose
for
your
applications
and
they
they
are
kind
of
standardized
and
everybody
is
referring
to
these
r's.
So
gartner
coined
them.
It's
unbelievable.
These
guys
are
like
definitely
everybody
and
everywhere
involved,
but
ultimately
they
it's
been
four
hours
and
they
got
like
developed
over
time
and
around
2011.
C
So
it
should
always
be
changing
requirements,
and
this
is
the
architect
in
me
talking,
because
ultimately
we
build
our
systems
conforming
to
functional
and
non-functional
requirements,
and
it's
like
simple
best
practices
out
of
software
architecture
and
design
that
help
us
select
the
right
infrastructures,
deployment,
ultimately
scaling
variants.
So
we
can
meet
these
needs.
So
just
because
there's
a
new
technology
and
we
want
to
like
stuff
everything
in
a
container-
that's
not
a
not
a
good
reason
but
yeah.
C
Ultimately,
the
best
platform
that
you
can
chose
is
something
even
if
you
want
to
standardize
that
supports
all
these
kind
of
variants,
and
maybe
you
even
find
a
platform
that
comes
with
supportive,
tooling,
and
we
haven't
talked
about
this
and
not
even
sure.
If
that's
on
an
upcoming
show-
or
somebody
talked
about
it
here
already-
there
is
the
modernization
toolkit
for
applications
that
red
hat
offers
as
open
source.
C
D
D
But
if
you
have
a
platform
that
can
run
vm's
catacombs
containers
in
jar
files,
you
can
harmonize
change
management,
networking,
firewalling,
ingress
control,
updates
everything.
So
you
get
a
lot
of
stuff
for
free
for
free
that
you
now
have
like
exchange
ticket
change
request
for
firewall
in
different
organizations
managing
different
parts.
So
it's
not
just
code.
It's
the
whole
end
to
end
that
you
have,
and
if
you
can
centralize
and
harmonize
even
some
parts
of
that
it
will
be
a
beneficial
for
you.
C
And
the
magic
doesn't
stop
in
your
data
center
right
I
mean.
Ultimately,
you
also
want
to
decide
on
on
how
how
costly
your
hardware
is
that
you're
running
it
on.
Maybe
there
are
governmental
reasons
that
you
need
to
keep
a
certain
data
set
on-prem,
literally
physically
locked
up
in
your
basement,
but
for
other
things
like
black
friday
sales,
and
you
need
to
expand
your
your
shopping
cart
part
of
your
application.
C
Maybe
you
just
want
to
shovel
that
out
to
public
cloud
provider
for
the
two
or
three
weeks
a
year
where
it's
needed
right,
so
you
ultimately
need
that
need
to
manage
that
complexity
of
your
applications
across
various
clouds
and
on-prem
hey
having
a
solution
that
can
provide
all
of
that,
I'm
starting
to
sound
like
a
marketing
person,
but
I'm
actually
a
developer.
I
can
still
code
so
natal.
Let's
talk
about
our
book
at
some
point,
I
I
heard
we're
allowed
to
talk
about
it.
We
can
like
spoil.
B
C
This
is
it.
This
is
how
it's
going
to
look
like,
and
I
talked
about
the
six
hours
so
natalie
and
I
teamed
up
because
we
really
wanted
to
put
a
lot
of
what
we
know
and
what
we
think
are
the
right
ways
to
modernize
existing
applications
into
a
book.
So,
to
give
you
a
little
bit
more
than
just
a
50
minute
show
to
watch
on
youtube.
C
C
A
C
D
B
In
fact,
big
big
shout
out
to
our
colleagues
that
are
helping
us
in
tech,
review,
jay
and
sebby,
and
all
the
colleagues
that
are
helping
us
with
the
tech
review.
All
the
colleagues
that
inspired
us
with
their
awesome
works.
So
we
will
mark.
We
will
do
a
really
big,
thank
you
page,
but
we
will
really.
I
would
really
like
to
thank
everyone
here
in
redata,
which
is
helping
us
this
book.
There
are
lots
of
kubernetes
inside
the
book.
Lots
of
modern
insertion
and
techniques
or
spring
would
work.
C
Yeah
and
I
think
what
what
really
makes
it
different
is
it's
not
just
a
cookbook
right,
so
it
is
something
that
really
takes
you
through
your
modernization
adventure.
So
we're
not
just
looking
at
code
we're
also
looking
at
all
the
non-functional
requirements
around
what
it
really
takes
to
replace,
maybe
an
application
server
with
modern
technologies,
so
we're
kind
of
trying
to
transition
your
existing
toolbox
and
knowledge
into
the
modern
world,
and
I'm
I
should
have
shouldn't
have
said
modern,
but
into
today's
world,
from
a
technology
perspective
but
yeah.
D
B
Awesome
experience
and
amazing
and
yeah
thank
you
and
cool
defaults.
We
have
time
to
remind
you
a
next
appointment
that
we
have
not
on
overshift
tv,
but
we
have
here
in
emma
and
I'm
going
to
share
in
the
chat.
Let
me
start
sharing.
We
have
this
and
robert
is
also
in
the
chat
we
have
the
openshift
and
then
the
threshold,
which
is
a
typically
a
german
event,
but
it
also
has
a
room
in
english,
typical
one
room,
english
one
room,
german
and
robert.
B
You
can
confirm
in
the
chat.
So
if
you
go
to
this
website,
11
am
says
time
we're
going
to
talk
more
about
openshift
with
all
the
other
news.
Other
discussion.
So
please,
if
you
have
time,
go
to
the
open
sheet
of
vendor
traffic,
because
it's
a
very,
very
nice
level.
I
think
the
last
one
was
for
400
people
attending.
So
that's
a
cool
one
and
martin,
you
joined
it
right.
I
don't
know.
C
C
A
lot
of
people
coming
to
these
online
meetings
and
even
the
in-person
meetings
are
really
like
something
that
you
need
to
keep
an
eye
out.
So
if
you're
not
already
part
of
this
amazing
community
sign
up,
it's
free,
there's
a
slack
channel,
there's
like
a
lot
of
people
around
who
can
help
you
with
your
questions
and
there's
literally
somebody
to
answer
everything
from
operations
to
ultimately
development.
C
A
B
A
Yeah
sure
so
again,
thank
you
very
much,
marcus
and
taro
for
for
being
here
as
guests,
so
natalie.
Of
course
you-
and
I
will
be
here-
I
hope-
for
every
other-
openshift
coffee
break
but
yeah.
So
what
we
saw
today
was
like
some
great
announcements
about
the
developer.
Experience
improvement
in
48
things
like
making
the
console
even
easier
to
use
with
the
drag
and
drops
for
deploying
jar
artifacts
and
creating
all
the
resources
or
even
connecting
the
applications
between
them
by
using
the
service
binding
operator.
A
So
this
is
still,
of
course,
in
tech
preview.
We
spoke
about
pipeline
s
code,
which
is
making
tecton
and
openshift
pipelines
even
easier
to
use
by
putting
the
pipelines
directly
in
the
source
repo.
So
I
think
all
of
that
is
gonna
improve
a
little
bit
more.
The
developer
experience
and
again,
as
you
said,
marcus
this
is
like
the
beginning
of
making
it
even
easier.
So
I
I
really
love
the
console.
It
has
been
going
through
a
lot
of
changes
when
we
switched
to
open
f4
and
it's
yeah.
A
I
can't
wait
to
see
how
many
improvements
we're
going
to
to
put
in,
especially
when
we
speak
about
functions
with
things
like
eventing,
being
able
to
drag
and
drop,
to
connect
to
to
kafka
topics
or
whatever
and
be
able
to.
You
know
just
graphically
build
your
application,
and
then
everything
happens
in
the
in
the
background
so
yeah
that
was,
that
was
very
nice.
So,
of
course,
don't
forget
guys
to
join
the
openshift
dot
tv
twitch
channel.
So
we're
going
to
put
the
yeah.
A
You
have
the
link
in
the
chat
and
our
next
episode
here
will
be
again
in
two
weeks
where
we
will
be
speaking
about
tectum
and
openshift
pipeline.
So
it's
going
to
be
our
second
episode
of
openshift
pipelines
and
texans.
So
what
we
will
be
covering
this
time
is
what
happens
when
you
commit
your
code
and
then
the
push
event
triggers
a
pipeline.
A
We
will
explain
in
detail
what
happens
in
the
pipeline
constructs
in
the
tecton
constructs
with
things
like
trigger
templates
and
all
the
little
things
that
work
together
to
make
that
automatically
trigger
a
pipeline
run.
So
again,
we
will
have
guys
from
tecton
engineering
and
openshift
engineering
tool
to
talk
about
it
and
we
will
show
you
some
cool
demos
and
go
into
the
under
the
hood
of
what
happens
when
when,
when
we
trigger
those
pipelines
and
so
yeah,
that's
it.
A
A
I
am
actually
aiming
for
that.
So
what
we
are
thinking
about
doing
now
is
keeping
our
regular
open
shift
coffee
break
meetings
like
by
bi-weekly,
but
every
other
week.
I
will
try
to
put
in
a
text
on
episode
in
between.
So
that's
my
my
end
goal
and
then
we
would
have
like
a
show
every
week,
but
one
one
time.
It's
gonna
be
a
main
topic
for
openshift
coffee
break
and
the
next
week
it's
going
to
be
dedicated
on
tecton.
So
it's
going
to
be
like
the
tectonics.