►
From YouTube: Intro to Kubernetes, GitOps, and Observability Hands-On Tutorial - Joaquin Rodriguez & Tiffany Wang
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Intro to Kubernetes, GitOps, and Observability Hands-On Tutorial - Joaquin Rodriguez, Microsoft & Tiffany Wang, Weaveworks
This tutorial offers newcomers a quick way to experience Kubernetes and its natural evolutionary developments: GitOps and Observability. Attendees will be able to use and experience the benefits of Kubernetes that impact reliability, velocity, security, and more. The session will cover key concepts and practices, as well as offer attendees a way to experience the commands in real-time. The tutorial covers: - kubectl - K9s - Metrics (Prometheus) - Dashboards (Grafana) - Logging (Fluent Bit) - GitOps (FluxCD) Attendees will be able to walk through the steps via a browser-based platform. Instructors will lead the topics and help to troubleshoot. Prerequisites: A computer with a modern browser (Edge, Chrome, Safari, Firefox) GitHub ID with 2FA enabled.
A
So
hi
everybody.
Thank
you
so
much
for
joining
us
today,
and
many
thanks
to
kubecon
and
cloudnativecon
for
having
us
we're
really
excited
to
be
here
in
our
session
today.
We're
going
to
be
covering
an
introduction
to
kubernetes,
git,
ops
and
observability
we're
going
to
start
out
with
a
few
introductory
slides
before
moving
on
to
the
hands-on
tutorial
portion
of
our
session
today,
I'd
like
to
kindly
ask
you
to
ask
questions
in
chat
and
we
will
be
having
a
dedicated
q
a
session
following
the
workshop
and
to
get
us
started.
B
A
And
I'm
tiffany
wang,
I'm
a
solutions
architect
on
the
customer,
success
team
at
weaveworks
and
I'm
originally
from
southern
california,
and
I'm
now
based
in
london
and
like
joaquin.
I
work
with
customers
to
streamline
delivery
and
deployment
to
kubernetes
clusters,
both
on
premise
and
in
public
cloud
following
get
ops
so
before
we
continue
on
with
the
introductory
slides
I'd
like
to
invite
you
all
to
register
for
the
hands-on
section
of
our
session
today.
A
If
you
could
please
navigate
to
https
cube101.dev,
the
username
and
password
are
displayed
on
the
screen
and
hopefully
might
be
available
somewhere
in
chat.
But
if
it's
helpful,
the
username
is
cube
and
the
password
is
capital
v
at
symbol,
valencia,
22
exclamation
point
and
once
you've
conducted
the
basic
auth
to
the
registration
page
you'll
need
to
register
with
your
github
username
once
you've
registered.
A
So
while
I
give
you
a
few
minutes
to
do
that,
I'll
begin
with
an
introduction
to
kubernetes
since
you're
all
here
at
cubecon.
This
is
information
that
you
probably
already
know,
but
we
can
start
from
the
very
beginning
and
talk
about
how
kubernetes
is
an
open
source
cloud
native
computing
foundation,
project
for
container
orchestration.
A
It
was
initially
created
at
google,
and
now
it
is
maintained
by
cncf.
Kubernetes
allows
you
to
define
declarative
configuration
to
manage
containerized
workloads
and
services,
and
kubernetes
kubernetes
is
cloud
native.
It's
highly
distributed
resilient
to
infrastructure.
Failure
and
outages
enables
frequent
releases
and
it
provides
automate,
automation
and
observability
self-healing
and
horizontal
scaling
service
discovery
and
load
balancing,
and
it
is
scalable
it's
capable
of
running
on
premises
and
in
public
cloud
or
a
mix
of
both.
So
you
can
have
a
similar
deployment
experience
regardless
of
target
cloud
cloud
provider.
A
A
We
have
the
scheduler,
which
determines
where
workloads
should
run
in
your
cluster,
and
we
also
have
an
additional
cloud
controller
manager
which
handles
any
cloud
provider
specific
logic
on
the
right.
We
have
three
work
nodes
and
worker
nodes
are
typically
where
your
workloads
will
get
scheduled
to
run.
A
A
A
A
Now
a
container
is
an
immutable
copy
of
your
application
code
and
all
of
its
dependencies,
and
it
runs
within
a
pod.
A
pod
is
the
smallest
deployable
unit
in
kubernetes,
and
it
can
include
one
or
multiple
containers.
Containers
within
a
pod
share,
a
network
namespace
and
the
pod
is
ephemeral.
It's
assigned
an
iep
and
you
can
add
metadata
to
it
like
labels.
A
A
A
So
kubernetes
does
a
lot
of
the
heavy
lifting
when
it
comes
to
creating
your
resources
and
scheduling
them,
but
there
are
a
lot
of
resources
to
manage,
especially
in
a
you
know,
microservice
architecture,
and
we
need
a
way
to
reproduce
what
we've
deployed
to
our
clusters
and
we
need
to
also
understand
conclusively
what
it
is
that
should
be
running
in
our
cluster,
and
for
this
we
look
to
get
ops
on
this
page.
Are
the
open
get
ops
principles
that
are,
or
rather
the
git
ops
principles
that
are
managed
by
the
open,
get
ops
group?
A
A
So
if
you're
new
to
get
ops-
and
you
are
thinking
about
all
the
benefits
that
it
can
bring
and
you're
wondering
if
you
have
to
scrap
everything,
it
is
that
you've
built
so
far
and
the
answer
is
absolutely
not.
On
the
left
hand,
side
you'll
see
a
continuous
integration
workflow.
That
starts
with
a
developer,
writing
application
code.
A
A
A
So
weaver's
actually
coined
the
term
git
ops
and
today
technology
has
advanced
to
the
point
where
it's,
no,
it's
not
required
that
you
use
git,
but
some
other
source
control
versioning
system,
but
that
is
where
the
term
came
from.
So
gitops
is
the
practice
of
using
git
to
store
declaratively
defined,
desired
state
and
continuous
delivery
agents
like
flux
to
automate
the
reconciliation
of
current
state
to
desired
state
with
gitops,
ci
and
cd
are
effectively
decoupled.
A
The
flexsource
controller
interacts
with
custom
resources
like
git
repositories,
buckets
helm
repositories
and
helm
charts,
and
in
today's
workshop
we're
going
to
be
focusing
on
the
git
repository
a
flux.
Git
repository
allows
flux
to
know
which
repository
it
is.
You
want
it
to
monitor
and
pull
from
as
well
as
the
branch.
A
We're
also
going
to
be
using
the
customize
controller
which
whose
corresponding
crd
is
the
customization
and
the
customization
custom
resource,
allows
you
to
tell
flux
the
path
within
the
specified
git
repository
in
our
workshop
today
that
flux
should
read.
Pull
resources
from
and
reconcile
to
your
running
cluster
flux
is
able
to
keep
your
kubernetes
in
sync
with
what
you've
defined
in
git
and
it
automatically
and
continuously
reconciles
running
state
to
desired
state.
A
So
now
we've
got
kubernetes
that
easily
allows
us
to
declaratively
define
our
resources
that
comprise
our
applications,
and
we've
got
git
ops
to
streamline
the
operation
operations
by
which
they
get
deployed
to
the
cluster.
We
need
a
way
to
easily
understand
the
goings-on
within
the
cluster,
and
we
can
accomplish
this
with
observability.
B
B
So
if
you
wish
to
participate,
make
sure
you're
part
of
the
org,
the
username
and
password
in
case
for
those
who
join
late,
it's
right
here.
Let
me
see
if
I
can
find
it.
That's
a
username
and
password
and
you
have
to
go
to
coupe101.dev
to
register.
You
should
get
an
email
with
an
invitation
and
once
you
join
you'll
have
access
to
code
spaces,
okay.
So
let's
get
started
so
the
first
thing.
B
C
B
B
B
B
C
D
B
So
essentially,
we
have
a
pre-built
image
for
code
spaces
that
we
have
everything
that
we
need
in
there.
So
it's
pretty
cool,
because
once
you
create
your
code,
space,
we're
gonna
have
a
k3d
cluster.
We're
gonna
have
all
the
deployment,
the
ammos
that
we
need.
We
have
some
cli
tools
already
pre-installed,
so
it's
kind
of
nice
as
a
you
know:
development
environment.
This
is
not
meant
for
production.
We
mostly
use
it
for
inner
loop
development
and
testing,
and
demos
like
like
this.
So
okay,
so
it
seems
like
it's
coming
up.
B
B
A
B
B
Okay,
so,
like
I
was
saying,
I
created
the
code.
Space
typically
takes
like
45
seconds
for
the
environment
to
get
up
and
ready
it's
pulling
an
image,
and
with
this
much
image
like
I
said,
you
know,
it
creates
a
kubernetes
cluster
for
us,
and
it
also
gives
us
all
the
tools
that
we
need
out
of
the
box
right.
We
have
the
yamos
for
deploying
the
applications
that
we
need.
C
B
B
C
B
B
A
B
B
B
B
Oh,
thank
you
that
out
of
the
box,
we
have
some
poor
forwards
defined,
so
these
are
defined.
If
you
click
on
the
reports
you
can
see
here,
we
have,
you
know
prometheus
and
port
30,
000,
imdb,
heartbeat
graphon,
etc.
So
we
have
these
out
of
the
box
that
way
whenever
we
want
to
connect
to
these
services,
we're
able
to
you
know,
connect
to
them,
but
right
now,
since
we
have
not
deployed
the
application
yet
we're
not
able
to
connect
to
them
yet.
B
B
B
This
application
essentially
runs
a
in
memory
movie
database
and
it
accepts
different
requests
right,
like
you
know,
get
and
post
et
cetera,
and
I'm
going
to
be
using
that
as
our
sample
application
for
today's
workshop.
So
the
first
thing
that
we
want
to
do
to
get
this
deployed,
we
created
a
workshop,
manifest
folder.
So
we're
going
to
cd
into
it.
B
And
the
first
thing
we're
going
to
do
is
we're
going
to
create
a
namespace,
so
our
resources
need
a
place
to
live.
So
for
that
we
have
a
namespace
and,
like
I
noted
here
on
the
notes,
kubernetes
namespace
provides
a
mechanism
for
isolating
groups
of
resources
within
a
single
cluster,
and
the
name
of
resources
need
to
be
unique
within
the
name
space,
but
not
across
different
link
space.
B
Imdb,
oh
yes,
thank
you
and
we're
going
to
go
to
imdb.
Okay.
So
in
order
to
create
the
namespace,
we're
going
to
do
coop
ctl
apply
dash
f,
which
the
f
is
for.
You
know
for
file
and
I'm
going
to
apply
the
zero
one
namespace
and
just
like
that,
you
can
see
that
our
namespace
was
created
and
if
I
go,
if
I
just
want
to
take
a
look
at
that
yamo
under
the
namespace
yaml
file,
it's
very
simple.
All
it
is
is
hey
kubernetes.
B
B
So
you
might
hear
a
little
bit
of
everything
I
think
tiffany
says
kodo,
so
I
think
there's
like
a
youtube
video
out
there
that
talks
about
all
the
pronunciation,
so
it's
kind
of
funny,
but
anyway,
so
just
want
to
mention
that
okay,
so
now
to
deploy
our
application,
we're
gonna
use
a
deployment
file
right
and
essentially
this
deployment
file.
Let
me
show
you
how
it
looks
like
so.
B
Like
I
said
you
know
it's
the
kind
deployment
we
want
to
create
this
deployment
in
our
imdb
namespace,
and
this
deployment
is
going
to
reference
this
image
right
now
we're
using
github
container
registry,
but
you
can
reference
any
content
registry
that
you
like
another
popular
one,
is
docker
hub,
we're
going
to
pass
in
a
few
arguments
to
our
application.
You
know
we're
saying
that
we
want
it
to
run
in
memory
and
we're
passing
in
the
zone
in
the
region,
which
is
in
this
case
it's
dev.
B
Deploy
so
as
you
can
see
right
away,
our
application
was
our
deployment
was
created
and
we
can
verify
that
by
doing
coop,
ctl
get
pods
dash
and
imdb
dash
n
means
what
namespace
we
are
referencing.
So
in
this
case
it's
imdb
and,
as
you
can
see,
20
seconds
ago,
we
have
a
pi
of
the
name.
Imdb
that
was
was
created,
okay
cool,
so
our
app
is
up
and
running.
It's
created,
okay!
Well,
so
then,
let's,
let's
access
it
right.
So
let's
call
this
endpoint,
I'm
using
http
http
pi,
which
is
an
http
client.
B
You
can
use
coral
if
you
choose
to.
We
chose
this
one
because
it
was
just
you
know:
it's
pretty
easy
to
use
and
very
human
readable.
But
if
you
choose
to
use
chrome,
you
can
do
that
as
well.
So,
okay,
so
let
me
copy
paste
this,
oh
by
the
way.
If
you
get
this
message
right
here,
you
say
allow
that
way.
You
can
copy
paste
into
the
terminal.
B
B
B
B
B
B
So
in
this
case,
for
example
like
I
want
to
see
my
prometus
metrics,
so
if
I
just
click
on
send
request,
you
can
see
that
you
know
the
response
here
on
the
right
or,
for
example,
if
you
want
to
query
all
our
actors,
you
can
see
here,
50
cents
is
there
or
like
movies,
for
example,
okay.
So
it's
working
right!
Everything
is
good.
Everything
is
great.
So
so
that's
great!
B
B
It's
going
to
create
a
port
forward
for
me
automatically
and
I
can
access
the
swagger
docs
for
that
application.
I'm
just
gonna,
try
it
out
and
it's
all
good.
You
can
first
execute
oh
execute
it.
Thank
you!
Okay.
So
again,
this
is
a
very,
very
basic
kubernetes
deployment.
I
mean
obviously
there's
a
lot
more
to
kubernetes
than
this.
B
I
mean
we're
at
a
conference
of
kubernetes,
but
the
goal
here
is
to
show
you
you
know:
what's
like
the
like,
the
basic
on
how
you
do
a
deployment
in
a
little
bit,
tiffany
is
going
to
be
talking
about
get
ups
on
how
we
can
scale
this
up
right.
Imagine
you
don't
have
one
app
what
if
you
have
100
apps
right?
What,
if
you
don't
have
one
environment
right
now,
it's
just
that
right.
What
if
you
have
pre-prod
and
prod
and
tests,
and
what,
if
you
have
a
hundred
clusters
right?
B
B
B
Okay,
so
great
our
pot
is
deleted
right.
So
we
might
think
okay,
we're
done.
Our
application
has
been
deleted.
Well,
that's
not
the
case.
If
I
do
get
pods,
you
can
see
that
a
new
pod
was
created
11
seconds
ago.
This
is
because
the
pods
are
managed
by
the
deployment
right,
so
the
deployment.
It's
making
sure
that
you
know
you
have
a
pod
based
on
whatever
description
you
have
defined
in
your
deployment.
So
if
you
need,
if
you
delete
the
pod,
the
deployment
is
going
to
recreate
it
for
you
automatically.
B
B
B
Okay,
so
that's
the
first
portion
of
this
demo
you
know,
like
I
said
I
walk
you
through
how
to
do
a
manual
deployment
of
kubernetes
kubernetes
application,
but
now
it's
going
to
get
pretty
interesting
so
now
tiffany
is
going
to
show
you
how
we
can
achieve
something
very
similar
using
git
ups.
So
tiffany
saw
yours.
A
Thank
you
very
much
joaquin
and
actually
before
we
get
started,
if
you
wouldn't
mind
creating
a
branch
for
today's
workshop,
we're
each
going
to
be
creating
a
branch
that
is
unique
to
our
username
as
well
as
it's
appended
with
a
random
set
of
characters
at
the
end
and
we're
going
to
check
out
that
branch
and
push
it
up
and
we're
going
to
change.
Directory
back
to
the
root
of
our
repository.
A
A
Looking
for
all
checks
passing
successfully
and
as
joaquin
mentioned,
you
know
you
can
absolutely
deploy
things
manually
to
a
kubernetes
cluster,
but
when
it
comes
to
being
able
to
reproduce
the
state
of
your
cluster,
you
need
a
way
to
easily
get
back
to
your
desired
state
and,
as
joaquin
mentioned,
we
have
some
manifests
that
are
already
included
in
this
repository
now.
Flux
has
already
been
installed
in
the
cluster,
and
what
this
means
is
that
the
flux,
runtime
components
like
the
controllers,
the
crds,
are
all
up
and
running
in
the
cluster.
A
A
The
significance
of
each
of
these
arguments
that
you
pass
in
the
url
signifies
the
url
of
the
git
repository,
which
is
in
the
kubernetes
101
organization,
the
kubecon
2022
repository
and
we're
passing
in
the
branch
variable
that
we
just
exported
in
the
previous
set
of
commands.
We're
specifying
token
auth,
and
what
this
does
is
tell
flux
that
we
want
to
use
a
github
token
and
conduct
basic
auth
to
be
able
to
allow
flux
to
read
from
the
specified
repository.
A
We're
also
passing
in
a
path,
and
this
path
is
used
in
the
flux,
customization
telling
flux
to
add
its
installation
manifests
and
the
sync
file
to
the
designated
path.
So
great.
If
you've
run
the
bootstrap
gate
command
successfully,
we
can
next
pull
to
get
the
latest
contents
from
git
and
you'll.
See
sorry
from
that
flux
made
to
the
repository
on
our
behalf
and
you'll
see
a
few
files
that
got
added.
A
A
A
You
can
pass
in
the
namespace
argument,
so
we
see
that
we
have
two
flux
resources:
the
git
repository
and
the
customization
you'll
see
that
the
revision
includes
the
name
of
your
branch,
as
well
as
the
latest
commit
on
your
branch,
so
3,
b,
5
c
3,
b,
5
c
and
more,
and
we
can
see
that
both
the
git
repository
and
the
customization
are
reporting
as
ready
in
the
readme.
I've
added
some
comments
to
explain
how
the
values
got
passed
in
to
create
the
git
repository
and
customization
pair.
A
So
that's
great,
we
have
flux
up
and
we've
pulled
down.
The
latest
commits
that
flux
made
to
our
repository
and
the
got
king
components
includes
all
of
the
flux,
runtime
resources
and
the
grt
sync
includes
the
git
repository
and
customization,
and
there
is
also
a
customization
yaml,
and
I
want
to
point
out
that
this
is
not
a
flux,
customization
resource.
This
is
a
customized
overlay
and,
as
its
name
suggests,
the
customized
controller
works
with
customize,
which
is
a
configuration
customization
tool
native
to
kubernetes.
As
of
114.
C
A
This
so
now
that
we
have
flux
pointed
at
this
repository,
you
might
have
noticed
that
the
path
was
very
specific
to
the
deploy,
slash
bootstrap
directory.
Now.
This
means
that
flux
is
only
monitoring
this
repository
right
now,
but
we
have
other
resources
that
we'd
like
to
deploy
to
our
cluster,
including
the
contents
of
the
application
directory
and
the
contents
of
the
observability
directory.
A
A
If
you
look
closely
in
the
application
customization,
we
added
a
field
called
depends
on
now.
This
depends
on
field,
tells
the
customized
controller
not
to
reconcile
the
contents
of
this
customization
until
the
dependency
is
ready.
So
in
this
way,
flux
natively
supports,
ordered
installation
of
manifests.
A
A
So
I
might
have
taken
too
long
and
flux
might
have
beaten
me
to
it.
Okay.
So
if
I
had
been
a
little
bit
quicker,
you
would
have
seen
for
about
a
minute
or
so
that
the
application
one
might
have
reported
as
unready,
because
the
observability
would
have
taken
a
little
bit
to
come
up,
but
we
can
see
now
that
the
observability
and
application
customizations
have
both
successfully
reconciled.
A
A
This
imdb
yaml
includes
both
the
deployment
and
the
service,
and
we
also
have
a
webv
heartbeat,
heartbeat
and
webv
deployment,
which
allows
us
to
run
load
tests
later
on.
In
the
workshop,
we've
also
deployed
the
observability
stack,
including
fluenbent,
grafana
and
prometheus,
and
all
of
the
resources
that
it
takes
to
deploy
and
configure.
Your
observability
stack
are
expressed
declaratively,
including
your
grafana
dashboards,
which
are
stored
in
config
maps.
A
So
now
what
we
can
do
is
take
a
look
at
all
whoops.
All
of
the
resources
within
the
cluster
now
and
we'd
expect
to
see
some
resources
running
in
the
logging
namespace,
the
monitoring
namespace,
the
imd
imdb
namespace,
and,
did
I
say,
monitoring
already
the
heartbeat
namespace
as
well.
So
all
of
our
resources
are
up
and
running.
A
A
So
what
we've
done
now
is
pointed
flux
to
a
repository
that
includes
that
deployment
definition.
So
what
we
can
do
is
run
a
cube,
cuddle
delete
deployment
for
our
imdb
deployment
and
we
can
put
a
watch
on
getting
the
deployment
now.
This
can
take
a
few
seconds
but
effectively
what
we're!
What
we
will
see
is
the
fact
that
flux
is
going
to
bring
back
the
deployment
on
its
next
reconciliation
loop
great.
So
we
see
that
it's
coming
up
now
and
in
a
few
minutes
well,
not
minutes.
It's
there.
A
We
can
further
verify
by
taking
a
look
at
the
pods
great,
so
flex
also
detects
drift
within
the
resources
that
you've
defined
in
git.
So
this
command
here
is
going
to
describe
the
deployment
that
we've
defined
in
git
and
just
to
show
you
the
replicas
field.
Sorry,
we
have
specified
that
we
want
one
pod
running
for
the
imdb
deployment
and
we
can
show
you.
I
can
show
you
that
here
as
well
great.
A
We
can
subsequently
run
a
cubecuddle
edit
command
and
that'll
bring
up
the
existing
resource,
and
you
can
edit
this
file
and
as
long
as
the
valid
sorry,
as
long
as
the
ammo
is
valid,
it
should
save
and
automatically
apply
that
change
great,
so
I'll,
be
quick
here,
because
I'm
competing
with
flux
now
awesome.
So
we
see
that
the
replicas
has
been
updated
to
two
and
great.
We
can
see
that
we
have
two
pods
running,
which
is
what
we've
manually
edited
the
deployment
to
show.
A
Now,
once
we
wait
about
a
minute
or
so,
what
flux
should
do
is
reckon
is
realize
that
the
replica
count
in
the
deployment
no
longer
matches
what
you've
defined
as
your
desired
state,
and
so
you
can
see
now
that
the
second
pod
is
now
being
terminated
now
has
been
terminated
and
we
can
take
a
look
at
the
pods
within
the
imdb
namespace
great.
We
see
one
if
we
hit
up
arrow
a
few
times.
We
can
see
that
the
replica
field
within
the
deployment
has
also
been
changed
back
by
flux,
so
yeah
flux.
A
B
You,
okay,
so
tiffany
already
got
the
applications
deployed.
One
way
to
verify
you
know
deployments
and
everything
it's
one
of
my
favorite
tools
is
canines,
so
essentially,
canines
is
a
ui
tool
that
runs
in
the
terminal
and
it
allows
you
to
inspect
and
you
know
see
what's
going
on
with
different
kubernetes
resources.
B
If
you
press
l,
it's
going
to
pull
out
the
the
logs
so
as
you
can
see
that
it's
making
a
request
around
every
five
seconds,
and
likewise
I
can
open
up
my
webv
imdb
pod,
and
if
I
press
l,
you
can
see
that
it's
sending
around
10
requests
per
per
second
right.
Likewise,
on
canines
you
can
see
different
types
of
resources,
not
just
pods
right.
B
If
I
do
shift
colon
and
if
I
just
type
for
example
deployment,
you
can
see
that
we
have
all
these
deployments
already
in
the
cluster,
I
can
do
let's
see
secret,
for
example,
different
secrets
are
defined,
etc,
so
pretty
useful
tool
highly
recommend,
especially
if
you
need
to
kubernetes
it.
You
know
it's
it's
great
now.
B
Essentially
we're
collecting
logs
from
our
application,
but
we're
not
really
forwarding
to
any
cloud
provider
right
now,
we're
just
pushing
it
to
standard
out
just
for
the
terms
of
simplicity,
but
should
you
choose
to
there's
different
connectors
that
you
can
use
in
fluid
bit
in
order
to
push
you
know
your
logs
to
you
know
you
know
azure,
google
et
cetera,
should
you
choose
to
so
all
I
wanted
to
really
show
from
fluent
bit.
Let
me
go
to
pods
and
if
I
just
go
under.
B
Flowing
bit,
and
if
I
press
l
and
then
I
can
do,
let's
see
w
or
for
the
for
the
wrap
and,
as
you
can
see
like
all
these
logs
are
the
ones
that
are
getting
printed
to
stand
there
out,
like
I
said
you
can
configure
it
the
way.
Whatever
way
you
choose
to
whatever
provider
you
want
to
use
as
well
now.
The
next
thing
that
is
actually
pretty
cool
that
I
want
to
show
is
prometheus,
so
like
tiffany
mentioned
on
the
slides
prometheus
is
a
metrics
collection
and
alerting
tool.
B
It
records
real-time
metrics
in
a
time
series
database
and
it's
built
using
an
http
pool
model
right
so
as
part
of
tiffany's
demo,
she
already
deployed
prometheus,
so
I
can
show
you
that
we
have
it
right
here.
The
pod
is
running
and
I'm
able
to
access
the
prometheus
ui.
If
I
click
on
ports
prometheus,
you
see
the
little
globe
icon
here.
C
C
D
C
A
B
B
So,
for
example,
like
our
imdb
app
that
we
showed
before
it
has
a
metrics
endpoint.
So
this
is
one
of
them
that
you
know
prometheus
is
scraping
and
you
can
see
the
status
set
to
up
and
then
as
well.
We
have
some
for
our
load
testing,
which
is
like
the
webv
applications.
So
everything
seems
to
be
good.
B
So
if
I
go
back
to
the
main
ui-
and
you
see
this
little
icon
right
here,
if
you
just
press
there,
it
will
show
you
what
are
the
metrics,
that
prometheus
has
been
able
to
scrape
for
us
and
it's
stored
in
the
database.
So,
for
example,
this
one
you
know
it
shows
there
so
yeah.
So
we
have
the
metrics
cool,
but
we
want
to
make
it
pretty.
B
You
know
grafana
temple
azure
monitor.
Is
there
grafana
cloud
et
cetera,
so
there's
so
many
options,
so
many
so
many
things
out
there
there's
so
many
plugins
out
there
that
you
can
use
for
today's
demo
we're
just
focusing
on
prometheus,
but
I
just
wanted
to
like
I
said
mention
that
this
exists
right
and
you
can
play
with
it.
Should
you
choose
to
so
okay,
so
we
have
a
prometheus
data
source.
It's
pointed
to
our
prometheus
service.
B
If
I
click
on
save
and
test,
we
know
that
everything
is
connected
as
expected,
and
now,
if
I
go
here,
you
can
see
that
we
have
a
dashboard
for
our
imdb
application,
which
keeps
track
of
what
how
many
requests
per
second
are
coming
into
our
application
and
also
how
long
the
requests
are
taking
and
if
there's
any
errors
at
the
moment.
So
right
now
we
have
no
errors
and
the
requests
seem
to
be
pretty
constant.
B
Okay,
great
so
now
we're
going
to
load
we're
going
to
run
a
load
test
so
that
we
can
see
some
some
action
here
under
funnel.
So
to
do
that,
we
have
some
already
pre-made
tools
to
load
our
load
test.
You
don't
have
to
worry
about
too
much
about
what
it
does
in
the
background,
but
all
you
have
to
do
is
just
run
this
kic,
which
stands
for
kubernetes
and
code
spaces
test
load.
Let
me
quit
from
here.
B
B
So,
okay,
so
now,
if
I
go
back
to
grafana,
you
can
see
that
our
load
starts
to
go
up
right.
We
have
more
requests
coming
in
per
per
second
and
then
in
a
little
bit
just
give
it
a
few
seconds.
Oh
there
you
go
you're
going
to
start,
seeing
that
we
have
some
errors
and
our
endpoints
as
we
expected.
You
can
see
that
the
requests
per
second
also
went
up
now,
we're
in
on
orange,
so
yeah
so
very
useful,
very
valuable.
B
You
can
do
so
many
things
with
it.
If
you
haven't
used
grafana,
I
you
know,
we
highly
recommend
it.
Okay,
so
I
think
that's
it
in
terms
of
demo,
if
you
have
a
code
space
still
running,
you
can
stop
it
by
pressing
this
little
code
space
button
down
here
and
then
you
can
see,
stop
current
code
space,
we're
gonna,
leave
this
access
open
for
you
know
maybe
like
another
few
days,
because
I
know
not,
everybody
was
able
to
get
the
access
today.
B
A
E
A
That's
a
great
question
and
helm
is
actually
a
great
templating
tool.
That's
you
know
cloud
native
and
allows
you
to
package
up
all
of
your
resources,
so
flux
and
helm
are
different.
I
would
say,
helm
does
include
some
cli
commands
that
allow
you
to
you
know,
do
things
like
helm,
install
helm,
upgrade
you
know,
etc,
but
what
flux
adds
to
that
is
the
ability
to
declaratively
define
home
resources
that
live
and
get
that
the
flux
helm
controller
manages.
A
So
I
might
have
mentioned
during
the
talk
that
the
customized
controller
is
one
of
flux's,
reconciler
controllers
and
flux's.
Helm
controller
is
the
other
reconciler
controller
and
it
interacts
with
a
helm
release
which
defines
a
helm
chart
from
a
helm
repository
that
flux
then
uses
to
do
something.
To
do
you
know
installations
and
upgrades,
but
instead
of
you
having
to
manually
call
helm,
install
or
helm
upgrade.
A
You
just
add
it
to
git.
Make
sure
that
it's
in
a
repository
that
flex
is
monitoring
and
flux,
can
perform
the
installations
and
upgrades
on
your
behalf,
and
you
can
define
values
either
within
the
helm
release
so
some,
similarly
to
passing
in
a
value
zml
to
any
helm,
commands
or
you
know,
setting
any
values
and
you
can
define
those
within
the
helm,
release
itself
or
externally
in
a
config
map
that
you
subsequently
feed
into
the
helm
release.
Does
that
answer
your
question.
A
G
A
So
if
you
store
the
secret
in
git,
it's
it's
no
longer
a
plain
text
secret
effectively.
You
can
also
use
and
flux.
Now
natively
supports
vault
integration
as
well
as
stops.
So
those
are
some
other
options
and
I
believe
that
your
your
second
question
was
other
options
apart
from
flux,
and
I
did
mention
that
git
ops
itself
is
agnostic
to
tooling
and
so
there's
a
few
others
that
are
available,
and
I
think
that
you'll
be
able
to
find
some
talks
on
those
as
well
at
cubecon.
C
A
E
Yeah,
I
will
just
briefly
ask
since
you
mentioned
argo,
which
is
another
continuous
delivery
tool
for
githubs
as
well.
So,
although
I'm
not
experienced
with
it,
so
I
I
want
to
ask
that
what
do
you
find
the
key
differences
between
flux
and
argo,
or
what
strings?
Do
you
find
in
flux
that
you
might
want
to
choose
over
argo
cd,
yeah.
A
Thank
you,
that's
a
great
question
and
I
will
be
the
first
to
admit
that
I
am
not.
You
know
supremely
well
versed
in
argo,
but
from
flex's
perspective.
Some
of
the
benefits
include
the
fact
that
it
leverages
a
lot
of
native
kubernetes.
Functionality
include
including
things
like
role-based
access,
control
and
flex.
A
D
D
H
A
I
I
only
say
that
as
a
joke,
but
I
would
say
that
if
you're
beginning,
you
know,
testing
out
and
figuring
out
what
metrics
it
is
you're
interested
in
collecting,
as
well
as
carving
out
you
know,
and
and
creating
specific
alerting
around
specific
metrics
and
gathering
information
about
the
general
performance
of
your
cluster.
Open
source
is
a
really
great
way
to
start,
and
I
know
that
you
I
think
you
mentioned
datadog.