►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
So
shortly
to
me
my
name
is
Eng
indiri
and
I'm
working
at
a
at
palumi
as
a
customer
experience,
architect,
I
do
Cloud
transformation,
enablement
and
I
really
love
to
continuous
everything
deploy
delivery.
You
name
it
I
put
also
my
socials
there.
If
you
would
like
to
follow
me
so
I'm
on
X,
LinkedIn
and
so
on,
and
so
on
so
feel
free
to
drop.
A
follow
and
I'm
joined
in
this
talk
by
Kingdon
and
I
will
pass
to
you
Kingdom
that
you
can
introduce
yourself.
B
A
Yeah,
absolutely
you're
right.
That's
going
to
be
awesome
so
again
for
everybody
who
who
watch
this
I,
give
you
a
short
introduction
on
palumi.
We
will
give
you
a
short
introduction
on
flux
and
a
short
introduction
on
Backstage
before
we
head
over
to
the
demo
and
see
every
Parts
in
action
working.
This
is
going
to
be
awesome
so
shortly
for
palumi
with
palumi,
you
have
the
option
and
we
have
here
this
three
pillars
to
have
built,
deploy
and
manage
you.
Can
everything
is
under
control
with
pollumi
on
the
build
part?
A
You
can
use
your
already
your
your
programming
language,
your
generic
programming
language,
for
example,
python
or
go.
You
can
reuse
your
Ides
of
your
choice.
You
can
use
your
your
package
manager,
which
you
already
use
for
your
language,
so
there
is
no
change
for
you,
so
you
just
continue.
You
import
the
library
in
your
your
IDE
for
div,
and
now
we
come
to
the
middle
part
to
provide
us.
You
can
choose
from
a
huge
variety
of
providers.
A
So,
if
you're
going
to
create
a
deployment
for
AWS,
for
example,
you
and
you
want
to
do
this
in
Python-
you
just
import
the
Pi
Pi
package
into
your
IDE
of
your
choice
and
yeah
start
to
program
your
your
infrastructure,
easy
as
it
is
then,
on
the
right
side.
Of
course,
polumi
embeds
perfectly
fine,
with
every
git
system
available
outside
of
every
Source
control
system
and
also
pulubi
is
not
inverse.
If
it
not
dictates
you
which
CI
CD
approach
you
have
to
take,
so
you
can
and
reuse
your
existing
pipelines.
A
You
can
build
new
pipelines
out
of
this,
so
there
is
a
polumi
CLI,
there's
a
polumi
kubernetes
operator,
and
you
can
tailor
pulumi
perfectly
fine
for
your
workflow.
You
have,
and,
of
course
we
have
also
when
you
use
the
polumi
cloud
offering,
for
example,
you
can
connect
also
your
your
identity
manager,
so
you
don't
need
to
create
some
local
users,
but
again
this
is
on
the
polumi
cloud
side,
just
short
again
to
say:
okay,
what
what
are
the
the
core
features?
As
I
mentioned
before
any
language
we
offer
State
Management,
we
offer
secret
management.
A
This
is
something
you
get
included,
but
with
every
approach
with
the
batteries
included,
but
replaceable
you
can
switch
the
palumi
secrets
management
to,
for
example,
Vault
if
you're
using
our
vault,
you
can
use
also
the
AWS
secret
manager.
So
it's
really
up
what
you
have
on
your
site
and
you
can
run
previews.
So
this
is
very
helpful
to
see
if
any
changes
are
there
which
could
maybe
affect
your
infrastructure
with
Crypt
effect.
Maybe
your
your
running
service,
because
some
of
the
changes
are
maybe
more
inversive
and
needs
a
delete
and
Recreation
of
the
resource.
A
You
will
get
the
feedback
and
then
you
can
embed
it
in
your
pull,
request
flow
and
decide.
Then,
if
you
want
to
go
with
it
or
maybe
you
need
to
ensure
that
the
services
are
still
running
with,
maybe
a
more
bigger
architecture
see
I
see
the
integration
I
just
mentioned
that
you
can
integrate
it
with
every
CI
CD
system.
You
have
on
your
side
web
hooks.
That's
really
really
awesome!
You
have
the
option
to
to
connect
different
web
hooks.
We
recently
launched
also
the
Microsoft
teams
integration.
A
Customer
asked
for
this
and
slack
integration
is
already
there.
Generic
web
Hook
is
also
present,
so
that's
really
cool
rest
API.
So
if
you
have
the
situation,
you
need
to
communicate
with
the
palubi
cloud
offering,
for
example-
and
you
can
just
connect
this-
we
will
see
the
snow,
for
example,
in
backstage
the
full
we
backstage
plugin
is
communicating
with
the
rest
API
automation.
Api
is
an
advanced
topic
where
you
can
programmatically
call
pulumi,
so
you
don't
need
to
have,
for
example,
the
palumi
CLI
commands
running
up
or
down
or
destroy.
A
You
can
just
use
the
problem,
automation,
API
and
which
is
also
very
useful,
dashboards
and
reports.
This
is
something
which
makes
sense.
If
you
have
shared
responsibility
team,
then
you
can
use
this
functionality
again,
just
to
mention
this
polumi
is
completely
open
source.
A
So
there
is
no
no
need
to
to
to
put
some
credit
card
details
into
the
purumi
cloud,
offering
the
problem
with
Cloud
offering
has
a
free
tier.
You
can
just
use
this
so
pollumi
Cloud
taking
care
of
your
States
and
that's
it.
So
from
this
part,
let
me
quickly
deep
dive
on
what
means
deep
dive.
A
little
bit
give
you
an
overview
and
high
level
overview
of
how
the
polumi
architecture
is
built
up.
So
first
this
this
picture,
really,
you
will
see
in
several
of
our
presentations
and
every
time
I
see
the
picture.
A
A
A
Here
we
use
go
and
I
say,
pollute
me
up,
the
CLI
will
detect
we're
going
to
use,
go,
it
will
start
the
go
language
host
and
then
communicate
with
the
CLI
to
say,
okay,
what
resources,
what
what
commands
we
are
actually
doing
here:
okay,
yeah
CLI,
that's
our
our
Communicator
here
and
the
main
core
engine,
and
then
we
start
to
find
out
what
kind
of
resources
we
are
creating.
So,
for
example,
in
my
code,
in
my
go
code,
I
want
to
use
AWS
I
want
to
start
an
eks
cluster.
A
For
example,
I
want
to
provision
as
a
free
bucket
pulumi,
the
textures
that
we
are
asking
here
for
the
AWS
provider.
It
will
download
the
AWS
provider
if
it's
not
already
present
on
your
machine
and
then
will
start
to
to
communicate
via
grpc
for
create,
update
and
delete.
So,
for
example,
if
I
started
a
fresh
program
and
defining
an
S3
bucket,
pullumi
will
see
this
and
say:
okay,
and
we
come
here
to
the
last
point
to
the
state
file.
A
It
will
check
the
state
file
and
say:
is
there
already
an
S3
bucket
with
this
name
present?
If
not,
we
have
VR
create
situation,
go
to
the
provider.
Does
the
create
come
back
with
the
results
like
the
URL
like
the
ID
and
everything
we
get
from
the
cloud
provider
will
store
the
state
in
the
State
Management.
As
you
can
see,
we
have
the
purumi
cloud
service.
We
have
also
the
option.
A
If
you
say,
hey
I
want
to
run
this
on
my
local
S3
bucket
artifactory,
you
name
it.
You
can
all
run
them
and
take
care
of
your
state
or
use
the
polony
cloud
service.
It
will
detect
any
changes,
gift
feedback
in
a
crate.
Of
course,
everything
is
new
if
I
start
up
the
second
time,
I
pull
me
up
and
maybe
I
change,
something
it
will
then
check
and
say:
okay
did
I
deleted
the
resource.
It
will
call
the
delete
on
the
provider
weight
that
the
provider
did
all
the
deletes
feedback.
A
The
result
go
to
the
state
file,
also
remove
the
resource
from
the
state
file
and
give
us
all
the
information.
If
it's
an
update,
you
can
imagine
that
polumi
is
doing
also
the
the
updates
and
put
the
changed
values
into
the
state
file
and
give
me
as
a
user
the
feedback.
This
is
following
properties
which
got
changed.
A
Oops
I
put
this
a
little
bit
too
quick.
So,
let's
head
back
to
this
one
as
I
mentioned
State
file
you
can
handle
on
the
cloud
or
you
can
handle
on
your
own.
So
next
view
is
our
programming
model
to
say:
okay,
how?
How
does
a
palumi
program?
Look
like
a
pului
project,
so
everything
starts
with
the
project.
A
A
project
is
actually
and
then
comes.
The
pulumi
program
is
where
our
polumi
yaml
file
lies
in
the
Paloma
yaml
file
defines
which
runtime
we
are
using.
If
it's
a
go
or
type
script,
there's
a
runtime
flag,
and
this
is
the
definition
of
your
polumi
program.
We
have
also
the
concept
of
so-called
Stacks
Stacks.
You
can
think
about
different
instances
of
your
program.
A
You
maybe
have
a
kubernetes
environment
with
no
GPU
supported
nodes,
because
it's
maybe
not
necessary,
or
maybe
the
notes
are
not
dimensioned,
for
example,
on
a
prod
system,
because
you
want
to
save
money
or
you
want
to
to
just
test
a
different
thing
and
the
clothes
that
you
get
to
prod.
Maybe
you
say:
Okay
I
I
ramp
up
the
the
infrastructure.
This
is
everything
what
you
can
do
inside
this
text.
You
can
overwrite
the
values
you
defined
or
you
can
keep
the
values
the
same.
The
building
blocks
for
our
pollumi
program
are
the
so-called
resources.
A
The
resources
are
really
like
the
lowest.
We
call
it
always
a
Lego
piece
to
say,
okay.
This
is,
for
example,
my
S3
bucket.
This
is
my
eks
cluster
and
then
you
start
to
to
put
them
together
and
say:
okay
for
a
kubernetes
cluster.
This
is
the
amount
of
nodes
I
would
like
have,
and
this
is
maybe
a
oh
I
can
see,
enabled
and
so
on
and
so
on.
Every
resource
has
an
input,
but
also
has
an
output
field.
A
So
the
moment
the
resource
is
created,
for
example,
you
can
get
the
output
and
now
comes
the
magic.
You
can
start
to
stitch
them
together
and
say:
okay,
the
output
of
one
is
the
input
for
the
next
resource
and
now
comes
the
clever
part
also
of
perumi
pulumi.
Let
me
switch
here.
Punumi
can
detect
when
you
create
your
program
dependencies
to
each
other.
A
It
builds
the
graph
and
say:
okay,
this
is
the
dependency.
This
is
the
tree,
I
need
to
fulfill
and
then
first,
the
kubernetes
cluster
gets
created,
maybe
depending
on
the
cloud
provider
also
the
nodes
get
created,
gets
attached
and
then
I
can
use
the
the
the
installation
of
a
Helm
shot,
because
now
everything
is
up
and
running.
So
here
we
have
a
dedicated
chain.
A
Last
but
not
least,
you
can
also
create
outputs
from
a
project,
and
this
is
something
I
will
show
also
in
the
demo,
so
we
can
use.
We
can
set
inputs
to
a
project.
We
can
get
outputs
and
use
the
output
from
one
polo
me
project
as
an
input
for
the
next
polonic
project.
This
is
called
stack
references,
and
this
is
very
powerful
and
very
interesting.
Where
is
potential
use
cases?
One
of
the
use
cases
could
be.
A
We
have
a
separation
of
concerns
inside
the
company,
so,
for
example,
the
networking
team
is
taking
care
of
creating
the
network
and
tell
the
people
who
are
consuming,
for
example,
a
subnet
and
so
on,
and
just
as
an
output,
the
ID
of
the
subnet.
So
when
I
create
now
my
application
or
my
infrastructure
on
top
of
the
networking
I
just
reference
to
the
subnet
and
use
this,
for
example,
or
I-
can
separate
also
with
different
velocities.
A
So
maybe
the
the
networking
layer
doesn't
change
so
much
so
I
I
take
every
part
out
of
the
of
the
less
chain,
quicker
changing
parts
and
run
them
and
things
which
have
maybe
a
higher
velocity,
because
it's
application
based
or
it's
development
team
working
on
this
can
be
a
known,
polumi
stack.
We
see
this
in
the
demo
and
it's
one
of
my
features
which
are
really
powerful,
and
then
we
come
into
the
situation,
what
we
call
it
pulumi
micro
Stacks
to
say.
A
Okay,
we
go
away
from
this
monolithic
infrastructure
definitions
where
it
takes
like
20
to
more
minutes,
depending
on
the
count
of
resources.
You
have
to
roll
out
any
changes
to
smaller
packages
to
smaller
Stacks,
which
give
you
a
quicker
feedback,
and
you
don't
need
to
wait
so
long
and
of
course,
when
something
happens,
the
blast
radius
is
also
not
that
deep,
because
you
maybe
not
accidentally
delete
your
S3
buckets
because
there's
three
buckets
belong
to
a
different
stack
where
you
don't
have
any
rights.
B
Okay,
perfect,
let
me
get
my
screen
share
going
here.
B
All
right,
hopefully
my
slides
work-
you
can
see
everything
all
right,
so
this
is
going
to
be
the
very
brief,
very
easy
for
beginners
flux
in
two
minutes.
The
main
concept
here
is
the
user.
Experience
should
always
be
simple
for
devs,
so
the
developers
are
just
pushing
their
changes
to
get
it's.
The
desired
state
is
what
we're
talking
about
and
they
go
automatically
to
kubernetes.
So
this
is
very
simple.
So
there
are
a
couple
of
variable
potential
variable
things
in
here.
The
developer.
B
Pushing
changes
to
git
git
is
just
a
version
store
here,
so
we
here's
also
the
possibility
that
something
goes
wrong.
We'd
like
to
know
when
everything
is
fine,
with
a
notification
of
some
kind.
So
this
is
all
part
of
git,
Ops
and
developer.
Pushing
the
changes
to
get
is
only
part
of
the
story,
so
there's
also
this
concept
of
reconciling
and
drift.
So
if
you've
created
some
infrastructure
and
the
infrastructure
is
changed
in
place,
it
can
drift
from
what
is
defined
as
a
desired
state.
B
So
get
Ops
will
put
it
back.
That's
part
of
GitHub,
so
this
is
distinguished
from
regular
imperative.
Ci
CD
experience
that
many
people
have
already
been
familiar
with
for
many
years
by
the
fact
that
we're
using
declarative
configuration
artifacts,
which
are
generally
item
potent
they
can
be
applied
as
many
times
as
we
want
without
changing
the
semantics
at
all,
they
should
be
reconciled
continuously
according
to
git
Ops.
So
that's
from
the
git
Ops
working
group
and
so
back
to
the
easy
version
for
our
visual
Learners,
like
I
said
this
should
be
very
simple.
B
The
user
is
pushing
to
get
and
it
goes
to
kubernetes
Via
flux,
but
there
are
some
ways
that
it's
a
bit
more
complicated
than
that
in
technical
terms
that
make
it
better.
So
what
we're
talking
about
is
on
kubernetes.
We
have
the
ability
to
subscribe
from
a
customization
to
a
git
repository.
These
are
technical
terms
for
moving
Parts
in
flux,
but
the
customization
is
actually
doing
the
applying
the
git
repository
is
doing
the
fetching.
B
But
what
we
can't
do
is
set
up
a
subscription
automatically
with
our
web
hook
on
the
internet,
so
GitHub
or
gitlab,
or
wherever
we're
hosting
our
source
code,
probably
has
capability
to
send
us
a
notification
right
away.
All
of
the
major
providers
have
this
capability
and
you
set
up
a
receiver
so
that
reconciles
the
git
repository
right
away,
which
then
notifies
the
customization
it's
time
to
pull
and
apply
the
changes
to
kubernetes.
So
the
experience,
though,
should
be
very
easy
and,
like
this
very
fast
for
the
user,
you
should
feel
right
away.
B
You
push
your
changes
they're
on
the
cluster,
so
that
requires
a
little
bit
of
extra
configuration
in
some
cases,
but
on
kubernetes
we
can
negotiate
subscriptions
automatically,
so
some
places
it's
needed.
Some
places
it's
not
and
if
you'd
like
to
know
more
about
flux,
we're
going
to
see,
but
also
there
are
public
Dev
meetings.
You
can
come
ask
us
questions
in
various
forums.
Flux
is
developed
under
the
open
in
the
cncf
and
we
have
a
public
roadmap
and
a
transparent
RFC
process.
So
if
you
want
to
participate
in
our
development
also,
we
offer
support.
B
So
you
can
contact
me
if
you'd
like
to
follow
up
on
any
of
these
support,
questions
that
you
might
have
after
you
try
what
we're
going
to
show
you
so
one
more
thing:
I
wanted
to
explain
about
flux
is
the
bootstrap
process.
The
typical
bootstrap
process,
which
is
different
than
what
we're
going
to
see
today
so
like
this,
is
get
ups
and
flux
is
doing
get
UPS.
So
how
does
flux
itself
actually
get
installed
on
the
cluster,
or
is
that
where
it
goes,
does
it
go
in
gear?
B
Is
that
a
job
that
we
can
delegate,
perhaps
we'll
see?
The
answer
is
yes,
of
course,
it
does
go
and
get
typically
that's
the
default,
but
it
is
up
to
you.
You
can
change
the
way
that
you
install
or
use
flux.
There
is
no
one
way.
Flux
is
also
called
the
git
Ops
toolkit,
because
it's
flexible,
you
can
build
it,
so
copying
flux
into
git.
That
is
an
optional
decision
that
you
can
make
it's
typically
what
we
do
if
you're
using
bootstrap
according
to
the
manual,
but
so
real
quick.
B
What
is
bootstrap
in
case
you've,
never
seen
flux
before
the
definition
of
the
flux
controllers
are
called
components,
they
go
into
a
file
and
then
the
other
file-
that's
created
here
in
this
directory
structure-
is
the
business
end
of
flux,
the
config,
so
we'll
see
more
of
that
as
we
go
along,
but
there
are
a
few
other
things
that
bootstrap
takes
care
of
for
us
and
the
the
security
issue
of
how
do
we?
B
So
this
is
probably
a
private
repository
where
we
want
to
put
our
infrastructure,
so
we
have
to
negotiate
a
way
for
that
to
come
into
the
cluster,
so
authentication
and
we'll
need
right
access,
but
only
temporarily,
since
we're
writing
to
the
cluster.
If
we
were
doing
bootstrap,
those
are
all
things
that
we
would
need,
but,
like
I
said,
that
is
an
option.
We
can
use
an
operator
to
install
flux
or
we
can
use
one
of
many
solutions
that
provide
flux.
B
A
Okay,
I
I
just
used
your
time
to
charge
my
headphones
because
I
heard
them
that
they
are
beeping,
so
let's
switch
to
them.
Okay,
so
you
can
hear
me
perfectly
yes,
okay,
perfect
fine!
So
then,
thanks
for
the
introduction
of
Lux-
and
you
will
see
also
in
our
demo,
some
of
the
things
we
saw
on
the
slides,
for
example
the
oci
artifact
I-
really
love
this
and
I
really
try
to
use
this
as
much
as
possible.
A
For
example,
our
palumi
operators,
also
the
helm,
chart
us
oci
artifact
available
that
it's
actually
the
currently
the
only
way
to
get
this.
So
that
makes
things
very,
very
easy,
especially
with
our
customers,
because
they
sometimes
they
have
an
art,
Factory
or
Harbor.
They
can
use
this
as
a
proxy
and
just
have
it
internally
always
available.
Okay,
so
I
will
activate
the
share
again
and
switch
back
so
okay,
now
we
come
to
the
last
part
Kingdom.
You
can
see
this.
The
the
screen
yes
backstage
I,
see.
A
It
at
all-
okay,
that's
just
me
who
see
this
okay,
so
backstage
what
is
backstage
it's
one
of
the
pieces
here
in
our
platform
tool
and
yeah
backstage
is
similar
to
all
of
the
pro
products
and
projects.
We
see
here
an
open
source
tool.
It
was
created
by
Spotify
and
then
later,
oh,
you
cannot
see
this
very
well
with
my
slides.
It
was
later
donated
to
the
cncer.
So
it's
probably
currently
is
it
a
graduated
or
sandbox
project.
I
have
to
look
this
up,
but
it's
around
this
at
the
maturity
level
of
the
cncf.
A
So
that's
awesome,
so
you
can
use
backstage
inside
your
company.
You
don't
need
to
be
concerned
about
any
license,
changing
and
so
on.
There's
the
cncf
behind
this.
There
are
also
office
hours
you
can
participate
and
so
on,
but
I
think
that's
not
in
the
scope.
Currently.
A
What
does
it
offer
us?
So
if
we
have
here
our
front
end,
we
can
use
backstage
as
a
front
end
here
as
a
communication
with
our
customers
with
our
internal
customers
to
say.
Okay,
we
offer
them
a
way
to
interact
with
our
platform
to
be
tunnel
to
have
a
selection
of
of
golden
paths
to
say:
okay,
I
can
choose
from
a
golden
path,
which
is
maybe
the
agreed
way
on
provisioning
on
deploying
stuff
on
creating
stuff,
because
it
has
a
scaffolding
functionality.
A
So
I
can
create
my
my
my
scaffold
of
a
project
of
the
infrastructure.
What
we're
going
to
see
now
and
then
I
can
just
amend
it
with
additional
informations
from
the
teams.
Maybe
they
have
some
requirements,
they
want
to
deploy
it
in
a
specific
region.
We
can
gather
the
information
we
can
deploy.
This
second
part
is
also
we
have
another
way
for
visibility.
We
have
a
a
tool
where
we
can
see
what
is
already
in
place,
so
imagine
you're
in
a
in
a
bigger
bigger
company,
and
you
start
typically
working
on
some
Enterprise
service.
A
Like
the
typical
ldap
lookup,
you
know,
there's
an
ad
directory
whatever
with
all
the
people
working
in
the
company
and
then
every
team
I
worked
in
place
where
every
team
created
the
hundreds
iteration
of
this
kind
of
service
reading
out
the
the
directory
of
the
company.
Now
you
can
see
inside
backstage
what
is
already
there,
there's
a
powerful
search
functionality
and
then
I
can
say:
hey
there's
already
a
team
working
and
I
can
see
the
name
of
the
team
who
belongs
to.
A
B
A
A
So
we
just
we
just
talked
about
this.
So
what's
the
benefits,
of
course,
yeah.
We
can
now
roll
out
the
compliance
and
best
practices
to
our
internal
Community
to
our
developers,
for
example.
So
we
don't
need
to
take
care
about
if
how
stuff
is
created.
We
know
there's
always
this
way
and
it
has
already
the
best
practices
in
place
and
we
have
the
central
localization
of
of
the
whole
software
we're
going
to
manage
and,
of
course
we
have
here,
a
software
ecosystem.
A
I
just
talked
about
the
collaboration
possibilities
we
get
with
backstage
part
of
just
what
we
see
now-
and
this
is
also
an
interesting
thing,
because
I
used
the
the
power
of
Backstage,
the
customization
and
the
extensibility
I
used
here
in
the
demonstration,
because
we
installed
here
not
only
backstage
and
doing
some
configuration
to
talk
with
GitHub
and
so
on.
That's
one
part,
but
with
works.
The
company
kingdom
is
working,
they
have
a
backstage
plugin.
A
The
company
I'm
working
for
polony
is
has
also
a
backstage
plugin,
so
we
just
amended
the
backstage
installation
with
both
of
the
plugins,
to
give
you
the
to
give
here
in
the
demonstration
in
you
when
you
try
this
out
the
most
visibility
of
everything.
So,
as
you
see
the
the
what
Kindle
just
mentioned,
you
see
the
git
repository.
You
see
the
helm
releases,
you
see
it's,
it's
really
amazing
and
you
don't
need
to
leave
here.
A
Maybe
you
don't
even
have
access
to
the
kubernetes
cluster,
but
now
you
have
a
place
where
you
have
the
possibility
to
see
what
is
installed
and
could
even
trigger
do
some
basic
day.
Two
operations
so
do
at
all
operations.
What
you
could
maybe
not
do
before
restarting
a
pod,
for
example.
Maybe
you
had
to
call
your
operations
team
and
ask
them
hey?
Can
you
restart
the
Pod
it's
behaving
strangely,
you
can
do
this
now
on
your
own.
Okay,
talk.
A
It's
an
important
point:
the
part
of
this
whole
webinar,
let's
head
over
to
our
demo,
so
asking
the
slot
machine
and
say:
okay,
what
are
we
going
to
use?
Yes,
we're
going
to
use,
go,
we
we
use
AWS
and
we're
going
to
use
an
eks
as
part
of
the
infrastructure.
Yes,
of
course
that
was
not
a
random
thing.
A
It's
not
it's
not
staged,
and
so
on
so
I
I'm
sure
if
I
could
trigger
this,
but
we
going
to
stick
now
with
go
AWS
and
eks
again.
I
give
you
a
little
bit
more
detail
about
the
architecture,
because
it's
a
little
bit
more
sophisticated
than
the
slot
machine
is
telling
us
so.
First
of
all,
this
is
our
very,
very
basic
infrastructure,
so
we
have
our
github's
platform
and
behind
this
kitos
platform,
this
little
avatar
on
the
top
is
our
platform
team.
They
own
the
gitos
platform
and
they're
like
okay.
A
How
are
we
going
to
set
up
this
again?
Please?
This
is
an
opinionated
solution.
Every
github's
platform
could
may
look
different
depending
on
the
company,
depending
on
all
the
circumstance-
and
this
is
the
power
also
Kingdom
mentioned.
You-
can
adapt
everything
on
your
needs,
so
this
github's
platform
consists
of
one
polumi
stack.
A
We
just
had
the
the
the
presentation
about
different
possibilities
with
micro
Stacks,
so
we
created
here
a
palumi
program,
I
called
it
github's
infrastructure,
which
defines
one
part
of
the
github's
platform,
and
this
is
the
eks
because
we
said
we
want
to
use
prolong
and
we
want
to
use
kubernetes
and
the
power
of
kubernetes
Kingdom
had
also
the
five
pillars
of
git
Ops
and
we
use
kubernetes
as
a
control
plane
here
so
I
provisioned,
an
eks
of
course
vncs
and
all
the
stuff
everything
vpcs.
Everything
is
also
behind.
This
I
just
dropped
this.
A
Second
part:
the
second
stack-
and
this
is
a
separation.
Again,
it's
the
architectural
decision
we
made
here
to
say:
okay,
then
we
have
the
backstage
installation.
We
don't
let,
for
example,
backstage
run
as
part
of
a
container
and
so
on
with
maybe
our
kubernetes
cluster
just
in
case
say:
okay,
we
want
that
backstages,
maybe
always
available.
We
want
to
connect
other
systems
to
it
and
so
on.
So
we
just
separated
this
one
and
I
installed
backstage
here
using
a
fargate,
for
example,
a
serverless
approach,
so
I
create
a
Docker
image
out
of
it.
A
A
container
image
with
my
backstage
installation,
with
all
the
the
customization
I,
did
installation
of
the
beefworks
plugin
and
everything
and
upload
the
container
image
to
ECR
configure
fargate
configure
our
manage
the
database
here,
a
postgres
database
from
AWS
and
everything
gets
delivered
via
the
application
load
balancer
of
AWS.
So
this
is
the
the
backstage
installation
separated
from
each
other.
A
Next
point
is
we're
going
to
install
flux.
Flux
is
the
ignition
here
in
this
case,
so
I
installed
and
again
this
is
an
operation
we
had
a
discussion
before
we
did
the
talk
with
Kingdom
about
hey.
There
are
different
ways
and
so
on.
There
are
also
downsides
on
some
of
the
insertion.
You
have
to
see
with
what
you
can
live
here.
A
So,
in
this
case,
I
installed
flux
using
polumi
using
the
polumi
resource
called
hen,
the
Henry
sauce
and
I
just
installed
flux,
but
start
then
to
say:
okay
now
everything
else
will
be
managed
by
flux,
so
I
create
the
custom
resource
of
looks
called
hand
release.
So
they,
coincidentally,
have
the
same
name.
The
helm,
release
custom
resource
is
already
in
the
flux
world,
so
it
will
be
delivered
via
pulumi
and
also
saved
in
the
git
repository
and
Zone.
A
A
Next
thing,
I
mentioned
this
before
the
backstage
installation,
installation
of
the
palumi
plug-in
kubernetes
and
refworks
plugin.
That's
fine.
Everything
points
to
a
GitHub
organization,
so
I
created
a
GitHub
organization.
Everything
is
wired
up
with
a
GitHub
application
set
up,
so
backstage
can
communicate
completely
with
our
organization
can
do
a
creation
of
a
pull
requests
of
creation
of
repositories.
Everything
what
we
maybe
need
and
now
comes
the
last
point
when
we
then
release
our
githubs
platform
to
our
self-service
github's
platform
to
our
development
team.
A
The
development
team
just
communicates
now
with
the
backstage
with
the
front
end,
so
we
have
a
unique
unified
interface
with
our
customers
and
then
does
everything
they
are
allowed
and
they
are
agreed
on
to
do
provisioning,
seeing
communicated
okay,
that's
that's
the
infrastructure,
so
let
me
show
you
now
decreases
in
action,
so
I
let
my
screen.
B
A
A
This
is
the
organization
I
talked,
so
there
are
three
free
repositories.
One
repository
contains
our.
Where
is
it?
Yeah
contains
our
polumi
code
for
for
for
managing
the
infrastructure
and
so
on.
We
will
go.
I
will
share
later
also
my
IDE
for
this
one,
so
no
variables
or
details.
This
is
one
of
the
repositories.
The
second
repository
I,
clicked
wrongly
here,
defines
now
the
template
we're
going
to
create.
A
So
that's
that's
very
important
to
say,
dear
backstage
this
is
the
scaffolding
I
created,
so
we
will
have
a
look
into
this
one.
So
here
this
is
backstage
terminology,
so
I
say
to
him:
hey
get
me
some
input
of
the
of
the
developers.
They
can
choose
from
some
things
here,
in
this
case
we're
going
to
create
a
static
website.
So
this
is
all
the
informations
I
gather,
I
need
the
stage
the
stage
and
so
on
then
I'm
going
to
render
all
the
informations
everything
gets
rendered
into
the
system.
A
And
last
but
not
least,
we
also
see
here
the
pull
request.
So
we
would
like
still
that
platform
team.
Maybe
we
don't
have
the
confidence
or
the
maturity,
or
it's
not
part
of
our
of
our
release
process
because
of
whatever
regulation.
There
should
be
still
a
human
looking
on
top
of
this,
so
we
create
a
pull
request.
People
get
a
notification.
You
can
now
attach
GitHub
actions
or
get
get
workflows,
which
maybe
also
do
some
automating
testing
to
give
you
some
feedback
and
we
will
get
the
output
of
the
URL.
A
So
that's
one
of
the
repositories
and
last
but
not
least
because
we
would
like
to
point
flux
to
unrepository.
There
is
this
pollumi
infrastructure
repository,
so
everything
what
gets
provisioned
will
create
a
pull
request
in
this
repository
I
created
a
customized
folder
we're
going
to
use
the
customization
resource
of
flux,
to
point
to
this
fold
and
say
hey
when
there
is
a
change
of
the
shot
of
this
git
repository.
Please
have
a
look
into
customization.
Folder
I
did
not
put
a
customization
yaml
inside
of
this
to
organize
I'm
like
I.
A
Don't
know
how
much
there's
inside
and
I
don't
want
to
work
now
with
adding
stuff
now
on
the
resource
text,
so
you
can
Define
flux
like
this
to
say,
look
into
this
and
then
create
on
top
on
yourself,
a
customization
virtual
customization
yaml,
but
everything
which
lands
here
will
then
automatically
picked
up
from
flux
deployed
on
the
git
repository
and
then
the
pollumi
operator
kicks
in,
because
it
listens
to
the
specific
crds
of
the
type
program.
We
will
see
this
in
the
code
and
then
starts
to
provision
this
stuff.
A
A
Okay,
so
you
mentioned
Kingdom
that
you
could
see
this
very
well
so
I.
Take
this.
Take
your
word
on
this
one.
So
this
is
the
first
stack
on
our
architecture:
diagram,
the
github's
infra
part,
so
everything
written
and
go
so
you
can
look
up
the
definitions
and
so
on.
But
to
give
you
a
short
insight
and
everybody
who
worked
with
AWS
and
eks
knows
that
I
cannot
start
now
a
fresh
one
because
it
will
take,
depending
on
the
the
the
the
load
on
the
region
up
to
10
15.
A
Whatever
minutes
to
get
the
things
up
and
running
so
eks
can
be
sometimes
very
slow,
so
we
create
our
VPC.
We
create
everything
we
need
for
the
networking.
Then
we
see
one
of
the
features
already
here.
We
export
because
we
want
to
consume
some
of
the
networking
informations
in
our
other
stack,
so
I'm
not
going
to
redefine
the
VPC
I'm
going
to
reuse
the
VPC,
but
I
export
some
of
the
informations
already
here.
So
another
stack
can
consume
this
so,
for
example,
the
route
table
at
the
bpc.
B
A
And
last
next
part
is
I
Define
here
my
kubernetes
cluster,
so
I
can
set
up
the
informations
and
accordingly,
what
I
need,
if
I'm
coming
now
into
the
situation
and
say
hey,
this
should
not
be
hard
coded.
This
should
be
separated.
I
can
put
this
in
the
config
file,
so
there's
a
polumi
config
file
where
I
can
Define
now.
Everything
which
should
be
configurable
I
can
take
this
out
here.
In
this
case,
it's
for
demonstration
purpose.
So
it's
here,
it's
very
hard
coded
and
any
changes
should
trigger
has
to
be
changed
in
code.
B
A
Then
we
we
finished
everything.
This
is
the
state
where
I
say:
okay,
I'm
going
to
export,
also
the
cube
config.
This
is
sometimes
very
helpful
if
you
want
to
run,
for
example,
K9s
or
cubecutive
commands,
you
can
get
the
Q
config
file
from
your
cloud
provider,
but
what
I'm
going
to
do,
because
everything
should
be
programmatically,
I'm
already
starting
to
to
provision
a
new,
so-called
pollumi
provider.
A
A
Want
to
use
patching
and
so
on,
because
not
every
Helm
shop
thought
about
this,
that
we're
going
to
use
next
stage
and
you're
not
able,
because
of
the
organization
to
set
in
the
thought
templates
back
and
so
on
the
this
label.
So
that's
the
thing,
but
it's
very
important
because
that's
the
way
backstage
know
how
to
look
up
the
stuff,
so
here
I
gave
it
a
kubernetes
ID.
This
is
later
configured
also
in
backstage.
A
Yes,
the
the
the
the
lookup
of
the
kubernetes
plugin
works
with
this
approach.
It's
interesting
and
makes
some
some
some
forces
us
to
do
some
customization
here
with
the
values
you
see
now.
I
start
to
deploy
the
flux
so
I'm
using
the
oci
artifact
here,
just
push
it
because
it's
already
palubi
uses
the
latest
version
of
the
helm
SDK
underneath
so
it
can
handle
an
oci
artifacts.
Also.
A
See
I
had
to
look
up
now
the
values
file
and
check,
where
are
the
labels
set
up
and
so
on?
So
this
is.
This
was
very
painful
because
I
have
to
go
through
all
the
stuff
and
set
the
labels.
And
yes,
if
you're
in
a
production
environment
you
already
maybe
set
stuff
up,
because
you
want
to
have
the
service,
Monitor
and
so
on
and
so
on.
In
this
case,
I
had
to
go
through
this
now
comes
the
part.
What
I
mentioned.
A
Also
some
of
the
stuff
were
not
able
to
configure
I,
should
do
a
pull
request
later
into
the
flux,
Community
provider
and
also
the
operator,
because
there's
also
the
situation
and
I
patched
now
the
deployment.
So
you
see
what
I
talked
about
dependency,
I
put
now
a
heart
dependency
and
said:
hey,
please
execute
this
part
of
the
code
only
when
the
flux
part
here,
the
flux
release
is
done
because
now
I
want
to
do
some
some
patching.
A
You
don't
need
this
part
when
your
Helm
chart,
when
you
write
your
own
Helm
chart,
for
example,
and
you
have
full
control
to
this
third
party
Helm
charts
either
you
fix
it
on
your
site
or
you
do
it
on
Upstream
here.
In
this
case,
I
did.
A
Now
we
come
to
the
next
part:
I
Define,
the
helm,
repository
resource
and
I.
Tell
now
flux,
listen
you're,
going
to
not
you're
going
to
deploy
now
the
The
polumi
Operators
I
Define
the
helm
repository
here
again.
I
use
the
type
oci,
because
I
also
want
to
deploy
the
pollumi
operator
via
the
oci
artifact
and
again,
because
we
would
like
to
see
in
the
weaveworks
plugin.
We
would
like
to
see
also
the
information.
Of
course
we
have
to
annotate.
Also
this
resource.
A
We
have
to
set
the
label
and
then
we
use
the
helm
release.
Everything
is
done.
We
come
to
the
next
point.
We
now
create
a
hand,
release
programmatically
same
thing,
annotating
the
labels-
and
you
can
see
now
here.
I
also
do
some
additional
stuff
here.
In
this
case
I
say:
hey
Helm,
normally,
don't
do
the
crd
parts,
it's
not
part
of
it,
but
the
people
from
fluxo
the
community,
around
flux,
created
also
a
nice
approach
to
take
care
to
overcome
the
shortcomings
of
the
CRVs.
B
Yes,
that's
that's
one
of
the
most
important
features
of
Helm
controller,
for
sure
is
the
ability
to
upgrade
crds
and
for
anyone
who's
not
familiar
intimately
with
Helm.
You
should
understand,
if
you're
using
Helm,
to
install
an
operator
that
has
a
crd,
it
could
be
problematic.
So
this
this
is
a
solution
for
that,
based
on
flux,
yeah.
A
Absolutely
nice
and
I
love
this
that
it's
already
thought
about
this,
because
otherwise
you
start
to
separate
the
stuff.
You
say:
Okay
first
deploy
the
crds
Via
GitHub
raw
yaml
to
the
repository
with
the
specific
version
attack
and
so
on,
and
when
this
is
rolled
out,
then
please
then
do
the
helm.
Release
I
mean
you
can
imagine.
This
makes
things
life
very
complicated.
A
Now
I
had
to
use
also
some
Advanced
topics
of
flux.
Also
here
so
I
I
deployed
everything
now
comes
the
situation
that
the
the
Lumi
operator
is
the
same.
Didn't
thought
about
that
people
going
to
use
backstage
so
I
I'm
in
charge
of
this
so
I'm
going
to
take
a
pull
request
on
the
spot
for
the
demonstration
I
didn't
want
to
change
this
so
I'm
using
here
now
the
post
renderer.
This
is
also
very,
very
cool.
This
is
part
of
the
helm
inbuilt
into
Helm,
so
you
can
create
post
renderers.
A
The
cool
thing
with
flux
is
that
they
already
have
some
some
post
renders,
for
example,
customized.
So,
in
this
case,
I
say:
hey,
use,
customize
and
use
strategic
merging,
so
I
could
Define
all
the
missing
parts
on
the
deployment
and
just
say
now:
do
a
strategic
merge
of
the
stuff
and
it's
not
going
to
to
break
so
I
just
created
now
here
at
the
missing
things,
I
say:
hey,
you
will
find
that
deployment
and
the
name
of
the
deployment.
A
A
You
have
also
the
option
to
use
the
patch
json's
6902,
whatever
that
means
where
you
can
use
op
path
and
value
and
I
think
it's
probably
nice
for
some
cases
where
a
strategic
merge
is
not
possible
because
it's
not
deterministic
or
whatever
I'm,
not
so
deep
into
the
law
of
the
whole
Json
stuff
yeah.
But
you
could
use
also
this
one.
B
Just
to
add
some
color,
the
the
two
different
patch
types
they
still
sort
of
notionally
exist,
but
in
a
modern
flux
and
in
modern
customize
they've
both
been
replaced
with
patches.
So
there's
one
directive,
you
can
use
now
called
patches
for
anyone,
who's
not
intimately
familiar
with
flux.
This
stuff
all
probably
looks
completely
foreign,
but
if
you
are
a
flux
user,
hopefully
this
looks
familiar
if
not
uncanny.
It's
like,
like
he's,
been
saying
another
one
of
the
most
important
features
of
flux.
A
Yeah-
and
yes-
that's
probably
due
to
my
because
I
worked
started
with
customized,
so
this
was
part
of
the
customer,
so
I
felt
welcome.
I
will
check
the
patch
one.
So,
yes,
you
have
the
option
to
use
a
post
renderer,
which
I
found
very,
very
useful.
So
in
this
case
I
overcome
a
shortcoming,
but
I
think
maybe
it's
for
your
company,
where
you
are
obliged
to
label
the
team,
the
the
cost
center
and
whatever.
A
So
you
have
now
the
way
with
flux
to
do
this
and
then
I
do
some
some
magic,
for
example,
the
problem
access
token
using
the
palumi
secret
engine
underneath
and
I
just
set
the
pulumi
path
as
a
secret,
and
you
can
see
the
seal
is
completely
not
visible.
I
can
commit
this,
it's
not
possible
to
to
decompress
this
oil
decrypt
this
and
that's
it.
So
that's
that's
the
part
to
deploy.
A
Last
but
not
least,
we
also
have
to
say
to
flux,
hey
and
don't
forget.
There
is
a
repository
to
look
for
any
changes
where
all
the
stuff
for
pollumi
license
so
again:
I
Define,
a
git
repository
I,
enable
the
stuff
because
I
want
to
see
the
stuff
and
here's
the
magic
I
point
now
to
the
plume
infrastructure
repository
which
we
saw
before,
which
is
containing
now
every
provisioned
stuff.
You
can
go
much
more
crazy
with
this.
You
can
separate
them.
You
can
say:
okay,
everybody
has
their
own
repository.
A
B
A
Okay,
that's
probably
that
the
battery
is
dying.
Is
it
the
microphone.
A
Sure,
okay,
that's
probably
my
yeah
I
mentioned
I
used
the
time
when
you
presented
to
charge
them
but
yeah
they
don't
hold
anymore.
So.
B
A
I
mentioned
this
one,
so
I
create
a
git
repository
playing
git
repository,
pointing
to
a
git
repository
backstage
is
no
what
I
say
with
Texas.
This
is
a
public
repository,
so
I
don't
need
to
set
any
credentials.
I
could
set
some
credentials,
SSH
keys
in
this
case.
This
is
a
public
one.
So
I
don't
need
to
say
to
flux,
say
you
will
see
them
because
they
are
publicly
available
and
now
I
create
an
another,
not
confusing.
With
the
customization
approach.
You
normally
know
with
the
customization
yaml.
A
This
is
a
resource
called
customization.
I'm
sure
that
you,
you
can
explain
this
a
little
bit
better
than
me
did
the
fine
details,
but
this
is
a
customization
resource
where
we
point
now
the
source
ref
to
the
git
Repository
and
now
I
also
set
the
path.
I
say:
hey,
please
look
into
this
folder.
You
will
find
kubernetes
manifest.
A
There
is
no
customization
yaml,
which
is
client-side,
and
it's
not
Deployable
to
to
a
kubernetes
cluster
where
we
can
do
some
patching
and
all
this
stuff,
because
here
I
did
not
want
to
take
care
about
Jay
about
yaml
and
adding
stuff
dynamically.
As
I
said,
I
throw
the
stuff
in
and
good
guy
flux
has
this
functionality
to
say:
I
gotcha,
when
in
the
folder
there
is
no
customization
yaml
I
can
still
handle
this,
because
I
will
take
here
to
create
a
virtual
one.
Oh
that's
it
so.
A
It's
deployed
last
part
service
accounts
that,
for
example,
our
backstage
user
can
see
the
resources
and
so
on.
So
as
a
good
security
guy
I,
of
course
gave
the
backstage
service
account
the
class
start,
minerals
yeah.
You
need
to
Nerf
it
down
for
your
use
case,
I
just
shot
with
the
highest
thing
on
this
one
and
gave
him
the
cluster
admin
and
yeah.
That's
it
so
reading
creating
a
token
for
this
backstage
user,
because
that's
the
way
we
configure
backstage
using
the
service
account
token.
A
B
A
Point
that's
a
big
thing.
So
now
we
come
to
the
last
part
before
we
see
moving
picture
from
Kingdom
and
The
Backstage
deployment,
similar
approach,
just
we
use
different
resource
again
we
get
our
VPC
ID
because
we
say
we're
going
to
create
new
subnets
on
the
same
VPC,
so
I
just
created
new
subnets
availability
zones.
So
this
is
for
everybody
who
is
into
the
cloud
architecture.
A
Very
interesting,
I
created
also
a
load
balancer
in
this
case
HTTP,
because
there
is
no
easy
inbuilt
way
from
AWS
to
give
us
an
URL
with
https
https
I
mean
some
cloud
provider
offer
this
here.
Not
and
I
just
didn't
want
to
point
some
of
my
domains
on
this
for
just
the
purpose.
So
it's
HTTP,
don't
do
this
in
prod
created
The
Listener.
A
A
So
if
our
gate
can
communicate
with
this
one
I
created
an
ECR
repository
to
upload
the
Dover
image,
give
it
a
lifecycle
policy,
so
I
don't
have
hundreds
of
images
lying
around
doing
the
iron
Magic
of
what
the
the
fargate
instance
can
do,
because
it's
assumed
policy
assumer
role.
So
this
is
everything
set
up.
I
just
go
over
this
because
it's
not
that
interesting.
A
Then
we
come
to
the
part
where
we
create
our
Docker
image.
So,
as
you
can
see,
I
checked
out
backstage,
and
this
is
now
goes
to
the
way
backstage
is
working.
You
need
to
clone
it.
You
need
to
change
the
code
pieces
and
so
on.
I
think
there
are
enough
videos
to
check
on
Backstage
if
you're
interested
just
short,
and
you
just
create
a
new
backstage
app
with
the
CLI
inside
the
folder,
and
then
you
point
the
pulumi
docker
provider
to
it
and
say
pulumi:
please
build
now
a
Docker
image
out
of
it.
A
A
The
lifecycle
policy
to
reduce
the
amount
of
stuff
and
then
I
do
a
yeah
and
fargate
task
definition
put
in
here
some
informations
inside
what
we
need,
and
so
on,
and
so
on
network
security
groups
and
to
Nerf
it
more
down
to
say
here
in
this
case,
I
again
opened
it
quite
widely
to
say:
okay
and
Ingress
egress
is
quite
open,
but
of
course
you
could
also
tune
this
down
and
say:
okay,
I.
The
target
instance
should
only
expose
the
port
of
Backstage.
There's,
not
anything
else
to
do
this
and
that's
fine.
A
A
If
I
want
now
to
deploy,
this
I
can
say
now,
pull
me
up,
I
can
say
pollumi
preview
and
it
will
run
and
I'm
sure.
In
this
case
my
AWS
token
is
expired.
So,
let's
see
doing
a
polo
me
up,
I
did
not
change
anything,
so
normally
I'm
not
expecting
any
any
changes
and
minus
y
minus
f
is
just
a
jump
over
some.
A
How
do
you
say
this
asking
telling
us
hey
I
want
to
do
you
really
want
to
do
this
and
so
on?
So
here
in
this
case,
I
know
but
I'm
going
to
do
and
you
see
here,
I
get
no
changes,
there's
nothing
is
changed
and
the
image
is
still
the
same.
There
is
no
change
on
this
one.
If
I
go
the
same
for
the
follow
me
github's
infrastructure,
it
should
also
not
give
us
any
any
changes.
So
I
can
be
very
confident
here
to
run
the
stuff.
A
So
let's
finish
this
one
again,
if
I
would
stop
something
new,
it
would
give
me
the
full
list
of
of
changes,
creation
and
so
on,
and
then
I
can
decide
on
this
one.
But,
as
you
can
see
here,
there
is
no
changes
and
yeah
everything
is
set
up
and,
as
you
see,
anything
which
is
secret
is
automatically
hidden
by
pulumi.
You
can
also
set
to
secret
manually,
so
you
never.
A
B
Us
all
right
so
I
know
that
we've
got
git
repository
and
we've
got
a.
You
gave
me
the
link
for
the
dashboard,
yes
I'm,
trying
to
find
our
history
here.
Okay,
so
we've
got
our
backstage
dashboard,
which
appears
to
be
up
and
running,
that's
pretty
cool
and
we
can
click
around
a
little
bit
and
see.
Let's
look
at
flux.
B
First,
okay,
so
we
see
flux,
see
some
details
about
flux
here
and
we
I
know
we
can
go
in
to
see
the
kubernetes
definition
of
flux
and
what
resources
here
so
we
have
pods.
These
are
all
of
our
flux.
Pods
that
looks
good.
B
A
You
can
show
the
polumi
operator
also,
if
you
want,
because
that's
you
see
also
the
the
dashboard
and
when
you
scroll
up
a
little
bit.
Yes
just
a
second,
so
perfect,
and
then
you
can
see
also
the
the
pulumi.
So
we
aggregate
the
informations
of
the
polony
cloud
here.
So
you
have
all
the
informations
by
hand
and
can
see
the
stuff.
So
what
you
can
do
now
you
have
now
the
role
as
a
developer.
A
A
You
can
see
the
code
also
of
the
template,
that's
very
cool,
because
now
we
have
a
transparent,
a
transparent
way.
I
can
participate,
so
Kingdom
can
say
now:
hey
I,
don't
like
this!
Oh
hey!
There
is
something
missing,
create
a
pull
request,
tell
the
platform
team
that
there
is
something
missing,
because
you,
as
a
Dev
team,
maybe
know
at
better
what
is
missing.
So
that's
one
of
the
thing.
A
So
there
is
a
definition.
It's
all
wired
up,
as
we
said
and
yeah.
That's
I
think
I
introduced
this
before.
B
B
I
I
guess
I
need
my
head
tag
here
been
a
while,
since
I've
written
an
HTML
document
in
full.
B
A
I
think
that's
fine,
it
should
look.
It
looks
pretty
good,
we'll
see
if
it
doesn't
work
and
the
input.
Other
things
depends
now.
You
can
get
more
information
out
of
your
people,
so
this
is
just
my
thing,
so
they
put
the
select
stack.
You
can
also
hard
code
and
say
everything
which
gets
created
via
backstage
is
always
development,
and
then
you
do
the
propagation
of
stages,
maybe
on
a
different
approach.
A
A
B
A
Okay,
the
component
is
important,
so
that's
the
reason.
I
created
a
folder
with
the
name
of
the
the
this
project,
because
backstage
is
always
looking
for
the
catalog
info.yaml,
so
I
want
that
it's
a
Pearson,
backstage
and
backstage
is
configured
to
scan
the
whole
organization
for
this
specific
yaml
file
automatically.
So
I
get
Auto
discovery
of
all
my
stuff
via
the
catalog
info
yaml
separate
I
mean
I,
have
separation,
but
still
aggregation
at
the
end.
So
you
do
what
a
good
developer
always
do.
You
approve
your
own
work
list.
A
We've
created
it,
so
you
can
assume
it's
goody
so
and
now
I
share
quickly
my
screen,
because
we
would
like
to
see
some
some
action
on
my
site.
So,
okay.
A
A
Via
K9s
and
Q
config,
yes,
of
course
you
could
do
it
so
I'm.
Now
the
platform
engineer
again
and
I
can
see
now
on
the
crds.
Let's
look
if
our
program,
yes,
our
program,
no,
it's
not
delivered
currently,
so
maybe
you
can
trigger
the
because
flux
has
an
interval.
A
How
often
it
checks-
because
maybe
you
don't
want
to
stress
your
apis
so
often
with
stuff,
like
hey
check,
keep
on
checking
the
stuff
and
so
on
so
and
to
trigger
the
story.
You
maybe
can.
A
B
A
B
To
the
flux
UI
here
and
Source
I
think
is
what
I
want
to
synchronize.
So
it's
57
seconds
ago,
so
yeah.
A
I
use
the
flux
reconcile
command
also,
so
you
can
do
this
on
everything
and
let's
hope
that
it's
working
now,
as
I
said,
if
the
demon
gods
are
not
hating
us.
A
A
The
HTML
tag,
so
what
you
could
do
just
go
to
the
pool
to
the
repository.
You
just
approve
the
pull
request
and
fix
the
part
there.
So.
A
B
Yeah
I
can
see
what
it
is
already
I
think
we
need
to
make
sure
these
are
all
consistently
indented.
There
might
be
something
we
can
do
in
our
backstage
template
to
make
that
work.
A
B
A
B
Just
gonna
sync
this
so
that
we're
like
I,
said:
if
you
have
a
receiver,
you
won't
have
to
do
that,
but
we
haven't
configured
web
hook
receivers.
So
hopefully
we
can
see.
A
Okay,
it's
there,
it
works,
so
you
can
now
click
on
the
dashboard
on
the
palumi
console
and
can
see
also
the
rollout.
So
you
see
there's
already
an
update
happening,
so
you
have
to
go
to
yeah
I.
Don't
know
why
the
first
one
failed,
but
you
should
get
the
URL
so
under
overview
or
you
can
copy
it
from
there.
B
Yeah
so,
and
then,
of
course,
what
I?
What
I
want
to
do
now
is
go
back
and
fix
my
link
so
that
it
actually
links
back
to
this
page.
A
Okay,
yeah
yeah,
of
course,
yeah,
of
course,
yeah
you
can
now,
okay,
you!
You
absolutely
understood
this
now
why
it
would
maybe
make
sense
to
give
every
developers
now
the
link
influx
to
their
own
repository,
for
example.
You
could
now
here
make
a
pull
request
to
additional
git
repositories
and
then
point
just
to
the
git
repository.
What
the
development
team
is
is
owning
and
then
they
can
change
the
infrastructure
on
their
own.
A
Yeah
it
you
can
see
in
the
palumi
activity
monitor
if
if
the
change
is
already
propagated
to
so
when
you
click
on
death,
again
to
the
stack
to
the
stack
on
death
and
activity,
and
it's
not
so
it
looks
like
you
have
to
trigger
flux
again.
The
flux
repository.
A
That's
always
when
I
do
a
demo
and
you're,
probably
too
it's
like
in
real
life.
You
don't
wait
like
this
two
minutes.
It
doesn't
pain
you,
but
you
know
things
like
geez,
something
didn't
work.
So
let's
hope
that.
A
A
A
Okay
and
we
say
play
from
current
slide.
Okay,
so
we
saw
the
demo
now
wrap
up
this.
We
do
I
mean
we
saw
now,
and
we
talked
about
this
away-
that
we
created
now
a
platform
with
a
highly
self-service
approach.
In
this
case.
Yes,
it's
a
static
page
and
so
on.
There
is
much
room
for
improvement,
but
the
engine,
the
automation
works.
You
can
get
stuff,
you
get
information,
I
mean.
What
is
missing
here
would
be
now
to
say:
I
need
a
grafana.
I
need
a
promoters,
I
need
that
YDC
and
so
on.
A
That's
all
things
you
can
now
create
creating
a
service
in
AWS,
so
Kingdom
would
not
look
into
some
git
locks
events,
but
would
look
up
in
in
a
Prometheus
on
a
grafana
this
stuff,
if
you
want
to
know
more
here,
are
some
follow-up
links,
so
the
link
to
Backstage
the
link
to
weaveworks
palumi,
with
all
the
documentation,
direct
links
to
the
flux,
CD
and,
of
course,
the
link
to
the
demo
repository
it's
here
in
the
bottom,
and
if
you
have
an
AWS
account,
you
can
easily
just
start
pulling
me
up
and
you
should
get
the
infrastructure
up
and
running.
A
If
you
want
to
get
backstage
up
and
running,
you
have
to
see
that
you
add
the
the
production
file
to
it.
Currently,
everything
if
you
run
it
like
this,
it
will
not
use
fargate
and
everything,
because
it's
the
the
local
stuff
doesn't
use
this.
It
uses
an
SQL
light,
so
feel
free
to
adapt.
This
then
or
reach
out
for
us,
and
we
can
help
you
also
to
get
the
specs
section
up
and
running.
But
with
this
saved
that's.
B
It
thanks
so
much
for
joining
us
everyone
in
the
audience
and
thank
you
and
game
for
the
wonderful
presentation,
yeah.
A
B
So
where
should
people
go
if
they
want
to
address
us
with
questions
we
well,
let
me
think
you
can
come
to
the
flux
channel
on
the
cncf
slack.
That's
one
place.