►
From YouTube: TGI Kubernetes 155: Backstage
Description
- 00:00:00 - Welcome to TGIK!
- 00:03:20 - Week in Review
- 00:20:17 - Starting with backstage
- 00:30:41 - Getting node env set up
- 00:32:20 - Creating the backstage app
- 00:35:54 - Exploring app structure
- 00:38:40 - Launching the app
- 00:46:38 - Configuring Auth
- 00:59:16 - Thinking about confused deputies
- 01:04:34 - Starting to explore catalog w/ Kubernetes
- 01:41:33 - Create new component from template
- 01:53:38 - Summing up
The live chat replay got cut disabled somehow! Sorry about that!
Full notes at https://github.com/vmware-tanzu/tgik/blob/master/episodes/155/README.md.
Come hang out with Joe Beda (@jbeda) as he explores something new in the Kubernetes ecosystem. Hang out as we explore something NEW for the first time.
This week we will be looking at Backstage! (backstage.io)
A
A
But
first
I
want
to
start
out
by
saying
hello
to
everybody
and
checking
to
make
sure
that
you
can
all
hear
me
fine
things.
You
know
one
o'clock
snuck
up
on
me
today
and
I
didn't
get
a
chance
to
do
any
sort
of
any
sort
of
av
check.
So
let
me
know
if
things
are
coming
through
fine
and
I
want
to
also
say
hello
to
all
the
folks
who
are
dialing
in
from
all
over
the
world.
It's
great
to
see
you
all!
A
It's
like
you
know,
friends
that
I
haven't
talked
to
in
for
a
while,
and
so
it's
just
great
so
starting
at
the
top
here,
lamati
good
to
see
you
you're,
always
first
to
say,
hi
rory
from
scotland
good
to
see
you
again
too
david
suresh
from
hamburg
ivan
martin
from
the
netherlands
walid
good
to
see
you
you're
always
joining
us
too
savvy.
I
hope
I'm
saying
your
name
right
from
istanbul,
suresh
yeah!
A
That's
the
countdown
that
you
all
are
mentioning
is
part
of
the
I'm
trying
out
we've
been
using
stream
yard
as
a
platform
for
doing
this
stuff.
It's
just
a
lot
easier
for
folks
to
get
up
and
running
with
versus
obs,
which
you
know,
learning
how
to
configure
obs
is
a
full-time
job.
To
be
honest,
there's
some
things
I
like
better
about
obs,
but
stream
yard
is
so
much
easier
to
get
going
with
so
dukkha
good
to
see
you
from
helsinki
khalid
chum's
from
tunisia
holy
moly.
A
So
a
lot
of
folks
saying
hi,
phoenix
tehran,
scottsdale
north
carolina,
belgium,
orlando
good,
to
see
you
all
all
right.
Well,
let's,
why
don't?
We
just
go
ahead
and
start
jumping
into
things.
So
the
first
thing
is
that
I'm
going
to
be
going
through
we're
going
to
have
a
a
shared
notes
document
and
you
can
always
get
to
that
at
tgik.
Dot,
io,
slash
notes-
and
this
is
where
both
will
pull
together
some
sort
of
interesting
things
that
I
I
you
know
pulled
out.
A
You
know
I
didn't
have
a
ton
of
time
to
do
with
this
this
time
around
that
we
can
go
over.
You
know
news
of
the
week,
but
also
as
we
go
through
the
rest
of
the
the
you
know
looking
at
backstage.
We
can
use
this
as
a
place
to
actually
you
know,
keep
track
of
interesting
links
and
things
that
we
find
as
we
go.
A
So
oh
wow,
amman,
jordan.
Good
to
see
you
massachusetts
all
over
all
over
all
right.
Let
me
go
ahead
and
start
broadcasting
here
now
I
can
do
two
formats.
I
can
do
this
where
it
shows
you
know
this
one
here
where
it
shows
me
and
the
thing,
but
I
actually,
I
think,
I'm
not
going
to
show
my
face
here
and
we'll
just
show
the
the
screen.
A
We
go
we'll
we'll
put
that
up
there
and
I
can
show
that.
That's
the
that's
the
link
that
you
want
to
go
to.
If
you
want
to
see.
Oh,
yes,
kind,
new
version
of
kind
good
for
whoever
is
putting
that
in
there.
Thank
you
very
much,
that's
something
that
should
definitely
be
there,
so
very
cool
all
right.
A
A
You
know
themes
start
to
emerge
here
and
it's
really
honestly
about
you
know.
None
of
these
things
are,
you
know,
I
think
groundbreaking
features,
it's
about
maturing
the
stuff
that
we
have
and
just
making
it
more
solid,
so
I'll
go
through
these
real
quick
here.
Let
me
close
some
of
these
other
links
that
we
have.
A
So,
let's
go
through
these
and
and
we
have
an
internal
sort
of
like
pulse
of
what's
happening
in
kubernetes,
and
thank
you
to
nikita
who
pulled
some
of
this
stuff
together
for
us,
because
I
think
that
definitely
helps
us
keep
an
eye
on
things
and
she's
been
driving
a
lot
of
these
things.
So
this
is
the
type
of
stuff
that
I
think
folks
are
focused
on.
Is
that
you
know
publishing
version
information
and
open
api
you
know
is
you
know,
is,
is
super
interesting.
A
You
know,
versions
and
apis
and
upgrades.
These
are
things
that
aren't
exciting
but
they're,
absolutely
critical
to
make
this
stuff
work
long
term
and
to
really
create
a
situation
where
you
know,
as
we
come
out
with
new
versions
of
kubernetes,
people
can
upgrade
with
feature
with
confidence,
and
we
can
actually
build
systems
that
work
better
and
better
in
the
face
of
these
types
of
things
that
are
going
on
and
being
able
to
take
this
type
of
versioning
down
to
the
field
level
is
really
interesting.
A
Also,
I
think
you
know,
there's
you
know
with
systems
like
kubernetes,
and
I
think
we've
seen
this.
You
know
talking
to
a
lot
of
pivotal
colleagues
in
the
experience
over
the
long
term
with
things
like
cloud
foundry,
you're,
always
kind
of
stuck
in
this
thing
of
like
hey.
If
I
upgrade
that
may
destabilize
things,
but
if
I
don't
upgrade,
then
I
get
left
behind
and
my
options
in
terms
of
support
and
being
able
to
use
the
new
features,
get
less
and
less
over
time
and
so
there's
a
real
need.
A
I
think
you
know
to
make
sure
that
we
create
you
know
the
ability
for
people
to
be
able
to
upgrade
with
confidence,
and
that's
just
really
critical
for
the
longevity
of
kubernetes
over
the
long
term.
So
that's
really
really
important.
Oh
nova's,
here
with
with
my
wife,
rachel's
down
there,
helping
nova
out
and
patrick
and
bjorn
her
her
little
pupper
so
good
to
see
you
yeah
so
so
yeah.
So
this
is
something
that
I
think
is
really
critical
and
I
think
so.
A
That's
really
cool
and
nikita's
been
working.
A
lot
on
that.
So
thank
you
nikita
around
that,
let's
see
next
thing
sub
resource
support.
This
again
is
is
maturing
the
kubernetes
api
server.
I
think
you
know
the
the
idea
of
a
sub
resource,
and
I
think
you
know
I
don't
know
how
familiar
folks
are
with
sub
resources.
A
A
A
I
think
where
you
can
actually
start
doing
more
dynamic
off
against
these
things.
One
of
the
things-
and
I
haven't
had
a
chance
to
look
at
it,
but
I
think
would
be
really
exciting
is
if
we
could
start
using
spiffy
inspire
to
be
able
to
do
this
stuff
too.
That
would
be
really
cool
and
that's
something
that
I'd
love
to
to
look
at
now,
not
mention
in
there,
but
I
I
would.
A
A
Yeah,
I'm
still
old
school.
I
like
using
nope.
Oh,
you
can't
even
see
me
right,
but
it's
me
being
old
schools.
I
use
like
a
notebook
and
like
a
pencil,
I
don't
know,
I
have
an
ipad
and
I
use
it
for
some
notes,
but
sometimes
there's
just
nothing
like
having
a
notebook
on
your
desk
when
you
want
to
jot
something
down
all
right,
let's
keep
moving
and
then
the
the
last
one
is
cubelet
cri
support.
This
is
something
that's
been
going
on
for
a
while.
This
is
a
general
idea
of
really.
A
You
know
this
push
to
take
everything
in
kubernetes,
that's
marked
as
beta
and
get
it
to
ga
and
just
make
sure
the
fact
that,
like
hey,
we're
being
honest
about
the
stuff,
that's
in
production
that
we're
serious
about
it
being
in
production
and
that
we've
actually
gone
through
and
dotted
all
the
eyes
and
crossed
all
the
t's.
The
particular
update
here
that
I
think
is
interesting
that
came
through
if
I
can
go
ahead
and
find
it
is
this
idea
of
pinned
images
and
there's
a
hit.
A
You
know
any
images
that
are
sitting
on
the
cubelet
on
you
know
on
the
node,
any
those
images
are
essentially
just
a
cache
right.
We
can't
let
that
grow
indiscriminately
over
time.
Otherwise
you
end
up
filling
up
the
disk
and
every
anybody
who's
run.
You
know,
machines
in
production
knows
that
you
know
filling
up.
A
disk
is
a
recipe
for
disaster,
and
things
generally
don't
work.
A
Well,
after
that,
and
so
early
on,
we
added
some
capabilities
in
the
cubelet
to
be
able
to
garbage
collect
images
that
were
running
on
the
disk,
and
it's
worked
pretty
well
over
time,
but
you
know,
I'm
sure,
there's
some
edge
cases,
and
this
is
fascinating.
So
now
you
can
go
through
and
actually
pin
some
of
these
things
and
say:
hey,
don't
clean
up
these
images.
A
You
know
the
release
train
keeps
moving
now,
we've
moved
to,
and
I
think
we
covered
this
in
a
previous
tjik
we've
moved
to
a
release
cadence
of
three
per
year
instead
of
four
per
year.
I
think
that's
probably
better,
for
everybody
gives
folks
a
little
bit
more
breathing
room
and
it
gives
in
terms
of
those
actually
driving
releases,
and
it
also
gives
consumers
a
little
bit
more
room
because
you
know
our
our
support.
A
What
the
schedule
looks
like
who's
driving
it,
how
it's
all
coming
together,
just
a
great
resource,
if
you're
actually
wondering
where
things
are
at
with
a
particular
release
and
actually
want
to
want
to
keep
up
with
it.
So,
let's
see
eric's,
saying
not
sure
if
we
covered
last
week,
but
there's
a
kep
2413
enabled
oh
yeah,
I
did
see
this
on
twitter.
I
don't
know
if
we've
covered
it
eric
if
you
want
to
put
that
in
the
notes.
That
would
be
great.
This
is
really
exciting.
A
Also,
I
think
you
know
there
are
all
these
things.
You
know
using
things
like
the
setcom
profiles
that
make
kubernetes
more
secure,
but
getting
to
the
point
where
we
can
turn
those
things
on
by
default
and
being
respectful
of
not
breaking
people.
It's
always
a
struggle,
there's
always
a
leap
of
faith
here
in
terms
of
you
know.
Turning
on
these
things,
you
know
introducing
these
new.
A
So
thanks
for
thanks
for
putting
that
one
on
there
and
let's
see
and
here's
the
here's
the
link
to
it,
super
exciting
and
yeah
so
yeah,
something
to
look
at
here,
and
I
just
I
love
how
you
know
the
the
kept
process.
I
think
this
is
again
part
of
the
maturity
of
part
of
the
maturity
of
kubernetes
itself.
A
It
feels
like
a
lot
of
process,
but
in
terms
of
being
able
to
communicate
across
both
the
contributor
and
the
user
community,
they're,
absolutely
critical,
and
so
it's
great
to
be
able
to
see
this
stuff
come
together
all
right.
You
know
looking
around
couple
of
other
things
that
I
wanted
to
call
attention
to
here.
So
we
have.
A
I
think
this
episode.
I
want
to
be
sort
of
the
start
of
a
series
where
we're
going
to
be
doing
more
and
more
of
looking
at
the
sandbox
projects.
Let's
see
other
stuff,
that's
going
on
here's
a
new
thing
that
showed
up
on
hacker
news.
I
saw
a
v-cluster.
This
is
really
interesting
and
there's
been
a
lot
of
efforts
to
be
able
to
do
this,
and
so
this
is
something
I'd
like
to
play
with
at
some
point.
It
looks
really
interesting.
A
It
essentially
runs
sub-api
servers
and
and
then
recreates
new
pop
pods
in
the
host
cluster
and
then
re.
You
know
I
want
to
understand
sort
of
what
the
networking
and
security
model
there
is,
but
it
looks
really
interesting
here.
So
that's
something
to
be
aware
of.
Let's
see
this
looked
really
cool
and
I
want
to
explore
this.
A
I
just
need
more
hours
in
the
day,
this
is
a
deeper
dive
into
ephemeral
containers
which
are
a
way
to
essentially
create
a
new
container
inside
of
a
pod,
mostly
for
the
purposes
of
being
able
to
debug
things,
and
it's
something
that
I
haven't
had
a
chance
to
play
with
yet,
but
I'm
really
excited
to
at
some
point
be
able
to
really
dig
into
and
understand
how
it
all
works.
So
that
looks
really
cool.
So
martin,
thanks
for
for
posting
that
yeah
chris
says
the
setcom
stuff
is
interesting
in
quotes.
A
I'm
glad
folks
are
starting
to
look
at
kernel
level
controls,
albeit
I
don't
know.
If
kubernetes
has
any
business
mutating
the
kernel.
Well,
you
know
the
kubernetes
and
the
colonel
are
always
you
know
tied
at
the
hip.
I'm
not
sure
that
there's
a
you
know,
there's
always
a
a
dance
there.
I
think
in
terms
of
making
it
easier
to
actually
orchestrate
this
stuff
versus,
expecting
people
to
have
other
systems
to
be
able
to
drive
this
so
yeah,
so
yeah
good
to
see
that
coming.
Oh
look
at
that.
A
A
A
At
some
point,
I'm
gonna
have
a
I'm
gonna
have
a
you,
know
an
r
mac
and
be
able
to
play
with
this
stuff,
and
so
it's
great
to
see
that
support
coming
together
and
then
oh
here's
a
conference
that
I'd
seen
some
some
some
talk
on
this
is
wtf
is
sre.
Is
this
put
on
by
the
who's
putting
this
stuff
on?
So
this
looks
looks
interesting.
Also,
so
lots
probably
lots
of
great
talks
there.
A
I
hadn't
had
a
chance
to
check
it
out,
but
very
cool
all
right.
So
let's
go
ahead
and
get
started
and
start
oh
yeah,
so
container
solutions
yeah
because
they
also
do
the
the
the
the
the
software
circus
conference
also,
and
so
that
looks
really
cool
there.
Yeah
the
and
software
circus
is
the
one
where
I
did.
The
talk
wearing
the
pickle
rick
costume
exactly
it
was
a
lot
of
fun,
all
right
cool,
so
backstage
dot
io,
let's
just
jump
into
it
here
so.
A
A
You
know
proxy
in
front
of
the
resources
that
you
need
so
oftentimes.
It's
like
you
know,
thinking
about,
like
you
know
a
you
know,
instead
of
a
cloud-like
very
flexible
api,
a
much
more
curated
set
of
services
to
be
able
to
get
to
what
you
need
to
get
to,
and
that
can
be
really
liberating
for
developers
inside
of
an
enterprise
to
have
that
curated
set
of
experiences.
A
But
I
also
worry
that
it
can
be
limiting
too
right
in
terms
of
hey.
If
what
you
want
to
do
is
acceptable
through
the
service
catalog
great.
If
it's
not,
then
what
do
you
do,
then?
Where
do
you
go
from
there,
and
so
one
of
the
things
that
I'm
going
to
keenly
be
looking
at
when
we
you
know
as
we're
playing
with
backstage
here,
is
how
much
of
black
backstage
tries
to
wrap
and
cover
the
underlying
infrastructure
versus?
How
much
does
it
really?
A
You
know
view
itself
as
a
can
you
use
it
as
a
transparent
way
to
be
able
to
accelerate
access,
make
the
easy
pass
easy,
but
doesn't
necessarily
cut
you
off
or
hide
you
from
the
underlying
infrastructure,
and
I
think
another
way
to
say
this
is
that
oftentimes
people
will
say
that
if,
as
a
application
developer,
someone
has
to
get
down
to
the
level
of
using
cube
control,
then
you
know,
then
maybe
something
is
going
wrong
right.
We
should
be
able
to
do
everything
using
other
tools
that
build
on
top
of
kubernetes.
A
That's
great
until
you
need
to
ssh
into
a
node,
and
so
there
may
still
be
situations
where
you
know
our
abstractions,
don't
necessarily
work
for
us.
Oh
bogdan's,
asking
why
you
can't
see
me
so
the
why
you
can't
see
me
is
like.
Let
me
know
if
you
like.
Actually
it's
this
view
this
view
here
where
I
have
the
background
here,
which
may
be
a
little
distracting.
I
can
change
that
a
bit,
but
the
screen
ends
up
being
a
little
bit
smaller
or
I
can
do
the
full
screen.
A
Let
me
know
what
you
guys
like
better
here
I'll.
Do
this
one
for
a
little
bit
so
yeah.
So
that's
what
we're
going
to
be
looking
at
with
with
backstage
here,
and
so
I
started.
You
know
you
know,
there's
a
bunch
of
marketing
stuff
here
talking
about
what
it
is,
but
I
always
go
right
to
the
docs
and
there's
what
is
backstage,
and
I
think
this
is
probably
more
likely
it's
an
open
platform
for
building
developer
portals.
A
So
you
guys,
like
this
view,
better
okay
cool
now
rory's
saying
we
don't
need
to
ssh
into
node
team,
where
we
have
cube
control,
debug,
node,
exactly
all
right
cool,
and
so
you
know,
there's
a
service
catalog
thing
and
I
think
that's
worth
like.
I
want
to
understand
what
exactly
they
mean
it
there's
this
other
thing,
which
is
software
templates.
This
is
you
know,
there's
this
thing
in
the
spring
world
and
I
think
you
know
if
you
look
at
spring
initializer.
A
This
is,
I
think,
in
the
spring,
world
is
a
great
way
to
get
started.
You're
like
hey,
start
me
an
app.
You
know,
maven
java
2.5,
you
name
it
you
know,
and
then
you
know
you
can
start
adding
dependencies
of
like.
I
don't
even
know
like
I'm,
I'm
a
spring
idiot
and
then
like
generate
it,
and
it
gives
you
essentially
a
an
application.
Starter
kit
right
similar.
We
have
things
like
you
know,
ruby,
you
know
being
able
to
bootstrap
stuff
we're
gonna
see
with
backstage
itself.
A
It
uses
npx
to
be
able
to
to
bootstrap
your
backstage
app,
and
so
I
think
that
this
sort
of
software
template
pattern.
We're
starting
to
see
this
show
up
in
a
whole
bunch
of
different
places.
Carlo's
asking:
is
there
a
go
equivalent
for
spring?
I
don't
think
there
is,
and
so,
but
I
think
you
know
we're
starting
to
see
like
hey.
Maybe
you
could
build
a
go
spring
starter
spring
initializer
using
something
like
backstage.
A
This
is
something
that
we're
looking
at
through
the
lens
of
tonzu,
too
yeah
go
people
like
to
suffer
well,
I
would
say
that
go
is
minimalist.
That's
probably
that's
probably
the
way,
I
would
say
it
and
yeah,
but
these
are
all
built,
as
sort
of
you
know,
plug-ins
on
this
core
sort
of
developer
portal
platform,
which
I
think
is
really
interesting.
A
So
there's
that's
what
we're
going
to
start
with
there's
an
architecture
overview
here
where
essentially,
you
have
a
user
talking
to
a
ui
in
the
browser
and
there's
a
whole
bunch
of
integrating
using
react.
Browser
ui
into
the
main
ui.
So
one
way
to
extend
backstage
is
to
essentially
extend
the
react,
app,
that's
all
running
client
side
and
then
those
things
can
actually
then
come
through
to
a
set
of
back
ends
that
can
be
running.
A
You
know
close
attention
to
as
we
go
through
this
stuff,
and
so
what
you
find
is
that
there's
some
core
components
here
and
then
the
plugins
actually
like
to
get
a
chance
to
actually
run
their
stuff
in
context
with
everything
else,
and
so
this
here
ends
up
being
the
service,
catalog
plugin
and
then
there's
different
plugins
that
actually
go
ahead
and
run
and
there's
a
circle
ci
one
there's
a
lighthouse
one.
I
haven't
used
lighthouse,
so
that
looks
interesting
and
then
so
there's
there's
documentation
on
installing
plug-ins.
A
Essentially,
fundamentally,
it
starts
with
the
ui.
A
plug-in
is
a
ui
thing
and
then
from
there
you
can
actually
plug
in
the
the
back-end
stuff
if
it
needs
it
and
there's
like
plug-ins
that
are
purely
client-side
stand-alone
plug-ins
is
what
they
call
them
and
then
there's
service-backed
plug-ins,
where
either
the
service
is
running
a
instance
of
the
service
for
you
or
perhaps
the
service
is
actually
you
know.
A
A
A
Now,
let's
go
ahead
and
let's
get
going
and
so
we're
going
to
do
getting
started,
and
so
we're
going
to
be
viewing
this
as
a
user,
not
as
a
contributor
and
so
ultimately-
and
this
is
where
I
start
looking
dumb,
because
I
don't
know
how
this
stuff
works.
I
am
I
thought,
with
my
with
my
computer,
to
get
node
up
and
running
before
this
episode
to
make
sure
that
at
least
I
could
run
the
singular
command
here.
A
But
this
is
like,
as
far
as
I've
gotten
is,
is
essentially
making
sure
that
this
line
works,
and
so
then
we're
going
to
be
playing
with
it.
After
that
so
shane
says
like
any
time
I
see
npm
or
npx.
I
just
run
just
me.
I
I
feel
the
same
way
to
be
honest.
There
is,
you
know
as
much
as
I
think
folks
are
intimidated
by
the
kubernetes
world.
I
feel
intimidated
when
I
start
dealing
with
the
the
node
javascript
npm
world.
This
stuff
changes
too
fast.
A
I've
never
used
npx
before
you
know
yeah,
so
that
carlos
says
we're
gonna
get
into
this.
You
know
backstage
only
works
with
node
v14,
and
so,
if
you
just
go
through
and-
and
you
know,
say
hey,
I
want
to
install
node
on
homebrew,
you
get
v16
and
things
don't
work,
and
so
now
you
have
to
figure
out
how
to
deal
with
an
older
version
of
node.
A
But
what
I
ended
up
doing-
and
I
put
the
notes
here
is-
is
there's
a
guide
that
I
ended
up
following
and
it's
just
the
best
way
to
install
node.js
with
yarn
this
as
a
is
as
of
april
6
2020.
So
I'm
sure
this
is
completely
out
of
date,
but
it
seemed
to
mostly
work
for
me,
and
this
got
me
to
the
point
where
I
was
using
mvm
to
be
able
to
install
14..
A
A
I
can
do
mpm
version,
which
I
think
is
the
latest
and
I
can
do.
I
have
yarn
version
here
too,
and
I
think
I
ended
up
using
homebrew
to
install
yarn
and
then
nvm
to
install
node,
so
yeah,
it's
confusing,
and
so
here's
the
wizard
to
create
an
app,
and
so
the
first
thing
that
we're
going
to
do
is
call
create
app
here
and
the
first
time
you
run
this.
A
I
think
sql
life
probably
seems
right
to
us,
and
so
what
this
is
doing
is
it's
creating
a
whole
bunch
of
files
in
a
specific
structure.
It's
templating
them
and
I
don't
know
what
the
hbs
extension
is
and
then
it's
essentially
calling
yarn
install,
which
is
then
downloading
all
the
dependencies
here
for
this
particular.
A
A
Yeah
this
is
this
is
this
is
the
my
experience
with
with
anything
in
the
node
world?
Is
that
there's
a
spinny
thing
there
and
if
it
fails,
I
have
no
idea
what's
going
on.
I
just
start
googling
stuff
until
I,
like
you,
know,
bang
my
head
against
the
wall
and
get
it
working
and
then
tsc,
I
believe,
that's
the
typescript
compiler
and
for
those
who
are
not
part
of
the
javascript
world.
Typescript
is
essentially
a
dialect
of
of
javascript.
A
That
has
a
lot
of
type
annotations
on
it,
mostly
driven
by
microsoft,
but
pretty
widely
adopted
in
the
in
this
world.
Now
all
right.
So
the
first
thing
here
is
that
we're
going
to
see
it
wants
us
to
go
through
and
points
us
to
mono
repo
app
setup
with
authentication,
which
is,
I
think
you
know
the
next
step
here
in
terms
of
being
able
to
get
this
stuff
going
and
and
then
we'll
look
at
this,
it
created
a
directory
based
on
the
app
name
that
I
gave
it
called
tgik.
A
A
Appearance,
zen
mode,
no
full
screen,
centered
layout,
reset
zoom
there
we
go
all
right.
Let
me
know
if
this
is
readable
for
y'all
all
right.
So
what
do
we
got
so
we
got.
This
is
the
other
thing
that
confuses
me
about
the
node
world.
Is
that,
like
I'm
pretty
sure
I
know
what
package.json
is
at
this
point?
A
This
is,
you
know
essentially
like
the
main
thing,
and
you
talk.
This
has
like
dependencies
plus
a
bunch
of
essentially
like
aliases,
for
running
various
commands
and
there's
a
you
know.
It's
all.
You
know
this
stuff
here.
So
if
you
want
to
upload
to
a
package
manager
that
type
of
thing
so
yeah
so,
but
I
what
is
lerna,
I
have
no
idea
what
this
is.
A
There's
some
yaml
files
here.
These
look
to
be
backstage
specific.
I
don't
know
what
appconfig.yml
this
is
probably
something
for
for
backstage
and
then
there's
a
production.
Okay,
so
there's
a
config
in
production
there
yeah,
so
you
end
up
with
a
whole
bunch
of
random
files.
Here,
good
luck!
It's
like
take
this
you'll
need
it
ts
config.
This
is
for
the
ts,
compiler
and
then
this
is
the
package
lock,
for
which
your
versions
were
okay,
yeah.
What
is
the
learn?
A
thing?
A
A
B
A
Dh.F,
what
is
the
this
size
just
this
size,
not
df?
I
always
well.
You
can
actually
get
the
the
summary
of
the
disk
size
but
yeah
there's
a
lot
of
modules
installed
there.
This
is
the
node
world,
of
course,
and
then
we
got
packages
here.
I
believe
this
ends
up
being
the
app
itself
here
that
actually
gets
pulled
together
where
we
have
app
and
back
end-
and
you
know
okay,
so,
let's,
let's
start
digging
in
here.
A
So
the
first
thing
here
is
that
let's
create
the
monorepo
application,
we
did
that
we
went
through
and
we
created
the
id.
We
chose
sqlite
and
then
we
start
the
back
end
locally.
Let's
give
this
a
try,
and
so
this
is
essentially
saying
yarn
current
working
directory
backend
start.
So
what
is
that
going
to
be
doing
so?
That's
going
to
be
putting
us
here
and
we
have
a
package.json
within
our
package.json,
and
this
is
going
to
be
calling
cli
all
right,
let
her
rip.
Let's
see
what
happens.
A
A
A
A
A
And
then
create,
we
have
templates
that
you
can
create,
so
we
can
create
a
new
react
app
from
within
our
react:
app
yo,
dawg,
all
right.
Here's
here's!
You
know
initializer
for
go
so
create
a
golang
repo
all
right.
So
let's
start
exploring
all
of
this
and
see
what's
going
on
here
and
then
tech
radar.
This
is
their
example
of
like
completely
static
stuff
going
on
here
and
then
settings.
A
We
have
a
profile
theme.
Of
course
we
get
dark
theme.
You
know
it's
not
it's
not
a
web
2.0
app
unless
it
has
dark
theme
and
you
can
set
up
authentication
providers
and
feature
flags
and
stuff
okay.
So
it's
a
great
experience.
It
gives
you
that
sort
of
like
hey,
I
get
a
sense
of
what
the
thing
is,
even
if
I
get
the
sense
that
a
lot
of
this
stuff
is
probably
mocked
up
and
fake,
but
it
gives
you
definitely
gives
you
an
idea
of
what
it
is.
A
You're
building
so
bogdan's
saying
that
this
is
more
like
an
average
sized
project
and
people
about
the
size
of
kubernetes
binaries
right.
It's
like
800
something
megabytes
of
of
dependency.
Here
is
kind
of
crazy.
Okay,
let's
keep
going
here,
so
we
got
that
going,
and
so
what
we
have
here
is
we
have
localhost
3000
is
where
we're
actually
hosting
this,
but
the
backend
is
running
on
7
000.,
and
so
I
don't
know
like
one
of
the
things
I
want
to
see
here
is,
if
I
go
through.
A
A
A
A
Okay,
so
that's
that's
feels
like
we
have
a
thing
here
and
we're
running
this
stuff
up
and
running
the
last
time
I
really
dipped
my
my
my
toes
into
the
node
world
was
when
I
did
the
the
example
server
for
kubernetes
up
and
running
qd-
and
I
did
all
I
you
know-
ended
up
doing
a
lot
of
this
stuff
and
learning
a
little
bit
of
react
and
I'm
sure
it's
it's
really
really
kind
of
out
of
date.
Now
so
khalid's
asking.
A
A
A
I'm
really
thinking
about.
Like
you
know,
how
do
we
actually
provide
that
one-stop
shop
that
integration
point
that
brings
everything
together
for
an
operations
function
similar
to
what
we
have
with
with
with
ides
so
yeah?
So
so
there's
one.
How
do
we
add
existing
apps
projects?
I
don't
know
we're
gonna
figure
that
out
dev
dashboards
for
devs,
but
there's
an
operational
aspect
of
this
also,
I
think
when
because
they're
talking
about
service
catalog,
I'm
still
learning
and
then
effx-
I'm
not
familiar
with
that.
So
I
don't
know
okay.
A
So
let's,
let's
keep
digging
into
this
since
there's
no
auth
currently
configured
you
are
automatically
entered
as
a
guest.
Let's
fix
that
now
and
add
auth,
so
I
went
through
and
so
they
provide.
So
this
is
where
a
lot
of
these
things
get
complicated,
because
the
minute
you
need
to
integrate
with
auth,
especially
within
certain
enterprise
environments,
it
gets
really
really
complicated.
This
is
filing
tickets,
justifying
your
existence
waiting
weeks
to
be
able
to
get
to
the
point
where
you
can
actually
do
this
type
of
of
integration
inside
of
a
corporate
environment.
A
You
know
thing
there,
so
I
what
I
went
through
is,
I
did
go
through
and
if
you
look
at
here
with
github
we're
gonna
use
github,
I
went
through
and
followed
these
instructions,
and
so
I
have
environment
variables
with
a
client
id
and
secret
going
on
already,
and
I'm
really
hoping
I'm
not
going
to
flash
any
secrets
on
the
screen.
But
you
know
we'll
see
how
things
go
so
we're
going
to
open
the
appconfig.yaml
and
then
change
the
auth
provider.
Here
like
this
for
github
and
so
appconfig.yaml.
A
A
I
don't
know
what
the
memory
means.
I
don't
know
enough
about
sql
like
to
say
there
and
then
integrations.
We
have
github
token.
I
don't
want.
I
don't
know
what
that
does
yet,
because
there's
integrations
then
there's
auth
and
so
we're
just
doing
the
off
stuff,
so
we're
going
to
go
ahead
and
do
that
and
that
should
work
and
then
scaffolder
and
catalog.
A
Okay,
and
this
is
pulling
stuff
from
some
example-
yaml
files
that
are
actually
running
as
part
of
this
stuff
here
in
the
backstage
repo
all
right,
so
we're
gonna
have
to
dig
into
that.
So
this
is
where
the
sort
of
the
example
mock-up
data
that
we're
talking
about
is
coming
from
and
we're
gonna
go
from
there
and
then
yeah.
Okay,
a
lot
to
dig
into
here,
yeah
we're
all
yaml
engineers.
Now
that's
definitely
true
eric
thanks
for
thanks
for
sticking
with
us
here.
Okay.
A
A
This
is
not
uncommon
in
the
in
the
node
world
to
be
able
to
think
about
extensibility
at
kind
of
this
sort
of
it's
not
a
framework,
but
it's
not
really
a
library,
this
sort
of
frameworky
source
code-
and
that's
really,
I
think
where,
where
backstage
fits,
I'm
not
super
comfortable
with
it.
It's
not
something.
I
have
a
lot
of
experience
with,
so
I'm
mumbling
through
here.
Okay,
so
we
went
ahead
and
did
that
I
got
the
secrets
all
up
and
running.
A
A
A
The
same
file
modify,
create
app
yeah.
I
think
what's
fascinating
to
me.
Just
to
be
honest
is
that
for
folks
who
are
like
part
of
react,
everything
we're
doing
here
is
second
nature,
and
it's
like
well
yeah.
Of
course
you
want
to
do
that
for
folks
who
are
not
front-end
engineers.
This
is
incredibly
intimidating.
To
be
honest,
I've
nev,
you
know
like
every
time
I
do
this.
I
feel
stupid.
A
A
A
All
right,
let's
decode
this
stuff,
a
little
bit,
because
I
think
I
understand
what's
going
on
here
and
and
folks
who
are
javascript
experts
can
help
me
out
here.
So
when
you
actually
so
essentially,
what
we're
doing
is
we're
passing
an
object
here
that
is
a
set
of
key
value
pairs
and
when
you're
doing
that,
if
the
name
of
the
variable
that
you're
passing
in
is
the
same
as
the
key,
then
this
is
just
syntactic
sugar
for
doing
apis
apis
right.
So
that's
the
same
thing
going
on
there.
A
A
A
A
A
A
A
A
There
we
go,
and
now
I
can
go
through
and
and
this
is
the
the
app
that
I
created
for
github
earlier-
I
can
go
ahead
and
authorized
and
boom.
Now
we
are
we're
here
and
we're
authorized
and
we
got
auth
running
now
and
you
can
see
it.
It
pulls
a
bunch
of
my
like
you
know,
stuff
from
github
and
all
that,
so
we
got
that
up
and
up
and
going
so
chance
like
yeah.
I
think
this
is
one
of
those
things
I
need
this
like
there's.
A
A
So
much
of
it
really
does
come
down
to
these
sort
of
like
hey,
if
you're
doing
machine
learning,
you
don't
know,
what's
going
on
with
web
development
versus
you
know,
versus
back-end
cloud
system,
and
so
yeah
so
like
having
to
know
react
to
be
able
to
actually
control
a
plug
in
here
like
yeah.
If
you
know
react
it's
easy,
if
you
don't
man
you're
going
down
you're,
going
down
a
complexity
curve
that
you
have
to
deal
with,
so
I
view
this
as
an
empathy
building
exercise
for
me.
A
Okay,
so
so
we
got
the
we
got
this
up
and
running.
One
of
the
things
that
I
think
is
fascinating
to
me
here
is
that
I
have
one
level
of
authentication
here
to
backstage
now,
as
I
configure
things
in
backstage
to
maybe
go
ahead
and
start
actuating,
something
in
a
kubernetes
cluster
behind
the
scenes.
A
How
do
I
know
that
the
identity
I'm
using
here
is
the
identity
that's
using
there,
and
it's
very
easy.
This
is
this
is
this
is
the
root
of
a
ton
of
security
issues
where,
where
I
actually
use
one
identity
to
be
able
to
talk
to
something
like
backstage
and
then
backstage
then
tries
to
use
that
identity
or
uses
another
identity.
A
A
And
this
is
the
confused
deputy
problem
and
there
you
go
barney.
Fife
is
the
idea.
You
know
where,
where
you
can
sort
of
trick
backstage
into
in
terms
of
elevating
privileges
that
you
wouldn't
see
otherwise,
and
so
that
ends
up
being.
You
know
something
that
I'm
keenly
looking
at
here
as
we
go
through
this,
and
so
it's
great
that
I'm
off
to
to
backstage,
but
that
doesn't
mean
all
our
off
problems
are
over.
A
There's
the
question
of
like
how
does
backstage
then
off
to
other
systems,
and
how
does
it
translate
my
auth
to
backstage
to
off
to
these
other
systems
and
so
oftentimes?
What
people
will
do
is
they'll
be
like
well,
you
know
backstage
will
be
our
auth
system,
but
now,
if
you
do
have
to
give
somebody
raw
access
to
kubernetes,
it's
very
easy
to
have
those
things
get
out
of
sync
and
so
having
a
single
identity
system.
A
That's
shared
across
these
systems
is
absolutely
critical
and
I
think
that's
one
of
the
reasons
why
I'm
you
know
you
know
looking
at
this
in
context
with
something
like
dex
or
pinniped,
using
pinniped
to
be
able
to
talk
to
these
things
is
going
to
be
really
interesting
over
time,
yeah
carlos
confused
deputy.
Now
you
know
it
right.
This
is
it's
great
to
have
that
name,
because
once
you
see
that
pattern,
you
start
spotting
in
a
bunch
of
places
and
we
have
it
within
kubernetes.
A
It's
like
creating
a
replicas
that
gives
you
permission
to
create
a
pod,
and
so
so
you
know
that's
why
within
kubernetes,
we
view
sort
of
the
the
the
tenancy
you
know
unit
as
being
the
name
space,
because
we
do
actually
make
sure
that
hey
there
are.
You
know
we
try
very
hard
to
make
sure
that
there's
no
confused
deputies
across
namespaces.
A
This
is
one
of
the
reasons
why
you
can't
access
a
secret
across
namespace
boundaries
is
to
try
and
make
sure
that
we
don't
get
into
those
confused
deputies
type
of
problems
yeah,
so
carlos
you're
right.
The
the
right
thing
to
do
here
is
to
to
create
you
know,
to
settle
on
an
idp,
make
sure
that
you
have
the
same
idp
id
provider,
identity
provider
across
both.
A
You
know
something
like
backstage
and
the
underlying
kubernetes
clusters
and
then,
as
backstage,
wants
to
act
into
that
kubernetes
cluster,
they
just
say
well:
user
x
here
means
the
same
thing
as
user
x
there.
That
makes
it
a
lot
easier
to
avoid
these
kubernetes,
these
kubernetes,
the
confused
deputy
things.
So
can
I
add
more
kubernetes
to
this
we'll
get
to
it.
I
want
to
see
I
want
to
see
where
it
goes.
I'm
sorry,
I'm
going
through
here
and
there's
definitely
lessons.
Okay.
A
A
So
I
think
one
of
the
things
that
that
can
happen
here-
and
this
is
where
I
wanted
to
get
to
here-
is
that
this
can
actually
then
go
through
and
there
we
go
yeah.
Let's
do
this.
Okay,
let's
go
through.
This
is
what
I
think
this
ends
up
doing
is:
has
backstage
talking
to
kubernetes
as
a
source
of
information
that
gets
then
gets
showed
you
know
dynamically
into
backstage.
So
I
think
this
is
under
the
s
software,
catalog
or
separate.
I
think
this
is
separate.
A
A
So
this
is
probably
the
front
end
and
then
the
back
end,
which
probably
is
a
proxy
to
the
kubernetes
api,
and
this
is
where
you
can
actually
start
getting
into
some
of
those
con
confused
deputy
types
of
things,
so
we're
going
to
go
through
and
install
the
kubernetes
plugins,
so
so
we're
going
to
go
through
and
let's
create
yet
another
window
here.
Another
tgik
155
tgik.
A
There
we
go
so
that's
up
and
running,
there's
some
common
stuff.
I
think
between
these
things,
all
right
and
then
once
the
package
is
installed,
we
need
to
import
the
plug
into
into
the
app
by
adding
the
kubernetes
tab
in
packages
catalog
entity
page.tsx.
So
this
is
the
stuff
where
this
seems
a
little
bit.
A
A
B
B
A
B
B
A
A
A
B
B
A
A
A
A
A
A
Add
entries
to
the
catalog
at
this
point:
the
catalog
back
end
is
installed
in
your
backend
page,
but
you
will
not
have
any
entities
load
to
get
up
and
running.
Try
out
some
templates
quickly.
So
we
have
this
where
it's
essentially
okay,
let's
back
up
a
little
bit
here
and
go,
I
did
do
the
yarn
ad.
I
did
that
I
did
that
back
here
when
we
look
at
installations.
I
did
run
this
this
yarn
ad
here,
so
that
is.
A
B
A
B
B
B
A
A
A
B
A
B
B
A
A
So
now
it
says,
run
it
locally
and
then
configure
it.
Configuring,
kubernetes
integration
enabling
the
backend
to
collect
objects
from
kubernetes
cluster,
surfacing
your
kubernetes
objects
and
catalog
entities;
okay,
so
let's
go
through
and
we'll
oh,
we
got
some
fun
stuff
going
on
here.
Okay,
so
where
do
we
in
appconfig.yml?
So
now
we're
going
to
teach
our
backend
how
to
actually
talk
to
kubernetes.
B
A
A
B
A
A
That
we're
on
yeah,
I
should
be
using
cube
context,
but
I
just
want
to
make
sure
I
can
copy
this
stuff.
Okay,
we're
doing
the
service
account
thing
skip
tls
verify
I
mean
true:
let's
not
get
stuck
on
that.
It
can
talk
to
multiple
clusters
here,
but
we're
only
talking
to
one
and
then
the
account
token
do.
I
have
to
like
create
that
and.
B
A
B
A
A
Get
you
have
the
default,
one
which
I
believe
that
gives
you
like,
read-only
access
or
no,
I
think,
by
default.
It
gives
you
no
access
right,
yeah,
I
think,
inside
the
cluster.
It
can
probably
do
that
without
doing
that
right.
So
at
some
point
you
know
we
can
go
ahead
and
do
that
yeah.
This
is
the
thing
where
it's
like
we're
giving
it
a
service
account
token
and,
like
you
know,
the
the
right
thing
to
do
is
you
know
I
mean
the
the
easy
thing
to
do
is
create
service
found
kubernetes.
B
B
A
A
A
B
A
A
A
I
know
I
need
to
do
the
alias
I
just
I
like
I
like
typing
it
out
and
especially
when,
like
I,
I
used
to
have
a
lot
of
aliases
that
I
used
all
the
time.
But,
like
you
know
not,
everybody
has
those
and,
I
think,
with
tgik.
It
sometimes
confuses
folks
when
I
have
like
my
own
sort
of
setup
for
all
this
stuff,
okay,
where
we're
at
so
we
have
this
thing
configured.
Well,
okay,
so
what
else
do
we?
A
It
probably
okay,
so
now,
okay,
so
now
we
we
may
have
this
stuff
working
okay,
so
but
like
we
wouldn't
know
right,
because
it's
not
going
to
show
stuff
up
it
doesn't
so.
The
idea
here,
I
think,
is
that
this
is
like
this
isn't
about
this,
isn't
like
a
kubernetes-centric
browser.
This
is
essentially
something
that
can
pull
together.
All
of
your
resources
and
one
of
the
sources
of
truth
is
kubernetes,
and
so
so
now
the
next
step
here
is
we
go
through
and
if
we
go
back,
one
thing
is.
A
A
A
A
B
B
B
A
There's
an
entity-
okay,
so
maybe
okay,
I
think
we
skipped
some
of
the
stuff
in
backstage,
so
that
now
we're
confused
here.
So
let
me
go
through
we're.
Gonna
back
back
up
a
little
bit
here,
software
catalog,
the
configuration
okay
system
model,
core
entities,
components
are
individual
pieces
of
software,
apis
and
resources
are
physical
or
virtual
infrastructure.
You
need
to
operate
a
component.
Cone
is
piece
of
software,
so
it's
a
component
that
we're
talking
about
here
model
so
domain
system
resource
a
component.
A
A
A
Okay,
backstage
and
backpage
service
kit
will
make
it
easy
one
team
to
manage
ten
services.
Okay,
getting
started.
Software
catalog
is
available
to
browse
a
catalog.
If
you
follow
the
installing
the
app
you
should
be
able
to
browse
the
catalog
okay,
so
we
got
that
right
so
we're
here
we
don't
see
anything
in
the
catalog,
but
we
do
in
the
apis
thing,
but
not
in
the
catalog
itself.
A
Adding
components
to
the
catalog
manually
register
components
create
new
component
through
backstage
or
integrate
with
an
external
source.
We
can
go
through
and
register
existing
components
and
then
that
actually
you
point
it
to
github
and
then
within
that
there's
a
whole
bunch
of
stuff.
So
there's
sort
of
a
git
ops
type
of
thing
here
to
actually
pull
this
stuff
out.
It's
important
to
note
that
any
kind
of
software
can
be
registered
in
backstage,
even
if
the
software
is
not
maintained
by
your
company
sas
offerings.
A
So
like
you
can
just
put
anything
in
there
and
it'll
start
showing
up.
All
software
created
through
the
software
templates
are
automatically
registered
in
the
catalog,
in
addition
to
manually,
registering
components,
also
possible
register
components
through
static
configuration,
so
you
can
statically
point
at
stuff
and
then
you
can
teams
owning
the
components
are
responsible
for
maintaining
the
metadata
about
it,
including
the
flow
finding
software
in
the
catalog
starring
components,
integrating
tooling
through
plugins,
okay.
So
let's
go
through
and.
A
A
Oh
there
we
go
all
okay,
so
we
have
artist
look
up
here
and
so,
when
we
click
on
this,
what
it's
doing
is
it's
actually
going
to
github
downloading
this
file
and
following
that
through-
and
it
says,
here's
a
new
component
here-
that
shows
this
stuff
coming
up
and
there's
a
whole
bunch
of
information,
essentially
like
that
it
pulls
together
based
on
the
metadata
there,
oh
where
to
go
here.
So
we
have
you
know,
and
then
we
can
go
through
and
edit
this
and
it's
like.
A
B
A
A
One
of
the
interesting
things
here,
just
just
to
be
clear,
is
that
the
system
of
record
is
get,
and
it
looks
like
what's
happening
is
backstage,
is
using
git
or
other
things,
as
a
system
of
record
to
be
able
to
initialize
its
database,
and
so
there's
a
really
interesting
pattern
in
terms
of
using
you
know
external
systems
like
this
as
a
way
to
actually
pull
this
stuff
in
all
right.
Let's
I
want
to
gets
we're
running
out
of
time
here.
B
B
B
A
A
A
A
A
B
A
B
B
A
A
A
I
have
to
clean
some
of
this
stuff
up
template
all
of
that,
so
it's
actually
creating
the
new
github
repo
for
me
and
then
I
can
link
to
the
repo
and
here
it
is
well
that's
kind
of
swift
kind
of
sweet
and
then
we
can
see
it
in
the
catalog
here
where
boom
there.
It
is
now,
if
I
go
to
that
repo
here,
not
this
one.
B
B
A
A
A
Do
the
new
repo
include
a
github,
I
think
so.
Yeah
yeah
github
workflows
build.yaml,
so
we
essentially
have
it's
trying
to
build,
pull
and
build
the
thing
and
it
kind
of
set
up.
I
mean
it's
kind
of
cool
that
it
actually
set
up
a
bunch
of
cool
stuff
there
right
like
this
is
all
best
practices
on
this
stuff,
which
is
cool.
B
A
B
A
B
B
A
Oh,
you
know
what
happened
you
know.
What
happened
is
that
this
stuff
was
only
storing
stuff
in
ram,
and
so
when
I
restarted
it,
it
actually
register
existing
component
repository
url
is
this
so
so
when
I
restarted
it,
it
lost
that
data
because
we're
essentially
doing
so
it
wants
me
to
log
into
github.
This
got
lost.
A
Okay,
so
I
so
it
sees
the
kind
cluster
here.
It
doesn't
actually
see
the
pods
there.
There
was
a
problem,
retrieving
it
and
so
for
some
reason
it
wasn't
able
to
actually
get
there,
but
I
think
I
understand,
what's
going
on
here,
I'm
going
to
have
to
call
it
here
guys
because
we've
been
going
for
about
two
hours.
A
A
A
A
So
you
could
generate
the
crd
from
this,
but
I
would
look
to
the
crd
to
be
the
source
of
truth
of
where
to
actually
go
and
look
for
your
sort
of
your
your
the
ammo
where
to
go
and
look
for
the
get
repost
with
the
yaml
files.
That
type
of
thing
all
the
auth
stuff
is
incredibly
confusing
in
systems
like
this,
I'm
like
well,
I'm
all
into
backstage,
but
then
I
have
to
also
off
to
github
and
like
how
do
we?
You
know
how
do
these
things
work?
A
Which
tokens
am
I
doing
what
I
honestly
don't
know
like?
There's
small
screens
coming
up
and
I
just
went
through
and-
and
you
know
clicked
yes
because
I
didn't
know
any
other
way.
I
think
in
terms
of
plug-ins,
like
it
has
a
ton
of
plug-in
mechanisms.
I
think
it's
just
like.
Maybe
there's
another
plug-in
for
being
able
to
discover
these
things
and
using
the
kubernetes
stuff
for
that
also.
A
So
I
really
like
the
idea
of
having
a
this
general
idea
of
a
component
being
able
to
aggregate
these
things
into
a
single
sort
of
card
or
home
page
and
then
having
plugins.
That
actually
key
off
of
that
homepage
should
be
go
off
and
get
other
data
and
integrate
that
and
show
things.
I
think
that's
really
interesting.
I
think
there's
a
lot
to
like
there
and
I
think
that
idea
definitely
has
legs
the
doing
this
through
the
lens
of
like
building
a
monolithic,
react
app.
A
These
are
folks
that
have
like
you
know
their
operators
through
and
through
asking
them
to
configure
kubernetes
is
enough
right
and
that's
something.
We're
working
on
is
getting
them
comfortable
with
kubernetes,
getting
them
comfortable
with
kubernetes
and
something
like
react
to
be
able
to
deploy
something
like
backstage
hoo
boy,
that's
that's
a
whole
nother
thing,
and
so,
and
then
carlos
is
saying,
is
that
select
the
plugin
from
the
ui
catalog
and
click
yeah
like?
Are
you
saying
they
have
that
or
like
yeah?
A
I
think
having
a
a
plug-in
mechanism
that
is
not
as
intertwined
with
the
actual
app
would
be
interesting.
I
think
you
know
you
look
at
the
maturity
of
the
wordpress
world
right.
You
can
install
wordpress
plugins
and
they
fundamentally
change
wordpress
without
understanding
php
right
so,
like
I
feel
like
over
time.
Something
like
this
could
get
to
the
point
where
it
actually
starts
feeling
like
wordpress
in
terms
of
of
of
being
able
to
actually
use
it
even
as
an
admin
without
actually
understanding
the
underlying
technology.
A
It's
clearly
not
there
right
now,
and
maybe
that's
something
that's
on
their
roadmap
and
something
that
they're
thinking
about.
So
with
that,
thank
you
for
sticking
with
me.
You
know
we're
pretty
much
at
the
two
hour
mark
here.
I
feel,
like
I
learned
a
lot
I
you
know
I
understand
sort
of
where
this
fits
in
a
lot
of
great
ideas,
understand
sort
of
the
the
level
of
skill
and
commitment,
then
to
start
using
this
stuff
also,
which
is
really
really
interesting.