►
From YouTube: Developer Experience Office Hours: Readout of the OpenShift Developer Experience 2020 Survey
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
A
Good
morning
good
afternoon
good
evening
and
welcome
to
another
edition
of
the
developer
experience
office
hours
here
on
openshift
tv,
I
am
chris
short
executive
producer
of
openshift
tv.
I
am
joined
by
two
of
my
favorite
red
hatters
serena
from
the
future
and
ryan
jarvanin
serena
nichols
is
her
real
name
today,
serena
we're
talking
about
what
exactly.
B
A
A
C
I'm
gonna
head
on
over
to
the
chat
on
on
twitch.
We
also
have
chat
running
through
youtube,
live
via
restream,
so
feel
free
to
join
us
on
either
of
those
outlets.
You
can
find
all
the
links
on
openshift.tv
and
yeah
I'll
be
keeping
an
eye
on
chat.
So
definitely
let
us
know
if
you
have
new
topics
that
you
would
like
to
see
on
this
show.
This
is
intended
to
be
a
an
office
hour
segment.
So
definitely
get
active.
C
Ask
your
questions
we'll
do
our
best
to
respond
to
any
that
you
have
and
yeah.
We
love
talking
about
kubernetes
and
developments
and
how
you
can
make
the
most
of
your
development
time
while
taking
advantage
of
kubernetes.
So
hopefully,
this
developer
survey
has
really
kind
of
collected
a
lot
of
our
feedback
from
you
in
the
past
in
2020,
and
we're
anxious
to
hear
what
you've
got
on
your
mind,
going
forward
in
2021
awesome
carlos.
A
A
C
C
Things
from
the
topology,
as
well
as
from
the
other
lists,
I
think
most
of
our
filtering
so
far-
has
been
around
kind
of
categories
of
things
like
d,
it's
probably
not
the
exact
example
but
like
hiding,
I
don't
know
up
like
if
you
didn't
want
to
show
certain
operators
or
certain
other
things
in
the
left-hand
column.
You
can,
I
think,
get
some
of
those
filtered
out.
Take
a
look
at
the
console.
A
B
B
I
am
happy
to
yeah,
definitely
okay,
so,
as
I
mentioned
we're
going
to
share
some
of
the
survey
analysis
of
the
2020
survey,
this
is
just
showing
that
we
did
have
was
our
data
scientist
associated
with
this
and
steve
speicher
who's
usually
kind
of
co-presenting
on
something
like
this
is
isn't
available
today.
So
I'm
just
going
to
be
talking
about
it
today.
B
You
know
the
background
is
around
to
learn
more
about
how
developers
are
interacting
with
openshift
and
help
drive
product
direction.
Of
course,
this
is
the
third
year
that
we've
run
the
survey
and
the
survey
ran
from
october
4th
to
november
22nd
so
about
six
weeks
at
the
end
of
the
year,
and
we
had
38
questions,
so
I'm
going
to
try
to
give
a
quick,
quick
overview
of
where
we
landed,
and
I
can
also
you
know.
Let
me
know
if
I
need
to
pause
for
questions
along
the
way.
B
B
B
Around
a
metric
of
understanding,
the
deviation
or
the
possibility
of
what
is
it
called
like.
The
answers
might
not
be
specifically
correct.
There's
a
a
chance
that
there's
like
an
eight
percent
right,
dipped
positive
minus
on
each
of
these
things,
based
on
the
sample
size
that
we
have
and
some
of
the
metrics
that
we
had.
So
just
remember
that
as
well,
and
so,
if
we
start
looking
into
some
of
the
questions,
we
asked
the
first
one
was
around.
What
type
of
application
are
you
running
on
openshift?
B
So
this
is
pretty
interesting
where
the
micro
micro
services,
stateless,
apps,
staple
apps
and
traditional
apps
are
definitely
the
most
popular.
But
if
you
kind
of
look
at
where
the
numbers
are
trending
from
2018,
19
and
20,
you
can
see
a
decrease
in
there
about
three
quarters
of
the
way
down
or
two
thirds
of
the
way
down
the
page.
You
can
see
that
we
did
add
event
driven
applications,
and
so
that
was
a
new
item
that
came
in,
but
it
did
come
in
at
six.
B
What
we
also
did
was
we
kind
of
pulled
in
some
of
the
slides
around
the
cncf
survey
to
try
to
back
up
some
of
the
data
that
we
heard
or
or
got
from
our
our
own
survey.
So
this
is
around.
Do
you
run
staple
apps
and
containers
and
according
to
the
season
cf
survey?
55
percent
are
yes
running
in
production,
so
again
pretty
interesting.
It
also
talks
about
12
or
evaluating
and
11
plan
to
use
them
in
the
next
12
months.
So
again,
some
similarities
of
of
the
trend
that
we
saw
through
our
survey.
B
This
one
is
again
from
the
cncf.
How
is
your
organization
using
serverless
technology,
and
so
just
under
a
third
of
the
respondents,
are
using
serverless
technologies
in
production
and
another
20
21
are
evaluating
and
14
plan
to
use
in
the
next
12
months.
So
again,
interesting
information,
as
you
know,
you
all
know
in
the
console,
which
is
where
I'm
spending
a
lot
of
my
time.
B
B
B
Around
the
question
of
what
did
most
people,
what
what
version
are
was
the
most
recent
that
they
had
experience
with.
You
can
see
a
good
decline,
a
decent
decline
in
the
3.11
or
earlier,
which
is
great
right.
So
the
if
you
kind
of
focus
on
that
311
or
earlier
80
percent
of
the
people.
Respondents
in
2019
said
311..
B
Now,
we've
got
about
36
37
percent
in
2020,
so
we're
seeing
that
decline,
which
is
what
we're
expecting.
The
thing
that
is
interesting
about
this
survey
is
that
we
are
getting
a
respondent
set
of
of
people
that
are
using
3.x
as
well
as
for
so
we're.
Not
quite
so.
Some
of
the
the
answers
that
are
we
we're
getting,
obviously
are
also
mixed
based
on
three
versus
four.
B
So
it's
a
little
bit
hard
to
kind
of
evaluate
if
some
of
those
answers
are
more
focused
on
one
version
or
the
other,
so
we're
hoping
in
2021
when
we
do
the
survey
again
that
most
of
our
customers
will
be
off
of
the
3.x
platform
and
or
we
are
also
going
to
change
the
way
that
we're
asking
questions
so
that
we
get
direction
on
the
4.x
experience.
Even
if
3.x
is
something
that
they're
also
continuing
to
use.
C
C
You
know,
you've
got
the
people
who
have
just
started
looking
at
four
and
never
ran
their
upgrades,
and
then
people
who
did
probably
continue
running
upgrades
and
ended
up
on
four
five
or
or
maybe
even
four,
six
eventually
so
cool
to
see
that
people
didn't
just
switch
to
four
and
then
stay
put
you
know
the
hopefully
the
auto
upgrade
or
the
support
for
in-place
cluster
upgrades
is,
is
working
well
for
folks.
So
it's
cool
to
see
some
of
that
shift
in
the
data.
B
Okay,
so
kind
of
a
summary
on
that
section,
the
top
up
five
apps
decreased
overall,
but
they
were
still
the
top
five
and,
as
we
noted
there
was
some
growth
in
this
in
the
next
six,
through
nine
and
eventing
or
I'm
sorry.
Serverless
was
one
of
those
that
was
kind
of
looking
to
take
possibly
a
major
role
in
in
the
future.
B
A
B
Wasn't
doing
anything
you
know
okay,
so
as
far
as
the
actions
like
I
mentioned,
we
are
thinking
about
how
we
can
focus
the
survey
or
over
the
survey
a
little
bit
more
so
that
we
make
sure
that
as
you're
going
to
see
in
in
the
next
couple
of
sections,
we
talk
about
ease
of
use
and
satisfaction
ratings.
We
want
to
make
sure
that
those
ratings
are
based
on
4.x
in
the
future,
so
that
we
so
that
it's
not
mixed.
So
we
have
a
better
understanding
of
the
baseline.
B
So
the
next
section
is
around
developing
and
testing
code
on
openshift.
So
the
first
question
this
first
question
here
is
around
is
openshift
easy
to
use
rate
your
agreement
with
the
statement
as
you'll
see
here.
This
is
one
of
the
outliers
and
we
had
a
scale
of
one
to
five
or
strongly
agree,
somewhat
agree
kind
of
neutral
and
then
somewhat
disagree
and
strongly
disagree.
B
B
You
know
a
couple
of
percentage
points,
but
nothing
substantial
there,
but
still
it's
good
to
see
that
we're
on
the
higher
end
of
that
scale,
and
now
this
is
an
interesting
one
where
we're
showing
rate
your
agreement
on
openshift
is
easy
to
use
based
on
the
release
you
are
on,
and
I
probably
cannot
increase
this
percentage.
So
I
apologize
for
this,
but
what
you
do
see
here
is
in
4
5.
We
see
a
pretty
good
uptake
on
what
people
are
doing
for
somewhat
agree
and
agree
and
strongly
agree
on
4.5,
where
we
had.
B
I
think
it's
between
the
top
two
we've
got
about.
25
percent
are
saying
that
either
strongly
or
somewhat
somewhat
agree,
but
then
we're
seeing
a
little
bit
a
big
fall
in
when
you
look
at
4.6.
So
we
got
to
investigate
that
a
little
bit.
It
could
be
that
4.6
had
just
come
out.
Maybe
people
weren't
used
to
it
yet
not
sure
what
features
they
were
trying
to
use,
but
that's
something
that
we'll
definitely
have
to
take
a
look
at.
B
B
B
Definitely
yeah
thanks
for
that.
Okay,
so
this
one
so
now
we're
going
back
to
openshift
is
easy
to
use,
which
is
interesting,
so
we've
got
the
311
or
earlier
is
on
the
bottom.
So
on
the
bottom
half
of
the
page
and
four
one,
two
four
six
is
on
the
top
half
of
the
page
and
again
I
think
this
is
great.
B
If
you're
looking
at
ease
of
use
from
four
one
to
four
six,
we
are
seeing
higher
percentage
right,
so
fifty
percent
of
the
people
are
saying
they
somewhat
agree
and
about
17
are
saying
that
they
strongly
agree
so
in
as
opposed
to
in
3.11.
The
percentage
was
much
lower,
I
think
for
those
top
two
ratings.
B
So
so
that's
that's
good
news.
When
you're
talking
about
relative
ease
of
use
from
one
product
from
one
release
to
the
next,
when
we're
talking
about
capabilities
meeting
our
requirements,
almost
all
the
respondents
found
that
openshift's
capabilities
do
meet
their
requirements.
You
can
see
again
a
little
bit
of
an
update
uptick
in
somewhat
agreed
from
2019
to
2020.,
but
everything
else
is
relatively
similar
across
the
board.
B
The
next
section
of
the
survey
is
really
focused
on
satisfaction
with
developing
and
testing
on
openshift,
so
rather
than
showing
each
of
the
individual
charts,
I'm
going
to
give
some
more
summary
type
information.
So
the
questions
that
we
talked
about
included
satisfaction
around
the
ease
of
getting
started,
interactive,
local
development,
open
shift
environment
used
to
develop
and
test
against
the
image,
build
process
and
source
to
image
and
the
time
it
takes
to
build
and
run
an
application.
B
So
again
would
be
interesting
for
people
to
continue
to
comment.
If
you
have,
if
you
agree
or
really
even
disagree
on
any
of
these,
it
would
be
interesting
to
know
right.
So
our
observations
was
that
the
satisfaction
of
interactive
local
development
made
a
big
jump
in
2020
and
that
had
previously
been
one
of
our
lowest
rated
items.
B
But
there
was
a
small
sample
size,
so
we
need
to
do
some
investigation
there
and
then
a
nice
thing
to
see
here
was
that,
with
the
steady
improvements
we
saw
across
the
board
from
image
build
process
in
s2i,
where
in
2009
I'm
sorry
2018.
It
was
19
to
then
to
23
then
to
31
for
that
very
satisfied
reading
and
as
far
as
actions
go,
we
were
talking
about
the
fact
that
it's
going
to
be
interesting
to
see
if
satisfaction
regarding
getting
started
will
increase
because
we've
got
all
these.
B
You
know
great
improvements
and
other
features
that
are
available
starting
soon
or
recently,
with
the
developer.
Sandbox,
the
you
know,
making
the
footprint
size
smaller
for
crc
in
the
console,
specifically
around
getting
started.
We've
introduced
all
these
new
quick
starts
some
in
four
six,
but
more
and
four
seven
and
guided
tours
as
well.
So
we're
hoping
that
those
things
will
help
to
improve
some
of
these
ratings
in
2021.
C
B
B
And
so
again
I
just
mentioned
some
of
the
things
here
that
we're
working
on
in
4.8
in
the
console
where
we
have
an
enhanced
catalog
experience
as
well
as
new
topology
feature
to
help
find
services.
So
we
think
that
that
will
really
bump
that
finding
service
piece
when
you
have
the
red
hat
integration,
kmlk
operator
installed
developers
will
also
now
see
in
the
event
source
catalog
camel
k,
connectors,
starting
with
a
few.
You
know,
starting,
I
think,
with
five
but
you'll
see
that
number
increase.
B
So
again,
the
number
of
options
that
developers
will
have
available
to
them
will
continue
to
increase,
and
then
there's
this
there's
a
bunch
of
work
going
on
with
manage
kafka
services
which
will
set
the
stage
for
a
consistent
experience
in
the
console
around
managed
services
across
the
board.
So
I
think
that's
super
important
as
well.
C
That's
interesting
to
me
that
managed
services
didn't
see
a
big
increase
with
all
the
operator
hub
options
that
are
potentially
available.
Not
all
of
them
are
pre-installed
on
your
cluster,
but
I
was
kind
of
expecting
to
see
a
big
jump
in
availability
of
of
related
services
that
are
just
easily
pluggable
and
instantly
kind
of
available.
B
A
Yo
jp
day
to
have
an
update
specifically
for
you
from
our
product
management
team
on
quays
requirement
for
docker
3-4
is
getting
released
this
week
and
there
will
be
improvements
in
the
documentation
to
handle
podman
versus
docker
better.
So
just
wait
till
the
end
of
the
week
and
you'll
have
an
answer.
B
Okay,
all
right
so
application
development
features
on
openshift.
This
section
of
the
survey
focused
on
application
development,
but
specifically
around
application.
Health
performance
visibility,
feedback
on
progress
and
errors
during
development,
application,
debugging
project
and
environment
organization
integration
with
ci
cd,
as
well
as
availability
of
modern
frameworks
and
runtime.
B
So
again,
just
kind
of
skipping
this,
the
charts
and
just
moving
down
to
our
observations
and
active
and
our
actions
overall
customer
satisfaction
is
pretty
flat
again
in
2020
application,
debugging
and
feedback
on
progress
and
errors
are
the
lowest
rated
items
around
satisfaction
that
we
have
so
as
far
as
actions
go,
you
know
there
are
ongoing
efforts
to
improve
application,
health
and
performance
visibility.
We've
got
a
lot
a
lot
of
work.
B
We
have
a
monitoring,
observability
team,
that's
doing
a
lot
of
work
on
the
back
end
and
the
console
team
is
is
working
with
them
to
see
how
we
can
bring
pieces
in
we've.
Also
we're
also
working
with
other
members
around
you
know.
Java
performance
is
their
way
for
us
to
bring
in
java
performance
dashboards
into
the
console,
etc
and,
as
far
as
like
the
the
one,
around
availability
of
modern
frameworks
and
runtimes,
what
we
are
doing
in
4.8
is
we're.
You
know
there's
more
and
more
corcus.
B
The
quarkus
experience
is
showing
up
more
and
we've
added
some
quick
start
so
that
to
provide
some
awareness
for
users
that
that
stuff
is
available
and
can
work
on
the
openshift
platform
and
how
and
kind
of
walk
you
through
how
to
do
that
and
then.
The
other
thing
I
did
want
to
note,
too,
is
since
integration
with
ci
cd
tools
was
part
of
that
you
know.
4.5
through
4.8
is
providing
a
seamless
integration
with
tekton
pipelines
inside
the
console.
B
C
I
I
particularly
appreciate
that
last
section
on
on
developer
productivity,
I
I
like
the
focus
on
feedback
during
my
development
loop
and
that's
something
that's
not
always
available.
Depending
on
how
you
have
set
up
your
development
environment.
A
lot
of
folks
will
do
a
very
minimal
setup
where
most
of
their
work
is
being
done.
It
may
be
locally
in
ide.
C
They
may
not
be
leveraging
their
cluster
to
get
that
kind
of
production,
quality
feedback
as
part
of
their
local
dev
loop.
They
might
only
be
getting
that
feedback
after
they
deploy
or
push
something
into
a
tecton
pipeline
or
others
right.
So
you
get
that
feedback
on
an
interval,
but
not
necessarily
as
you're
doing
the
iterative
development
work.
C
So
we've
added
a
lot
of
capabilities
to
get
more
feedback
out
of
your
cluster
production
quality
feedback,
while
you're
actually
doing
that
iterative
work
to,
hopefully
give
you
just
a
better
reflection
of
of
what
production
is
like
and
to
help
you
save
time
and
energy
as
you're
working
leveraging
that
improved
feedback.
So
I
know
we're
doing
a
lot
of
work
to
help
connect
the
dots
for
folks
on
on
those
pieces.
B
Yeah
for
sure
this
piece
is
interesting
as
well,
so
this
is
around
resources
for
openshift
and
we're
not
talking
about
kubernetes
resources
but
more
like
resources
for
a
user
to
go,
get
more
information
right,
so
focused
on
satisfaction
of
resources
for
openshift
around
product
help
and
documentation
blogs
whether
they
go.
You
know
blogs
covering
developers.redhat.com
as
well
as
the
openshift
blog,
and
I'm
noting
that
here,
because
we
don't
have
a
satisfaction
reading
based
on
each
of
the
different
areas.
It's
on
blogs
overall,
as
well
as
how
to
guides
and
tutorials.
B
So
our
numbers
aren't
terrific
here
by
any
means,
there's
a
lot
of
improvement.
I
think
room
for
improvement
and
you
can
see
like
there's
slight
changes,
but
it's
not
it's.
Nothing!
Really
substantial
across
the
board
for
product
help
blogs
you
can
see.
We
have
10
from
the
very
satisfied
rating
we've
gone
up
from
2018..
B
B
We
did
see
some
slippage
in
satisfaction
in
product
health
and
docs
and
blogs
from
2019
to
2020,
and
we
clearly
need
to
focus
in
these
areas,
but
we
are
anticipated,
anticipating
specifically
in
the
console
that
quick
starts,
are
going
to
address
some
of
these
areas
around
the
tutorial
piece,
and
it's
really
interesting.
So
we
are
utilizing
quick
starts
or
trying
to
utilize.
Quick
starts
from
the
pm
and
the
ux
side,
but
we're
also
talking
the
developer
advocate
team
on
like
how
they
might
be
able
to
take
advantage
of
them.
B
We've
also
had
a
number
of
meetings
with
some
customers
who
are
really
interested
in
bringing
quick
starts
into
their
own
environment
and
utilizing
those
to
help
to
teach
best
practices
on
how
to
create
or
man
you
know,
create,
upgrade
maintain
applications
in
their
own
environment
for
their
own
developers.
So
that's
pretty
interesting
to
see.
I
think.
B
And
I
guess
that
last
bullet
is,
we
do
have
a
plan
on
focusing
focused
on
how
we're
improving
blog
content
delivery
as
well
as
contribution
I'd
really
be
interested.
If
people
have
the
opportunity
to
kind
of
say
something
in
the
chat
like
what
are
the
most
useful
types
of
blogs
that
you
guys
see,
do
you
like
the
what's
new
blogs?
Do
you
like
more
something
around?
It's
walking
you
through
something
and
you
can
learn
about
something
really
specific
and
or
are
you?
Are
you
typically
looking
at
openshift
blog
versus
the
red
hat?
A
A
C
C
A
Yeah-
and
you
know,
good
feedback
is
the
challenges
you're
hitting
right,
like
gp
date,
was
talking
about
his
challenges
with
installing
quay
key.
However,
you
want
to
say
it
on
rail8
right,
like
we
need
feedback
like
that,
to
get
you
all
great
blog
posts
to
help.
You
enable
yourselves
to
go
hard
and
fast
right,
like
that's
the
idea,
move,
move
quickly
and
safely.
B
I'm
also
just
going
to
pull
these
in
here,
I'm
just
going
to
add
a
couple
of
tabs,
so
I
think
probably
everybody
knows
about
the
openshift.com
blog.
I'm
sure
one
of
the
things
that
we
have
been
doing
is
a
concerted
effort
when
we're
doing
something
for
the
developer
is
that
we
are
posting
our
blogs
on
developers.redhat.com.
B
I'm
not
sure
if
you
guys
are
all
signed
up
for
that
program
or
not
definitely
look
into
it
if
you
are
are
interested,
but
if
you
go
into
the
products
tab
on
the
top
right,
let's
see
what
did
I
just
do
and
then
scroll
down
to
the
bottom?
There's
a
red
hat
open
shift
here,
and
this
is
kind
of
where
you
can
see
downloads
getting
started
an
overview,
but
this
is
where
you
can
see
a
lot
of
the
content
that
we
do.
I
think
it's
underneath
getting
started
as
well.
B
B
B
A
D
A
B
And
it's
actually,
I
mean
it's
also
pretty
yeah
exactly,
and
it's
also
pretty
interesting
too
right
like
so.
We
you
think
about
like
what
we're
doing
with
their
developer
experience
office
hour.
We
oftentimes
are
talking
about
how
to
customize
the
experience
for
developers
which
might
be
tailored
to
admins
right
that
the
admins
have
to
do
the
customization,
whether
they
expose
operators
or
shut
off,
helm
or
or
add,
more
home
repositories
or
whatever,
but
it's
there's
still
an
overlap,
so
it
is.
D
B
B
Four
is
very
satisfied,
so
we're
seeing
numbers
kind
of
right
around
satisfied,
I
guess
so
pushing
builds
boiled
artifacts
to
my
repo
is
three
one,
along
with
security
concerns
with
builds
and
ability
to
apply
runtime,
config
and
availability,
availability
of
builder
images,
and
then
the
straight
3.0
around
injecting
dependencies
and
ability
the
ability
to
extend
and
modify,
build
steps
and
then
a
little
bit
lower
around
build
speed
and
the
resulting
image
size.
So
some
you
know,
observations
and
summary
around.
That
is
the
overall
satisfaction.
B
Again,
it's
pretty
much.
Everything
is
relatively
flat.
This
in
this
instance
slightly
up.
Unless
we
just
noted
dependency,
injection
and
image,
size
and
speed,
build
speed
are
ranked
the
lowest.
So
part
of
those
actions
are
to
prioritize
some
of
those
features
in
the
upcoming
roadmap
and
investigate
dependency,
injection
issues
so,
and
also
hoping
again.
This
goes
back
to
guidance
and
documentation
best
practices
on
how
to
achieve
those
kind
of
build
improvements.
B
Some
of
these
are
so
we're
going
to
start
with
the
cncf
survey,
where
what
their
challenges
were
in
using
and
deploying
containers,
so
their
top
challenges
were
complexity,
joint
cultural
changes
with
the
development
team,
so
that
is
kind
of
interesting.
And
then,
if
you
take
a
look
at
some
of
the
our
things
on
our
survey,
the
observations
were
top
issues
were
time
and
culture,
local
environment,
cnc,
new
and
getting
started
or
documentation
performance
and
resources
and
stability.
B
So
it
is
interesting
that
that
new
user
getting
started
documentation
and
performances,
performance
or
being
able
to
kind
of
observe-
or
you
know,
monitor
things
are
seen
to
be
some
of
our
largest
challenges
there
so
again
for
around
actions,
increased
priority
of
features
and
documentation
to
reduce
friction
for
adoption
and,
of
course,
continue
to
try
to
reduce
that
crc
footprint,
which
is
already
in
the
plan,
and
we've
definitely
made
some
improvements
to
date.
But
we're
continuing
to
work
towards
that.
C
We
had
some
kind
of
lower
scores
around
the
getting
started
experience,
and
I
think
part
of
that
is
just
for
folks
who
are
moving
to
kubernetes
or
two
containers
from
a
before
kubernetes
type
of
era.
There
is
a
lot
of
it's
so
there's
a
lot
of
knowledge,
a
lot
of
learning,
a
lot
of
skills
you
have
to
adopt,
and
all
of
that
takes
time.
All
of
that
takes
energy.
C
Hopefully
openshift
is
doing
a
good
job
of
hoping
of
helping,
reduce
the
complexity
and
the
amount
of
learning
that
you
have
to
do.
It's
definitely
a
challenging
situation
because
we
want
to
give
you
full
access
to
all
the
underlying
kubernetes
resources,
while
still
hiding
enough
of
it
to
make
it
easy
for
new
users,
so
hopefully
we're
doing
a
decent
job
of
kind
of
splitting.
That
balance
there
I
mean
it's.
A
B
Right
yeah,
I'm
just
noticing
something
here
that
somebody
had
mentioned
it
would
be
nice
to
get
if
there
was
a
openshift
only
newsletter.
I'd
subscribe
to
get
it
if
it
was
once
a
week,
but
I'm
not
going
to
visit
the
sites
every
week
to
check
what's
new.
So
I
don't
know
if
anybody
who's
who
are
like
chris
or
ryan.
I
don't.
I
do
not
know
this,
but
the
red
hat
developers
newsletter.
Do
we
know
how
frequently
that
goes
out.
A
A
B
B
A
B
We're
seeing
a
decline
on
that?
I
know
these
are
images
too,
so
I
can't
do
anything.
Unfortunately,
the
next
one
is
around
oc
or
cube.
Cuddle
creates
the
next
one
is
around
internally
developed
internally,
developed,
tooling
and
then
helm
charts
is
the
fourth
open
shift.
Templates
is
the
one
that's
only
highlighted
in
pink
audio
create,
so
that's
kind
of
where
we
are
with
the
top
ones.
B
C
Right,
that's
cool!
That's
cool!
To
see
folks,
move
to
standard
kit
that
is
maintained
by
a
community
rather
than
all
in-house.
There's.
Definitely
some
value
to
doing
it
all
in-house
when
you
need
to,
but
it's
nice
to
see
home,
charts
kind
of
moving
up
as
a
widely
adopted
way
of
packaging
and
distributing
your
solutions.
So
that's
that's!
Pretty
cool.
B
Yeah
the
interesting
thing
like
I'm
just
trying
to
look
at
the
percentage,
so
in
2019,
helm,
charts
was
it
about
18
and
now
is
it
about
37?
So
that's
a
pretty
big
hike,
yeah
yeah,
okay,
the
next
one
again
is
around
which
languages
and
tools
are
used
by
your
applications
on
openshift,
so
I'll
I'll.
Take
a
I'll
read
down
like
the
top
eight
or
so
so.
Java
was
number
one
open,
jdk
two
javascript
python,
jboss
eap,
go
tomcat,
jboss
web
server
and
then
net
core,
and
then
we
also
see
corcus
again.
B
Corcus
is
new,
so
you
see
quarkus
kind
of
where
were
they
they
were
at
about
12
last
year
and
then
this
year,
at
about
24,
so
will
be
interesting
to
see
if
that
continues
to
grow,
or
it
will
be
interesting
to
watch
that
grow,
and
it's
also
well
interesting
that
the
top
languages
are
used
by
apps
in
openshift
or
java,
with
jdk
javascript
and
python,
but
you're
also
seeing
a
decline
from
2018
to
20.
With
a
few
of
these,
so.
B
C
C
A
D
C
It
could
be
like
static
web
versus
actually
run
via
a
node.js
server
that
that
you
want
to
distinguish
between,
which
is
somewhat
valid,
but
yeah.
It's
interesting
to
me
that
there's
a
a
java
and
then
an
open,
jdk
and
then
also
wildfly
and
like
a
couple
potential
ways
to
roll
up
java
into
a
larger
category.
C
C
B
All
right,
so
this
next
slide
is
around,
like
we
pulled
in
a
part
of
the
github
survey
as
well
right
just
to
show
top
languages
over
the
years
as
well.
So
if
you
can't
read
the
image
on
the
left
2014,
it
starts
on
the
left-hand
side
and
moves
over
to
2020
on
the
right-hand
side.
So
you
again
see
javascript
remaining
concept.
A
A
C
D
B
And
then
here
is
another
survey
stack
overflow
kind
of
the
same.
You
know
trying
to
tease
out
the
same
types
of
information
but
where
they
see
python
moving
down
for
eighth
year
in
a
row,
javascript
has
maintained
its
strongholds.
You
know
so
yeah
kind
of
some
interesting
things
and
we're
seeing
some
similarities
between
these.
So
it's
interesting.
B
B
B
A
B
B
Fourth
is
refactor
and
rehost.
Fifth
was
third
party
consulting
then
strangler
pattern,
replacing
monolith's
capabilities
with
independent
microservices,
then
internally
developed
tooling,
then
red
hat
migration,
tooling
for
applications
and
other.
So
it
is
interesting.
I'm
just
going
to
note
that
really
quickly,
red
hat
migration,
tooling
toolkit
for
applications
was
newly
added
in
2020
and
about
17
of
the
people
have
noted
that
which
is
interesting,
so
it'll
be
cool
to
see
if
that
continues
to
grow
as
well
so,
but
as
go
ahead.
A
B
B
C
Yeah,
I'm
curious
to
see
I'm
curious
to
see
if
we
have
a
operator
hosted
pattern
showing
up
here
in
future
results.
I
know
that's
something:
we
talk
about
being
a
a
way
of
hosting
stateful
applications,
because
you
could,
if
you
had
a
step
where
you
needed
to
bootstrap
a
database
and
pre-populate
it
with
a
set
of
data
or
do
backups
or
or
do
other
more
complicated,
app
performance
things
in
the
background.
D
B
A
C
D
C
In
go
right
right
and
not
everyone
is
is
up
for
that
challenge
of,
like
oh,
go,
write
a
second
app
and
go
to
package
your
first.
It's
it's
a
yeah.
It's
not
super
easy,
but
with
support
for
helm,
charts
operator
backed
helm,
charts
that
might
be
a
little
bit
easier
option,
but
there's
definitely
some
trade-offs
and
and
more
work
for
us
to
document
how
you
might
adopt
one
of
those
approaches.
A
B
All
right
so
going
through
some
of
the
observations
audio,
I'm
not
sure
how
many
people
are
on
the
caller
using
that,
but
we
it
made
a
jump
from
a
percentage
perspective
from
5
to
13.
So
that's
great
news,
but
the
overall
usage
is
still
low.
I
think
we
we
need
to
continue
to
kind
of
make
people
aware
of
that,
and
the
power
explain
the
power
and
why
somebody
would
want
to
use
that
cli.
B
Over
50
of
the
respondents
are
using
the
console
to
start
application
creation,
I'm
going
to
downplay
the
next
couple
of
items,
some
other.
On
the
action
side.
We
are
starting
to
gather
metrics
for
odo
usage,
as
well
as
some
of
our
other
areas
in
the
portfolio
helm.
Certification
process
is
going
to
be
started
and
will
be
supported
in
the
console
sometime
within
2021,
which.
A
B
I
think
good
news
and
we're
going
to
continue
to
improve
and
enhance
the
console
and
support
multiple
methods
of
creation.
Dev
files
are
something
that's
really
exciting
that
people
are
talking
about,
which
are
that
you
know
that's
going
to
help
satisfy
our
kind
of
roar
launcher
use
cases
and
those
are
going
to
be.
B
So,
looking
at
the
clock,
I'll
just
do
this
one
section.
So
where
do
you
develop
and
test
your
application
for
open
shift?
So
the
first
one
is
around
local
desktop
instead
of
openshift
other
internally
hosted
local
on
desktop
with
application,
runtime
externally
hosted
or
local
desktop
instance
of
other
container
platforms.
B
B
So
what
do
you
use
to
run
a
desktop
instance
of
openshift,
so
we
have
code.
Ready.
Containers
is
the
first
one.
The
first
option
mini
shift
is
the
second
option.
Oc
cluster
up
is
third
container
development.
Kit
cdk
is
fourth
and
then
other.
So
we
do
see
again
a
big
kind
of
uptick
on
code
ready
containers
where
in
2019
it
was
at
about
39
percent
and
it's
gone
to
60,
64
or
so,
which
is
exciting
and
we
do
see
mini
shift
declining
so
as
well
as
oc
cluster.
A
C
C
B
And
so
this
one
is
around
which
local
desktop
instance
of
other
container
platforms.
Do
you
use
in
docker
run
so
again,
docker
runs,
first
mini
cube.
Second
pod
man
run
third
other
and
then
docker
swarm
so
again
just
interesting
information,
and
this
is
aligned.
Now
we
pull
back
in
the
cncf
survey,
where
the
top
kubernetes
environments
are
mini,
cube
37
for
them
on
prem
kubernetes
installations,
which
is
31
and
docker
kubernetes,
which
is
29.
B
A
B
A
A
A
B
C
B
Yes,
so
last
week
we
had
this
little
survey
around
you
know.
What
would
you
like
to
see
in
the
developer
experience
office
hours
going
forward?
We
kind
of
ryan
did
a
great
job
at
like
notating,
some
of
the
the
different
types
of
options
that
we
can
provide
and
really
getting
feedback
from
you
all
to
make
sure
that
we're
sharing
what
you
want
to
hear.
So,
if
you
can
find
that
quickly,.
B
C
Yeah
pasted
that
into
chat-
and
I
should
get
a
shorter
url
for
folks
tuning
in
later,
but
yeah
there's
a
somewhat
shortened
url.
We
would
love
to
hear
your
ideas
for
additional
topics
on
the
show.
There's
a
fill
in
the
blank
area
at
the
bottom
of
that
feedback
form.
So
definitely
let
us
know
if
you
have
more
topics.
You
would
like
to
see
and
thank
you
to
everyone
who
contributed
in
chat
today.