►
Description
Did you know you can customize the OpenShift web console? In today's stream, Senior Principal Software Sam Padgett and Senior Principal Product Manager Ali Mobrem join to help us inspect the OpenShift web console, looking at all the features and functions within. We'll also look at web console extensions, where you can customize the web console by running a script and loading custom stylesheets when the console loads. Extension scripts allow you to override the default behavior of the web console and customize it for your needs. So why would anyone want to use the web console and run custom extension scripts? What value does it offer? Maybe you want to change the colors of your OpenShift console from red to chartreuse? Or possibly disable certain features or preferences? Or even use it as a backend for a different deployment tool. We'll answer all of your questions, as well as any more you may have, so please join us as we dive into the OpenShift web console.
Learn more:
https://docs.openshift.com/container-platform/4.9/web_console/customizing-the-web-console.html
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Chris Short sit down to answer your questions about Red Hat OpenShift.
Follow us:
Andrew Sullivan, https://twitter.com/practicalandrew
Jonathan Rickard, https://twitter.com/jrocktx1
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
Openshift.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk
#RedHat #OpenShift #ContainerPlatform
B
Well,
hello
and
good
morning,
good
afternoon,
good
evening,
wherever
you
may
be,
and
welcome
to
this
week's
ask
an
openshift
admin
live
stream.
So
thank
you
very
much
to
everybody
who
is
joining
me
today.
Hopefully
you're
all
able
to
hear
me.
Well,
I
hope
everybody
is
safe
out
there
and
today
is
exciting
for
a
number
of
different
reasons.
B
So,
first,
this
is
the
the
first,
the
first
stream
we've
had
in
two
weeks.
That
always
makes
it
a
good
day,
but
second
you'll
notice
that
I
was
only
without
you
know.
I
was
only
by
myself
for
really
one
stream.
I've
got
two
guests
with
me
today
to
talk
about
our
topic.
If
you're
paying
attention
to
our
our
titles
here,
that's
gonna
be
console,
features
console
customization,
something
that
I
know
a
lot
of
folks
are
interested
in,
but
you
also
notice
a
third
face
there
and
that
is
johnny.
B
B
C
Awesome
thanks
andrew
yep,
so
I'm
johnny
rickard,
I
I've
been
in
the
it
industry
for
over
22
years,
I've
pretty
much
been
a
linux
unix
nerd.
Since
the
beginning,
I've
been
at
red
hat
for
the
last
five
and
a
half
years
working
in
consulting.
I
was
a
senior
architect
and
I
just
recently
transitioned
over
to
engineering
as
a
special
projects.
Engineer
so
got
a
lot
of
history
with
sysadmin
and
system
engineering
and
now
hopefully
going
to
get
to
dive
into
more
of
the
day.
Two
you
know
and
beyond
operations
at
openshift.
B
C
B
Well,
I'm
I'm
really
happy
to
have
you
join
and
I
know
when
we
were
talking
about
this
beforehand.
You
know
I
I
was
saying
how
you
know
you've
been
in
consulting
for
the
last.
I
think
you
said
five
years
or
something
like
that.
So
you're,
like
you,
have
been
in
the
trenches,
hands-on.
You
know
implementing
working
with
folks.
You
know
who
are
doing
openshift
day-to-day.
So
it's
not
just
the
the
pre-sales
where
we
come
in
and
tell
you
all
the
fancy
things
that
it
can
do.
C
Yeah
absolutely-
and
you
know,
like
a
big
thing-
that
we
talk
about
when
we're
going
into
consulting,
is
like
the
pre-sale
stuff
is
all
about
like
the
the
art
of
the
possible
and
we're
really
there
for
the
art
of
production
right
like
we're
trying
to
get
you
into
production.
So
that
way,
you
can
run
your
workloads
and
everything
on
your
clusters.
B
B
You
know
for
for
a
long
time
or
for
a
long
time
you
and
I
were
we
were
effectively
peers
in
a
previous
life
right
a
couple
of
jobs
ago.
We
just
were
at
different
sites
within
the
same
organization
and
it
was
a
lot
of
fun.
I
always
liked
coming
out
to
texas
and
and
getting
to
visit,
and
you
know
eating
lots
of
barbecue,
because
that's
what
you
do
in
texas,
that's
what
you.
B
C
C
B
A
Sure
thank
you
for
having
us
today
so
name's
ali
mober.
I
am
the
product
manager
for
the
openshift
console.
I've
been
with
red
hat
for
the
last
three
years,
and
I'm
very
very
excited
to
be
here
today,
because
we're
going
to
show
you
some
really
really
cool
stuff
that
we've
had
in
the
works
and
in
order
to
do
that,
I
brought
our
lead
architect,
sam
padgett,
with
us.
So
sam.
You
want
to
introduce
yourself,
hey.
D
B
D
B
B
I've
been
wanting
to
do
this
stream
for
like
a
year,
and
it's
been
one
of
those
like
you
know,
yeah,
but
just
just
wait
like
yeah
there's
a
lot
of
we're
working
on
some
really
cool
stuff,
just
wait,
because
the
the
historical
set
of
things
that
were
capable
or
possible
while
goods
there's
so
many
exciting
things
that
are
getting
ready
to
happen.
So
I'm
very
happy
that
we
are
finally
able
to
have
the
stream
and
to
talk
about
these
things
so
before
we
get
to
that.
B
B
But
this
is
one
of
our
office
hours
series
of
streams
here
on
red
hat,
live
streaming.
What
that
means
is
that
we
are
here
for
you
for
our
audience,
so
any
questions
that
you
have
any
things
that
are
top
of
your
mind.
Anything
you'd
like
to
talk
about.
Please
put
that
into
chat,
so
whatever
platform
you're
watching
us
on
whether
it's
youtube
or
twitch,
or
whether
you're
on
your
phone
or
whether
you're
at
your
desk,
put
it
in
the
chat.
B
So
we
we
use
fancy
software
here
called
restream,
it'll
it'll
make
sure
it
goes
across
all
of
those
and
our
producer.
In
the
background,
our
silent
advocate
here
stephanie.
She
makes
sure
that
we
see
all
of
those
that
we
address
as
many
of
those
as
possible.
So
thank
you
stephanie
for
working
diligently
in
the
background
to
keep
us
on
track
and
in
mind,
so
the
ask
an
openshift
admin
stream
we
like
to-
or
I
you
know,
I
guess,
because
I'm
the
only
one
who's
been
here
for
more
than
one
stream
right.
B
So
I
like
to
focus
on
a
couple
of
things
up
front,
and
that
is
what
I
call
the
top
of
mind
topics.
These
are
effectively
things
that
have
happened
that
I
feel
like
you,
our
administrator
audience
should
be
aware
of,
or
should
be,
might
be
important
to
you.
It's
not
everything
in
the
whole
world
right.
I
actually
had
a
chat
with
somebody
about
creating
a
newsletter
for
such
things,
but
hopefully
it's
some
things
that
help
you
do
your
job
better.
B
So
the
first
thing
that
I
want
to
talk
about
is
to
what
sam
was
saying
a
moment
ago.
Openshift,
as
a
team
has
gotten
massive,
and
you
know
you
would
expect
this
as
openshift
has
continued
to
grow
in
popularity.
You
know
ali
over
on
the
pm
team.
When
I
joined
three
years
ago,
I
think
I
was
the
third
tech
marketing
person
and
there
was
roughly
20
pms
at
the
time
and
now
we're
up
to
it's
close
to
60
pms.
B
You
know
the
tech
marketing
team
is
now
close
to
20..
You
know
it's
just
grown
in
leaps
and
bounds
and
the
reason
why
I
bring
that
up
is
because
well
it's
continuing
to
do
so.
So
there
is
a
number
of
positions
that
are
opening
on
the
product
management
team,
so
I
saw
kirsten
newcomber
posted.
I
think
it
was
four
security-centric
product
management
roles
the
other
day
there
is,
I
think,
five
or
six
tech
marketing
positions
that
are
open
on
my
team.
B
So
if
you
go
to
you
know
the
the
red
hat
careers
page
you
search
for
that
product
management
for
that
tech
marketing.
Any
of
those
things
please,
if
you,
if
you
have
any
interest
in
joining
us
and
working
on
openshift
and
and
doing
all
the
great
things
that
we
do
we'd
love
to
see
your
application
come
in
and
you
know
hopefully
someday.
We
can
work
together.
B
B
B
So
the
fix
is
in
open
shift,
4.8.16
and
later
and
4.7.25
26,
whatever
whatever
it
was.
However,
that
release
was
not
promoted
from
candidate
into
fast
or
stable.
So
what
that
ultimately
means
is
that
well
updates
from
4.7
to
4.8
are
still
blocked,
so
you
can
use
the
fast
channel.
I
believe
that
there
is
a
fast
channel.
Let's
see
am
I
logged
in
here.
B
I
am
not
so
I
will
have
to
I'll
log
in
while
we're
off
screen
but
anyways.
If
you,
if
you
were
to
look
inside
of
the
channels
essentially
4.8.15,
is
the
current
stable
release.
I
think
it's
4.8.17
is
in
fast
and
candidate,
if
I
remember
correctly,
so
it
hasn't
been
promoted
to
stable.
So
if
you
just
if
you're
using
stable
channel
move
over
to
fast,
if
you
think
that
that's
bug
doesn't
affect
you
and
if
we
click
on
the
bug
here,
this
should
take
us
to
so.
B
B
So
the
next
thing
that
I
wanted
to
talk
about
is
regarding
the
one
of
the
things
that
we
talked
about.
Last
week
with
the
or
excuse
me
two
weeks
ago,
with
the
what's
new
in
openshift
4.9,
so
a
couple
of
things
came
up
with
that,
so
the
first
one
was
I
talked
about.
We
showed
deploying
single
node
openshift,
utilizing
there
we
go
so
we
talked
about
deploying
single
node
openshift.
I
used
the
cli
to
do
that.
B
I
actually
showed
it
in
a
virtual
machine
and
one
of
our
pms
reached
out
to
me
to
point
out
that,
even
though
it
technically
works
in
a
virtual
machine,
it's
really
only
fully
supported
right
now
with
physical
servers.
So
just
please
be
aware
of
that.
If
you
want
to
test
it,
if
you
want
to
work
with
it,
inside
of
virtual
machines,
vmware,
rev,
etc,
should
work
just
keep
in
mind
that
it
is
only
fully
supported
with
physical
servers.
B
So
this
time
is
on
your
side
article.
So
in
this
blog
post,
mike
barrett
talks
about
how,
as
of
openshift
4.8,
essentially
all
of
our
releases
will
be
supported
for
the
same
period
of
time.
If
we
scroll
down
to
this
graphic,
this
graphic
shows
basically
18
months
for
each
release
going
forward.
So
one
thing
about
this,
I
definitely
want
to
highlight
that
this
dates
are
estimated.
This
is
not
a
road
map.
This
is
not
a
promise
of
specific
versions
of
specific
times
or
anything
like
that.
B
This
is
just
for
illustrative
purposes
of
that
18-month
timeline,
so
I
just
definitely
want
to
eliminate
any
confusion
there,
but
the
difference
between
a
an
eus
and
a
non-eos
release
going
forward
is
effectively
the
update
process
associated
with
it.
So
if
all
releases
are
supported
for
18
months,
the
difference
between
eos
and
non-us
is
that
from,
for
example,
4.8
to
4.10
you'll
be
able
to
do
an
accelerated
update
where
effectively
it
pauses.
B
So,
unfortunately,
that
does
not
apply
with
4.6
and
4.6
us,
so
4.6
non-eos
is
currently
out
of
supports
with
the
release
of
4.9
but
4.60
us
in
order
to
get
to
4.8.
You
do
need
to
do
a
sequential
update,
so
just
follow
the
normal
update
procedure
so
4.6
to
4.7
to
4.8
and
then
in
the
future
when
4.10
ships
you
would
then
have
that
accelerated
update
process
available.
B
So
a
bit
of
disappointing
news.
I
think
I
mentioned
that
last
week
that
I
would
find
out
the
answer
to
that,
because
a
couple
of
folks
have
been
asking
so
yeah.
I
I
wish
that
we
could
do
it
before
that,
but
it
turns
out
there's
a
lot
of
technology
in
the
background
that
they're
that
they're
using
they
actually
backported
some
of
that
from
what
I
understand
from
4.10
all
the
way
to
4.8.
B
To
make
all
of
that
happen,
I'm
an
rhte
interviewing
for
a
container
infrastructure
consultant
consultant
position,
any
tips.
So
congratulations,
you
know
get
getting
past
all
of
the
hr
stuff.
These
days
alone
is,
is
a
a
pretty
impressive
feat
in
getting
to
that
point
so
johnny
I
I've.
I've
not
worked
for
red
hat
consulting,
so
I
don't
know
if
you
have
any
thoughts
on
that.
C
C
You
know
kind
of
take
into
consideration
some
of
the
things
that
you've
done
as
far
as
designing
or
when
you're
talking
to
a
customer
about
implementing
a
solution
that
you
maybe
need
a
whiteboard
and
kind
of
go
and
get
permission
from
them
on
something
like
that.
So
those
are
probably
the
key
areas
to
focus
on.
It's
awesome
that
you
have
your
rhce.
That's
that's,
definitely
a
good!
It's
a
big
bump
for
me.
If
I
were
to
be
interviewing
you,
I
would
take
that
into
like
massive
consideration.
C
So
congratulations
on
that
like
andrew
said,
but
yeah
just
just
be
honest
about
your
experience.
You
know
know
what
you
don't
know
and
be
don't
be
afraid
to
say
that
you
don't
know
something.
You
know
because
there's
no
expectation
that
you're
going
to
know
everything
so
just
go
in
and
have
fun
with
it.
B
Yeah,
it's
it's
funny.
You
say
that
when
I
used
to
interview
folks
back
when
I
was
a
customer
back
when
johnny
and
I
worked
together,
I
would
interview
the
linux
and
unix
admins
and
my
my
approach
is
always
I'm
gonna
ask
you
like
the
most
esoteric
crazy,
unknown
things
possible,
not
because
I
want
to
test
your
knowledge
of
of
you
know
unix
or
linux,
but
because
I
want
to
know
that
you
understand
how
to
find
the
answer.
B
Like,
oh
well,
I'd
start
by
looking
at
the
man
page
for
this
or
oh,
I
would
go
and
search
for
this
inside
of
the
help
files
or
whatever
it
happens,
to
be.
There's
there's
just
too
much
when
it
comes
to.
You
know
whether
it's
linux,
whether
it's
openshift,
whether
it's
kubernetes
for
anybody
to
know
everything
I
also
when
I
started
working
for
a
vendor.
It
was
funny
because
so
I
worked
for
a
storage
vendor
and
I
was
a
virtualization
expert
and
it's
one
of
those.
B
Well,
I
can
teach
you
the
storage,
but
I
cause
that's
what
we
do
like
we're
a
storage
company.
So
we
can
teach
you
our
own
product,
but
I
can't
teach
you
the
other.
You
know
our
partner's
product
so
still
4.6
still
a
few
months
until
4.6
goes
end
of
life.
Yes,
I
think
there
is
a
brief
overlap
period
there,
but
yeah
for
a
4.6
non
eus.
It
is
it
the
the
end
is
nigh
if
you
will.
B
So
that's,
that's
really
all
I've
got
for
today.
So
I
don't
have
any
other
top
of
mind
topics,
anything
that
we
really
need
to
address.
So
hello
khalid,
thank
you
for
for
joining
us
again
this
week.
So
with
that,
let's
talk
about
the
console
and
customizing
the
openshift
console,
and
it's
funny
that
we
we
talked
about
this
this
week
so
over
in
the
kubernetes
slack
channel.
Somebody
asked
me
like
monday,
like
oh
yeah,
how
do
you
you
know?
Two
weeks
ago
we
had
talked
about?
B
How
can
I
identify
which
cluster
I'm
looking
at,
which
cluster
I'm
using?
You
know
quickly
and
easily,
and
you
know
I
suggested
just
a
console
banner.
You
know
something
very
simple,
very
easy
and-
and
somebody
asked
me
about
that
in
in
slack
the
other
day-
and
I
was
oh
yeah-
very,
very
good
timing-
excellent,
oh
jamie
yeah,
you
might
have
been
the
one
to
ask,
or
I
know
you
were
definitely
in
that
in
that
thread
over
in
slack,
so
so
yeah
ali
sam
console,
customization.
A
So
though
the
openshift
console
is
bringing
this
up.
We've
kind
of
designed
this
thing
to
be
extensible
from
day
one
right,
and
we
had
to
do
this
not
only
for
our
customers,
but
we
had
to
do
it
for
our
internal
teams.
So
the
way
I
look
at
ocd
console
is
kind
of
a
layered
ui
right
and
by
layered
ui,
I
kind
of
mean
we
have
like
serverless
team.
We
have
pipelines
team.
We
have
the
cmv
team,
as
as
our
customers
pick
and
choose
what
technologies
and
what
features
and
capabilities
they
need.
A
The
ui
will
kind
of
grow
with
it
right.
So
it'll
it'll
allow
all
these
third-party
or
not
third-party,
but
all
these
extensions
to
come
in
and
to
really
expand
the
ui
and
give
our
customers
a
great
experience.
So
if
you
got
the
next
slide,
I'm
going
to
talk
about
just
high
level
like
why
we
kind
of
did
this
right
so
number
one.
Is
we
really
wanted
to
empower
our
customers
to
build
a
kubernetes
platform
that
that's
right
for
them
and
that's
a
little
bit?
A
I
talked
about
of
how,
with
bringing
different
features
and
capabilities
on
you
could
expand
your
your
platform
or
you
could
just
have
a
smaller
platform
it
all.
It
all
depends
on
your
needs
right,
so
we
want
to
enable
our
customers
to
come
and
do
that.
So
when
we
built
openshift
platform,
we
a
wanted
to
be
able
to
customize
that,
but
we
also
want
to
give
the
ability
for
our
partners
and
our
customers
to
customize
and
extend
the
platform
themselves.
A
So
if
you
go
to
the
next
slide,
I
will
start
talking
about
the
different
mechanisms.
We
have
to
extend
the
platform
so
just
to
extend
the
the
functionality
we
have
our
operators
in
our
operator
plat
pattern
where
you
come
in
and
install
an
operator,
for
example,
cmd,
and
if
you
enable
cmd
operator
on
your
platform,
you
now
can
run
and
manage
vms
right
within
openshift,
and
with
that
you
could
also
get
ui
that
comes
into
the
console.
A
You
could
natively
from
the
ocp
console,
come
in
and
manage
you
and
run
your
vms,
which
is
fantastic
so,
but
that's
for
our
own
internal
cnd
or
openshift
virtualization
add-on
right.
Not
only
we
wanted
to
allow
that
to
happen,
we
wanted
partners
to
come
in
so,
for
example,
let's
say
a
mongodb
or
a
crunchy
dv
or
whoever
wants
to
come
in.
We
have
the
ability
for
them
to
come
in
and
extend
the
platform
as
well,
which
is
great.
A
A
So
we
not
only
allow
the
own
descriptors
to
come
into
like
add
and
and
improve
the
the
creation
and
update
experiences
of
crds
for
that
that
are
managed
by
that
operator.
But
we
also
allow
open
api
v3
schema
to
auto,
generate
the
the
creation
form
from
the
beginning
as
well.
So
it's
kind
of
you
get
the
you
automatically
get
the
form
with
the
the
schema
and
then
you
add,
the
o
element.
A
Descriptors
and
you'll
get
a
higher
level
nicer
interface
for
that,
and
then
today
the
big
thing
that
we're
gonna
talk
about
is
the
new
console,
dynamic,
plug-ins
and
we'll
do
a
deep
dive
here.
Sam's
gonna
come
in
and
do
a
demo
and
talk
through
kind
of
how
this
has
been
implemented
and
how
users
can
come
in
and
create
their
own
dynamic
plugin.
This
is
really
to
come
in
and
build
a
solution
on
top
of
the
ocp
console,
so
this
is
yeah.
Okay,.
B
Ali
I'm
just
going
to
interrupt
you
briefly,
because
I
want
to
kind
of
review
those
things
that
you
talked
about
so
far
just
very
quickly
and
sam.
I
don't
know
if
you're
intending
to
show
those
or
not.
I
don't
want
to
step
on
your
toes.
I
do
have
a
cluster
where
I
can
walk
through
those
a
little
bit.
D
B
B
B
So
a
couple
of
the
things
that
ali
was
talking
about.
There
is,
for
example,
and
please
correct
me
if
I'm
wrong.
If
we
go
to
you
know
our
installed
operators
here,
you
know
those
llm
descriptors
effectively.
It's
this
set
of
information
here,
where
you
can
look
at
and
see
what
are
the
crds
that
are
managed
by
this.
What
are
the
ones
that
need
to
be
associated
with
it?
This
is
the
package
manifest.
Let's
go
with
both
the
terminal,
the
web
terminal.
B
So
if
we
install
this
guy
so
one
I,
I
know
that
this
is
all
some
fancy
integration.
In
the
background
the
openshift
virtualization
one
I
I
was
looking
at
the
new
one
with
4.9
and
it's
like
they've
integrated
like
a
whole
slew
of
questions
and
config
and
all
kinds
of
other
stuff
into
this
gui.
It's
really
quite
quite
impressive,
but
yeah.
B
B
So
what
I've
got
here
is
just
a
link
to
the
documentation
for
the
customizing,
the
web
console
page.
So
a
couple
of
interesting
things
here.
So
first
with
4.9,
we
talked
about
this
before
you
can
customize
the
routes.
So
if
you
don't
want
to
use,
you
know
this
console
dash
open
shift,
console
blah
blah
blah
route.
A
B
B
A
B
A
B
That's
great,
and
you
can
you
know
you
saw
I
just
clicked
this-
the
schema,
the
console
notification
specification
right.
So
this
is
basically
the
same
thing
as
walking
through
and
doing
like
an
oc,
explain
exactly
everything
that
you
want
to
know.
So,
let's
do
we'll
do
a
red
hat
color
here
and
then
we'll
just
click
create
and
what
we
should
see
almost
immediately
is
our
banner
pop
up
with
a
link
at
the
end
of
it.
It's
just
that
easy
and
I
can
create
another
one.
So
console
notifications
create
this
one.
B
B
A
Let's,
okay,
let's
just
show
maybe
one
more
okay,
one
of
my
favorites.
So
if
you
go
back
to
the
custom
resource
definition,
section
type
in
console
again,
and
so
one
of
my
other
favorite
ones
is-
and
we
have
a
bunch
here,
so
you
got
like
the
cli
download
which
allows
you
to
put
your
own
downloads.
We're
not
gonna
do
that
one,
but
you
can
show
where
that,
where
it
shows
up,
it
would
be
under.
A
A
That's
based
off
k,
native
key
native
has
its
own
command
line.
That
operator
now
actually
installs
a
link
to
the
k
native
cli
right
there
then
and
there.
So
that's
really
cool.
There's
console
quick
start.
So
if
you
want
to
make
your
own
quick
start
yeah,
you
could
do
that
which
is
really
cool
as
well.
If
you
want
to
highlight
that
just
click
the
help
menu
icon
at
the
very
top
I
should
list
out
quick
starts-
is
the
first
item
there
and
here's
a
list
of
all
the
kind
of
quick
starts.
A
A
A
A
I
I
create
that
resource,
and
then
I
tweak
it
to
to
do
what
I
needed
to
do
well,
we're
like
well,
why
do
people
have
to
keep
going
searching
for
it
in
the
web?
Why
not
they've
done
it
once
and
they've
actually
got
it
working?
They
want
the
way
they
want
it.
Why
don't
we
just
allow
them
to
save
it
right
then,
and
there
so
the
next
time
they
come
to
that
resource.
They
have
that
example
available
for
them.
A
A
B
Yeah,
I
I
could
see
this
being
a
very
easy
way
to
add,
like
you
said,
those
common
things
that
that
you
come
up
with
I'm
already
brainstorming
and
all
the
demos
that
I
do
of
just
having
my
my
script
that
goes
through
so
that
way
I
don't
have
to
copy
and
paste,
but
having
a
part
of
my
cluster
setup,
script
go
through
and
add
these
things
in
there.
So
that
way,
when
I'm
doing
a
demo,
I
just
click
the
button
exactly.
A
A
We
so
we
kind
of
glanced
over
this
one
we're
going
to
talk
about
this
minute,
so
we
we
allow
you
to
come
in
and
customize
the
branding
for
for
openshift.
So
here
in
the
screenshots
you
see,
I
just
replaced
the
openshift
logo
with
the
generic
kubernetes
logo.
It
updates
the
masthead
updates
about
page.
You
can
also
come
and
tweak
the
the
login
page
as
well
as
the
error
page
and
input
put
your
own
logos.
There.
A
Next
item
was
the
jumping
around.
The
next
item
was
crds:
well,
the
console
crds,
which
is
what
kind
of
demo
the
notification.
Next,
let's
see
yeah
here
we
go
crds,
and
this
is
when
we
showed
you
could
customize
links,
notifications,
command
lines.
Yaml
samples,
quick
starts
that
now
added
in
there
as
well.
A
So
those
are
all
customizable
and
it's
just
via
yaml.
Right
next
slide
this.
So
this
is
what
andrew
was
about
to
show
with
the
web
terminal
one,
and
this
is
olm
descriptors.
So
when
your
operator
comes
in
and
gets
installed,
your
operator
usually
manages
a
a
bunch
of
custom
resource
definitions.
So,
let's
say
I'll
give
the
example.
I
need
to
create
a
database
instance
now
right.
A
We
will
automatically
generate
the
creation
form
for
that
via
open
api
b3
schema,
but
it's
usually
kind
of
rough
right
because
it
like,
for
example,
if
you're
one
of
the
fields
needs
a
secret
you're
going
to
have
to
type
in
the
secret
as
just
it's
just
a
basic
text
field.
So
we
have
something
called
on
descriptors,
which
will
override
fields
and
one
of
the
the
descriptors
we
have,
for
example,
is
like
the
secret
type
and
we
put
the
secret
type
there.
A
D
D
A
And
with
all
indescriptors,
you
could
do
some
really
cool
things
like
showing
required
fields
hiding
different
fields
that,
unless
like
like,
for
example,
you
might
select.
Oh,
I
need
to
select
a
node
and
if
you
select
node,
then
you
get
a
bunch
of
options
to
say,
okay
and
put
the
name
and
what
so
it
allows
you
to
hide
sections
of
the
form
based
off
of
input
and
again
really
really
improves
the
experience
versus
just
getting
like
every
field
in
the
schema,
which
could
be
really
really
long
and
yeah
and
cumbersome.
A
A
Let
me
start
with
this
history
part
and
then
I'll
hand
it
off
to
sound,
so
dynamic,
plugins
kind
of
came
about,
or
at
least
the
beginning
was
we
had
static,
plug-ins
and
the
reason
we
had
static
plug-ins
is.
I
talked
a
little
bit
about
that.
Layered
ui
approach,
like
you
start
with
the
base
console,
but
you
know
what
now
I
want
to
have
openshift
virtualization
or
I
want
to
have
serverless
capabilities
or
pipelines
or
get
ops.
A
We
wanted
our
our
other
teams
to
be
able
to
come
in
and
contribute
ui
code
and
update
that
experience
and
have
it
be
native
right
in
the
console.
We
didn't
want
someone
to
have
to
go
to
like
some
other
ui
to
do
serverless
or
to
go
manage
their
vms.
We
wanted
them
to
be
able
to
do
it
right
there
natively
in
the
console,
so
we
we
started
with
a
static
plug-in
mechanism.
It
was
our
first
iteration
of
creating
plug-ins.
It
was
only
available
available
to
internal
teams.
A
A
We
could
only
update
the
plugins
with
every
ocp
release.
So,
for
example,
let's
say
openshift
pipelines
is
on
a
faster
release,
cadence
and
they
want
to
update
the
operator
they
weren't
able
to
update
the
ui
with
that
operator.
They
had
to
wait
to
the
next
version
of
ocp
console
to
come
out
to
update
their
ui
with,
so
that
was
one
of
the
issues
that
we
encountered.
A
D
Yeah,
I
I
think
you
you
hit
on
all
the
big
points.
This
was
really
you
know
something
I
mentioned
earlier.
Our
team
has
grown
a
lot
and
we've
got
a
lot
more
ui
developers
contributing
to
consoles.
So
this
was
kind
of
our
first
step
to
allow
more
teams
within
red
hat
to
contribute
right.
So
it's
still
all
through
a
single
mono
repo.
It's
it's
tied
to
a
single
image
with
static
plug-ins.
D
Our
our
long-term
vision
was
always
to
try
to
break
that
out
right.
So
this
is
the
first
step
which
leads
us
to
dynamic,
plug-ins
and
dynamic
plug-ins
in
a
way
are,
are
similar
to
static
plug-ins
like
we.
We
have
the
same
goals
with
them.
It's
really
an
evolution
of
it
right.
So
what
we
wanted
to
be
able
to
do
is
take
what
we
do
with
static
plugins
in
the
in
the
repo
and
and
break
it
out,
so
that
teams
could
work
a
little
more
independently.
They
could
deliver
on
their
own
schedule.
D
D
It's
all
based
on
some
new
features
in
webpack
5
called
module
federation
which
allows
you
to
basically
have
your
own
project
and
build
your
plugin
and
have
everything
dynamically
linked
at
runtime
right.
So
it
doesn't
have
to
be
built
as
part
of
the
console
image
console
will
discover
your
plugin
load
it
and
you
can
dynamically
update
the
ui
and
update
your
plugin
without
needing
to
update
all
of
openshift
right.
D
So
it's
it's
a
nice
evolution.
This
is
still
very
early,
so
it's
still
an
alpha
api,
we're
beginning
to
use
this
internally
for
some
of
our
plugins
there.
You,
if
you
look
on
the
cluster,
there
is
like
a
console,
plug-in
resource,
that's
still
an
alpha
resource.
I
I
do
want
to
caution
that
you
know
we're
kind
of
looking
a
little
ahead
here.
We
want
to
show
you
what's
coming
and
and
show
you
what
will
be
possible.
D
D
D
D
B
D
D
B
B
D
Yeah
yeah,
no
it
it.
It's
really
cool
and
you
know
get
to
them
in
a
moment.
So
you
can
see
it
in
action,
but
the
the
third
piece
is
the
actual
federated
modules.
So
you
will
have
to
write
code
to
make
use
of
dynamic
plugins.
If
you
want
to
make
simple
customizations
the
you
know,
the
crds
and
the
om
descriptors
are
a
good
fit.
You
know
I
just
want
to
add
a
link
somewhere
in
the
ui
or
I
want
to
tweak.
D
D
A
D
Shared
components
that
that
we're
working
to
make
available
so
that
your
ui
is,
you
know
consistent
with
the
rest
of
the
openshift
console.
If
you
reuse
these
components
for
things
like
list
pages,
filter,
toolbars,
details
pages
and
and
those
sorts
of
things
right
so
again,
yeah
you
declare
all
your
extensions,
the
json
manifest.
You
know,
you
can
add
pages
routes.
You
know
catalog
items,
developer,
catalog,
you
know
tabs
to
our
dashboards.
You
know
there
are
literally
dozens
of
places.
D
D
All
right
so
broadly,
this
is
the
the
architecture
so
I'll
work
from
the
bottom
up
here.
So
we
have
the
the
console
core
here,
which
is
really
the
framework
for
running
plug-ins
today
that
also,
I
would
count
like
the
existing
console
pages
as
part
of
the
core,
but
you
know
we're
working
to
split
those
out.
So
eventually
we
want
the
core
just
to
be
almost
all
a
lightweight
framework
for
running
plug-ins
and
then
everything
that
sits
on
top
of
that
runs
as
a
plug-in.
B
D
Yeah,
absolutely,
like
you
know,
long-term
can
vision,
you
know
being
able
to
update
any
of
those
components
independently
and
potentially
separately
from
the
normal
release
cycle.
So
you
could
go
into
like
operator
hub
and
control
when
the
console
itself
updates,
you
know,
versus
you
know,
having
upgrade
the
entire
cluster
to
get
new
console
features
so.
D
Right
absolutely
yeah,
so
console
itself
uses
a
project
called
patternfly.
It's
an
open
source
project
that
has
a
bunch
of
ui
widgets
and
it's
used
throughout
like
the
various
red
hat
web
applications.
You
know,
provides
a
common
look
and
feel
as
well
as
you
know,
common
components
for
building
web
applications.
You
know,
masthead
nav
form
elements
buttons.
You
know
all
those
sorts
of
things
are
provided
through
pattern
fly
all
those
pattern.
Fly
components
will
be
available
through
dynamic
plug-ins
right.
D
D
So
on
top
of
this,
the
next
layer
is
the
extensions.
The
various
extension
points
that
we
make
available
to
plugins
throughout
the
ui
and
again
there
there
are
literally
dozens
of
these
and
we
have
like
a
markdown
document
that
is
generated
from
the
code
that
outlines
all
of
them.
So
there
are
lots
of
places
you
can
plug
in
and
then
we
have,
of
course,
the
sdk
and
shared
components
that
you
can
reuse.
D
Yeah,
so
if
you're
building
a
list
page,
you
don't
have
to
start
from
scratch,
you
know
you
use
the
common
list
components.
You
know
you
get
your
data,
you
pass
those
the
common
list,
components
and
you
know
a
lot
of
the
heavy
lifting
is
done
through
those
shared
components
that
are
available
through
the
sdk
and,
of
course,
on
top
of
it
are
all
the
plugins
right.
So
today
you
know
it's
still
very
early.
D
It's
an
alpha
api,
we're
beginning
to
use
it
internally,
for
you
know,
console
itself
as
well
as
other
red
hat
plugins
like
you
know.
Eventually
we
want
to
make
it
so
that
when
you
install
the
various
red
hat
operators
that
extend
the
ui,
that's
all
contributed
through
dynamic
plugins
from
the
operator
you
know,
pipelines,
serverless,
container
native
virtualization,
ocs
and
and
so
on.
D
D
D
D
D
So
we
have
a
demo
plug-in.
That's
part
of
the
openshift
console
repo.
I
can
show
you
where
it
is
really
quickly
and
we
have
some
links
available
through
the
slide
deck
as
well
for
some
of
the
stuff.
So
this
is
the
openshift
console
github
project.
We
have
a
dynamic
demo
plugin
here.
You
know,
of
course,
everything's
open
source,
so
all
the
source
codes
available.
D
We
have
some
instructions
here,
for
you
know
how
you
can
run
and
use
the
plug-in
both
locally
if
you're
doing
development
on
the
plug-in,
as
well
as
deploying
it
out
to
a
cluster.
So
really
what
I've
done
here
is
I'm
doing
this
step
here
where
I
drag
this
manifest
file
over
into
the
import
yml
view
here,
and
I
just
wanted
to
show
you
like
what
you
know
what
resources
this
is
going
to
create.
D
I
have
a
service
that
exposes
it
on
the
cluster,
so
the
console
will
always
use
this
service
to
get
the
assets
for
the
plugin,
and
then
I
have
this
console
plugin
resource,
which
we
really
alluded
to
earlier.
So
the
this
is.
This
is
pretty
simple.
The
console
plugin
just
says:
here's
my
plugin
name.
Here's
a
display
name
and
here
are
the
coordinates
of
the
service
that
hosts
the
plugins.
So
the
service
name,
the
service
name,
space,
the
port
and
you
know
any
path-
that's
needed
to
to
load
the
plugin.
D
Exactly
yep,
so
let
me
create
this
and
you
can
see
the
resources
were
successfully
created.
I'm
gonna
go
look
at
the
deployment
it
looks
like
the
pod
is
already
running,
so
there's
one
more
step
if
you're
delivering
your
plug-in
through
an
operator
when
you
install
the
operator
you'll
have
the
option
of
enabling
the
plugin.
At
that
time
we
do
have
an
extra
step
where
we
want
admins
to
be
able
to
decide
what
plugins
are
enabled
or
not.
D
D
So
you
really
want
to
trust
any
plugins
you
enable
because
they
can
make
requests
as
as
any
user
who's
logged
into
the
console.
So
I'm,
like
I'm,
cube
admin
here
right
so
like
the
plugin,
can
make
api
requests
as
keep
admin.
So,
as
you
know,
in
the
interest
of
security,
we
do
want
like
a
cluster
in
to
go
in
and
and
confirm.
Yes,
I
want
to
enable
this
plug-in.
D
D
So
the
one
in
the
operator
api
group
here,
if
you
click
on
that
there
is
a
console,
plugins
tab-
and
you
can
do
this
through
the
cli.
If
you
want,
but
it's
nice
that
we
have.
You
know
a
ui
for
for
enabling
this.
You
can
see
the
demo
plug-in
that
I've
added
and
I
can
go
through
and
enable
it
here
and
again
you
get
the
warning
that
you
know
the
plugin
can
you
know,
run
api
commands
as
your
user.
You
know
make
sure
you
you,
you
really
trust
this
plugin
before
clicking.
B
You
touched
on
something
there
really
quickly
that
I
always
like
to
highlight,
which
is
the
console?
Isn't
it's
not
adding
magic
per
se
right
everything
that
you
do
in
the
console
you
can
do
directly
through
the
api
directly
through
yaml,
because
the
console
does
add
a
lot
of
convenience
features.
You
know.
D
Yes
straight
through
yaml,
yes,
absolutely
so
when
someone
enables
a
plug-in,
the
console
will
throw
up
this
toast
notification
and
it
will
say:
hey
their
change
is
available,
and
this
isn't
just
shown
to
me.
This
is
shown
to
any
user
who's
using
the
plugin.
So,
basically,
you
need
to
refresh
the
console
to
see
the
updates.
D
And
now
it's
loaded
the
plugin,
so
you
can
see
here
there's
a
new
nav
item,
demo
plugin
and
this
is
really
just
a
sample
plug-in.
It
doesn't
add
any
real
capability.
It's
just
kind
of
demonstrating
some
of
the
features
that
are
available
through
dynamic
plug-ins.
You
can
see
here
it's
added
a
nav
section,
a
number
of
nav
items.
D
This
particular
plugin
has
some
example
pages
and
it's
using
some
of
these
pattern
fly
components.
Just
to
give
you
an
example,
some
of
the
things
you
can
do
with
pattern
fly.
So
it's
adding
various
cards
to
the
page
alerts
at
the
top
of
the
page.
You
know
a
hit,
and
there
there
are
different
pages
here
as
well
that
tests
different
apis
that
are
available
and
the
source
code
for
all.
This
is
available
on
the
repo.
D
A
D
D
D
D
So
here's
an
example:
so
it
tries
to
bring
all
the
customization
resources
into
a
list
view
here,
gives
you
a
filter,
so
you
can
see
all
the
various
ones
like.
If
I
want
to
look
at
say
the
cli
download
resources,
I
can
filter
it
here.
It
brings
it
into
one
list
and
also
there
is
I'm
working
on
adding
some
forms
for
some
of
these
things.
So
you
don't
have
to
use
ammo.
B
D
So
console.link's
a
pretty
simple
resource,
but
it's
nice
to
be
able
to
just
fill
out
a
form
and
add
one
right.
So
let
me
submit
one
and
it's
showcasing
some
of
the
things
you
can
do
with
plugins
right.
You
can
add
list
pages,
you
can
add,
you
know,
creation
forms
and
details
pages
and
all
sorts
of
things.
So
I
created
my
new
console
link
here
and
if
I
look
at
the,
where
did
I
put
it,
did
I
put
it
in
the
help
menu
user
manual,
so
I
can
find
it.
B
D
Yeah,
so
I
realized
we're
running
short
on
time,
but
you
know
I
wanted
to
give
you
guys
a
demo
and
seeing
this
stuff
in
action.
So
you
know
this
is
something
that
I
think
is
both.
You
know
in
inside
of
red
hat's
really
going
to
help
us
as
teams
contribute
and
extend
the
console,
but
you
know
hopefully
I'll
help.
You
know
different
people
in
the
community
and
you
know
our
customers
who
are
using
console.
C
B
Think
it
was
earlier
this
year,
maybe
late
last
year,
so
that's
just
some
examples
of
what's
available
prior
to
dynamic
plug-ins.
I'm
I'm
looking
forward
to
seeing
what's
possible
with
dynamic
plugins.
I
don't
know
if
we'll
have
another
competition
or
not,
but
I've
already
got
some
things
in
my
head
that
I'd
love
to
see.
A
We
could
we
could
definitely
throw
another
competition
and
just
to
reiterate
one
piece.
This
is
very
early
days.
This
is
alpha,
but
it
it's
there.
If
you
want
to
go
and
actually
start
creating
one
there's
that
demo
plug-in
grab
it
fork,
it
build
your
own
start,
start
using
it
and
if
you
want
to
provide
us
any
feedback,
we'd
love
to
hear
what
you
think.
So,
please
reach
out
to
us
and
let
us
know.
A
C
D
A
B
A
B
Yes,
very
much
so
so.
Thank
you.
Both
really
appreciate
you
joining
today
again.
This
is
something
that
I've
been
looking
forward
to
in
a
stream
that
has
been
on
my
agenda
for
a
long
time,
so
I'm
so
happy
that
we
finally
get
to
show
this
stuff
off
and
get
to
see
what
it
looks
like
to
our
audience.
Thank
you
for
joining
us
today.
I
know
we're
running
a
couple
of
minutes
over.
I
hope
you
don't
mind.
B
So
we've
been
a
little
inconsistent
due
to
conflicts
and
stuff
like
that,
but
the
next
few
episodes
or
next
few
weeks
we'll
have
a
stream,
including
one
johnny,
and
I
are
planning
on
another
a
refresh
of
the
disconnected
experience
which
we
might
turn
into
a
bit
of
a
longer
deeper
dive.
So
we'll
have
to
figure
out
what
that's
going
to
look
like
in
the
next
week
or
two
just
a
warning.
B
B
B
You
can
also,
of
course,
subscribe
to
the
various
youtube
channels,
twitch,
etc
and
you'll
get
the
dings
every
time
we
we
go
live
whether
or
not
it's
the
ask
an
openshift
admin
show
or
not.
So
thank
you
very
much.
Everybody
for
joining
this
week
keep
an
eye
out
later
this
week
or
early
next
week
for
the
blog
post
that
follows
this
up.
I'll
include
a
link
to
all
of
the
various
well
all
the
links
that
we
use
today,
as
well
as
the
slides
and
I
like
to
put
a
little
table
of
contents.