►
From YouTube: Get Your Helm Charts Out There!, Reinhard Nägele, Senior IT Consultant, codecentric AG
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Get Your Helm Charts Out There!, Reinhard Nägele, Senior IT Consultant, codecentric AG
A
All
right
good
morning
so
welcome
everyone
to
my
chalk.
Get
your
home
charts
out
there!
So
I'm
Reinhart,
I
work
on
site
in
that
code,
centric,
which
is
a
German
IT
consultancy,
probably
one
of
the
most
awesome
German
life
patching
employers,
I,
would
say
we
also
have
offices
in
Amsterdam
and
Breda
by
the
way.
So,
if
you're
interested
speak
to
me,
I
might
have
an
organ
charts,
maintainer,
yeah,
uhm
and
Twitter.
A
A
What
are
we
going
to
do
today,
so
I'm
gonna?
Take
you
on
a
little
journey
and
show
you
how
you
basically
can
host
your
own
head
shots
on
github
pages,
and
this
involves
the
home
hub,
how
you
can
test
your
charts
on
an
ephemeral
cluster
and
how
you
can
finally
post
all
the
stuff
on
github
and
in
the
end.
I
also
have
an
example
and
get
up
which
puts
everything
together.
So,
first
of
all,
let
me
introduce
you
to
the
home
hub.
A
The
home
hub
was
introduced
last
year
at
Yukon.
It's
basically
a
platform,
a
portal
where
you
can
find
in
Hampshire.
It's
basically
obviously
a
distributed
search
and
anyone
can
host
I
can
can
register
their
own
reports
with
the
hub.
So
you
can
find
ham
charts
that
are
not
only
in
the
community
charts
ripple,
but
in
many
other
repositories,
as
I
said,
you
can
register
your
own
repositories.
It
just
takes
a
pro
request
and
what's
also
interesting,
and
we
will
be
able
to
search
to
help
directly
so
without
even
adding
a
report.
A
Who
of
you
has
contributed
to
the
community
chargeable
few
hands
excellent?
So
then,
you
are
probably
aware
that
this
repository
is
basically
a
victim
of
its
own
success
right.
So
it's
it's
yeah
the
community
is,
is
growing
tremendously,
which
is
which
is
great
but
which
causes
problems.
Of
course
it's
barely
managed
of
lis
anymore.
So
we
try
to
find
ways
how
to
to
make
that
better.
A
So
one
of
the
things
we
did,
we
added
honest
files,
so
chart
owners
can
basically
manage
and
merge
their
own
Appeals
for
their
own
charge.
This
worked
together
with
the
with
the
CI
infrastructures
or
the
pod
comes
along
and
merges.
If,
if
you
have
the
permissions
for
that,
if
you
are
an
owner
of
a
chart,
you
can
do
that.
This
make
the
things
a
little
bit
better,
but
still
it's
it's
not
girl.
A
Eternally
we
have
like
I,
don't
know
20
or
50
of
them
pull
requests,
which
is
really
a
lot
and
turnaround
times
are
still
still
long.
So
this
is
what
we
also
invented
the
up,
so
people
can
host
their
charts
somewhere
else
in
their
own
repositories,
but
still
get
the
visibility.
People
can
find
the
charts
via
the
hub,
and
so
we
would
really
like
to
promote
to
happen
also
get
folks
who
to
to
host
the
charts
on
their
own.
A
So,
okay,
step
right,
so
so
in
the
end
we
would
try
and
move
move
and
and
convince
people
to
host
charts
really
on
their
own,
and
so
in
the
long
term.
You
may
be
thinking
about
replicating
the
charts
report,
but
this
is
not
there
don't
worry,
and
it's
not
clear
yet
if
we're
going
to
host
hand
three
charts
there,
so
it
is
still
being
discussed
so
it,
but
in
order
to
get
folks
to
host
propose
on
their
round,
we
need
to
make
this
easy
right.
A
So
not
everyone
is
a
company
and
has
it
as
as
infrastructure
and
can
can
afford
setting
up
clusters
and
stuff
like
this.
So
we
need
to
find
a
way
to
make
this
easy,
and
this
is
why
we
are
developing
tooling
for
this
and
I'm
going
to
show
you
what's
already
there
and
how
this
can
be
done.
So,
first
of
all,
there's
the
charts
testing
tool.
If
you
host
the
charts
on
your
own,
you
want
to
test
your
charts.
You're
gonna
have
to
see
our
infrastructure,
you
want
to
make
sure
you
offer
quality.
A
So
if
somebody
wants
to
use
your
chart,
they
want
to
be
sure
it's
tested
and
it
works.
So
the
chat
testing
tool
basically
grew
out
of
what
we
have
for
the
community
charts
repo
initially
does
what
like
just
a
set
of
shell
scripts
and
we
thought
would
it
be
cool
if
we
factored
that
out,
so
anybody
else
could
use
it,
and
this
is
what
what
I
did
don't
remember
so
so
the
first
attempt
was
just
reflecting
everything
and
the
result
was
like
a
500
line.
A
Shell
script,
which
is,
as
you
might
guess,
not
the
best
thing
to
maintain
so,
but
it
was
a
great
first
step
and
people
could
use
it.
It
was
packaged
in
a
docker.
It
was
a
docker
image
and
so,
as
a
second
step,
I
reflected
the
whole
thing
again
and
it's
no
ago
application,
which
is
great,
and
we
are
also
growing
the
community
around
that
we
get
excellent
contributions
and
folks
use
it.
So,
and
this
is
also
used
by
the
CI
first
infrastructure
in
the
charts
repository
in
the
community
repository.
A
So
what
can
it
truly
do?
It
can
run
some
linting
stuff,
Yama's
validation,
and
it
will
lint
your
chart
even
install
your
chart.
It
automatically
discovered
charts
that
are
changed
in
the
git
repository
and
tests,
only
the
change
charts,
so
in
exhaustion
runtime
test,
and
it
can
also
run
upgrade
tests,
which
is
really
important
to
make
sure
you
don't
break
things
when
you
update
your
chart.
A
So
what
it
does
it
installs
the
previous
minor
version
and
upgrades
to
the
to
the
current
version,
and
it
also
does
in-place
updates
of
the
same
version,
which
can
also
fail,
because,
even
if
you
don't
change
your
manifests,
as
you
probably
know,
hem
can
generate
random
values
and
stuff
like
this
or
you
may
have
labels
in
there
which
changed,
because
they
refer
to
the
chart,
version
and
stuff
like
this.
So
you
actually
get
changes,
even
if
you
do
upgrade
of
the
same
version,
and
this
might
cause
problems
which
we
should
discover.
A
So
now
we
have
a
testing
tool
now
we
also
need
a
cluster
to
run
the
tests
on
so
and,
as
I
said,
if
you're,
not
a
company
that
has
infrastructure,
you
need
some
kind
of
kubernetes
cluster
that
you
can
spin
up
on
on
your
CI
infrastructure,
and
this
is
where
can
comes
into
play.
Kind
is
kubernetes
in
Tucker,
which
is
an
excellent
tool
which
allows
you
to
spin
up
kubernetes
blasters
in
docker
and
actually
much
in
our
clusters,
not
just
like,
if
you
know
mini
cube
or
kubernetes,
and
in
taka
desktop
it's
only
single
node.
A
A
And
it's
really
fairly
easy,
install
in
just
to
pancreas
lustre.
You
can
specify
a
config
file.
If
you
need
multiple
nodes,
you
can
even
add
further
configurations
under
the
hood.
It
uses
cube,
EDM
and
even
pass
in
configuration
for
that
and
I
think
for
the
two
blade
and
stuff
like
this.
If
you
need
special
special
things
and
you
can
also
specify
the
kubernetes
that
the
node
image,
which
allows
you
to
test
against
specific
kubernetes
versions,
if
this
is
interesting
for
you-
and
this
is
something
you
can
do
in
my
case-
it's
uncertainty
I.
A
A
All
right
now
we
have
a
classroom,
you
test
it
and
in
the
end
we
need
to
host
the
stuff
somewhere.
So
and
why
not
house
it
on
github,
directly
github
has
github
pages
and
a
chart
repository
is
basically
just
you
need
an
HTTP
server
that
can
serve
llamó
files
and
tell
fast
it's
that's
all.
You
need
there's
four
four
hundred
use
ozi
registries,
but
this
is
out
of
the
picture
now.
A
So
this
is
a
forehand
to
or
was
to
the
support
it
in
hem,
three
I
guess
it's
just.
You
need
an
index
EML
file,
entire
files,
and
when
you
Austin
on
data
pages,
you
basically
have
two
options:
either
your
committee
or
your
table,
so
the
repo
on
your
github
pages
branch
or
the
other
option
would
be
to
use
github
releases,
which
is
basically
more
native
integration.
This
is
what
what
we're
doing
here,
what
I
prefer
and
what
the
tooling
also
does.
A
So,
as
I
said,
this
tool
generate
releases
in
the
XML
file
for
you,
you
still
need
some
bunch
of
shell
scripting
around
that.
We
have
plans
to
to
improve
that.
We
may
create
a
github
app
that
make
things
easier
or
two
to
great,
really
a
full-featured
solution
that
allows
you
to
to
set
up
the
CI,
and
that
also
does
the
packages
in
packaging
and
stuff
like
this
and
whatever
is,
is
needed
right.
So
all.
A
A
Which
demos
everything
this
is
basically
an
application
and
in
the
chart
it's
it's
all
in
one
repo
just
for,
for
the
sake
of
this
demo,
it's
a
simple
application.
It's
just
a
web
app
that
prints
hello,
helm
or
something
and
yeah.
Let
me
show
it
here,
so
can
you
read
this?
You
need
to
make
it
bigger,
so.
A
A
A
A
Later
on
for
for
testing,
so
I'm
starting
the
container
in
the
background
mounting
in
like
the
root
directory
and
the
config
file
for
for
testing
and
here
I'm
creating
a
kind
cluster,
this
is
just
downloading
kind.
Create
cluster
I
have
a
config
file
in
this
case,
config
yummo
I'm,
creating
a
cluster
with
two
worker
nodes.
A
Get
the
coop
config
put
it
into
my
client
container,
my
char
testing
container
and
just
check
if
things
work
here
and
then
the
interesting
part
is
here
are
just
two
char
testing
city
installed:
that's
basically
all
I
need
to
do,
and
this
checks
the
repo.
If
there
is
a
change
in
my
charts
and
then
all
change
charts
are
tested.
A
A
Installed
tiller
and
then
I
run
car
testing.
So
first
it
prints
out
the
configuration
and
it
says:
okay,
this
is
the
chart
it
detected
that
needs
to
be
tested
because
it's
changed
indeed,
and
then
it
installs
it
prints
out
the
homesteaders
information
and
I
see
describe
outputs
of
other
part
of
the
deployment
and
all
the
parts
I
think
and
all
the
other
logs
are
also
printed
there
and
in
the
end
it
was
successful,
and
this
means
my
pull
request
can
be
merged.
A
A
A
See
if
they
have,
if,
if
I,
have
changes
since
this
tag,
if
no
I
just
return
otherwise
I
try
and
identify
the
to
change,
charts
here,
doing
a
git
diff
against
the
the
charts
directory.
This
returns,
an
array
of
change,
charts
and
I
loop
over
them
here
and
package
them.
This
is
what
you,
what
I
still
need
to
do
on
my
own,
which
doesn't
it
yet
package
shot?
It
just
calls
he'll
package.
A
A
A
A
A
A
So
this
is
just
just
one
way
to
do
it.
You
can
host
them
anywhere
else,
as
I
said
in
any
HTTP
server,
but
this
is
just
basically
if
someone
has
their
own
open
source
project
and
cool
application,
once
the
hosted
doesn't
want
to
spend
any
money
on
huge
infrastructure.
This
is
basically
the
way
to
go
to
host
your
your
shots
for
free
right.
So.
A
A
A
The
lobby
we
might
enable
that
at
some
point
I
guess
many
charts
will
fail.
This
is
why
we
are
hesitant
to
to
activate
it
so
and
I
discovered
a
few
issues
with
some
charts
and
we
need
to
look
into
that.
But
if
you
run
it
on
your
own,
you
should
probably
activate
it.
So
I
didn't
activate
it
here
for
the
demo,
but
it's
off
by
default.
A
Okay,
so
the
question
was
when
you,
when
you
test
a
child,
if
you
can
also
do
some
kind
of
integration
tests,
when
you
have
an
application
that
has
data
associated
with
on
a
PVC
or
a
database,
and
data
needs
to
be
migrated.
If
this
can
be
tested,
what
does
it
runs
home
tests?
Basically,
anything
you
can
do
with
home
tests
can
be
done.
You
can
use
hand
tests
to
to
to
spin
up
a
test
container,
and
this
container
can
verify
your
data.
A
B
A
Okay,
so
I
thought
the
question
was
for
Child's
listed
on
the
home
hub.
If
you,
if
you
have
any
Indians,
if
they
need
to
be
open
source
or
so
the
answer
is
yes,
we
required
a
chance
to
be
I,
think
Apache,
licensed
and
I
need,
and
also
the
hem
happens
in
the
readme
file
from
the
repo
it
needs
to
be
publicly
accessible.
Otherwise
it
can't
be
listed
on
the
up.
A
A
Yeah,
so
the
question
was:
if
you
can
have
multiple
charts
in
the
charts
ripple,
there's
only
one
shot
in
my
example.
The
answer
is
yes,
you
can
have
any
number
of
charts
and
our
testing
tool
will
discover
which
charts
change
and
only
test
those
charts
and
released
us
that's
possible.
Yes,
and
this
is
probably
what
what
you
will
do.