►
Description
Developing Locally with Kubernetes [I] - Ryan Jarvinen, Independent
This talk will cover several common local development scenarios, and will review the major tradeoffs found when adopting minikube, minishift, draft, and other popular tools for enabling local development of distributed web solutions.
Learn how using Kubernetes locally can help your web teams deliver solutions faster and more reliably.
About Ryan Jarvinen
Ryan Jarvinen is a Developer Advocate and Open Source Evangelist focusing on improving developer experience in the container community. He lives in Oakland, California and is passionate about open source, open standards, open government, and digital rights. You can reach him as "RyanJ" on twitter, github, and IRC.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 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.
A
Okay,
hello
welcome
come
on
in
so
we
got
a
couple
people
still
coming
through
the
door.
It's
just
about
2:45,
so
I'm
gonna
get
move
in
with
my
talk
about
local
development,
using
kubernetes,
yeah
feel
free.
There's
a
good
number
of
seeds
down
here
in
the
front
right
feel
free
to
point
people
this
direction.
If
they
come
in
late,
all
right,
so
accelerating
local
development
with
kubernetes
I
am
Ryan
Jay.
You
can
find
me
online
on
Twitter,
github
and
IRC.
A
More
than
an
ops
person
awesome,
all
right
you
hopefully
have,
and
how
many
of
you
here
are
have
used
kubernetes
for
less
than
six
months,
excellent,
all
right!
Well,
this
is
a
very
introductory
kind
of
talk.
I'm
going
to
try
to
use
just
the
upstream
tooling
and
show
you
as
much
as
I
can
from
there
and
then
we'll
talk
about
what
additional
tooling
you
might
want
to
layer
on
as
well,
and
so
here's
my
let's
go
with
so
why
are
we
so
bad
at
pitching?
Kubernetes
I?
A
Think
it's
because
it's
primarily
you
know
it
was
a
tool
that
was
kind
of
built
by
and
for
site,
reliability,
engineers
or
operations,
folks,
or
really
folks,
that
are
looking
at
use
cases
that
are
about
system
reliability,
high
availability,
you
know,
there's
there's
a
lot
in
here
that
people
kind
of
package
into
their
description
of
what
is
kubernetes
and
it
rarely
has
any
type
of
value
or
any
type
of
resonance
with
developers,
and
often
it's
loaded
with
boatloads
of
terminology.
That
is
just
more
insult
to
injury.
A
Yet
at
the
same
time,
if
you
ask
kubernetes
core
maintainer
what
is
an
app,
they
will
very
likely
struggle
to
come
up
with
a
clear
definition,
because
there
isn't
a
clear
upstream
definition
in
the
kubernetes
community,
of
what
an
app
really
is
because
a
lot
of
it
they'll
say
well,
it
depends.
Are
you
talking
about
workloads?
A
Webpart,
you
know,
there's
there's
so
much
in
there
I
mean
people
started
off
with
docker
was
going
to
be
what
solved
it
all
we'll
containerize
all
the
things
and
then,
as
soon
as
people
realized,
we
need
to
scale
these
decompose.
These
monolithic
applications
reflect
what's
happening
in
the
micro
services
community
and
allow
these
pieces
to
be
scaled
independently.
A
That's
that's
what
your
app
is
right,
but
that's
not
a
very
clear
standards,
compliant
definition
that
we
can
that's
developer
friendly
in
any
way
right,
especially
if
they
don't
already
have
you
know
a
lot
of
kubernetes
access
to
play
with
so
there's
a
proposal
I've
linked
to
around
label
recommendations,
I.
Think
if
you're
a
app
developer,
definitely
look
into
whether
this
proposal
fits
the
bill
for
you.
Does
it
meet
your
needs?
A
Does
it
make
sense,
as
far
as
how
we
model
apps
I,
think,
there's
still
a
lot
more
work
to
do
in
helping
define
this
term,
but
what
you
can
do
in
the
meantime
is
start
talking
about
kubernetes
in
in
a
way
that
hopefully
makes
a
little
bit
more
sense
to
developers
and
I'll
try
to
show
that
today.
So
this
is
where
I
want
to
get
us.
I,
don't
know
if
we
can
get
there
today,
but
what
I
want
everyone
to
confidently
say
eventually.
Is
why
kubernetes
development
velocity?
That's
why
right?
A
Just
behind
him.
We've
got
Will
Ferrell,
that's
our
our
front-end
web
developer
right
and
the
product
team
is
over
on
the
far
end
and
I
invest
in
a
nice
jacket,
so
generally
operations
teams
will
come
in
and
and
they'll
realize
that
you
know
the
the
dev
teams
been
working
non-stop
they've
been
accumulating
technical
debt.
A
Why
is
he
obsessed
with
things
that
have
nothing
to
do
with
what
we're
responsible
for
we
need
to
ship,
we
need
to
ship
product,
we
need
to
ship
features
and
we
need
to
ship
them
faster
than
our
competitors
right.
We're
not
shipping
kubernetes,
we're,
not
shipping
developer
tools
go
find
the
best
in
the
industry.
Use
those
and
let's
get
back
to
business
is
generally
the
conversation
and
the
inertia
that
you
need
to
overcome.
A
They're
always
going
to
want
more,
and
the
web
team
is
going
to
honestly
want
to
know
how
do
I
maintain
my
velocity
while
using
containers.
It's
a
fair
question
and
the
kubernetes
community
needs
to
have
a
real
answer.
So
I've
tried
to
package.
So
don't
screw
it
up
for
us
Jeanne,
we
need
to
get
there
to
container
town.
We
need
to
roll
out
kubernetes.
A
A
We
use
read-only
whenever
possible
and
if
you
expect
that
data
to
stay
around
you're
gonna
want
to
use
a
volume
or
some
kind
of
persistence
mechanism
so
make
sure
as
developers
that
is
clearly
in
your
scope
to
know
where
your
data
is
as
you're
operating
on
it
and
then
the
third
one
is
really
kind
of
evaluate
what's
available
as
far
as
toolchain
goes
and
and
choose
what's
the
what's
the
best
of
the
day,
so
here's
the
easy
part
mini
coop
start.
That's
it
it's
one
command!
Well,
there's
one
other
curl!
A
You
could
do
a
to
commands
if
you
want
to
do
a
curl
and
then
pipe
it
into
your
user
local
bin.
You
know
you
could
do
a
one-line
install
and
then
a
one-line
boot
up
essentially
but
mini
coop
start.
Is
the
easiest
way
to
get
going
I'm
going
to
open
up
a
terminal
and
just
paste
in
just
so.
You
could
see
how
easy
it
might
be.
This
is
using
a
virtualization
mechanism
to
spin
up
a
VM.
They
also
have
a
new
way.
You
could
do.
A
Vm
provider
equals
none
and
then
it'll
try
to
skip
the
virtualization
and
spin
up
kubernetes
using
only
containers.
You
need
a
docker
engine
or
something
for
that,
but
looks
like
I'm
up
and
booted
I
didn't
need
to
sign
up.
I
didn't
need
to
wait
for
the
ops
team
to
provision
any
servers.
I'm
now
unblocked
right.
So
that's
that's
the
this
is
the
easy
part
make
sure
that
everyone
knows
not
having
a
kubernetes
environment.
Ready
is
not
an
excuse.
A
Stagings
down,
ops
isn't
ready.
No,
everyone
gets
a
kubernetes.
You
all
look
under
your
seats.
You
all
get
a
kubernetes
mini
Kubb
is
yeah
the
best
way
to
get
started
on
that
today.
Yeah
any
coop
start
I
have
a
link
to
the
official
mini
coop
Doc's.
If
you
want
setup
help,
I
also
have
a
set
of
slides
I
put
together.
I
do
a
lot
of
presentations
and
so
I've
put
together
a
series
of
getting
started
with
kubernetes.
That's
all
about
half
an
hour
to
one
hour
chunks.
A
So
if
you
end
up
at
this
bitly
k8s
mini
coop,
I've
got
about
four
different
half
an
hour
long
chunks
of
what
one
is
just
the
set
up.
Next
one
is
getting
familiar
with
coop
CTL.
So
if
you
want
to
learn
more
I've
got
a
whole
series
on
that
share.
What
you
know
is
the
next
big
tip
and,
like
I
said,
model
your
I/o
as
developers.
That's
going
to
be
a
major
part
of
what
you're
gonna
need
to
be
aware
of.
A
Here's
one
way,
I
like
to
share
what
I'm
working
on
so
if
I'm
starting
from
scratch
and
all
I
have
is
a
repo
and
I've,
maybe
maybe
a
docker
file.
I'm,
not
gonna!
Start
you
guys
entirely.
Like
you,
don't
know
what
containers
are
I'm
assuming
you
you're
here
at
a
kubernetes
conference,
I'm,
just
gonna
assume
you
have
a
docker
file
or
a
docker
image,
or
some
kind
of
container
image
that
you
could
coop
CTL
run.
So
if
I
do
this,
coop
CTL
run
command.
I
can
name
my
application.
A
If
you
will
load
this
image
and
while
I'm
at
it
I
can
also
add
a
load
balancer
that
is
compatible
with
many
Kubb
and
then
add
this
dry
run
flag.
This
is
kind
of
a
complicated
example,
but
dry
run
allows
me
to
do
something,
particularly
special,
that
allows
me
to
share
what
I
know
with
other
folks.
So
normally,
if
I
ran
this
command
without
the
dry
run,
it
would
immediately
go
provision
the
new
container
using
a
deployment
and
it
would
set
up
a
service
or
a
load
balancer.
So
I
can
contact
this
this
web
service.
A
A
A
Let's
see
no
outputs,
oh
oh
I,
piped
it
all
to
this
metrics
file.
Here
we
go
metrics
review,
so
it
looks
like
the
first
data
element.
I
have
is
a
service
and
then
I
have
a
deployment.
So
this
is
now
something
that
I
can
take.
Oops
I
can
take
that
run.
Coop's
ETL
create
F
on
that
file
or
hand
it
to
someone
else
and
allow
them
to
run
Coop's
ETL
create
F
and
they
have
their
local
development
now
staged
up
with
whatever
I
wanted
to
deliver
right.
They
have
something
that
they
are
now
at.
A
Their
I
was
able
to
deploy
hello,
world
I
haven't
iterated
on
hello
world
yet,
but
I've
I've
deployed
it
locally
and
that's
one
significant
step
in
your
onboarding
process
for
new
developers.
Next
they're
going
to
want
to
test
that
mini
koobs
service
allows
you
to
open
up
that
new
deployed
resource
in
your
browser.
It
looks
like
this
is
still
downloading
the
container,
but
it
should
pop
open
in
the
browser.
As
soon
as
that
downloads
completed.
A
And
if
the
y5
holds
up,
let's
see
what
we'll
be
doing
is
checking
out
a
copy
of
this
repo.
Well,
then,
using
the
mini
cube
mount
command
to
mount
the
repo
folder
inside
the
virtual
machine
right.
So
now
it's
essentially
exposed
to
the
node
or
the
host
machine
inside
the
mini
coop
environment
and
I'm
gonna
expose
that
inside
the
VM
on
var
dub,
dub,
dub
HTML
looks
like
I've
got
a
little
bit
of
a
weight
here,
see
if
there's
a
network
cable,
they
told
me
there
would
be
Ethernet.
A
Okay,
here's
our
deployment
has
finished.
So
it
looks
like
part
of
our
download
happened,
and
hopefully
that
cleared
up
bandwidth
for
the
rest
of
my
network
connection.
But
this
is
what
I
was
deploying
it's
a
some
kubernetes
contributor
graphs
that
I
was
kind
of
tweaking
on
some
some
data
for
contributor
graphs,
and
this
was
an
example
project
that
I
wanted
to
iterate
on.
So
it
looks
like
we've
created
the
new
open
the
browser
session.
We've
got
our
local
clone
of
the
repo.
Let
me
get
out
of
full
screen
mode:
okay,
oops
too
far
back
okay.
A
Here
we
go
dry,
run
modeling.
Your
eye,
oh,
we
did
the
clone
now
I
can
mount
this
folder
inside
the
VM
and
I'll
need
to
leave
this
window
open
to
keep
that
connection
available
to
mini
cube
next
I'm
gonna
make
a
copy
of
metrics
review
and
I'm
gonna
modify
it.
This
is
something
that
you
will
have
to
do
by
hand,
unfortunately,
but
now
that
you
have
a
starting
point,
it's
easier
to
go
in
and
look
up
what
is
a
pod?
A
What
is
a
service
and
then
look
up
the
actual
spec
find
out
what
fields
and
what
values
you
might
want
to
tweak
and
then
go
based
on
the
spec.
Now
that
you
have
a
valid
starting
point,
so
this
I
actually
have
a
completed
copy
of
all
of
these
modifications
inside
the
repo
at
this
stored
in
this
file.
Metrics
dev
yamo,
but
all
it
does,
is
it
takes
the
earlier
file
that
we
use
dry
run
and
adds
a
volume
mount
into
the
pod
spec.
A
It's
metrics
dev,
so
we
could
see,
looks
like
there's
some
volume
specifications
and
it's
going
to
do
a
host
path
mount
from
this
folder
on
the
node
host
into
this
folder
inside
the
container.
And
if
you
look
at
the
docker
file
for
this
project,
the
entire
repo
is
basically
sitting
inside
this
folder,
so
I'm
going
to
mount
a
raw
repo
inside
a
running
container.
That's
basically
serving
this
repo
a
static
web.
A
A
A
A
A
What
that
will
allow
me
to
do
is
it'll
basically
bind
to
the
docker
demon
inside
the
VM
and
then
when
I
run
docker
build
the
result
of
the
build,
goes
direct
into
the
VM
and
I.
Don't
have
to
go
out
to
docker
hub
and
back
down
to
my
machine,
so
I
could
be
developing
fully
containerized
fully
offline
in
airplane
mode.
You
know,
while
I'm
flying
over
the
ocean
and
potentially
have
a
full.
You
know
multi
service
application
deployed
developed,
complete
with
kubernetes
all
on
my
laptop.
A
This
is
going
to
boost
your
memory
expectations,
of
course,
but
if
you're
developing
with
small
solutions
or
scaled-down
solutions,
this
gives
you
a
much
more
production,
like
representation
of
what
you're
going
to
be
working
on,
and
hopefully
less
surprises.
When
you
do
go
to
promote
your
code
to
production.
A
A
So
the
question
was:
what
are
the
virtualization
options
available
for
many
Kubb?
There's
a
pretty
solid
list?
There's
a
cait,
libvirt
KVM,
one
I
think
you
need
one
extra
download
to
get
that
to
work.
There's
also
support
for
using
the
Apple
native
virtualization,
a
VMware
fusion,
KVM
X
hive
yeah
good,
solid
list
yeah
and
all
of
that's
available
on
the
mini
cube,
Docs
yeah,
Tom.
B
A
Okay,
yeah
this
there
are,
you
will
see
sometimes
mixed
results
if
you're
using
different
virtualization
providers,
sometimes
mounting
external
files
into
the
VM
works
great
with
one
with
VirtualBox,
but
not
with
kbm
or
vice-versa
right.
So
some
of
these
you
may
have
to
do
some
experimentation
figure
out.
What's
the
best
fit
for
your
dividing
on
linux
here,
but
if
you're
on
all
Apple,
you
know,
maybe
you
want
to
use
x5
as
long
as
this
mount
operation
is
working
appropriately.
A
A
Different
requirements
from
different
teams
and
different
people
will
be
a
different
states
of
adoption,
some
of
them
fully
containerized,
some
of
them
with
a
lot
of
legacy
workloads
that
they
are
stuck
with.
So
this
is
a
kind
of
a
typical
adoption
path
that
I've
seen
people
generally
kind
of
start,
with
playing
with
docker,
eventually
they're
going
to
need
to
start
modeling
their
I/o,
creating
volumes,
persistence,
volumes,
mapping
those
into
the
containers.
A
Hopefully
they
pick
up
mini
coop
at
some
point
and
then
easy
way
to
model
kubernetes
abstractions
right
on
their
laptop
and
having
that
as
a
just
a
modeling
language
on
your
laptop
I
find
incredibly
useful.
Next.
After
that,
you
could
definitely,
if
you're,
looking
to
share
what
you
know
look
into
charts
the
the
kubernetes
charts
are
the
official
way
of
packaging
up
these
solutions.
They
don't
currently
they're,
not
really
labeled.
A
You
could
use
really
any
kind
of
template
Emmure
for
width
and
hand
roll
your
own
specs
once
you
know
what
you're
dealing
with
right,
so
maybe
start
with
dry
run,
generate
a
couple
manifests
and
then
figure
out
which
values
you
need
to
modify
frequently
and
develop
workflows
for
assisting
with
that,
whether
it's
hand-rolled
manifest
charts
or
you
know.
Eventually
people
are
going
to
be
looking
at.
A
You
know
this
new
Service
Catalog
or
even
leveraging
a
full
past
solution,
and
really
the
more
you
add
the
closer
you
get
to
pass
here
so
so
I
have
a
from
here.
I've
got
a
variety
of
solutions
that
I
wanted
to
give
the
audience
an
opportunity.
But
my
theme,
for
this
is
keep
it
simple,
make
it
try
try
to
describe
these
in
a
way
that
is
easy
for
developers
to
understand
so
from
the
audience
who
has
heard
of
draft
here,
Dre.
A
B
A
Is
close,
anyone
else
have
a
guess.
What
I
think
of
draft
draft
is
really
kind
of
you're,
so
event-driven
scripting
system.
That's
next
on
my
list.
Thank
you,
Joe
and
so
sorry,
event-driven
scripting
system
is
the
next
one.
But
draft
is
from
the
the
azure
team.
It's
the
I
think
one
of
the
best
ways
to
get
yourself
a
starting
point.
A
If
you
are
not
familiar
with
the
dry
run
command
or
you
want
to
get
a
good
starting
point,
use
draft
in
your
repo,
it
will
attempt
to
produce
a
docker
file
for
you
and
your
kubernetes
manifests.
So
you
can
deploy.
That's
my
lowest
simplest
tool.
Make
it
easy
to
get
started
with
draft
charts.
Is
my
next
one
and
my
simple
explanation
is
to
share
what
you
know:
Hellman
tiller
have
folks
heard
of
helm
and
tiller
more
folks
than
that
have
heard
of
charts
you
use
chart
Hellman
tiller
is
what
deploys
your
charts.
A
This
is
how
you
should
come
on.
Okay,
all
right
here
we
go
here,
we
go
Joe.
Would
you
like
it
up?
Nothing
I'll
quit
picking
on
Joe
Brigade?
Is
there
event-driven
system
for
producing
workflows?
If
you
would
like
to
see
a
demo
head
on
over
to
the
azure
booth
I'm
sure
they
would
be
happy
to
give
you
a
demo.
A
It's
a
new
project,
so
I
don't
have
any
demos
prepared
for
this,
but
definitely
give
it
a
look
if
you're
interested
in
delivering
workflow
or
event-driven
systems,
I
think
they've
definitely
produced
a
really
good
collection
of
developer
tools
in
the
past.
How
many
folks
have
heard
of
telepresence,
not
too
many?
Okay,
this
one
I
think
is
particularly
important
if
you're
using
kubernetes
on
your
laptop.
If
you
are
spinning
up
large
numbers
of
micro-services
and
you're
on
a
MacBook
Air,
how
far
do
you
think
you're
gonna
get?
A
You
know
you
could
get
a
couple
containers
going,
but
with
only
eight
gigabit
memory
max
on
your
on
your
hardware,
you're
gonna
run
into
some
limitations
real
quickly,
so
you
can
customize
many
ku-band.
You
could
say
I
want
to
give
it
more
memory
or
less
memory,
or
you
know,
there's
a
lot
of
customization.
You
could
do
there
you'd
give
it
more
CPU
cores,
but
telepresence
really
helps
pitch
in
by
allowing
you
to
leverage
a
hosted,
kubernetes
environment
and
then
make
those
hosted.
A
Services
appear
as
if
they're
running
locally
on
your
local
mini
coop
environment,
so
it
uses
proxies,
and
so
you
could
have
a
large.
Maybe
you
have
a
full-scale
Oracle
big
Oracle
database
somewhere
else,
but
you
want
to
be
able
to
leverage,
hopefully
not
production
data,
but
production
quality
services
during
your
local
development.
A
A
Don't
want
to
put
too
much
ven
during
in
here,
but
man,
the
more
of
this
tooling
you
layer
on
top
the
more
complicated
you
get,
the
more
you
start
to
get
into
that
problem
of
drowning
people
in
terminology
and
getting
distracted
from
your
core
mission
of
delivering
product
and
features,
and
if
it
all
all
the
talking
and
all
the
communication,
goes
to
help
accelerate
your
velocity
and
help
the
bridge
the
communication
gap
between
the
dev
teams
and
the
ops
teams,
then
that's
exactly
what
it
should
be
doing.
Make
sure
you
don't
overwhelm
people
with.
A
You
know
a
boatload
of
new
terms,
fresh
out
of
coop
con,
try
to
give
them
just
what
they
need.
Give
them
a
solid
starting
point.
Mini
shift
and
OC
will
give
you
a
it's
basically
just
like
many
Kubb,
except
it
spins
up
an
open
shift
environment
instead
of
a
kubernetes
environment.
Open
shift
is
fully
it's
a
it's
a
kubernetes
environment
currently
at
kubernetes
1.7,
if
you're
using
the
open
shift
3.7
release.
A
So
these
basically
give
you
a
more
secure,
multi
tenant,
safe
version
of
kubernetes,
one
of
the
unique
things
about
it
is
none
of
your
processes.
What
we
won't,
let
you
run
jobs
as
route.
It's
not
a
best
practice
for
folks
at
Red
Hat
to
run
every
process
at
route
as
route,
usually
not
a
good
practice
in
production.
I
would
argue
if
you're
not
doing
it
later
down
in
your
pipeline.
A
Why
do
it
in
local
development,
if
you
don't
need
to
run
things
as
route
in
local
dev
than
why
do
it
there
either,
but
generally
docker
run
and
coops
ETL
run
is
generally
going
to
run
things
as
the
root
user.
So
if
you
have
PCI
compliance,
HIPAA
compliance,
any
kind
of
aspirations
towards
security
at
all,
take
a
look
at
open
shift
and
I'd
be
happy
to
give
you
a
demo
of
what
we
offer
down
in
the
Red
Hat
booth.
So,
hopefully
I've.
A
Given
you
a
simple
overview,
just
a
small
couple
pieces
of
what
you
can
learn,
what
you
can
share.
Here's
a
collection
of
other
learning
opportunities,
the
kubernetes
io
tutorials,
are
pretty
solid.
There's.
Also,
a
good
collection
of
developer
focused
education
on
the
catacomb
examples.
I
have
a
lot
of
developer,
focused
workshops
packaged
up
using
these
reveal
j/s,
slides
and
those
are
easy
to
fork
and
share.
A
So
if
you
want
to
fork
any
of
my
talks,
feel
free,
steal
them
and-
and
let
me
know
if
you
get
some
use
out
of
them-
we
also
have
an
interactive
learning
portal
at
learn:
openshift
comm
and
a
challenge
to
developers
in
the
red
hat
booth.
If
you
complete
one
section
of
our
learning
learning,
we've
got
a
free
hoodie
for
you,
so
definitely
stop
by
the
Red
Hat
booth.
A
You
need
to
have
a
solid
way
to
maintain
and
distribute
that
that's
either
gonna
be
your
dev
leads
or
your
architects
or
but
it
might
not
be
your
web
developers
initially
at
least
QA
folks,
look
forward
to
saying
sorry
works
on
my
kubernetes
operations.
Folks,
mostly,
hopefully
it's
getting
pretty
boring
for
operations.
Folks
or
it
should
be
I
know.
There's
still
a
lot
of
work
to
do
with
kubernetes,
but
primarily
you
want
to
be
focusing
on
keeping
the
environment
running
upgrading
the
environments
and
not
getting
involved
in
too
much
trash
yeah.
A
The
yeah
also
you
want
to
loop
in
security.
Security
is
a
big
thing
to
keep
in
mind
and
being
able
to
organize
your
work
in
a
way
where
you
don't
have
things
like
a
situation
where
your
front-end
web
developers
are
maintaining
your
docker
images
and
having
old
versions
of
libous
SL
or
you
know
outdated
core
libraries.
A
You
want
to
have
a
solid
mechanism
for
patching
your
workloads,
monitoring
your
workloads,
doing
a
security
analysis,
vulnerability
analysis
on
your
workloads,
so
my
send-off
for
you
folks,
definitely
join
the
community
on
slack
in
kubernetes
users
and
in
cig
apps.
Most
of
the
developer,
focused
content,
happens
and
sig
apps
come
and
join.
The
conversation
share.
What
you
know
share
your
use
cases
and
experiences
and
help
us
develop
a
range
of
solutions
that
expose
or
hide
kubernetes
in
an
appropriate
amount
of
visibility
for
developers
right.
A
There's
a
lot
of
great
videos
on
the
cig,
apps
YouTube
channel
as
well,
so
definitely
check
that
out.
Hopefully,
that
will
help
you
learn
to
deliver
consistent
consistently
with
containers
choose
the
right
tool
for
the
job.
If
you
are
building
a
pass,
recognize
it
and
maybe
use
that
tool
right.
If,
if
you
don't
need
a
pass,
hopefully
I
gave
you
a
good
collection
of
tools
to
leverage
and
then
hopefully
you
all
get
back
to
making
gold
records
right.