►
From YouTube: Tutorial: Set Up Your Shell For Kubernetes... - Sebastien Thomas, Wunderkind & Archy Khayretdinov,
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. 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.
Tutorial: Set Up Your Shell For Kubernetes Productivity And Be Efficient Quickly - Sebastien “Prune” Thomas, Wunderkind & Archy Ayrat Khayretdinov, Google
Speakers: Ayrat Khayretdinov, Sebastien Prune Thomas
You just started a new gig ? You switched laptop ? or you're new to using Kubernetes ?
From the new users of Kubernetes to the most experienced gurus, we all spend a large amount of time on the terminal* (shell).
This talk will focus on setting up your laptop and terminal, installing all the cool tools to get you productive fast with Kubernetes. It is intended for all levels of experience.
By mixing a presentation of the tooling and demos, you'll quickly see how some little tuning can increase your productivity by a large amount.
During this talk you'll learn (not limited to):
- setup your shell to connect to a Cloud K8s service
- add shortcuts to type less when using kubectl
- get a clean access to cluster's logs
- add colors to your kubectl outputs
- install and use a local k8s cluster for prototyping
- work with Containers without Docker-For-Desktop
- get to know a lot of small tools to ease the pain of maintaining a cluster, playing with yaml and more
This talk also gives access to a companion tutorial with all the commands that you can play on your laptop, during the talk or at home.
Bring your laptop and start being more productive right now !
Join us in this adventure and impress your co-workers on your first day at work !
WARNING !
If you want to follow the talk and replicate on your own laptop, you will need a Kubernetes cluster.
it is advised to pre-install some tools so we don't burn down the WIFI of the whole conference: either Docker Desktop, Podman and Kind
For Mac OS X:
brew install podman
brew install kind
podman machine init --cpus=2 --memory=4096 --disk-size=200 --now
kind create cluster dev
A
How's
everybody
doing
you
guys
how's
cubecon,
going
I
didn't
expect
that
we're
gonna
have
such
a
big
audience
today,
thanks
for
coming.
So
this
is
a
tutorial.
A
one-on-one
session
set
up
your
laptop
for
kubernetes
and
get
proactive
and
I'm
just
straight
out
of
the
back
I
just
want
to
ask
like:
do
you
guys
like
to
be
productive?
Do
you
like
to
be
you
know,
yeah.
B
A
Yes,
that
was
good
yeah,
because
we've
actually
been
surprised.
We've
seen
a
lot
of
people,
even
at
this
conference.
You
know
they
have
a
nice
laptop
set
up
with
Cube
cuddle,
and
you
know
the
way
they're
doing
is
basically
running
commands
in
a
pool.
Shall
you
know
not
proactive,
just
trying
to
type,
and
you
know
I've
been
at
the
showrooms
booths.
Those
demos
boring.
You
know
people
typing
slowly
so
same
here,
like
you
know
like.
If
you
like
to
drive
a
you
know
old
car.
That's
that's
fine!
A
We'll
do,
but
there's
always
better
choice
right.
You
can
get
something
like
Tesla
and
you
know
get
an
autopilot
nice
screen
like
iPad
in
front
of
you,
and
you
know
everybody
around.
You
will
be
like
wow
this.
This
is
cool,
and
so
you
guys
here
at
kubecon,
probably
also
you
know
getting
a
lot
of
stickers
at
the
booth.
If
you
didn't
get
it
I
think
you
know,
there's
still
a
lot
of
them
out
there,
but
you
know
there's
something
inside
that
you
have
to
fix
on
your
laptop
side.
A
So
our
tutorial
is
pretty
much
starting
for
you
here.
You
are
a
young
Sky
worker.
Trying
to
you
know,
figure
out
the
nice
Cube
cuddle
commands
and
you
know,
try
to
switch
namespaces
contexts
and
see
what
happens
right,
but
we're
hoping
like
by
the
end
of
the
session
you're
going
to
become
you
know,
experienced
Jedi
and
will
be
able
to
surprise
your
colleagues
at
at
work
and
get
productive
sounds
like
a
plan
all
right.
A
A
B
Actually
bring
back
good
color
to
something
working
efficiently.
If
you
don't
know
that
you,
you
will
learn
during
the
conference,
so
so
to
sit
and
wait,
but
yeah
but
I
had
this
talk.
It
was
a
like
15,
20
minute
talk
just
presenting
the
tool
and
and
how
to
install
it
and
the
URL.
So
this
is
totally
different
because
we're
going
to
do
a
Hands-On,
we're
going
to
demo
everything
that
we're
saying,
and
we
will
try
to
give
you
everything.
A
And
you
apologize
we're
from
Quebec,
so
our
accent
is
a
little
bit
weird,
but
thanks.
So
what
what
we
need
for
this
tutorial?
And
unfortunately,
we
just
heard
that
you
know
the
previous
tutorial
in
this
room
had
had
some
issues
with
Wi-Fi,
so
we're
hoping
for
the
best,
but
it
might
be
a
complex
problem
for
us
as
well.
So
what
we're
looking
here
is
we
want
to
have
your
laptop
with
pretty
much
cell
item
setup
and
we're
going
to
be.
A
You
know,
playing
with
kubernetes
cluster
and
we're
not
gonna
go
inside
of
the
kubernetes
control
plane
we're
not
going
to
talk
about
API
servers,
schedulers
controllers
and
whatnot
and
cubelets.
Our
talk
is
really
going
to
be
focusing
on
on
the
laptop
itself
talking
to
kubernetes
API
server
for
the.
B
B
A
Then
all
right,
so
that's
good
yeah,
so
yeah
so
for
the
requirements
for
this
tutorial,
we
try
to
you
know,
cover
as
much
platforms
as
possible,
but
mainly
we
were
doing
our
preparation
on
the
Max,
and
so
this
part
has
been
tested
well
for
the
rest
of
the
part
we
give
our
best.
Our
tutorial
is
open
source.
So
if
you
see
any
issues,
we're
happy
for
the
PRS.
B
A
Possible
all
right,
I
I,
think
you
know
it's
still.
There
will
be
an
experience
that
you
know
you
might
not
be
able,
maybe
to
run
some
of
the
commands,
but
you
can
go
check
in
the
documentation.
Maybe,
but
there's
obviously
there's
some.
You
know
if
you
cannot
use
dsh,
there
will
be
potentially
some
of
the
features
that
you'll
not
be
able
to
use,
but
yeah
like
we're,
hoping
you
still
gotta,
learn
a
lot.
A
So
what
we
basically
need.
The
key
requirements
is-
and
we
put
it
in
our
tutorial-
we
don't.
We
cannot
provide
you
any
kubernetes
clusters
today,
we're
hoping
you
have
one
on
your
laptop
or
you
have
one
on
your
cloud
provider
and
whatnot.
So
pick
any
kubernetes
cluster
that
you
want,
and
you
know
you
can
install
all
of
the
tools
that
we're
going
to
be
talking
on
your
laptop
and
they
will
be
communicating
with
this
kubernetes
cluster.
So
just
want
to
ask
like
who
who
has
any
kubernetes
running
on
on
your
laptops?
A
Okay,
so
good
and
who
has
like
cluster
in
the
cloud
that
they
can
connect
and
potentially
play
around,
sounds
good
I,
don't
know
for
the
rest
of
the
folks.
I
just
think
like
we
have
all
the
steps
to
install
kubernetes
cluster
on
laptop.
It's
just
this
potentially
might
be
problematic
with
the
Wi-Fi,
so
I
don't
know,
I
I
would
I
would
I,
don't
know
what
to
say,
but
yeah
don't
blame
us
yeah
blame
Cisco
all
right.
A
So
if
you
want
to
follow
tutorial
on
your
laptop-
and
you
know
if,
if
you
wanna
reproduce
steps
with
your
colleagues
friends,
so
we
have
a
website
where
all
the
steps
are,
and
you
can
pretty
much
you
know
do
it
at
your
personal
time.
If
you
didn't
finish
some
of
the
configurations
so
we'll
give
a
few
minutes
to
scan
the
barcode
or
I
think
this
is
a
short
short
link.
That
also
brings
you
to
the
website.
So
I'll
give
you
a
few
minutes
just
to
make
sure
everybody's
connected.
So.
B
You
can
follow
along
if
you
go
on
the
website
and
start
to
do
everything
from
the
website.
You're
not
going
to
follow
us,
because
there's
some
few
things
we're
not
doing
some
things
we're
doing
a
little
bit
differently
during
the
demo.
Some
things
that
you
shouldn't
do
because
it's
just
for
demonstration
purpose
so
keep
following
us,
but
still
we're
going
to
go
on
this
website
and
copy
and
paste
all
the
comments
in
our
demonstration.
A
Okay,
cool
doesn't
work
the
QR
or
okay
good.
All
right,
okay
sounds
good,
so
we
can
carry
on
and
we're
gonna
start
the
first
chapter,
so
we
were
young
future
Jedis
and
you
wanna
come
to
kubecon.
Maybe
learn
some
kubernetes
understand
how
things
are
working.
So
this
is
a
one-on-one
tutorial,
so
we
decided
you.
A
You
know,
there's
probably
a
lot
of
people
who
was
just
starting
with
kubernetes,
so
we're
probably
going
to
catch
up
some
really
Basics,
but
we're
gonna
try
to
move
forward
fast
and
then
once
we
explain
the
namespaces
context
says
we
can
move
forward
and
show
more
advanced
stuff.
Does
that
sound
good
with
everyone
all
right.
A
Okay
so
first
we're
going
to
talk
about
new
SSH,
which
is
our
cube
cutter
so
for
the
systems
out
there,
who
probably
you
know,
never
connected
to
kubernetes
Cluster,
I
I,
think
this
is
a
very
good
analogy.
You
know
back
in
the
days
we
had
servers,
we
want
to
connect
to
them
and
we
used
our
SSH.
You
know,
provided
our
credentials,
provided
the
address
of
our
server
and
then
we'll
be
able
to
connect,
and
you
know,
manage
our
application
and
then
you
know.
A
Obviously,
technology
is
like
ansible
game
where
you
can
specify
many
directions
and
provision.
Many
servers
so
I
think
there's
a
some
analogy
here
with
kubernetes.
So
Cube
cuddle
is
a
CLI
that
works
with
kubernetes
communicates
with
kubernetes
Kelsey
Hightower
says
it's
a
new
SSH
and
I
agree
with
him.
So
the
idea
here
is
that
you
have
a
cube
cuddle
installed
on
your
laptop
or
maybe
on
the
cloud
shell
and
through
the
HTTP.
A
A
A
B
A
Yeah,
so
for
people
who
doesn't
have
Cube
color
installed
on
the
laptops,
please
go
ahead
and
run
the
command
that
you
should
run
for
your
platform,
whether
it's
Apple
Mac
OS,
Linux
windows.
So
the
commands
are
here.
If
you
have
like
using
Google
Cloud,
if
you
have
gcloud,
you
can
also
install
Cube
cutout
through
the
gcloud
components,
install
so
just
to
check
that
you
know
we
have
our
Cube
cuddle
here.
So.
A
Pretty
much
we're
running
on
the
bleeding
edge,
so,
as
you
know,
kubernetes
1.285
is
the
latest
release
today
and
our
community
of
kubernetes
maintainers
working
to
have
a
support
for
kubernetes,
126
and
I.
Think
a
couple
of
weeks
and,
as
you
know,
kubernetes
has
right
now
really
cycled
three
three
releases
per
year,
so
it
used
to
be
four
and
I
was
three,
so
that
is
gonna.
You
know
change
so
right
now
you
see
that
the
connection
to
the
server
localhost
was
refused.
A
Yeah
and
another
thing,
probably
that
Worth
to
mention
you
know
sometimes
people
install
Cube
cuddle
on
their
laptop
and
after
a
couple
of
years
they
decide.
Okay,
let
me
like
refresh
my
knowledge.
Obviously
the
kubernetes
is
keep
up,
keep
moving
forward
right
and
if
you
want
to
be
successful
and
have
a
good
experience,
try
to
make
sure
that
your
Cube
cuddle
client
version
is
at
least
one
release.
You
know
below
or
or
should
be
like
exactly
the
same
release.
A
The
reason
for
that
is,
you
know:
kubernetes
sometimes
duplicates
some
apis
and
there
are
some
changes
in
the
schema,
so
your
experience
with
kubernetes
might
not
be
as
good
so
make
sure.
You'll
stay
up
to
date
and
when
you're
printing
out
this
version,
Cape
cuddle
version
command.
You
see
that
we
have
a
version
difference
here
already
signaled
as
a
warning
and
obviously,
if
you
have
much
bigger
Delta,
then
you
might
have
some
problems.
Unexpectedly
happening
and
you'll
be
troubleshooting
things
that
you
shouldn't
be
troubleshooting.
B
A
Right
cool,
so
anybody
has
problems
with
Cube,
cuddle,
installation,
just
I'm
sure,
there's
no
problems
but
I'm
sure
the
problems
coming
when
the
kubernetes
is
installation
starts
all
right.
So,
okay,
so
now
we
have
our
keep
cuttle
installed
and
obviously
we
need
to
have
a
kubernetes
cluster.
So
hopefully
everybody
have.
You
know
kubernetes
installed
on
your
laptop
and
we
probably
want
to
give
everyone
some
time
to
check
you
know.
A
So,
like,
let's
imagine
you
are
you
know,
working
in
a
company
and
you
need
to
work
with
kubernetes
day
to
day,
and
you
need
to
like
answer
to
the
question
like
what
is
the
requirements
I
should
have
in
order
to
be
able
to
develop
build.
My
images,
you
know,
run
containers
on
my
laptop
and
deploy
them
to
kubernetes
Cluster
right.
A
So
I
think
this
is
the
first
three
requirements
that
you
really
should
kind
of
cross
check
and
it
sounds
very
obvious
right,
like
you
know,
Docker
build
Docker
Run
keep
cut
I'll
create
deployment.
Those
are
like
things
that
you
probably
do
day
and
night,
but
like
those
are,
the
things
that
you
should
be
probably
must
have.
A
The
other
things
that
I
think
less
important
is
something
you
know
capability
to
run.
Docker
compose
I.
Think
Docker
compose
is
a
pretty
nice
solution
in
the
sense
that,
because
you
have
a
nice
little
yamo
that
you
can
put
multiple
applications
do
Docker
compose
up
it's
going
to
bring
it
up.
Unfortunately,
kubernetes
is
much
more
complex,
so
instead
of
one
yamo
you're
gonna
have
50
ammos.
A
So
we've
seen
a
lot
of
people
in
community
they're
like
oh
Docker
compose
was
nice,
but
you
know
we
we
have
to
adapt
to
the
kubernetes
world,
so
I
see
less
and
less
interest.
You
know
around
using
Docker
compost.
Things
like
scanning
images,
I
think
might
be
important
for
some
organization
and
there's
a
lot
of
open
source
Solutions
out
there,
like
trivia,
for
example,
that
you
can
install
and
do
similar
things
and
then
for
the
UI
I.
A
A
B
A
A
A
Yeah
exactly
so,
some
some
gentleman
in
the
room
actually
brought
up
a
valid
concern,
so
myself
and
and
Sebastian
we're
working
in
companies
with
over
250
employers
and
last
year,
Docker
basically
said
that
you
know.
If
your
company
is
larger
than
250
people,
you
basically
have
to
pay
the
subscription
license,
and
this
is
kind
of
not
nice
for
a
lot
of
people.
A
So
the
browse
for
the
docker
desktop
multi-platform,
amazing,
nice,
UI
I
think
it's
a
great
experience,
but
unfortunately
it's
a
paid
product
for
Enterprise
I
personally
was
annoyed
like
coming
to
work
and
every
time
my
laptop
was
updating,
Docker
desktop.
This
was
like
pretty
much
twice
three
times
in
a
week
and
it
was
like
high
CPU
consumption
but
like
this
is
something
you
know
less
negative,
but
at
least
it
was
free
before
but
not
anymore.
A
So
I
actually
spoke
to
many
people
and
they
were
asking
like
what
I
should
do
now
like
I
cannot
use
Docker
desktop,
but
I
want
to
use
kubernetes
on
my
cluster
and
actually
we
put
some
of
the
solutions
for
you
out
there.
So
if
your
manager
or
somebody
from
your
colleagues
is
going
to
ask
you
a
question,
you
actually
have
several
options
today
that
you
can
actually
take
advantage
and
we're
gonna
quickly
cover
some
of
them,
while
your
laptops
are
booting,
so
my
favorite
option
today
I
think,
is
going
to
be
rent
your
desktop.
A
It's
a
pretty
new
solution.
I
would
say
it's.
Last
year
it
has
been
announced
it's
free,
open
source
backed
by
company,
but
you
know
so
far
so
good.
The
reason
I,
like
Rancher,
desktop
first
of
all,
that
you
know
it
supports
containerd,
which
is
like
right
now
at
default,
runtime
for
kubernetes,
but
also
it
has
support
for
Docker.
Just
in
case,
if
you're
still
like
running
Legacy
kubernetes
clusters,
you
can
choose
the
version
of
kubernetes
cluster.
A
You
want
to
deploy,
but
most
important
importantly,
I
think
they
are
the
way
they
architected
this
solution.
It's
pretty
nice,
so
they
actually
using
Nord
CTL,
so
nerd
CTL
is
basically
a
replacement
for
docker
CLI.
So
if
you,
you
know
like
even
like
Docker
desktop,
is
they
saying
if
you,
you,
cannot
even
use
Docker
cell
anymore?
If
you
know,
if
you
have,
if
you
have
it
so
like
you
can
just
so,
you
need
to
find
the
the
replacement
for
it
right
and
nerd
cattle
is
basically
a
alternative.
A
Obviously,
another
solution
that
the
interest
like
which
is
I
really
like
as
well,
is
that
the
kubernetes
itself
is
running
k3s.
So
k3s
is
a
lightweight
kubernetes
clusters,
so
that
makes
the
platform
lightweight
as
well
and
k2s
has
been
built,
for
you
know
smaller
clusters
that
running
on
the
edge
so
like
it's
a
good
use
case
for
laptops
right.
B
B
So
it's
a
simple
kind
of
Brew
installed
Colima
and
then
you
callima
start
it's
going
to
build
up
use
qmu
on
your
laptop,
create
a
Linux
VM
and
then
everything
is
executed
into
that
and
it
also
bundles
kubernetes
cluster
within
it
and
once
again,
q3s
the
same
as
with
Rancher.
It
has
no
UI
at
the
moment
and
and
I
guess
when
you're
using
that
you
don't
need
a
UI
anyway,
but
that's
my
personal
take
on
that
and
I
I
guess.
B
A
Cool
yeah,
no,
that's
absolutely
and
finally,
I
would
say
maybe
the
least
coolest,
but
it
works.
You
know
if
your
purse,
man
solution
like
I,
think
that's
that's
gonna
cut,
so
you
can
actually
install
mini
Cube
mini
cube
is
basically
fetches
the
VM
that
runs
Docker
engine
in
it
and
you
can
install
Docker
CLI
on
your
laptop
and
then
you
will
be
able
to
open
up
some
ports
on
minicube
and
connect
to
Docker
engine
that
sits
inside
of
the
VM.
A
So
you
pretty
much
have
Docker
working
on
your
laptop,
so
you
can
do
the
build
images.
You
can
do
push
images
and
you
have
kubernetes
cluster
where
you
can
deploy
things
so
like.
If
you
don't
have
you
know,
choice,
I,
think
that
that
would
work
as
well,
but
for
today's
tutorial
we
decided
to
choose
another
option.
This
it's
called
kind,
so
kind
stands
for
kubernetes
and
Docker.
It's
a
tool
to
create
super
lightweight
kubernetes
clusters,
and
the
reason
is
super
lightweight
is
because
they
actually
deploy
it
as
a
Docker
images
themselves
right.
A
So
if
you
want
to
deploy
control
plane,
it's
going
to
be
one
Docker
image.
If
you
want
to
deploy
a
note,
it's
going
to
be
another
Docker
image.
So
that's
why
it's
super
lightweight
and
it's
supported
by
kubernetes
6
and
it
can
be
deployed
for
local
kubernetes
clusters,
but
in
the
in
the
early
days
of
kind.
This
was
the
solution
to
run
CI
for
kubernetes
itself,
but
you
know
the
the
use
cases
has
expanded
and
I
love
to
run
kind
of
on
my
machine
because
it's
super
fast.
B
A
There's
so
many
options,
but
I
think
we
tried
to
find
the
options
that
you
know
like
can
replace
backward
desktop
today,
and
you
know
if
you're
really
looking
for
that
solution.
You
have
an
answer
and
the
slides
is
yours,
so
just
to
finish
up
with
the
kind.
So
we're
actually
going
to
go
ahead
now
and
install
the
current
cluster
right,
yeah.
Okay,
so
there's
one
caveat
actually
with
kind
right
so
as
as
you
remember,
kind
itself
is
deployed
as
a
Docker
in
containers
right.
A
So
you
need
to
have
Docker
engine
somehow
running
on
your
laptop,
but
it's
not
free
anymore,
with
Docker
desktop
so
again
for
the
mac
and
windows
users.
You
need
to
find
a
solution
where
you
can
actually
deploy
that
Docker
image
to
that
spins
up
the
kubernetes
cluster
and
we
found
the
solution
which
is
called
podman,
so
podman
is
actually
solution
from
Red
Hat
guys
and
it's
replacing
Docker
engine
requirement
for
your
laptop,
and
it's
also
provides
a
rootless
containers.
I'm,
not
a
secure
security
specialist.
But
everybody
says
this
is
super
cool
and
provides.
A
You
know
much
smaller
footprint.
I,
don't
know
for
for
the
personal
laptop.
If
it's
it's
a
big
concern,
but
like
I'm
sure,
if
you're
running
in
production,
you
know
you
don't
want
to
run
containers
so
podman
is
a
they
say.
Swiss
army
knife
that
is
maintained
by
Red
Hat
replaces
a
Docker
for
desktop
Docker
engine
and
Docker
CLI
podman
itself
doesn't
run
kubernetes
right,
it's
just
replacement
for
Docker
engine
and
Docker
CLI,
and
it
works
for
Windows,
Mac
and
Linux
and
for
people
running
M1
Max.
It's
also
supported.
B
Is
far
more
than
just
a
replacement
for
the
docker
thing
yeah,
there
is
a
lot
of
tooling
and
new
comments
that
you
can
use
with
podman.
It
manage
different
kind
of
images,
container
images
how
to
call
that
type
format,
so
it
usually
builds
faster
than
using
the
regular
Docker.
For
example,
it's
it
can
build
and
deploy
rootless.
That
means
you
you're
sure,
you're,
whatever
you
deploy.
B
A
And
for
people
who
love
UI,
they
also
have
a
podman
desktop.
So
like
you
can
see
your
images
and
scans
and
stuff
like
that,
so
anybody's
using
podman
just
I'm
so
curious.
Oh
all
right!
So
we're
not
alone
good,
so
yeah!
So
we'll
have
a
quick
demo
to
install
podman
and
Ken
again,
like
we're
not
recommending
you
download
anything
at
this
Wi-Fi,
but
you
can
try
and
at
your
own
risk.
So
you
want
to
do
it
or
you
want
me
to
do
it.
C
B
So
yeah,
obviously
you
have
nothing.
You
just
grab
the
podman
command
line,
but
so
it's
just
a
CLI
and
then
you
need
to
bootstrap
an
image
or
something
to
run
the
containers.
You
know
kind
of
a
virtual
machine
and
is
intelligent
enough
to
find
on
which
lab,
which
kind
of
os
you're
using
and
do
some
skills
to
have
a
little
bit
differently.
So
on
my
OS
as
every
other
solutions,
they
are
going.
It's
it's
using
an
emulator,
it's
creating
a
Linux
VM
and
then
it
it
runs
things
inside
the
VM
yeah.
B
Batman
info
is
giving
a
ton
of
information
about,
obviously
the
VM,
the
memory,
the
whatever
you
have
installed.
So
what
is
interesting
here
in
Poland?
It's
not
much
about
myself,
but
it's
going
to
create
a
virtual
machine
in
your
laptop
and
you
can
change
the
CPU
memory
disk
size
and
I
recommend
you
do
that,
because
the
default
is
very
small.
So
unless
you
don't
want
to
run
a
very
big
kubernetes
cluster
or
deploy
many
things,
you
should
increase
that
a
little
bit.
B
So
we're
not
demonstrating
that
because
one
so
it's
600
Megs
to
download-
and
it's
it's
not
very
interesting
in
the
end,
I
guess
what
we
or
what
I
usually
do
again.
What
we're
seeing
here
are
not
recommendation,
it's
what
we're
usually
doing
and
it's
what's
making
us
like
working
faster
with
kubernetes,
just
replace
the
docker
recommend
line.
If
you
have
it
and
be
careful,
because
every
Docker
for
desktop
upgrade
will
reset
that
I
usually
remove
the
docker
command
line
and
I,
replace
that
with
podman
and
I.
B
Don't
use
aliases,
because
some
commands
are
hard-coded
for
using
Docker.
So
if
you
just
alias
in
your
shell
and
you
run
something
it's
not
going
to
work,
you're
going
to
have
very
strange
results,
and
just
because
that
Docker
command
line
or
the
application
is
looking
for
the
docker
options
or
Docker
stuff
that
are
not
working
actually
with
podman
or
is
working
a
different
way.
Most
of
the
time
it's
about
the
socket
to
reach
to
the
docker
demon,
yeah.
A
A
B
A
And
you
can
see
we're
running
Docker
PS
and
it
really
works
because
we
just
basically
hard
linked
it.
It's
basically
just
pointing
to
the
apartment,
but
it's
actually,
you
know
written
as
Docker.
So
all
right,
so
that's
that's
done.
We
have
our
apartment
running
up
and
running.
So
the
next
thing
we
want
to
do
is
to
install
kind.
So
we
already
pulled
up
kind
itself
and
we're
gonna
run
kind,
create
cluster
command,
and
obviously
you
know
if
you
want
to
make
sure
your
deployment
is
persistent.
A
You
can
also
have
option
to
deploy
it
with
kind
configuration
file
where
you
can
specify
how
many
nodes
you
want
to
have
so
kind
is
pretty
flexible.
You
can
deploy
multiple
control
planes,
multiple
modes,
if
you
want,
but
obviously
for
the
purpose
of
the
demo.
We
just
went
with
the
one
control,
plane,
node
and
one
worker
node
when
installing
kubernetes
124
and
anything
else
to
call
out
so
nice
United's
default
yeah.
B
We're
just
forwarding
we're
not
going
to
use
that
and
and
we're
not
actually
digging
into
that
so
go
read
the
documentation,
but
we're
forwarding
some
ports
from
the
node
from
the
local
node
to
be
reachable
inside
our
cluster.
So
that
way
you
can
install
an
Ingress
controller,
for
example
inside
the
cluster
later
on
and
reach
that
from
your
laptop
directly.
Yes,.
A
B
B
So
even
if
you
delete
that
and
you
restore
it,
you're
not
going
to
really
re-download
the
600
Megs,
it's
the
same
for
podman,
because
podman
is
before
sorry
for
can
can
is
creating
containers
in
the
end,
so
it
pulls
the
image
it
creates
the
containers
and
when
the
image
are
downloaded
already,
you
can
create
as
many
cluster
like
quickly,
because
the
image
is
already
here
and
available.
Yeah.
A
So
we
have
a
first
cluster
deploy
if
we
do
podman
as
yes,
sorry,
we
see
that
we
have
two
images:
one
for
Dev
worker
and
one
for
Dev
control,
plane
and
those
are
pretty
much
our
kubernetes
nodes
that
is
running
as
a
Docker,
Docker
images,
Docker
container,
sorry,
and
just
to
prove
that
the
cluster
is
up
and
running.
If
you
do
Coral
get
nodes,
we
can
see
that
we
have
two
two
nodes:
one
is
for
control
plane.
One
is
for
worker.
A
A
B
The
difference
here
with
the
second
one
is,
instead
of
using
one
API
server
and
one
worker
node,
where
we
only
have
one
API
servers
that
will
also
be
the
worker
node
and
for
the
sake
of
the
demonstration,
we're
also
changing
the
version.
So
this
one
is
version
1.25
dot,
something
the
two.
This
stanza
is
pretty
long
and
complicated,
it's
the
full
hash
to
to
whatever
and
it
changes
every
time
there
is
a
new
kind
release.
B
That's
usually
how
you
want
to
do
that.
So
that's
why
it's,
and
so
what
I
do?
Is
this
kind
cluster
yaml
file
I
store
that
in
my
kubernetes
folder,
and
so,
if,
like
I,
can
reuse
this
file
to
deploy
this
exact
same
cluster
same
configuration
on
another
another
laptop
or
I
can
totally
destroy
the
cluster
and
recreate
it
exactly
the
same.
So
that's
very
useful
when
you
want
to
trash
the
cluster,
you
want
to
deploy
something
to
break
it
and
you
can
recreate
it
exactly.
The
same
same
version
same
everything,
yeah.
C
B
Good,
so
that's
also
another
difference
is
because
you
have
this
config
file,
it's
very
easy
to
bootstrap
multiple
clusters
on
on
the
same
laptop,
which
is
a
little
bit
harder,
maybe
or
even
impossible,
with
Docker,
desktop
or
or
even
Colima.
I.
Don't
even
know
how
to
do
that.
Having
multiple
clusters
by
default
with
Colima,
maybe
it's
possible
I,
don't
know,
but
Kini
is
just
your
kubernetes
cluster,
so
you
can
start
the
numbers
of
cluster.
You
want
yeah.
A
So,
okay,
so
now
we
have
Cube
cuddle.
We
have
kubernetes
cluster
deployed
now.
The
next
step
is
basically
to
connect
Cape
Coral
to
kubernetes.
Quest
right
basically
want
to
authenticate,
and
this
is
pretty
much.
You
know
the
scenario
where
you
have
a
laptop
and
you
need
to
be
able
to
communicate
for
kubernetes
API,
and
you
know
talk
to
kubernetes
how
we
can
do
that.
A
A
Yeah,
so
we
need
a
cubeconfig
file
that
basically
tells
us
where
to
connect
and
how
to
connect
and
I
have
actually
a
quick
demo
just
to
show
how
we
can
work
with
they
keep
config
file,
so
usually
the
once
once
kubernetes
clusters
of
kind
get
deployed.
What
it's
going
to
do.
It
will
automatically
update
cubeconfig
file,
so
it
will
already
populate
all
the
configuration
for
us.
So
it's
kind
of
you
know
easy
start.
It's.
B
Kind
of
a
managed
file-
usually
you
don't
want
to
go
play
in
that,
because
that
when
you
have
multiple
clusters
with
a
like
security
CRT
certificates
in
that
for
authentication,
it
gets
very
like
big
and
difficult
to
read
so
there's
twoing
around
that.
But
but
that's
where
everything
happened
actually
exactly.
A
So
what
we
have
inside
of
the
cubeconfig
file
is
actually
it's
pretty
simple
file
right
I,
try
to
minimize
it
as
much
as
I
can,
but
basically
you
have
here
clusters,
contexts
and
users
right
so
clusters.
If
we
open
up
clusters
is
pretty
easy.
Basically,
this
cluster
is
trying
to
connect
to
gkey
Cluster.
This
cluster
is
trying
to
connect
to
one
of
the
kind
Dev
local
cluster,
so
the
IP
address
you
see
here
is
the
controller
API
controller
IP
address
that
it
communicates.
So
this
is
very
similar
to
vmw
right.
A
Next
thing
we
want
to
touch
base
is
users,
so,
as
you
know,
kubernetes
doesn't
have
users
so
the
way
we
have
establish
this
communication,
for
example,
for
current
clusters,
we
are
creating
during
the
kubernetes
cluster
bootstrap.
It
generates
certificate
keys
from
that
cluster,
and
it's
happened
many
times
where
you
know
you,
you
bootstrap,
you
get
the
certificates
and
they
have
expiration
date
one
year.
A
So
if
you
didn't
upgrade
your
cluster
for
one
year,
you
might
get
expired
certificate
so
something
to
look
for
for
a
cloud
cast
through
the
cloud
you
know
like,
for
example,
gkey.
You
can
see
here
they
have
actually
a
little
bit
more
authentication
provider
configuration.
So
this
is
more
secure,
but
essentially
you
know.
This
is
a
certificate
that
coming
from
cluster,
that
let's
communicate
with
the
kubernetes,
and
then
we
have
context
right
so
context
is
basically
tells
where
to
connect,
and
then
we
have
also
the
current
context.
A
So
current
context
is
basically
tells
right
now
my
cubeconfig
file
is
looking
at
staging
cluster
and
the
reason
it's
looking
for
the
staging
cluster,
because
the
last
cluster
we've
deployed
in
the
demo
was
staging
cluster.
So
it's
probably
you're
going
to
ask
how
we
can
switch
that
to
another
one,
and
this
is
actually
pretty
straightforward,
but
still
complicated,
at
least
for
me,
because
there's
many
commands
that
you
need
to
run
in
order
to
get
there.
A
We
can
also
see
what
type
of
context
we
have
in
our
config
file.
So
we
can
see
here
that
we
have
kind
depth
and
staging
NG
key
cluster,
and
we
can,
for
example,
switch
back
to
kind
of
kubernetes
cluster
by
running
cube
cutter,
config,
use
context,
kind
Dev.
So
once
I
do
that,
if
I
do
get
context,
you
can
see
that
my
current
context
switched
from
current
staging
to
kind
of.
So
this
is
the
way
that
you
have
to
do
like
every
time
to
switch
between
clusters.
A
It's
not
the
best
option
and
we're
going
to
talk
a
little
bit
more
in
the
future,
like
once,
we
go
to
a
more
advanced
tool
how
to
simplify
this
pane,
but
for
now
we're
going
to
go
forward
and
in
general
you
can
also
like
there's
some
people
like
to
split
up
these
cubeconfig
files
into
multiple
files,
so
this
is
also
covered
here.
If
you,
you
know,
if
you
want
to
do
that,
you
can
try
it
so.
A
Right
so
so
now,
like
now,
you
have
kubernetes
cluster.
You
authenticated
with
your
Cube
cuddle
command.
The
next
thing
you
want
to
do
is
deploy
resources
right,
so
we
have
two
commands:
Cube
cuddle,
create
and
keep
cuddle
apply,
and
obviously
you
know
like
the
first
steps
that
you
might
do
is
to
run
Cube
cuddle,
create
deployment,
create
service,
create
config
map.
This
is
more
imperative
way
where
you
basically
specifying
similar
to
what
you
you
know.
We
did
before
with
virtual
machines
just
running
commands
this.
This
method
is
not
recommended.
A
I
would
say
it's
good
to
starting.
We
always
recommend
to
use
yaml
manifest,
because
it's
a
declarative
way.
You
basically
Define
your
state
in
the
yaml
file
and
then
Cube
color
will
apply
this
request
to
kubernetes
Cluster
and
we
have
something
called
control
manager
that
will
every
now
and
then
synchronize
the
state
of
the
you
know
what
is
stored
in
its
CD
to
the
kubernetes
cluster.
So
we
call
this
the
declarative
way,
and
this
is
the
beauty
of
kubernetes
and
we
highly
recommend
you
to
use
manifest
files.
B
A
Yeah
so
the
first
thing
I
also
like
to
mention
before
we're
gonna,
go
to
like
deploying
things
like
we
want
to
quickly
talk
about
the
namespaces,
so
kubernetes
has
once
you
deploy
a
kubernetes
cluster
out
of
the
box.
It
has
multiple
name
spaces
that
it
it
deploys
and
the
first
name
space
is
called
default.
So
this
is
where
your
current
context
is
looking
for.
Every
time
you're
gonna,
you
know
start
with
kubernetes
cluster,
it's
going
to
be
pretty
much
looking
into
the
default
namespace.
A
This
is
not
a
good
practice
and
we're
going
to
show
how
you
can
deploy
things
in
a
different
name:
spaces
there's
also
Cube,
not
least
cubenot
public
Cube
Cube
system.
Those
those
are
the
things
that
is
created
by
the
cluster
itself.
So
Cube
system
is
a
namespace
that
pretty
much
runs
a
control
plane
for
kubernetes.
A
C
A
A
A
Yeah
so
we
created
a
service
and
deployment
inside
of
the
cubecon
namespace.
So
that's
that's
the
first
demo
and
then
we're
going
to
create
a
pod
that
is
basically
created
the
cloud
declaratively
with
the
ammo
and
for
that
we're
actually
using
interesting
command,
which
is
called
Cube
cuddle
around,
which
creates
pods
and
we're
using
Dash
oyama
that
basically
generates
dumps
everything
in
the
yaml
file
and
we
are
using
dry
run
client
command,
which
is
basically
doesn't
apply
it
on
the
cluster.
But
you
know
just
on
the
client
side.
B
A
B
B
Now
we're
getting
closer
to
the
interesting
thing
where,
but
we
still
need
more
in
the
Clusters
so
to
be
able
to
demo.
So
it's
a
simple
web
application.
So
it's
a
go.
Application
a
web
app
that
we
built.
We
created
an
image
and
there
is
a
my
SQL
database
along
that
they
tied
together
and
and
so
just
sample
application
very
two
deployments.
A
Two
Services
all
right,
so
things
are
coming
up
slowly,
so
the
difference
here
we're
using
a
declarative
way.
We
have
generated
the
yaml
file
and
this
is
you
know
this
is
how
it
looks
like
it
looks,
there's
more
lines
there.
We
try
to.
You
know,
follow
the
best
practices
added
liveness
prop
Readiness
props
request
request
resources.
So
this
is
how
you
know.
Ideally,
you
should
look
into
deploying
application
into
kubernetes
cluster.
B
That's
what
you
would
do
in
real
life,
because
this
yaml
file
would
be
in
your
git
repo.
So
let
me
introduce,
can
alright
get
UPS
do
get
up,
so
you
put
all
that
diamond
in
a
repo,
a
new
version
that
and
you're
good
to
go.
Okay.
So
so
now
we
have
the
basic
stuff
as
you've.
Seen
like
we
cooked
all
yeah.
A
B
I,
don't
know
next
one
yeah
yeah,
so
aliasing
so
k-u-b-e-c-t-l,
it's
too
long
like
let's
use
an
alias
like
k
equals.
So
now
it's
just
K
you
put
that
in
your
shell.
So
every
time
you
open
a
new
terminal,
you
will
have
this
Alliance
already
defined
I,
don't
remember:
let's
go
there.
I'm
typing
too
much
yeah
yeah,
just
I
asked
that
we
we
copy
that
we
switch
to
terminal
it's
not
working.
Okay,
Alias,
okay,
again.
B
And
now
K
get
bonds.
Oh,
like
it's!
It's
five
letters
already.
It's
not
one.
Two,
three,
four,
five,
six
letters,
less!
That's
the
first
trick
and
seriously
you
can
imagine
how
many
people
even
trained
with
kubernetes.
They
don't
use
that
they
don't
know
or
they
just
like
they're
used
to
type
cuddle
and
I'm.
Sorry,
the
last
I
type,
the
more
I
feel
kubernetes
is
based
on
apis
and
and
resources
and
pods
deployments.
Usually
the
by
default
resources
are
plural,
so
you
have
an
S
at
the
end
of
most
of
them.
B
B
B
I
can
handle
that,
so
there
is
completion
in
most
of
the
shells
now
bash,
crsh
or
whatever,
and
every
most
of
the
kubernetes
clis,
whoever
they
are.
They
usually
have
a
completion
file,
so
you
could
cut
all
completion
dsh
or
it
could
cuddle
completion
bash
and
it
will
dump
us
a
long
list
of
things
for
the
shell
to
be
configured.
B
B
Okay,
pour
it
forward
and
there
there
you
go
so
I,
just
type
poor
tab,
Port,
four,
it's
even
better
than
that,
because
what,
if
I
get
pods
okay,
but
this
is
the
default
namespace
we
deployed
also
in
the
crypto
space
so
minus
and
to
to
Target
another
namespace
and
then
tap.
Oh,
what
do
I
have
so
in
the
background
will
get
namespace
was
run,
grab
the
list
and
then
I
have
all
that
as
options.
So
I
want
to
look
in
the
coupon
actually
Cube
tab.
B
B
Is
that
will
come
in
and
the
go
client
program
for
for
group
cuddle
is
Sometimes
using
a
lot
of
resources
like
opening
a
lot
of
files,
doing
a
lot
of
calls
to
the
API
server
most
of
the
time
on
Mac,
the
the
number
of
Max
open
file
is
like
256,
or
something
or
like
that.
So
it's
usually
a
good
practice
to
like
raise
that
a
little
bit.
B
B
Okay,
okay,
so
this
talk
is
based
on
dsh,
so
we
picked
all
my
CSH.
Oh,
my
CSH
is
a
framework
that
you
install
in
your
shell.
It's
going
to
like
bring
up
a
lot
of
of
things
already
set
up
for
you
shortcuts
and
like
we're
going
to
see
a
lot
of
stuff
plugins,
for
example
here
and
what
plugins
do,
for
example.
B
Let's,
let's
have
a
look,
can
we
have
a
look?
No,
not
yet
okay,
I'm
going
to
to
finish
these
slides
first,
and
there
are
themes
that
you
can
apply
on
my
CSH,
so
I
used
to
use
agnoster
CSH,
damn
theme
for
a
long
time.
It's
very
good!
It's
like
bringing
a
lot
of
different
things
and
then
I
discovered
the
power
level
10K.
B
A
B
B
So
what
do
you
get
when,
when
you
install
that
so
remember,
we
here,
Arcadia
is
the
name
of
my
laptop
everything
is
black
and
white,
maybe
like
a
lot
of
views
to
read?
Okay,
when
you
install
when
you
install
the
the
oh,
my
zsh,
plus
the
poor
phone
shell,
the
poor
line,
shell,
you
get
a
prompt
and
what
is
the
prompt,
The
Prompt
is
here
at
the
side
on
the
left
side
and
on
the
right
side
of
your
of
your
shell.
B
You
have
some
information
by
default,
so
all
that
can
can
be
changed
to
it
and
whatever
so
here
on
the
left.
I
have
like
Apple,
because
I'm
on
a
Mac,
I
guess
the
smaller
house
just
because
I'm
in
my
default
user
folder.
So
if
I
go
in
the
demo,
folder
for
example-
and
you
see
when
I
do
a
tab,
for
example,
completion
is
now
red.
So
it's
easier
to
read
already
okay,
so
then
I'm
in
a
folder
about
the
demo.
B
There
is
a
lot
of
things
that
is
coming
with
the
installing
this.
This
tool,
like
oh,
my
CSH
and
the
theme
and
I'm,
not
an
expert
in
that
like
it's,
bringing
maybe
I'm
using
like
five
percent
of
the
thing
and
like
people
will
keep
asking
me
like.
Why
should
I
install
that,
like
it's
doing
too
much
for
me?
B
Let's
say:
I
go
back
here,
I
go
in
there,
personal
on
GitHub
and
I,
go
to
the
cloud
native
Canada
here
and
then
this
is
our
repo
for
the
for
the
presentation
and
you've
seen
the
The
Prompt
is
now
green
and
we
have
a
small
GitHub
thing
and
we
have
a
kind
of
let's
say
a
branch
and
I'm
actually
on
the
branch
last
tuning
right
now.
So
I
can
like
get
Branch
branch
me
me
and
keep
damn
it
check
out.
B
B
B
B
Three
letters
and
I
have
all
my
pods
or
services.
No,
yes,
sir.
Yes,
okay
get!
Yes,
you
see
I'm,
not
using
that
much
actually
I.
Don't
know
why
I'm
trying
I'm
used
to
k
something
so
I'm
using
K
instead
of
two
color
I'm,
not
using
all
these
aliases,
but
sometimes
there
are
like
they
can
get
very
efficient
and
the
more
you're
tapping
and
and
using
the
long
comments
like
port
forward
roll
out
history
scale
deployment,
for
example.
B
That's
three
letters
instead
of
a
whole
lot
of
comments,
so
we're
switching
now
to
keep
color.
So
we,
as
we
said
it's
still
black
and
white
in
the
terminal
and
maybe
not
really
not
easy
to
read
Cube
color-
is
a
tool
that
was
developed
some
time
ago
and
was
unmaintained
in
the
last
few
years.
So
I
decided
recently
to
like
Clump
the
thing
and
making
it
live
again
apply
the
patches.
So
it's
straightforward
to
install
it's
Brew
installed.
B
So
there
is,
the
new
project
is
in
Cube,
color
folder,
so
it's
Brewing,
Salt
color
tab
could
color.
You
can
grab
the
version
from
the
the
GitHub
repo.
You
can
install
that
directly
from
go
if
you
have
the
the
go
command
line,
so
this
is
a
way
to
set
the
version
to
latest,
for
example,
but
you
can
pick
any
version
you
want
and
the
color
is
kind
of
a
replacement
for
good
color.
B
It's
not
actually
a
replacement,
because
Cube
color
is
going
to
call
in
the
background
and
it's
going
to
take
the
output
from
crypto
and
color
it.
So
let's
just
have
it.
What
did
I
do
so
yeah?
This
is
the
difference
we
had
only
black
and
white,
and
now
we
have
like
black
white
and
blue
wow
that
that's.
C
B
One
one
color
better:
okay,
but
what
happened
in
the
real
life?
You
have
crass
crash
pods.
You
have
both
just
started,
so
you
can
change
all
that.
So
it's
pretty
obvious
that
in
the
default
namespace
the
test
spot
is
not
running
here.
It's
pretty
obvious
that
the
age
is
only
six
minutes
ago.
So
that's
my
new
deployment
actually
that
just
failed
and.
B
B
So
now
we
have
an
alias
so
K,
again,
K
get
pot
bam.
I
have
the
coloring
here,
I
can
describe.
Okay
describe
put
go
web
app.
Like
the
you
know,
the
simple
deployment,
for
example,
simple
deployment,
blah
blah
blah
and
here
again
I
do
have
some
coloring
in
here.
So
it's
very
easy
straightforward
to
see.
What's
going
on
here,
the
last
message
that
is
failing,
it's
a
great
helper,
so
that
is
good
color.
B
One
so
the
next
tool
is
Stern,
Stern
I,
don't
know
why
I,
who
knows
about
Stern
already
one
two,
three
four,
maybe
five,
it's
an
a
very
interesting
Tool
Stern
is
a
way
to
add
colors
and
to
to
to
filter
how
you
get
the
logs
from
the
pot
like
logs
is
a
command.
You
run
a
ton
of
time.
Usually
you
deploy
something.
It's
not
working.
You
want
to
go
and
see.
B
What's
happening,
you're
going
to
grab
the
logs
what
is
turned
giving
you
is
coloring
with
different
colors
every
pot,
and
if
you
have
multiple
containers
inside
the
Pod,
there
will
be.
There
are
going
to
be
added
here.
Also,
that
means
in
one
command.
You
can
all
the
logs
of
all
the
containers
inside
inside
a
pod
is
that
for
service
mesh
in
this.
B
B
B
So
usually
you
would
do
that.
Like
do
we
have
the
multi-deployment
or
this
is
so.
Let's
deploy
that
it's
another
thing
we're
deploying
and
then
we
can
look
at
it.
So
K
get
pod.
Okay,
we
don't
care,
we
did
that
already
K
locks.
Okay,
this
is
what
you
usually
do.
Is
K
logs
in
the
default
name,
space
with
a
selector
I
want
the
logs
from
the
application,
which
has
a
live,
a
label
app
equal
multi-deployment
and
that's
usually
what
you
do
and
what
you
get
is.
B
Because
we
have
it's
a
deployment,
we
have
two
parts
we're
getting
the
logs
from
the
two
pods
but
defaulted
container.
First
out
of
first
and
second:
that's
they
there's
two
containers
inside
the
Pod
and
K
logs
is
only
giving
the
for
the
first
container.
If
you
want
the
second
one,
then
you
have
to
tell
it
like
at
one
second
and.
B
B
Look
at
that
Stern
multi
and
then
we
have
like
in
yellow
and
green
two
different
parts
with
each
the
container
first
and
second,
which
is
named
here
first
and
second.
So
in
one
command
we
can
quickly
like
grab
all
the
the
same
kind
of
PODS.
So
that
means
the
multi
I.
Just
typed
here
is
actually
a
selector.
So
of
course
I
can
go
to
deployment
if
I
want
or.
B
Okay,
get
part
then,
or
you
can
Target
one
specific
if
you
want
so
you
can
put
the
full
name
so
and
there's
a
lot
of
other
options.
We're
not
going
to
end
as
you
see
it.
It's
tailing.
That
means
if
new
logs
are
coming
they're
going
to
be
displayed,
that's
the
equivalent
to
the
to
the
W
option
on
the
the
cubicle
logs.
B
Sebastian,
no
we're
not
done
already,
because
we
we
have
another
staff
which
it's
it's
a
new
addition
to
what
we
do
so
we're
just
going
to
redeploy
it's
kind
of
another
version
of
the
same
deployment
here.
The
difference
as
you
can
see
here
is
it's
very
dumb.
You
never
do
that,
but
when
the
container
is
starting,
it's
just
echoing
something
a
message,
and
now
the
message
is
Json
and
that's
a
way
to
demo
that
with
turn
you
can
dump.
So
the
command
is
just
here.
B
Stern
multi
as
before,
but
I
want
the
output
as
Json
and
actually
I
can
pipe
that
into
JQ
and
we're
running
very
light,
so
we're
going
to
to
move
forward,
but
that's
new
options.
You
can
Json
here
or
X
Json,
which
is
giving
like
it's
parsing
the
message
itself
as
Json
to
so
Stern.
Like
it
it's
one
of
the
tools,
I
guess,
I
use
the
most.
A
Yep
thanks
Sebastian
honestly
like
if
you
saw
these
two
tools
right,
you
have
to
install
them
separately
like
binary
and
we
actually
in
kubernetes
Community.
We
actually
recently
find
a
nicer
way
to
actually
integrate
those
Solutions.
So
we
have
a
cube
cutter
plug-in
mechanism
right
now,
where
you
can
bring
the
the
different
solutions,
like
Sebastian,
showed
two
Cube
currents.
A
So
now
it's
going
to
be
part
of
the
cube,
cuddle
command
line
right
so
and
the
way
you're
going
to
be
doing
this
is
you
can
go
to
a
cube
the
website
which
is
called
crew.
So
a
crew
is
a
cube,
cutout,
plugin
manager,
and
if
you
go
on
their
website,
you
can
actually
see
that
today
they
have
over
200
different,
interesting
plugins
that
you
can
use
we're
gonna
cover,
maybe
a
few
of
them.
A
The
most
interesting
ones,
but
like
I,
think
this
is
a
you
know,
a
nice
way
to
actually
bring
any
nice
ideas
like
Sebastian
had
with
Cube
color.
It
probably
should
be
here
at
the
plugin
manager
for
for
crew,
so
crew
is
basically
all
it
does.
Is
it
stalls
the
plugins
for
could
cuddle
and
one
of
the
plugins
that
we
want
to
shows
actually
first
plugin
that
we
want
to
mention
is
something
called
need,
so
I
keep
cutting
it.
B
The
idea
is,
when
you
cook
a
little
get
something
in
the
cluster.
You
will
get
the
yaml,
but
you
will
get
a
ton
on
of
other
information
that
you
don't
care
about.
If
you
watch
one
is
the
actual
yaml
or
even
the
Yamaha
storage
somewhere
for
reuse
or
store
it
modify
and
and
reapply
so
neat
is
a
plug-in
that
is
tripping
everything
that
is
not
needed.
That
is
specific
to
this
deployment
or
this
and
is
not
needed
to
replicate
or
to
store
the
yaml.
So
we
don't
need
the
demo.
A
A
A
Yeah
all
right,
another
plugin
that
we
want
to
show
is
a
cube
cutter
CTX.
So
this
one
is
basically
lets
you
easily
switch
clusters.
So
if,
if
I
run
CTX
CTX,
you
can
see
our
current
cluster
is
kind
of,
so
we
can
actually
change
it
to
staging
with
one
Command
right.
So
it's
much
easier
experience
than
before.
We
have
to
like
type
three
commands
to
list
our
current
context
and
then
switch
to
the
context.
B
B
Be
or
yeah-
and
we
have
another
option
like
when
you
when
you
as
you
saw
the
context,
is
written
in
the
kubeconfig
file,
so
it's
Global.
So
if
you
have
multiple
shells
and
you
switch
one
to
another
namespace,
all
your
channels
are
going
to
be
switched
to
another
namespace.
So
QB
is
a
way.
It's
a
it's
a
little
application
that
is
using
the
the
the
color
mechanism
and
and
kind
of
stripping
your
your
configuration
file
to
be
specific
to
the
Shell.
B
So
when
you
you
use
QB,
it
works
almost
the
same
as
CTX
is
QB
CTX
and
you
select
a
a
cluster,
and
this
cluster
will
be
the
only
one
known
by
the
shell.
That
means
you
can
then
change
the
default
context.
It
will
not
change
in
this
channel.
So
if
you
have
multiple
share,
you
can
have
one
specific
to
your
development
and
another
shell
for
staging,
let's
say
and
the
third
one
for
production.
A
B
B
B
So
all
this
is
coming
from
the
theme,
the
it's
working
for
K,
it's
working
for
cuddle,
it's
working
for
istiocre,
for
example,
and
all
that
is
something
that
you
can
configure.
Actually,
when
you
install
the
theme,
you
have
a
p
10K
zsh
file
that
is
created
with
all
your
configuration
and
if
we
search
for
cuddle.
B
Free
search
for
kukuro
here
we
have
a
power
level
9
key,
so
some
of
the
commands
are
still
named
about
the
previous
version:
9k
instead
of
10,
but
here
is
the
list
of
all
the
comments
that
will
act
as
if
it
was
scripted
and
will
display
this
prompt.
This
Dynamic
prompt,
and
you
have
that
for
crypto.
You
have
that
for
terraform,
you
have
that
for
AWS
CLI
you
have,
and
there
is
a
ton
of
information
and
of
stuff
you
can
configure
in
this
and
and
again
this
all.
This
is
coming
like
for
free.
A
Cool
all
right,
thanks,
I
will
yeah
I'll
carry
the
rest
part.
So
we
obviously
you
can
do
similar
things
with
your
Cloud
providers,
but
we
want
to
move
forward
and
just
quickly
touch
base
on
the
part
how
you
can
actually
deploy
your
applications
right.
So
usually,
when
you're
deploying
your
application
to
Dev
staging
and
production
environment,
there's
going
to
be
some
changes
in
your
deployment
right
and
what
are
the
options
you
have
out
there
in
order
to
solve
this
challenge?
I
have
my
personal
recommendation?
A
Is
you
know
if
you
have
something
simpler
to
deploy,
and
you
know
we
have
a
nice
tool
called
customize
right.
Customize
is
a
kubernetes
native
template
free
way
to
customize
applications?
So
you
have
your
existing
yaml
file
and
you
create
a
customization
file
that
will
customize
it
for
Dev,
staging
and
production,
and
you
can
apply
this
manifest
with
changes
to
the
different
environments.
A
So
basically,
your
existing
manifest
is
not
going
to
change,
so
we
call
it
base
you're
gonna
create
a
folder
structure
for
your
overlay,
which
is
going
to
be,
but
maybe
in
this
case
Dev
staging
in
production-
and
you
will
say,
I
want
to
modify
my
deployment
only
and
I'm
going
to
be
changing
replica
count,
for
example,
for
my
file.
So
this
is
an
example
where
we're
using
customize.
A
We
have
base
yaml,
which
is
our
you
know,
untouched
existing
manifest,
and
we
have
Apache
ammo,
which
is
we
call
overlay,
and
when
we
combine
those
changes
together
on
the
right
side,
you
can
see
that
the
the
the
Pod
took
the
value
from
our
patch
right.
So
you
can
imagine
that
basically,
you
can
apply
the
similar
one,
but
for
staging
similar
one
for
production,
so
you'll
be
able
to
modify
your
deployment
without
any
pretty
much
changes
configurations
you
can
easily
to
modify
it.
This
is
on
the
left
side.
A
This
is
the
structure
of
the
customized.
So
if
you
want
to,
you
know
build
it,
you
have
your
base,
which
is
your
existing
yamu
manifest.
In
this
case
there
is
a
folder
called
Dev.
They
could
be
other
folders
like
staging
production
and
that's
where
you're
putting
your
customizations
right
and
then
you
can
build
hydrated
manifest.
That
has
already
the
values
that
needs
to
be
deployed
for
Dev
environment
and
you
can
do
keep
cut
out
deployment.
A
Sure
now
we
have
another
tool
which
is
called
help
right
and
how
it's
a
little
bit
different.
It's
something
you
you
have
to
templatize
right.
So
we
think
Helm
is
a
great
solution
for
things
that
already
exist
out
there.
So
if
you
want
to
install
any
application
that
you
see
at
kubecon
or
any
database,
we
have
artifact
Hub,
that
stores
all
the
help
charts
and
you
can
deploy
any
existing
applications.
A
B
And
yeah
the
interesting
part
here
man-
because
maybe
maybe
it's
not
well
known
it's
when
we
deploy
with
hell
I,
wanted
to
emphasize
on
how
this
kind
of
comment.
But
there
are
like
quite
new
I
guess,
maybe
for
with
Helm
three
Helm
show
values,
so
you
can
display
the
values
that
are
defined
in
the
chart.
So
if
you
don't
know
what
to
tune
before
you
deploy,
you
can
have
a
look
at
them
very
quickly
and
then
you
have
Helm
templates
to
generate.
B
So
you
see
I
I've
said
some
alerts
here,
so
I'm
changing
some
values
that
I
grabbed
just
from
the
command
above
and
I'm
just
generating
the
template
for
review,
then
I
can
install
once
you
install
Helm
will
create
a
secret
in
the
namespace
where
you
deploy
the
application
and
in
this
name
phase
it's
going
to
keep
a
trace
of
what
was
deployed.
What
are
the
values?
What
are
the
yaml
and
it's
used
for
him
to
either
roll
back
or
or
or
keep
track
of
what
was
deployed?
A
Really
like
this
command,
how
diff
that
shows
yeah
difference
between
what
you
deployed
before
and
you,
let's
say,
applying
a
new
chart
with
some
modification.
It's
going
to
give
you
exactly
what
is
going
to
change
instead
of
trying
to
figure
out
all
the
changes
that
is
coming
in
that
chart.
That's.
B
Another
cool
comment:
if
you're
using
Helm
quite
often
like
install
the
plugin
for
a
for
a
div
and
then
this
this
secret
that
I
was
talking
about.
So
you
can
see
what
was
deployed
in
the
cluster
Helm
list.
You
will
see
what
what
projects
were
deployed.
History
of
the
project.
Let's
say
we
deployed
promoters.
We
want
to
see
the
history.
There
was
two
deployments
and
then
you
want
to
see
the
values
that
were
used
to
deploy
this
application
with
Helm,
so
Helm
get
values
and
you
can
have
all
that.
B
So
all
that
is
coming
from
the
secret
that
was
deployed.
So
you
can
also
because
it's
a
secret,
you
can
access
it.
So
you
see
there
is
two
secret
because
we
had
two
deployments
and
you
can
get
secret
with
this
very
funky
command
base64
two
times
and
then
unzip
you
can
see
what's
inside
the
inside
the
secret
and
what's
what
was
used
for
all.
A
Right
so
I
think
we're
getting
to
the
dark
side
of
the
things
already
like
we're
going
to
talk
about
uis,
and
this
is
like
the
ultimate
stage
and
the
reason,
probably
you
want
to
use
something
like
uis.
You
already
have
things
deployed
on
your
cluster,
but
you
want
to
try
to
figure
out,
maybe
what's
happening,
there's
maybe
many
users
on
the
cluster.
You
know
Cube
cuddle
get
commands
not
always
as
visible
right.
So
there's
actually
a
lot
of
interesting
options
out
there
that
we
want
to
recommend.
B
A
A
You
can
do
port
forwarding
out
of
this
there's
a
I
think
there
is
obviously
curve
to
learn,
but
like
once,
you
look
into
the
their
resources
and
and
helps
like
it's
starting
to
make
sense.
So
we
have
a
few
few
things
in
the
tutorial
that
you
can
probably
go
ahead
and
also
you
know,
check
at
home,
yeah.
A
A
B
Other
one
that
we
would
recommend
is
lens
lens
is
the
full
application
you
install
that
it
gets
access
to
all
the
resources.
It's
straightforward,
it's
multi-clusters!
So
it's
grabbing
the
Clusters.
You
have
in
your
in
your
group
configuration
and
you
can
switch
from
one
to
the
other.
It
the
interesting
part
that
I
kind
of
just
learned
and
I'm
not
into
uis.
But
if
you
are
I
just
talk
about
the
helm
secrets,
you
can
drill
in
the
helm
Secrets
directly
from
this
UI.
B
It's
if
you
have
Prometheus
deployed
it's
going
to
grab
the
metrics
from
your
cluster,
so
you
have
in
the
UI
already
like
a
view
of
how
the
cluster
is
behaving
and
if
you're
into
you,
deploy
the
port,
and
you
want
to
port
forward
into
it
to
check.
What's
running
on
this
port,
you
can
do
that
directly
from
the
UI.
So
it's
a
very
neat
tool.
If
you're
into
uis
yeah.
A
B
This
is
our
last
minute,
so
I'm
sorry,
we
were
like
we
spent
too
much
time
at
the
beginning.
I
guess
look
at
the
slides
look
at
that.
You
can
download
the
slides
from
from
the
the
schedule
website.
Look
at
the
content
of
the
website
in
the
GitHub
repo.
There
is
a
ton
of
stuff
like
there
is
only
three
vs
code
extensions,
but
they
are
like
worth
it
seriously
show.
Oh,
we
switch
over
yeah.
There
is
different
other
tooling.
There
is
diesel.
B
A
D
B
It's
a
great
question:
we
had
no
time
to
to
talk
about
that,
but
yeah
the
customized.
That's
why
we
recommend
I
think
it's
working.
We
recommend
using
the
full
version
of
customize.
Actually
customize
is
embedded
in
Coupe
cuddle,
but
it's
a
lighter
version.
You
don't
have
access
to
all
the
features.
Sometimes
you
may
find
some
blocking
things.
If
you
use
the
full
version.
No
problem
and
customize
can
use
plugins,
so
plugins
can
be
just
a
shell
script
or
something
or
a
container
that
is
going
to
be
run.
B
So
obviously
you
can
have
a
Helm
plugin
that
is
going
to
render
the
chart
as
yamo
and
pass
that
into
customize.
Then
you
can
use
customize
to
apply
a
patch
or
drop
or
add
something
into
the
into
the
final
yaml.
So
yeah
customize
is
a
Nifty
tool
and
it
totally
complements
and
helps
Helm,
because,
like
I'm,
not
a
ham
lover
and
for
I
guess
for
good
reasons
and
customize
can
touch
what
Helm
is
not
able
to
do.
B
Okay,
how
to
list
the
aliases
that
are
bring
up
by
by
the
the
theme
and
oh,
my
CSH,
so
it's
just
the
aliasco
man
in
the
Shell.
It's
going
to
list
all
the
aliases
that
are
created
so
I
just
showed
you
some
of
the
crypto
audiosis,
but
actually
there
is
a
ton.
Other
aliases
for
git
commands,
for
example,
exact
same
thing.
Instead
of
git
check
out
something
it's
JC
like
I,
don't
know
them
I'm,
actually
not
using
them
much,
but.