►
From YouTube: Developer Experience Office Hours
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
This show features product enhancements and changes that are still in flight. These changes may or may not land in the the version of OpenShift being talked about (or at all in some rare cases).
A
Good
morning,
good
afternoon,
good
evening,
hello,
everyone
and
welcome
to
another
episode
of
the
developer
experience
office
hours
where
we
are
featuring
things
from
the
future.
So
with
that
I'd
like
to
put
in
just
a
quick
disclaimer
that
things
that
you
see
on
this
show
today
may
or
may
not
land
in
the
product.
At
the
certain
version
we
say
so
this
is
all
kind
of
future
stuff.
But
we'll
talk
about
that
and
disclaim
as
appropriate
in
in
the
features
we
discussed.
A
A
B
B
C
A
D
Ryan,
hey
ryan
jarvanine.
You
can
find
me
most
places
online
as
ryan
j.
I'm
here
from
the
shift,
developer,
advocate
team
and
I'll
be
helping
out
answering
questions
in
chat
feel
free
to
send
them
to
me.
Let
us
know
what
you're
thinking
and
hit
us
up
with
questions
topics
for
the
future
and
I'd
be
happy
to
help.
D
B
All
right,
thank
you.
So,
let's
see
the
first
thing
that
we're
going
to
talk
about
is
visibility
of
applications
across
environments
which
is
available
in
four
six.
It's
a
dev
preview
feature
we're
going
to
do
a
quick
demo
and
we
have
a
cluster
kind
of
already
set
up.
That
shubik
is
going
to
explain
how
that
configuration
was
done
and
we'll
kind
of
look
through
some
things
here
in
openshift.
B
A
B
B
Here
you
do
have
an
applications,
application
stages,
tab
or
item
in
the
navigation,
where
I
can
see
the
numerous
applications
I
have
access
to
that
have
been
configured,
and
I
can
see
that
the
name
of
the
application,
this
one
is
app
taxi
and
how
many
environments
that
it's
that
it
it's
on
and
if
I
click
into
that,
I
can
see
a
detailed
view
of
that
application
and
when
it
comes
up,
it
shows
me
that
it's
running
in
three
different
environments-
one
is
dev.
One
is
prod.
B
One
is
stage,
it
shows
me
the
last
time
these
environments
were
actually
updated
with
a
little
label
on
the
top
and
then
gives
me
some
additional
information.
But
before
we
go
into
any
more
detail,
I'm
going
to
pass
it
over
to
shubik.
So
he
can
explain
how
this
configuration
occurs
or
how
you
can
do
it
on
your
own
clusters.
C
C
C
Repo
and
the
donuts
at
the
bottom
are
effectively
the
state
of
your
workloads,
which
can
be
mapped
to
what's
the
expected
state
in
the
git
repository,
so
we'll
quickly
go
over
to
figure
out
what
really
powers
these
this
behind
the
scenes
from
a
kit
from
a
git
ops
perspective.
What
exactly
do
you
need
to
do
so
that
you
know
you
get
this
visualization?
C
So
we
have
a
new
project
called
the
get
ops
application
manager,
it's
a
cli
which
helps
you
set
up
your
githubs
repository
with
both
ci
and
cd
built
into
it.
When
I
say
ci,
I
effectively
mean
that
if
you're
managing
your
manifests
for
different
environments
on
git,
you
would
want
to
make
a
pr
to
them,
ensure
that
everything
works
fine
and
then
merge
it.
Now
to
ensure
everything
works.
Fine,
some
pipelines
would
have
to
be
run
in
this
case.
It
automatically
bootstraps.
Your
github's
manifests
with
takedown
pipelines.
C
Without
you
having
to
choose
that
or
make
a
decision
about
that
or
even
think
about
it,
and
then
once
you
merge
it,
it
gets
step
it
gets
deployed
on
your
cluster
using
argo
cd.
Now
all
that's
abstracted
out
from
you,
because
let's
say
you
just
want
to
deploy
something
called
an
app
taxi
in
three
environments
and
you
you
know
what
your
deployment
manifest
looks
like,
etc,
and
you
just
want
to
manage
that
on
git
and
ensure
that
it
keeps
getting
synced
to
your
cluster.
C
C
This
is
the
url
to
reach
it
too,
and
then
here's
my
token,
if
needed,
to
be
able
to
make
calls
to
that
git
repository
and
you're
good,
and
you
see
that
view
in
there.
So
right
now,
as
a
day
on
operations,
there
are
a
few
things
that
you
know
you
would
typically
do
in
any
github
scenario
like,
for
example,
I'm
a
team
lead.
I've
got
a
new
application.
I've
enjoyed
applying
it,
and
I
want
this
to
be
deployed
across
three
environments,
so
you
would
effectively
need
your
manifests
to
be
deployed
using
argo
cd.
C
You
would
need
those
manifests
controlled
in
your
git,
using
pipelines
so
that
somebody
doesn't
enter
a
paragraph
of
some
jargon
and
commit
that
yaml
into
git.
That
has
to
go
through
pipelines
and
it
has
to
be
validated
and,
of
course,
if
you're
managing
secrets
on
git,
you
better
have
them
encrypted.
C
So
this
effectively
uses
sealed
secrets
behind
the
scenes.
Without
you
caring
about
it
much
so
yeah
and
that's
pretty
much
it
it.
It
has
a
very
simplistic
manifest
of
how
to
have
a
single
ammo
define
where's
your
environment,
where's
your
service,
you
could
add
new
services
to
an
environment,
you
could
add
new
environments
and
add
new
services
to
it.
If
you
want,
and
at
the
end
of
it,
everything
gets
automatically
synced
into
the
clusters
that
have
been
configured
with.
C
Argo
cd
out
of
the
box,
and
now,
if
you'd,
want
to
come
back
to
openshift
console
and
there
see
how
the
view
of
it
looks
like
we
provide
you,
this
multi-environment
view
for
all
your
different
applications.
So,
let's
say
you've
chosen
to
use
the
get
ops
application
manager
to
bootstrap
the
app
taxi
app
across
three
environments.
C
C
Give
me
a
visualization
of
what
the
expected
state
is
and
what
the
workloads
look
like
right
now
and
that's
what
this
page
does
for
you.
There
are
a
few
improvements
that
that
are
that
will
happen
on
an
iterative
basis,
which
is
you
should
be
able
to
see,
which
is
the
latest
commit
that
powers.
This
current
deployment,
you
should
be
able
to
see
which
clusters
your
stuff
is
deployed
on.
So,
if
you
know,
argo
city
or
general
tops
practices,
you
could
have
your
application
deployed.
C
On
the
same
cluster
on
multiple
different
clusters,
it
could
be
an
openshift
cluster,
it
could
be
on
and
amazon
kubernetes
cluster
it
could
be
anywhere
you
want
it
to
be.
The
goal
is
that
this
view
lets
you
visualize
the
whole
thing
in
a
single
page
setup,
while
behind
the
scenes
a
lot
is
happening.
B
A
C
C
E
E
C
The
version
number
would
tell
you
that
it's
not
a
major
release
yet
so,
which
means
this
is
still
in
dev
preview,
but
we
already
have
some
friendly
customers
who
are
trying
this
out
on
a
daily
basis.
So
this
is
not
something
that's
going
to
break
every
week.
This
is
something
we
just
want
to
take
it
through
a
good
maturity
staircase,
so
that
we
get
enough
feedback
and
at
the
same
time,
we
do
the
right
thing
that
addresses
problems
of
our
customers.
C
C
E
C
We
are
basically
working
on
making
those
hey
if
it's.
If
route
api
is
not
available
on
your
cluster,
just
use
an
ingress,
and
it's
very
fine.
So
I
think
those
are
the
primary
things
but
other
than
that
in
principle
and
in
design.
This
should
work
on
both
only
like
kubernetes,
as
well
as
openshift
awesome
good
to
hear.
A
Cool
and
yes,
the
the
office
hours
broadcast,
is
open
for
questions
and
answers.
So
if
you
have
them
feel
free
to
fire
away
with
whatever
you
know
open
shift
rel
whatever
you
want
right,
like
ansible,
you
name
it,
I'm
answerable
and
rail.
Certified
we've
got
openshift
people
everywhere.
You
know
so
like
fire
away.
Unless
it's
something
that
we've
not
touched
lately,
we'll
probably
get
you
an
answer
to
it
on
the
show.
A
B
C
C
What's
there
behind
the
scenes,
so
there
there
are
a
few
things
that
powered
this
today,
and
this
is
not
super.
This
is
not
super
indicative,
but
I'll
go
over
that
so
you'll
need
argo
cd
to
be
running
on
your
cluster.
It
could
be
through
an
operator
or
it
could
be
without
an
operator.
It
doesn't
matter,
but,
of
course,
from
a
red
hat
support
perspective,
it
will
be
with
an
operator.
C
Like
I
said,
if
you
don't
like
the
operator,
you
just
want
to
take
the
upstream
argo
cd
and
run
it
even
that's
fine.
You
need
tekton,
because
the
kit
ops
repositories,
which
holds
your
manifests,
it
has
pipelines
and
built
into
it,
and
we
use
tekton
or
openshift
pipelines
for
that
now,
there's
also
something
called
github
service
operator,
which
is
a
bit
of
a
bit
of
a
meta
operator.
C
C
C
A
B
B
B
Yeah,
and
so
you
can,
you
can
quickly
get
in
if
you
want
to
see
status
if
there's
something
wrong
or
whatever
you
can
see
some
status
there.
So
that
is
one
of
the
changes
that
will
be
coming
in
z
stream,
one.
The
other
thing
is:
if
your
application
has
multiple
deployments
deployment,
configs
in
it,
etc,
you
would
be
seeing
those
in
the
inside
of
this
column.
B
C
B
A
B
B
A
A
A
A
D
B
B
A
Eyes
off
for
a
second
and
oh,
my
gosh,
all
right
so
head
low,
okay,
dang,
there's
a
lot
of
chat.
I
just
missed
my
bad
y'all.
Sorry,
let's
see
yes!
Yes!
Yes!
Yes,
yes,
out
of
curiosity!
Okay,
so
is
promoting
from
different
clusters,
easy
to
set
up
in
tech
tom,
promoting
from
different
clusters.
So,
like
this
build
is
good
and
in
staging
I'm
assuming
how
do
you
normally
manage
applications
in
ocp
on
a
project
level?.
A
C
Some
of
the
other
things
that
we
encourage
generally
compared
to
that
is
that
tech
town
shouldn't
itself
go
and
deploy
things
in
a
different
environment.
Rather,
if
we
had
to
have
takedown
do
a
promotion,
it
should
make
a
pr
to
the
manifests
of
the
other
environment
and
that
could
either
become
an
automatic
merge
but
effectively.
What
I'm
saying
is
the
deployment
should
always
be
reflected
from
the
git
repository
not
directly
through
the
pipelines.
C
A
Okay,
cool
next
question.
Definitely
this
is
not
related
to
get
ups,
but
this
is
office
hours.
So
here
we
are.
I
have
a
cluster
deployed
connected
to
an
ad
provider.
I
then
added
a
group
called
paths
from
ad
and,
as
a
member
of
that
group,
I
can
log
in
then
on
ad
I
added
a
group
called
container
dev
nested
under
the
paths
group,
so
container
dev
under
paths
added
container
dev
to
the
ocp
cluster,
with
the
edit
role.
A
Ocp
has
sync
to
ad
and
shows
the
users,
but
they
get
access
denied
when
they
try
to
log
in
where
should
I
start
looking
for
problems,
so
that
kind
of
depends
how
you're
setting
up
the
provider
in
ad?
You
would
want
to
look
at
those
logs
first
to
see
what
it's
saying,
because
something
if
the
users
are
there
and
they're,
not
logging
in
there's,
probably
some
other
r
back
thing.
That's
not
toggled
on
potentially
is
what
I'm
thinking.
So
there
might
be
an
error
in
that
log
from
the
provider.
I
would
imagine.
A
C
Yeah,
I
think
in
general.
The
thing
that
that
would
try
at
first
is:
could
the
admin
impersonate
another
user
and
use
the
cli
called?
Can
I
or
so
so,
there's
a
cli
option
we
have
like?
Can
I
edit
pods?
Can
I
see
pods,
etc?
I
think
that
that's
the
first
thing
I
I
would
try
to
do
as
a
cube
admin
impersonated
as
one
of
those
users
and
see.
C
C
A
Oh,
my
gosh,
okay,
so
is
it?
Oh
all,
right
miranda's
got
a
long
question
here
for
me
no
big
deal.
I
tried
out
istio
service
mesh
with
k-native
using
istio
as
a
network
layer
instead
of
glue
or
contour.
So
all
the
pods
have
three
containers
any
time
when
hitting
the
k
service
endpoint.
So
can
you
have
it
in
here?
A
A
C
I
mean
from
a
wall
perspective
it
works.
The
thing
about
sealed
secrets
is
that
it
has
a
more
controller
based
model
of
rewriting
of
secrets
in
a
different
way,
while
they're
represented
as
secrets,
whereas
I
think
walt,
on
the
other
hand,
basically
takes
the
encrypted
at
rest
and
projects
it
into
your
application
whenever
needed.
C
So
you
I,
I
think,
with
the
vault
the
vault
implementation
that
has
been
put
on
chat,
you
aren't
truly
storing
your
secret
on
git
to
be
honest,
you're,
storing
it
in
a
slightly
different
place,
whereas
compared
to
sealed
secrets
there
is
a
representation
of
the
secret
on
git.
So
from
a
github's
perspective.
C
E
A
It
really
depends
on
the
application
like
do
you
want
to
have
you
know
four
containers
per
pod,
or
do
you
want
to
just
use
sealed
secrets
right,
like
okay,
so
narrative
just
put
in
so
for
clarification?
The
containers
here
are
one
is
for
the
app
one
is
for
the
k
native
servers.
One
is
for
the
service
mesh,
so
you
would
have
another
one
for
I
think,
a
site
car
that.
A
B
There
is
the
responsive
nature
to
this,
so
if
there
is
a
fourth,
you
can
actually
see
it.
If
there's
more
than
four
you'll
get
a
horizontal
scroll
and
just
remember
everybody
that
it's
not
the
best
user
experience.
But
if
you
run
out
of
real
estate,
you
can
always
hide
the
menu
right.
So,
if
you're
sitting
an
application,
if
this
is
a
view
that
you
want
to
be
sitting
in
and
working
in
for
a
long
time,
you
can
always
click
on
that
hamburger,
menu
and
and
get
more
real
estate.
B
That
way,
but
I
did
also
add
a
little
question
there
just
curious
on:
what's
the
typical
number
of
environments,
people
are
working
with,
and
then
what
do
you
top
out
at
because
that
would
be
good
for
us
to
know
and
to
bring
back
to
our
ux
team
so
that
we
can
redesign
this
view
appropriately
as
needed
based
on
the
requirements
that
we
have
and
again
that's.
One
of
the
reasons
we're
putting
stuff
out
is
dev
preview
right.
B
A
And
I
I
can't
say,
screen
names
that
well
so
forgive
me
the
live
gas.
We,
however,
you
say
dell
like
whatever.
Should
you
put
everything
in
one
project?
I
think,
is
the
question
right
like
do
you
put
the
front
end
in
a
project?
Do
you
put
the
back
end
on
a
project?
Do
you
put
the
dv
in
a
project?
Do
you
put
it
all
in
one
project?
It's
really
like.
A
If
you
have
multiple
apps,
I
would
encourage
you
to
put
all
the
application
components
in
a
single
project,
but
if
you
have
like
a
huge
database
cluster
right
like
and
you
want
to
use
that
one
big
database
for
everything
that
should
live
in
its
own
project
right
and
then
you
should
have
ingresses
or
routes
to
interface
with
it
and
and
there's.
It
really
depends
on
your
application
model.
How
you
want
to
build
out
those
best
practices.
In
my
opinion,
if
you
have
like
most
people,
multiple
small
apps
do
multiple
small
projects.
C
A
A
B
Awesome
all
right,
so
this
is
just
super
quick
talking
about
again
what
we
are
going
again
so
post
four
six.
We
are
looking
at
changing
some
things
in
the
view
that
we
just
showed
you
one
of
the
things
that
we're
talking
about
doing
is
changing
the
name
from
application
stages
to
actually
application
environments,
because
it's
really
your
application
across
environments.
B
There's
some
history
as
to
why
we
didn't
do
that
in
the
admin
console
and
in
some
of
our
detail
pages
today,
there's
a
tab
called
environments.
We
didn't
want
to
include
this
as
application
environments
from
the
get-go
and
have
there
be
a
conflict,
so
we're
going
to
be
renaming
that
and
then
making
this
be
application
environments.
B
So
that's
one
thing:
another
thing
that
we're
going
to
be
doing
and
again
this
is
in
design,
so
I've
stolen
a
whole
bunch
of
mock-ups
from
the
ux
team
and
put
them
into
this
document
so
that
we
could
share
today.
That
doesn't
mean
that
they'll
be
implemented
to
design
right
because
they
might
they're
going
through
reviews.
B
So
there
may
be
some
small
tweaks,
but
one
of
the
thoughts
here
is
that
there'd
be
a
link
up
here
that
says
argo
cd
and
that
will
actually
bring
you
to
the
argo
cd
ui,
where
you
would
be
able
to
go
to
the
dashboard
and
see
all
of
your
applications
so
schubeck.
I
don't
know
if
you
want
to
add
any
more
detail
there.
C
Yeah,
I
think
nothing
more
from
my
site.
I
think
so.
The
goal
here
is
that,
from
an
argo
city
perspective,
we
don't
want
to
show
everything,
as
is
here.
This
provides
a
multi-environment
view,
but
argo
city
has
an
amazing
experience
as
well.
So
if
you're
fond
of
that,
you
should
totally
go
there
and
to
do
things
with
with
the
arab
city
experience,
but
we
are
totally
compatible
with
that
and
we
complement
the
experience
there.
So
yeah
back
to
yours
right
now,.
B
So
those
are
some
things
that
we're
looking
at
there
in
post
four
six.
I
am
now
going
to
just
quickly
go
back
to
the
beginning
of
my
presentation
and
okay.
So
here
we
go
we're
going
back
to.
I
put
this
picture
for
future
right,
so
everything
we're
talking
about
here
is
what
we
are
looking
at
for
4.7
main
areas
of
focus.
B
So
what's
planned,
not
necessarily
what
will
be
implemented,
as
chris
stated
at
the
beginning
of
the
conversation,
so
some
of
the
things
that
we're
doing
is
I
18
and
support,
so
we're
externalizing,
all
client-side
strings,
and
so
that
works
already
being
in
process
on
both
the
admin
and
and
the
developer
console
side.
So
that
will
be,
I
think,
really
helpful
and
useful
to
get
more
users
more
acclimated
in
seeing
things
in
their
own
language.
The
next
thing
that
we
are
looking
at
is
again
additional
enhancements
to
the
topology
experience.
B
So
one
of
the
things
that
we've
heard
quite
a
bit
about
is
concern
that
when
you
go
and
make
changes
to
your
topology
layout
and
leave
the
view
and
come
back,
we
don't
persist
those.
So
that's
going
to
be
changed.
That
work
is
already
being
it's
in
flight
and
there's
a
couple
of
other
things:
a
quick
ad
from
the
developer,
catalog
and
more
in
context
support.
So
what
I'm
going
to
show
you
now
is
the
designs
for
being
able
to
do
a
quick
ad
from
the
catalog.
So
this
is
the
topology
view.
B
There's
a
new
icon,
that's
going
to
be
on
the
top
left
hand,
corner
might
not
look
exactly
like
that
icon,
but
when
you
click
on
it,
it
will
bring
you
a
search
component
in
the
middle
of
your
page,
and
you
can
start
typing
and
like
so.
If
I
typed
in
django,
it
would
show
me
all
of
the
matches
that
I
have
available
from
the
developer
catalog.
B
It
will
give
me
it
will
give
you
that
preview
right
in
this
right
hand
this
right
hand
section
of
the
modal
as
well.
So
when
you
click
on
either
you
double
click
on
the
entry,
that's
on
the
left,
left-hand
side
or
if
you
click
on
the
button
on
the
right
instead
of
bringing
up
the
right-hand
panel,
it
will
bring
you
directly
to
the
form.
So
again,
this
is
like
just
an
another
mechanism
for
us
to
provide
more
efficiency.
B
C
C
You
have
very
specialized
guidance
about
how
that
app
needs
to
be
deployed
on
openshift,
so
that
guidance
can
live
on
the
dev
file
and
if
you
import
an
application
which
has
that
guidance,
then
this
is
a
flow
that
you
need
to
be
using
and
it
will
then
no
and
and
the
ui
will
not
take
its
own
choices.
Rather
it
will
respect
the
choices,
the
team
leader,
the
developer,
made
and
prescribed
and
had
prescribed
in
their
file,
and
it
would
deploy
according
to
that.
B
B
This
won't
be
so
we
are
going
to
allow
cluster
admins
to
be
able
to
remove
or
add
subcategories
and
categories
that
will
be
part
of
their
categorization
in
the
developer
catalog.
There
won't
be
a
ui
per
se
to
do
to
do
this,
but
we
are
going
to
provide
a
mechanism
to
do
that.
So
I
think
we've
got
a
number
of
requests
there,
so
that
that
should
make
people
happy.
B
Another
piece
that
we
are
going
to
be
doing
is
we
already
do
allow
users
to
or
an
admin
to
add
additional
helm
chart
repositories,
but
what
we're
going
to
be
doing
is,
if
you
remove
all
of
the
helm,
chart
crs
the
helm,
chart
c
repo
crs.
What
we'll
do
is
automatically
hide
helm
from
the
console.
So
these
three
areas,
where
you
see
the
pink
boxes
or
dashed
lines,
if
you
removed
all
of
the
crs
indicating
what
your
helm
chart
repos
were,
then
you
would
not
see
helm
in
the
nav.
B
C
B
In
the
topology
view,
so
yeah
thanks
for
adding
that
another
piece
that
we're
looking
at
is
application
dependency
vulnerabilities,
and
I
know
that
peter
joined
us.
I
think
two
or
three
week
weeks
ago
and
did
a
great
presentation
on
this.
So
again,
this
is
just
showing
that,
on
the
project
details
page,
we
will
have
a
section
that
has
image
vulnerabilities
and
you
can
get
some
details
there
and
you
can
drill
in
and
actually
see
the
vulnerabilities
that
are
associated
with
your
project.
B
So
here's
one
piece
is
that
we're
adding
the
events
tab
on
both
the
task
runs
page
and
the
pipeline
runs
page,
so
those
are
new
tabs
and
something
that
has
is
missing
in
in
all
the
way
up
to
four
six.
So
that's
something
that
we're
looking
at
another
thing
is
allowing
when
you're
looking
at
a
task
run
allowing
easy
access
to
the
pod,
that's
associated
with
it.
B
So
if
you
see
the
screenshot
and
sorry,
this
is
probably
still
too
small,
but
we'd
have
a
link
to
the
pod,
that's
associated
with
the
task
run
and
then
also,
we
also
are
adding
a
logs
page,
a
logs
tab
here
for
the
task
run
so
similarly
to
on
the
pipeline
runs
page.
We
have
a
logs
tab
that
shows
all
the
compilation
of
all
of
the
task
logs
and
stuff
step
logs.
This
is
showing
them
the
logs
associated
for
all
steps
that
are
in
that
task
run.
C
A
A
A
Mean
we
can
yeah
yeah,
so
jp,
like
he's,
he's,
got
a
whole
team
of
developers
that
works
underneath
him
and
he's
kind
of
running
the
the
open
shift
show
by
himself
for
like
a
better
term,
and
you
know,
he's
trying
to
figure
out.
You
know
which
developers
are
determining
which
knobs
the
most
right
like.
Where
should
you
know
effort
be
focused
or
what
features
are
we
using?
That
kind
of
thing,
so
he's
looking
to
try
and
find
a
view
of
like
what
features
are
actively
in
use
in
his
cluster?
A
A
The
developer
console
and
loading
apps
this
way
or
are
they?
You
know
standing
up
routes
and
everything
kind
of
doing
it,
like
all
gluey,
together
kind
of
deal
right
like
what
you
know,
cumulatively,
what
developers
are
using
what
things
to
do?
What
like
he
just
kind
of
wants
this
audit
view
of
everything
going
on
in
this
cluster
right,
and
I
don't.
A
A
A
B
A
B
B
B
Yeah,
I
do
think
it
was
something
that
was
either
added
in
four
five
and
I-
and
I
also
don't
know
if
there's
anybody
on
the
ux
team,
the
admin
ux
team,
that
is
on
chat
or
maybe
even
steve-
speicher.
Possibly,
if
he's
there,
because
I'm
pretty
sure
that
we
did
add
something
on
the
admin
side.
Just
don't
remember
what
it
was
and
if
we
don't
figure
it
out
before
the
end
of
this
call,
we
will
get
back
to
you.
A
B
E
B
A
B
B
B
B
B
A
B
All
right,
so
the
next
piece
is
around
enhancements
of
the
developer
catalog.
So,
as
you
guys
know
today,
when
you
go
to
the
ad
page
there's
you
can
either
get
directly
into
the
developer,
catalog,
where
it
says
from
catalog
or
that
we
have
also,
we
have
individual
catalogs
as
well,
which
are
kind
of
like
a
subset.
B
So
one
of
the
things
that
we're
doing
the
design
work
that's
being
done
and
starting
to
implement
now
is,
if
I
clicked
on
helm,
chart
today
through
this
kind
of
prototype,
what
it
would
do
is.
It
brings
me
into
a
more
prescriptive
view,
just
for
helm,
charts
and
it
ends
up
providing
additional
filters
that
are
specific
to
that
type.
So
now,
when
I'm
in
the
helm
chart
catalog,
I
am
now
able
to
see
if
my
admin
had
configured
multiple
chart.
B
B
So
I
think
that's
you
know
a
nice
feature
that
we're
gonna
have
again.
If
I
go
in
show
what
we're
gonna
do
for
event,
sources
with
event,
sources,
we're
not
going
to
have
categories
on
the
left-hand
side,
it's
going
to
be
a
little
bit
more
simple,
because
we
we
don't
have
the
appropriate
metadata
for
that
when
we're
bringing
in
the
event
sources.
So
in
4.5,
when
you
did
a
creation
of
an
event
source,
it
was
all
through
a
form.
You
saw
little
blocks
or
tiles
at
the
top.
B
That
allowed
you
to
pick
from
like
five
or
ten
pre-defined
event,
sources.
We're
now
going
to
be
supporting
dynamic
event
sources
as
well
as
integration
with
kamlets.
So
we
have
the
potential
that
the
event
source
catalog
could
have
hundreds
of
items
so
we're
moving
towards
a
more
catalog
catalog-based
approach
for
event,
sources
going
forward
and
again
this
is,
if
you
have
openshift
serverless
operator,
installed
a
couple
other
high-level
things
that
we're
going
to
be
doing
that
I
don't
necessarily
have
the
mock-ups
for,
but
just
talking
about
them
is
again
enhancing
the
getting
started
experience.
B
So
we're
going
to
add
usability
enhancements
to
quick
starts,
one
of
them
being
the
ability
to
have
hints.
If
we
tell
you
where
to
click
so
like
if
we
said
click
on
application,
stat
stages,
you
could
click
on
that.
It
would
highlight
the
element
inside
of
inside
the
navigation,
which
will
be
nice
and
again
that's
to
improve
learnability
or
discoverability
for
the
user.
B
We're
going
to
be
providing
a
number
of
new
quick
starts,
as
well
as
providing
an
updated,
updated,
guided
tour
focused
on
four
seven
on
the
developer
side
and
then
we're
also,
you
know,
working
with
the
admin
console
team
to
provide
again
general
console
and
improvements.
I
already
talked
about
internationalization,
we're
removing
the
browser,
local
storage
and
providing
persistent
storage.
B
So,
for
a
lot
of
the
things
that
people
have
mentioned
before,
where,
if
I
change
my
browser,
if
I
change
to
another
machine,
I
know
that
I
got
a
one
customer
site
and
some
people
had
said
that
you
know
they
literally
have
three
machines.
If
they're
working
from
home,
they
have
one,
they
have
a
laptop,
and
you
know
a
desktop,
maybe
at
work.
B
So
the
fact
that
we
had
things
in
local
storage
was
pretty
difficult,
so
this
persistent
storage
should
help,
I
think,
with
the
general
usability
of
the
console,
we're
also
providing
the
quick
start
extension
capability,
which
I
know
that
we
myself
and
ollie
have
talked
about
in
the
last
couple
weeks.
So
I
think
that's
going
to
be
a
great
addition
both
for
operators,
as
well
as
for
cluster
admins
at
on
site.
You
can
add
your
own
quick
starts
and
we're
updating
web
terminal
so
that
you
will.
We
will
provide
support
for
privileged
users.
B
So
right
now,
if
you
are
cluster
admin,
meaning
web
terminal
does
not
work
again.
That
is
dev
preview
currently,
but
when
we
go
ga
we
will
be
supporting
privileged
users
and
cluster
admins,
and
with
that
that
is
the
last
of
what
we're
talking
about
in
four
six
and
then
I'm
of
course,
going
to
plug
our
console
customization
competition
again.
A
So
shubik
you
helped
out
jp
quite
a
bit
there
with
that
command.
Thank
you
for
that
mustafa
from
youtube
says
you
could
write
an
ansible
operator
that
kicked
off
info
when
a
login
logout
happened
to
track
user
usage
yeah.
That's
I
mean
there's
like
a
lot
of
ways
to
figure
this
out
and
do
this
because
the
audit
log
is
there.
A
A
We
being
read
at
engineering,
need
to
engage
on
something
like
that,
since
it
isn't
a
ask
and-
and
I
will
put
the
bug
in
people's
ears-
yes,
thank
you
mustafa
for
their
disclaimer
yeah
needle
on
the
haystack,
exactly
jp,
and
I
think
we've
lost
serena,
somehow
whoops,
oh
well,
but
shubik
you're
still
with
me.
So
I'm
happy
about
that
so
yeah!
I
don't.
A
Even
better
yeah
so
we're
talking
about
like
the
easiest
way
to
spin
up
a
three-note
okd
cluster
and
I'm
going
to
go
to
the
youtube
archive
to
find
that
link
real
quick
but
the
okd
working
group.
They
have
a
mailing
list.
I
would
recommend
asking
there
to
not
just
here,
because
there's
probably
a
bunch
of
people
that
have
already
done
it,
like
probably
with
the
hardware
software
combo
that
you're
trying
to
use
so
like.
A
I
would
highly
recommend
going
to
the
okd
to
io
site
and
jumping
into
that
working
group
and
just
kind
of
asking
like
hey.
How
would
you
do
this
three
node
okd
cluster?
They
will
be
happy
to
answer
that
question
and
I
will
also
find
the
link
deep
in
the
archives,
because
this
was
a
while
ago,
where
craig
robinson
from
east
carolina
university
came
in
and
showed
us
how
he
stood
up
okd
clusters
for
his
university,
but
it
is
way
way
back
and
I've
got
to
go,
find
it.
A
A
If
you
don't
want
to
ask
your
question
publicly
feel
free
to
email.
It
there's.
You
know
right
like
there's
no
such
thing
as
a
wrong
answer.
Who
was
asking
that
ryan
was
asking
that
ryan
check
out
this
link,
and,
let's
see
I
haven't,
received
confirmation
email
after
registering
on
the
contest
rules.
Okay,
yeah
we'll
be
sending
it.
C
B
B
A
A
A
To
moving
to
production,
okay,
fair
enough
wow,
all
right
got.
Some
worker
got
some
windows
projects
there.
Do
you
fun
good
to
know
all
right?
Well,
thank
you,
shubik!
Thank
you!
Serena!
We
got
five
more
minutes.
If
there's
anything
else,
you
want
to
show
off.
Otherwise
you
know
we
can.
You
can
have
the
time.
A
No,
actually,
I
don't.
I
don't
have
anything
in
my
calendar
in
five
minutes.
Sadly,
but
at
one
I
have
a
fun
little
experience
that
you
all
may
want
to
tune
in
for
we're
going
to
be
running
some
cobalt
on
kubernetes,
that's
right,
mainframe
stuff
in
kubernetes
bringing
the
two
worlds
together,
so
yeah,
jj,
ashgar
from
ibm,
will
be
joining
us
and
we
will
have
a
wonderful
discussion
about
cobalt
on
kubernetes.
So
yeah
so
see
you
in
an
hour
folks-
and
thank
you
all
for
tuning
in.