►
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.
A
B
A
Or
second,
or
last
tuesday,
of
the
month,
I
should
I
don't
know
what
tuesday
it
is
anymore.
What
day
is
it?
What
year
is
it,
but
we
are
joined
by
the
one
and
only
serena
nichols
aka
serena
from
the
future,
and
we
are
going
to
be
discussing
some
new
things
with
the
openshift
connector
for
vs
code.
I
use
this
tool
all
the
time.
I'm
excited
to
hear
more
about
it
and
some
of
the
new
things
in
it
so
serena.
Why
don't
you
introduce
our
host
of
characters
and
take
it
away.
D
Hey
thanks
serena,
so
hi
guys
today,
the
main
focus
of
the
show
is
how
openshift
connector
will
provide
a
seamless
developer
experience
around
different
tools.
What
things
we
have
improved,
what
new
features
you
guys
would
get
to
experience
and
a
short
demos
around
it.
So
I
hope
everything
will
work
and
we
can
start
with
that.
A
Yeah-
and
I
would
like
to
introduce
the
one
and
only
ryan
jarvin
who
is
here
to
answer
any
questions
you
may
have,
he
will
be
monitoring
chat
and
I,
of
course,
will
be
around
to
answer
any
questions
you
have
as
well.
So
thank
you
all
for
joining
us
today
and
ryan.
You
wanna,
if
you
want
to
introduce
yourself,
feel
free.
E
Hey
give
me
a
shout
out
in
chat
and
definitely
as
always,
we
want
this
show
to
be
interactive,
and
the
purpose
is
to
be
here
to
answer
your
questions
and
to
act
as
an
office
hours.
If
you
have
topics
that
you
would
like
to
see
in
the
future,
definitely
pester
me
in
the
chat.
Please.
A
A
D
D
D
We
also
have
a
new
release
of
red
hat
code,
ready
containers
which
is
going
to
support
openshift
4.5.14,
and
this
week
we
are
also
going
to
do
a
new
release
for
it,
so
it
you
might
get
a
chance
to
experience
openshift
4.6
cluster,
directly
running
from
your
extension
itself
on
your
local
system,
so
that
would
be
pretty
exciting
and
I
hope
we'll
have
more
feedback
around
it.
D
D
The
release
is
similar.
What
we
have
on
the
vs
code
marketplace,
so
the
experience
will
be
exactly
similar
and
the
idea
is
whatever
new
releases
we
are
going
to
have
in
the
future
weeks.
The
extension
will
be
available
on
both
places,
vs
marketplace
and
on
the
open,
vsx
registries.
D
So
this
is
the
visual
editor
and
if
you
go
into
this
extensions
place-
and
you
just
search
open
shift
here-
you
see
this
is
the
extension
which
is
being
prompted.
D
We
just
have
to
install
it
and
once
the
extension
is
installed,
if
you
go
over
here-
and
you
see,
this
is
the
icon,
which
will
be
shown
on
the
panel,
which
means
that
okay
extension
is
there
ready
and
you
can
use
it.
So
the
idea
here
for
this
demo
is
we
are
going
to
showcase
that
how
you
can
quickly
deploy
any
application,
be
it
on
node.js,
be
it
on
java
or
be
it
on
python,
using
dev
file
directly
on
openshift
cluster.
D
The
experience
will
be
similar
that
how
you
deploy
in
a
diff
file
or
how
you
deploy
a
s2i
component,
so
let's
quickly
start
and
connect
to
an
openshift
cluster
just
for
the
sake
of
demo,
so
that
things
don't
break
up.
I
have
already
connected
to
an
openshift
instance
here,
which
is
running
remotely.
D
You
can
also
go
ahead
and
create
a
new
open
shift
cluster
directly
from
quality
containers.
You
just
have
to
do
add
openshift
cluster
and
that
will
open
a
new
view
here
and
you
just
have
to
create
a
refresh
cluster
and
if
you
I
don't
think
the
screen
is
that
okay,
so
the
current
version
on
the
extension
is
1.16
auto.
But,
as
I
mentioned,
the
release,
which
is
going
to
happen
this
week,
we'll
have
1.17.0
and
the
openshift
version,
for
that
will
be
4.5.14.
D
But
if
I
all
goes
well,
I
we
might
also
have
4.6
release,
but
that
depends
on
the
release
cycle
of
redhead
quality
containers.
But
the
idea
is
whatever
will
be
the
latest
release
that
will
be
supported
by
the
extension
completely
so
that
you
just
can
quickly
test
out
local
clusters
and
start
with
it
cool.
So
I'll
just
start
with
any
remote
openshift
cluster,
so
I'm
already
connected
to
it
and
the
idea
is,
I
will
deploy
a
simple
node.js
application.
D
It
can
be
any
application
using
react
using
angular
or
any
other
framework,
so
it
doesn't
vary
a
lot
that
okay,
if
it's
a
react
application,
will
the
experience
with
different
or
related
angular
application.
Will
the
experience
be
different?
The
idea
here
is:
we
have
the
configuration
on
dev
file
once
the
configuration
is
there.
Any
application
which
is
supported
can
be
directly
deployed
on
any
openshift
cluster
and
the
most
important
part
for
this
release
is
previously.
D
We
used
to
only
support
openshift
clusters,
but
from
this
release
going
forward,
we
also
support
kubernetes
raw
kubernetes
cluster.
So
it's
just
not
open
shift
anymore.
It's
open
shift
and
kubernetes
together
with
this
extension.
So
whatever
experience
you
want
to
have
an
open
shift
will
also
be
there
on
core
kubernetes
cluster,
also
cool.
So
just
start
with
the
demo
I'll
just
go
ahead
and
create
a
new
project,
I'll
say:
twitch
demo.
D
Okay,
so
once
I
go
here
so
this
is
the
new
project
which
I
I'm
already
logged
in
into.
D
We
also
have
an
option
where,
if
your
cluster
has
multiple
projects
and
you
switch
need
to
switch
between
different
projects,
you
just
have
to
change
your
active
project
and
it
will
basically
list
down
the
list
of
different
projects.
You
have
you
just
select
it
and
the
context
of
your
project
will
automatically
change
right.
So
this
is
the
new
project.
I
have
created
I'll
just
go
ahead
and
do
a
new
component.
D
So
before
creating
a
new
component,
it
will
prompt
me
to
provide
an
application
name
so
I'll
just
say
application
demo.
D
D
Okay,
so
I
already
have
a
folder
in
my
workspace,
where
I
want
to
create
my
dev
file,
so
I'll
just
select
that
once
that
is
selected
I'll
showcase
you
what
the
repository
contains
and
what
are
the
files
inside
it
and
how
we
can
check
the
dev
file
configuration
directly
on
top
of
it.
So
the
component
name
is,
let
me
just
save-
is
at
covad19,
because
that
is
the
simple
application
which
we
have
created
just
to
showcase
different
rates
of
coffee
cases
across
the
globe.
D
I
understand
that's
not
a
good
scenario
currently
in
the
world,
but
we
have
to
adjust
to
it
so
I'll
go
ahead
and
do
this
now.
The
fun
part
comes
here
previously.
The
different
type
of
components
which
were
allowed
to
be
created
using
the
openshift
extension
was
just
s2i
build
images.
So
if
you
see
the
lists
which
have
been
provided
have
been
marked
separately
for
s2
images,
and
if
you
go
down
you
can
see,
there
are
different
diff
file
components
also,
which
are
being
supported
so
now.
D
D
So
now,
if
you
go
to
the
workspace
folder,
so
this
is
the
repository
which,
which
is
already
there
now,
if
you
see,
there's
a
def
file,
dot
yaml
file,
which
is
created
because
this
gets
created
as
soon
as
I
create
this
component
in
that
depth.
File.Yaml,
if
you
see
all
the
configurations
are
mentioned,
that
on
what
what's
the
end
point,
which
is
there,
what
should
be
the
first
command
which
it
runs
and
what
should
be
the
executable
commands
that
it
should
do
npm
start
or
something.
D
D
So
basically,
this
dev
file
is
supported
so
that,
once
you
have
this
dev
file
based
configuration,
it
can
be
shared
across
to
different
editors,
and
the
experience
will
be
same
throughout
say
if
you're,
using
in
in
eclipse
say
or
you
are
using
any
editor,
though,
that
support
should
also
be
there.
D
So
once
we
have
this
dev
file.yaml
file
and
you
see,
there's
a
dot,
odo
folder,
which
gets
connect
created
and
which
basically
will
have
all
your
name
of
the
components.
So
what
is
the
name
of
the
component
under
which
project
it
is
and
what
is
the
name
of
the
application?
So
this
is
basically
the
environment
which
gets
created
in
the
gamma
and
dot
auto
folder
inside
your
repository.
D
So
once
we
commit
this
code
on
github,
it
can
be
shared
across
to
different
users.
So
different
teams
who
are
working
on
the
same
repository
can
use
the
same
configuration
and
just
quick
start
their
development
process,
so
basically
enhancing
the
quick
way
of
running
your
application,
testing
it
on
openshift
and
seeing
if
everything
works
smoothly.
D
So
once
we
have
this
thing
there
I'll
go
back
to
my
this.
D
Component
here,
so,
if
I,
if
you
see
if
I
extend
this
component,
this
was
the
name
of
the
component
and
we
also
label
it
as
dev
file
to
just
separate
it
that
gets
a
default
component
or
a
s2i
component.
Now,
if
you
see
the
dev
file,
as
I
mentioned,
it
already,
has
a
url
mapped
to
it.
So
basically
the
it
will
be
running
on
port
3000
with
the
http
mapping.
D
Now,
once
we
do
a
push
command,
the
idea
here
is
whatever
configuration,
which
was
there
in
the
dev
file
will
be
directly
pushed
to
the
openshift
cluster,
which
is
running
here
which
I'm
connected
to.
So,
if
you
see
it
says
that
validating
the
dev
file,
once
it
is
validated,
it
will
start
creating
the
kubernetes
resources
on
the
openshift
cluster.
Once
the
kubernetes
resources
have
been
created,
it
will
also
push
the
urls
which
is
needed
to
open
that
component.
D
D
So
once
that
thing
is
completed,
we'll
have
a
better
look
at
how
that
component
looks
and
what
the
ui,
so
the
basic
idea
is,
however
complex
your
repository
is
so.
If
you
see
this
workspace,
it
is
it's
an
entire
react
application
which
has
different
apis,
which
are
different
components.
It's
using
different
cards,
different
charts.
It
has
different
mappings.
It
has
multiple
images
to
be
loaded,
but
the
idea
here
is
as
a
development
team.
We
should
not
worry
that
whether
the
application
is
too
complex
or
how
is
it?
D
The
idea
is
to
just
be
quickly
able
to
deploy
that
application
on
openshift
and
test
it.
Does
it
work
seamlessly
or
not,
so
it
can
be
a
simple
node.js
application
or
it
can
be
a
very
complex
react
application
who
does
communication
throughout
the
server
and
integrates
with
different,
like
charts,
3d
mapping
and
everything
else,
and
this
experience
is
similar
if
we
are
also
trying
to
deploy
any
component
using
the
file
support
for
java
or
any
file
support
for
python.
D
So
once
this
command
is
finished,
I'll
show
you
what
are
the
different
type
of
registries
or
the
components
which
are
being
supported.
Currently
so
if
you
see
the
changes
are
successfully
pushed
to
the
component
and
the
status
of
the
component
has
been
changed
to
push
so
once
this
is
there,
you
can
see
the
number
of
commands
which
we
have
for
the
component
have
in
case
now.
You
can
open
directly
in
the
browser
or
you
can
watch
also.
So
if
I
do
a
watch
for
this,
you
see
this
basically
will
open
a
watch
station
here.
D
So
this
is
one
of
the
improvements
on
the
ui.
You
can
directly
see
what
what
sessions
are
currently
running
for
your
component.
So
once
you
have
this
watch
station,
it
has
a
separate
view
and
if
we
need
to
do
a
debug
of
it,
it
will
basically
currently
the
debug
support
is
not
there
for
dev
files,
because
the
idea
here
is,
we
need
to
make
sure
whatever
components
we
are
running
with.
D
S2
images
and
files
should
be
having
the
same
experience
with
debug,
so
the
debug
for
s2i
works
seamlessly,
but
we
need
to
make
sure
that
the
same
experience,
what
we
have
for
s2
is
for
div
dev
file.
So
for
this
0.2.0
release,
debug
feature
is
not
there,
but,
as
I
mentioned,
we
have
a
release
coming
up
this
week,
so
once
that
is
there
we'll
have
a
debug
support
for
java,
node.js
and
python
components.
D
So
that
is
something
I
think
people
will
be
excited
about
to
explore
it
around
once
they
use
this
dev
file
support
and
once
the
debug
session
is
active,
you
will
see
there's
a
debug
session
view
over
here,
so
those
whatever
debug,
which
is
running
will
be
mentioned
over
here.
The
same
way
as
we
have
the
watch
session
view
over
here,
so
this
is
basically
to
segregate
different
actions
which
are
available
for
the
components.
So
this
is
basically
the
explorer
view
where
you
see
all
the
listing.
The
tree
view
support.
D
D
So,
if
you
see
I
have
done
it's
a
very
simple
workflow,
I
have
a
comp
com,
git
repository,
which
has
been
cloned
into
my
system.
I
just
use
a
dev
file
configuration
and
just
deployed
internal
pressure,
and
once
I
open
it,
fingers
crossed
everything
should
work
and.
D
D
This
basically
does
a
lot
of
communication
from
the
back
end,
so
I
would
say
this
is
the
very
latest
data
which
we
have
for
kobe
19.,
and
this.
If
you
see
this
is
a
very
com,
this
tries
to
integrate
with
different
scenarios
like
you
have
charts,
you
have
graphs
and
you
also
have
like
search,
for
example,
let's
say
what's
the
status
in
france
for
covid19
today
and
if
you
see
the
number
of
infected
cases,
the
recovered
cases
and
the
death
ratios
have
been
dynamically.
These
are
changing.
D
So
if
you
see
the
integration
which
is
there
on
your
repository,
is
it
need
not
be
changed
when
you're
trying
to
deploy
any
application
on
openshift
or
any
kubernetes
cluster?
You
just
have
to
provide
the
dev
file
configuration
and
just
push
it
on
the
cluster
and
that's
it,
and
this
works
like
for
any
country
right
like
I'm,
not
sure
how
about
india
but
I'll
search-
and
I
will
be
very
sad
about
it.
D
But
if
you
see
this
is
how
bad
a
situation
is,
but
the
general
idea
is,
you
can
deploy
any
any
complex
application
or
any
simple
application
just
using
default
support.
So
if
you
see
the
main
idea
here
was
just
to
have
a
workspace
repository
based
on
this
dev
file
configuration
everything
is
getting
deployed
here
on
to
the
cluster.
C
When
you're,
when
you're,
referring
to
a
component,
there's
some
questions
in
the
chat
around,
what
are
you
talking
about
when
you're.
D
Strange,
okay,
so
yeah.
I
guess
that
that
might
be
a
question
from
many
folks,
so
the
workflow
here
is
basically
the
nomenclature.
What
we
are
following
currently
is
open
shift.
Connector
tool
on
vs
code
or
intellij
is
supporting
odo
2.0,
so
auto
is
a
command
line
interface,
which
allows
you
to
run
or
connect
with
different
kubernetes
and
open
shift
clusters.
D
D
Files
like
it
might
be
node.js
component,
it
might
be
a
java
component
or
it
might
be
a
python
component.
Now
that
component
is
basically
defined
or
can
be
created
using
multiple
ways.
A
simple
git
repository
can
also
be
added
as
a
component,
and
that
component
basically
is
having
this
odo
dot,
auto
configuration
which
is
going
to
map
you,
this
mapping,
the
project
application
and
the
name
of
the
component,
or
it
can
be
a
simple
folder
which
is
running
on
your
workspace.
It
should
not
be
from
a
git
repository.
D
It
can
be
just
simple
folder
on
your
workspace.
So
if
you
see
this
is
a
simple
workspace
folder,
which
I
have
just
created,
a
dot
auto
configuration
on
top
of
it
or
it
can
be.
As
I
mentioned,
a
binary
folder
right,
it
can
be
a
dot,
dot,
zip
or
dot
r
file,
where
we
want
to
deploy
that
entire
bundle
on
top
of
open
shift.
So
that
is
also
counted
as
a
component
right
now.
D
So
these
are
the
three
different
ways
where
you
can
create
a
component
and
it's
it's
not
necessary
that
we
need
to
just
be
creating
a
component
and
then
trying
with
openshift.
So,
for
example,
if
you
have
bs
code
quarkx
extension,
so
let
me
just
check
out
if
I
have
a
quarkx
extension,
okay,
so
vs
code,
calculus
extension
is
already
installed
on
my
system.
Basically,
what
I
can
do
is
I
can
just
go
ahead
and
do
generate
a
simple
quarkus
project,
and
I
can
this
will
basically
create
a
simple
quarkus
project.
D
It
can
be
a
simple
endpoint
project
or
it
can
be
some,
maybe
a
maven
project.
What
I
want
to
do
so
I'll,
select,
maven
and
I'll
do
okay.
Group
id
is
this:
quark
is
getting
started,
snapshot
package
name.
Let
me
say
hello:
world.
D
Cluster,
okay,
so
once
that
is
created,
basically
that
is
the
same
workflow
as
I
did
for
node.js
dev
file.
That
will
be
same
as
doing
a
java
dev
file.
So
now,
if
you
go
to
this
cluster
and
do
list
catalog
components.
D
D
D
D
Yeah,
so
the
new
url
and
new
storage
command
are
also
same
across
the
dev
file
support
or
the
s2a
support.
So
the
idea
is
the
experience.
What
we
had
when
we
wanted
to
deploy
any
s2i
source
to
image
components
will
be
same
when
we
are
trying
to
deploy
any
dev
file
component,
so
that
experience
is
not
going
to
change.
That
experience
is
going
to
be
same.
The
only
added
advantage
is
now.
Users
have
a
default
deployment
method
using
dev
files,
and
that
is
supported
in
the
latest
version
of
the
extension.
C
E
Yeah
so
from
this
list
I
would
probably
say
component
maps
from
a
developer
perspective
to
a
runtime
component
or
runtime
language
that
you
might
use.
So
you
might
have
multiple
node.js
microservices,
so
you
might
be
using
the
node.js
component
multiple
times
depending
does
that
make
sense
to
folks
in
the
both
on
the
stream
and
in
chat?
Hopefully
yeah.
I
mean
that
makes
it.
D
Yeah,
it
also
allows
you
to
select
different
versions
of
that
node.js,
for
example.
Right
now,
if
I
have
node.js
it,
you
can
create
a
component
on
node.js
10,
11
12,
whatever
your
application
supports,
so
it's
just
not
runtime
that
it
only
supports
node.js.
It
is
also
specific
to
a
version
of
node.js.
Also
and
similar
goes
for
any
other
runtime.
D
A
So
there's
a
question
in
chat:
do
you
have
a
link
to
the
code
base
you're
using
like?
Is
that
public
anywhere
that
you
could
share
with
us.
D
This
is
the
github
url
which
we
have-
and
this
is
also
mentioned
on
the
vs
code
marketplace
list
where
we
have
the
repository
link,
so
user,
who
are
downloading
it
from
vs4
marketplace,
can
directly
see
the
repository
link
and
just
try
it
out.
So
we
are
always
looking
for
more
feedback
and
more
scenarios
from
the
developer
community.
That
do
we
need
to
improve
on
something
and
how
we
need
to
improve
the
experience.
D
E
Mohit,
you
know
if
we
have
like
a
dev
file
launcher
or
anything
like
something
you
can
embed
in
your
github
readme,
where
people
could
click
and
then
that
would
try
to
open
it
in
vs
code
or
something
like
that.
That
would
be
cool.
A
Okay
and
and
mohit
people
are
asking
for
the
code
to
your
sample
application
with
the
covid.
You
know
data
and
everything
right
like
that's
what
they're
asking
for.
I
already
dropped
the
the
link
to
the
the
vs
code,
openshift
tools,
repo
yeah
yeah,
I'll,
provide
that
link
too
awesome.
Thank
you,
sir.
C
Hey,
I'm
curious
how
how
if
you
want
to
try
to
show
this
an
openshift
console
is
that?
Could
we
possibly
try
to
see
if
that
works,
or
is
that
too
risky
of
a
demo
today,.
D
We
can
definitely
try,
because
if
you
see
we
also
have
this
kubernetes
view,
which
is
supported
with
this
extension.
So
if
you
see
this
is
the
view
which
is
supported,
and
if
you
see
this
is
my
open
shift
cluster,
which
is
running
so
it
has
been
highlighted
with
openshift
logo
and
other
other
kubernetes
logos,
because
that
is
how
it
is.
So
if
you
expand
it
and
if
you
go
to
nodes
and
not.
D
D
Okay
yeah,
so
let
me
just
switch
my
project,
which
I
have
not
done
because
currently
I
was
a
default
project,
so
my
project
name
was
what
was
the
name
of
my
topic
so
go
back
to
here.
So
this
is
the
extra
feature
which
we
have
with
the
kubernetes
extension
where
you
can
automatically
switch
between
different
projects
which
we
are
running
so
which
demo
is
my
current
project.
So
it
is
loaded.
D
D
D
So
if
you
see
these
are
the
different
scenarios,
which
are
there
for
the
deployment
configs,
and
it
will
be
same
for
the
different
parts
which
are
running
or
for
different,
build
configs
or
different
deployment
configs,
which
are
there
on
the
cluster,
the
communities
view.
But
if
you
go
here
and
open
console
dashboard
that
will
basically
lead
us
to
the
dev
console
ui.
C
D
I
hope
it
works.
It
should
work
because
there
is.
The
experience
is
very
seamless,
so
I'm
very
much
hopeful
that
it
will
work.
C
D
It
is
so
awesome,
so
if
you
see
this,
basically
the
application
was
deployed
in
openshift
4.6,
so
you're
trying
to
deploy
on
the
latest
cluster.
And
if
you
go
to.
D
Yeah,
so
if
you
see
we
have
the
topology
view
up
check.
C
C
D
You
can
see
the
logs
here,
you
can
see
different
parts
which
are
running
you
can
see
which
port
it
has
been
mapped
to,
and
you
can
directly
open
the
url
from
this
route.
It
will
be
the
same
application
so
yeah.
The
idea
is
basically
you
can
directly
from
your
vs
code
editor.
You
can
directly
switch
to
your
openshift
dev
console
and
you
can
see
all
the
scenarios
which
are
available
on
dev
console
seamlessly.
D
D
C
B
D
So
if
you
see
I,
I
also
had
a
previous
node
application,
which
was
running
on
my
cluster.
So
if
I
look
into
that
and
that
will
also
be
seamlessly
available
on
the
dev
console
side-
and
that
is
there,
if
I
open
it
again,
it
has
a
different
ui,
but
the
idea
is,
you
can
deploy
any.
As
I
mentioned
any
application
on
top
of
openshift.
It
works.
So
the
use
case
for
this
ui
was
to
just
see
a
weather.
So,
for
example,
okay,
let's
say
paris.
D
Yeah,
I
guess
so
yep
so
yeah,
so
whatever
whatever
scenarios
which
you
try
to
as
a
developer,
try
to
do
it
on
your
b,
vs
code
beat
intellij
and
you
try
to
create
your
components,
deploy
and
openshift
without
leaving
your
editor
at
the
same
experience
you
can
see
on
the
dev
console
side,
so
the
idea
is
you
just
have
to
on
the
cluster.
You
have
to
right
click
and
you
have
to
open
control
dashboard
and
that
would
basically
lead
you
to
this
view.
D
A
D
A
It
does
say
well,
this
is
all
in
fahrenheit,
52,
white
rain,
so
switch
it
to
celsius,
I'm
not
sure.
What's
currently
in
my
city,
so
let
me
check
yeah.
This
is
saying:
I'm
like
paris
isn't
like
12..
A
D
Yeah,
sorry,
okay,
my
phone
also
says
24,
so
yeah,
it's
more
or
less,
okay,
so
yep.
I
think
that
is
what
the
main
end
goal
of
having
this
release
was.
We
are
going
to
support
that
file
and
we
are
also
going
to
support
any
kubernetes
cluster
with
openshift
cluster.
So
it's
just
no
more
just
openshift
cluster.
D
It
is
any
kubernetes
cluster.
Any
openshift
cluster
will
be
supported
by
this
extension.
You
can
deploy
applications
on
using
dev
file
or
using
search
to
image
any
scenario
which
the
developer
wants
to
do
it
and
you
can
run
credit
code
ready
containers
directly
from
your
id
without
leaving
the
editor
and
create
a
local
version
of
openshift.
So
these
three
are
the
highlights
of
this
release
and
I
think
we
are
looking
to
improve
it
more
in
the
upcoming
releases,
so
stay
tuned.
A
Awesome
question
in
chat:
is
it
possible
to
work
with
the
connector
and
odo
together?
D
Yes,
yeah
so
yeah,
the
idea
is
basically
whatever
experience.
Odo
has.
The
same
experience
will
be
provided
to
the
developers
through
the
ide
support,
because
I'm
assuming
that
people
prefer
sometimes
using
ids
to
do
different
type
of
applications.
D
So
whatever
experience
we
have
for
odo
will
be
same
for
using
the
same
extension
and
this
extension
is
also
available
on
red
hat
code,
ready
workspaces.
D
So
if
some
developer
wants
to
use
it
at
quality
workspaces,
the
extension
is
available
there
and
it
will
have
the
same
experience
there.
So
that
way,
the
overall
end-to-end
experience
using
different
ids
is
going
to
be
same
when
we
are
saying
that
open
shift,
connector
integrates
with
different
clusters
and
supports
different
depth
files
and
store
images.
C
D
D
E
I've
been
busy
with
kubecon,
but
I
fully
intend
on
updating
the
odo
2
learning
scenario
on
learn.openshift.com.
That's
still
odo
1.0
currently,
but
that's
should
be
updated
relatively
soon.
I
did
a
test
the
other
day
where
I
pulled
down
the
odo
2
binary
and
dropped
it
into
the
demo
and
and
followed
along
using
odo
2
against
the
older
cluster,
but
we're
going
to
get
it
upgraded
to
a
newer
cluster
version
in
that
demo,
environment,
so
that'll
be
in
the
next
couple
weeks.
E
I
think
beautiful
and
we
should
have
a
nice
example
repo
in
here.
I'm
not
sh
in
in
that
update.
I'm
not
sure
this
covet
tracker
was
really
cool.
I
haven't
found
the
link
to
that
repo.
Yet
I
was
trying
to
troll
through
mohit's
commits
on
github,
but
it
doesn't
look
like
he's
been
contributing
on
that
specific
repo.
So
I
wasn't
able
to
track
it
down.
D
E
We'll
we'll
try
to
get
a
link
for
y'all.
D
And
even
the
idea,
what
we
have
for
the
next
releases
is
we'll
we'll
also
support
some
starter
components.
For
example,
you
can
directly
create
a
node.js
component
or
a
java
component,
and
that
will
have
the
starter
repositories
mentioned.
So
we
are
also
trying
to
work
on
that,
and,
hopefully,
we'll
have
the
support
for
that.
This
coveted
19
tracker
example
was
is
on
github.
It
was
just
a
simple
application.
I
just
wanted
for
the
demo
purpose
so
that
we
can
demo
that
it
doesn't
depend
upon
the
complexity
of
the
app.
C
A
A
D
Yeah
there
might
be
some
challenges,
for
example,
when
you're
trying
to
deploy
any
component
on
openshift.
There
might
be
scenario
that
the
deployment
conflicts
are
not
getting
created
properly
or
even
the
build
configs
are
not
getting
created.
So
when
these
kubernetes
resources
are
not
there
on
the
cluster,
then
the
app
doesn't
work
seamlessly.
D
We
have
to
undeploy
and
try
to
post
the
components
again.
So
that
is
some
of
one
of
the
challenge
which
we
figure.
We
have
figured
out
that
it
might
be
there
for
some
users,
but
that's
not
so
consistent.
That
is
just
for
few
users.
D
So
I
think
overall,
we
are
trying
to
expand
the
expand,
the
interface
trying
to
include
operator
hub
scenario
into
the
extension
also
where
users
can
see
the
different
lists
of
operators
which
are
currently
installed
in
a
cluster
and
what
are
the
other
operators
which
you
can
also
install
on
your
cluster.
D
So
that
is
also
in
discussion
phase
currently
and
we're
trying
to
see
the
feasibility
of
it
into
the
extension
and
try
to
implement
that.
So
that
will
also
be
one
of
the
cool
features
where
users
can
directly
install
any
operator.
On
top
of
their
cluster
and
just
start
using
it
directly
from
your
id,
that's
awesome,
so
that
is
that.
E
A
They
probably
are,
let
me
know,
okay,
let
me
double
check,
though,
because
it
could
be
disconnected
somehow.
A
Aggregate
chat
together,
but
while
I
pop
over
there
go
ahead
and
jab.
E
A
little
we
had
one
that
was
kind
of
off
topic,
given
today's
discussion,
but
we're
happy
to
have
it
anyway.
Someone
was
asking
about
access
to
logging
and
granting
specific
teams
access
to
logs,
it
kind
of
depends
on
which
logs
they're
looking
to
access.
I
I
would
say,
as
a
short
answer
to
that,
one
option
would
be
enabling
that
team
with
a
prometheus
operator,
you
could
make
sure
that's
available
cluster-wide.
E
If
everyone
wants
to
use
it
or
install
it,
just
in
a
namespace
specific
to
them,
and
then
they
should
have
their
own
logging
infrastructure
available
via
that
operator.
D
Okay,
so
the
idea
is,
you
are
connected
to
one
instance
of
the
cluster
at
one
point
of
time.
So
if
say,
for
example,
you
are
connected
to
this
cluster
and
you
need
to
change
so
you
there
is
an
action
item
here
which
is
like
logging
into
the
cluster,
and
if
you
click
on
that,
basically
it
will
prompt
you
that
you
are
already
connected
to
a
cluster.
Do
you
want
to
switch
it?
So
if
you
see
you're
already
logged
into
the
cluster,
you
want
to
switch
to
new.
I
said
yes.
D
Very
nice
yeah,
so
now
you
can
basically
decide
that.
Do
you
want
to
login
using
credentials
or
do
you
want
login
using
token
once
you
say:
okay,
I
want
to
log
into
the
credentials,
so
this
will
basically
list
down
all
the
clusters
which
you
are
previously
connected
to
and
this
mapping
is
being
taken
from
your
cube,
config
file.
So
if
you.
C
D
File
basically
has
this
entry.
This
will
be
shown
up
here.
D
So
if
you
have
a
class
already
there,
you
just
provide
the
credentials
directly
or,
for
example,
I
have
my
quality
containers
running
so
I'll,
just
use
that
api.css
testing
and
I
have
to
provide
the
cube
admin
as
a
user,
and
let
me
just
see
what's
the
pass.
So
if
you
see
the
password
is
already
present
here,
so
the
extension
allows
you
to
do
two
things.
First,
is
it
will
ask
when
you
provide
the
password
for
the
first
time?
It
will
ask
you
whether
you
want
to
save
the
password
or
not.
D
If
you
say
yes,
it
basically
saves
the
password
in
kept
it
format
using
a
node
module
known
as
ketar,
so
that
saves
it
in
encrypted
format
so
that
once
you
try
to
log
in
in
the
second
or
the
next
iterations,
you
did
not
manually
again
enter
the
password,
it
would
already
be
stored.
You
just
have
to
say
yes
and
now,
if
you
see
it,
says
log
into
the
cluster,
it
will
try
to
log
into
the
cluster
and
now
you're
successfully
logged
into
quadratic,
continuous
instance.
D
A
D
A
D
A
As
you
saw
like
when
mohit
went
to
the
view,
I
forget
which
view
it
was,
I
actually
just
clicked
the
kubernetes
logo
above
the
open
shift,
connector
yeah.
So
if
you
see.
A
Are
right
there
and
he
can
log
into
any
of
them,
including
this
mini
cube,
one
right
like
right
there
from
the
ide,
so
yeah.
You
would
have
no
issues
running
this
with
kate's
aks,
I'm
assuming
would
even
work
right
like
it's
kubernetes
primitives.
So
if
it's
kubernetes
native,
it's
gonna
work
right
and
that's
the
beauty
of
it.
D
E
I
haven't
tried
it
out
on
vanilla
kubernetes
yet,
but
that
is
definitely
on
my
list
of
things
to
try
if
any
of
y'all
out
in
the
audience
end
up
accomplishing
that.
Definitely
let
us
know
in
chat
give
us
some
feedback
on
how
it
worked
for
you
really
cool
stuff
or
how
it
didn't
work
for
you,
yeah
yeah,.
A
All
right,
wonderful,
wonderful,
wonderful
work!
Mohit
like
this
is
awesome.
I
really
appreciate
you
bringing
this
onto
the
channel
today.
Currently
on
iks,
said
they'll,
give
it
a
try:
okay,
cool
that
should
work
yeah,
so
serena
anything
else.
You
wanted
to
mention
the.
C
C
Just
wanted
to
mention
that
one
more
time,
so
I
left
a
link
in
the
chat
for
the
registration
form.
So
again,
that
is
a
showcase.
The
best
open
shift
web
console
customizations
using
the
current
supported
mechanisms
for
openshift
four.
So
I
think
we've
had
a
few
shows
on
that.
So
far,
we're
gonna
have
another
one.
C
I
think
it
is
in
two
weeks
going
to
be
another
one
where
we
talk
about
some
of
the
entries
that
we've
gotten
and
then
on
december,
1st
we're
going
to
have
a
live,
a
live
show
showing
like
the
top
entrance
as
determined
by
the
committee
and
allowing
the
people
online
to
do
voting
for
the
top
three.
So
keep
your.
C
Please
join,
I
know,
we've
got
a
number
of
registrants
already,
but
we
love
the
more.
We
get
the
better.
E
We
had
a
really
slick
if
you
missed
it,
I
can't
recall
whether
it
was
last
week
or
not,
but
we
had
a
really
nice
demo
of
how
to
customize
the
com
console.
So
if
you
missed
that
show
definitely
take
a
look
for
that
that
video
on
youtube
or
on
twitch.
C
A
A
C
C
I
think
one
of
the
goals
too,
is
just
is,
is
not
only
show
us
what
you
can
do,
but
also
let
the
community
and
other
customers
like
see
all
the
cool
things
that
are
being
done
so
that
you
know
sharing
sharing,
is
caring
exactly
so
and
also,
I
think,
one
of
the
follow-ups
after
that
is
like
you
know
what
our
customers
and
our
users
and
the
community
really
looking
for
going
forward
and
trying
to
gather
some
more
of
those
requirements
too
for
people.
So
I
think
all
this.
A
Was
it
yes?
Okay,
let
me
drop
this.
I
believe
this
was
the
right
one.
Yeah
customizing
find
the
chat,
drop
it
and
restream
chat.
Here's
the
previous
episode,
everybody
and
without
further
ado,
if
there's
nothing
else,
let
me
double
check
chat.
A
Question,
oh,
let's
see,
is
it
possible
to
use
kind
for
development
and
then
go
to
openshift
using
the
same
dev
file?
I
believe
so
yeah.
It
should
work
in
theory
unless
you're
using
some
like
openshift
specific
things
that
don't
exist
in
kind
or
you
know,
if
you're
doing
that,
then
that's
not
going
to
work,
but
otherwise
it
should
work
right
because.
E
Yeah,
theoretically,
there
may
be
some
differences
in
the
security
model
between
those
two
environments.
So
if
you're
running
things
in
local
dev,
where
every
process
is
run
as
a
root
process,
then
you
may
have
some
surprises
further
downstream
in
your
release
pipeline.
But
that's
all
cluster
configuration
and
security-
not
necessarily
about
about
this,
but
assuming
the
clusters
are
configured
consistently.
E
C
A
E
We
are
taking
a
break
on
the
show
next
tuesday,
but
we
will
be
back
the
following
week.
A
And
so
yeah
next
tuesday
is
going
to
look
a
little
different
on
the
channel.
I
will
be
out
I'll
be
out
voting
and
then
you
know
just
staying
away
from
the
deluge
of
information.
That'll
happen
after
that
and
not
be
in
front
of
a
computer
is
a
good
healthy
way
to
get
away
from
that
for
me,
so
yeah,
but
we
will
have
devnation
that
day
we
will
have
an
openshift
commons
that
day.
So
I
think
we're
having
openshift
comments.
That
day.
A
A
There
should
be
a
little
plus
sign
next
to
the
google
calendar
logo,
assuming
they
didn't
change
it
with
all
the
logo
changes,
and
you
can
add
that
to
your
calendar
and
get
reminders
whenever
on
the
show-
or
you
can
just
pick
an
individual
show
and
say
subscribe
to
this
show
and
add
that
to
your
calendar.
So
whatever
works
for
you,
please
have
at
it.
We
welcome
you
back
anytime,
so
without
any
other
questions
in
the
chat
and
without
any
other
demos
to
be
done.
A
Thank
you
all
for
joining
today,
really
appreciate
ryan
mohit
serena
everybody's
sitting.
Here
I
just
listed
that
in
order
is
no
particular
priority
and
I
really
appreciate
everybody
in
chat
today.
Chat
was
lively,
so
I
always
appreciate
that.
We're
glad
and
happy
to
answer
your
questions
and
stick
around
top
of
the
hour.
So
in
eight
minutes
ish
we
will
have
an
open
shift.
Commons
briefing
on
three
scale
and
api
management,
so
that'll
be
fun
as
well
as
an
operator
demo.