►
Description
- 00:00:00 - Welcome to TGIK!
- 00:03:25 - Week in Review
- 00:19:11 - Ko
- 00:49:42 - Configula
Notes: https://github.com/vmware-tanzu/tgik/blob/master/episodes/102/README.md
Come hang out with Joe Beda as he does a bit of hands on hacking of Kubernetes and related topics. Some of this will be Joe talking about the things he knows. Some of this will be Joe exploring something new with the audience. Come join the fun, ask questions, comment, and participate in the live chat!
This week we'll be looking at a couple of interesting deployment tools. First will be ko (https://github.com/google/ko). This is a go focused tool that really streamlines the building and deployment of go based services. Second will be Configula from Brendan Burns (https://github.com/brendandburns/configula). This TGIK8s is a lightening round!
A
A
So
I
was
talking
with
some
of
the
folks
that
we
hired
that
work
on
K
native
some
folks
that
I
had
worked
on
before
Google
before
VMware,
and
they
were
talking
how
much
they
love
this
tool.
Ko-Ko
and
I'm,
like
hey,
should
I
do
it
on
TGI,
K
and
they're
like
yeah.
It
takes
about
five
minutes
and
I
think
it's
probably
gonna
take
a
little
bit
longer
than
that.
So
I
think,
looking
at
that
and
and
then
my
eye
on
a
project
that
Brendan
released
a
couple
of
weeks
ago,
I
figured.
A
Hopefully
we
can
sort
of
speed
through
a
couple
of
them
and
and
and
see
what
they're
about
because
they're
both
relatively
small
projects.
So
so
this
should
be
fun.
So
I'd
like
to
start
off
by
saying
hi
to
everybody-
and
you
know
some
of
you
all
were
on
the
chat
earlier
and
started
saying
hi.
So
you
know
Moza
fir
hello,
Rory
from
Scotland
good
to
see
you
again,
suresh
la
Maddie,
always
joining
us
Christophe,
let's
see
so
yeah
so
so
George
is
hanging
out
with
us
here.
A
Duffy
I
think
is
hanging
out
a
little
bit
Martin
from
the
Netherlands
marcin
from
kracko.
What
is
vernal
ve
are
any
L
I,
don't
know,
get
gal
gal
from
France
Steve
good
to
see
you
gustavo
and
then
matt
is
one
of
the
authors
of
coe.
So
he's
a
hope.
We
gonna
be
able
to
talk
to
us
about
it
and
tell
me
where
I'm
doing
wrong
Frederico
good
to
see
you
good
to
see
you
all
right.
So,
let's
jump
in
and
get
started.
Oh
no!
No!
A
A
Yeah
here
we
go:
do
you
enjoy
popular
mid
20
2006
yeah?
So
this
is
so
all
profits
donated
to
women
in
Linux.
So
that's
kind
of
fun.
It's
a
fun
t-shirt.
Alright,
oh
look
and
you
can
get
in
on
all
sorts
of
colors
I
could
have
done
blue
there
we
go
so
I
encourage
you
all
go
buy
Alice's
shirt,
okay
still
on
face.
Yes,
so
let
me
switch
to
the
screen
it's
okay,
so
we
may
end
up
with
like
as
I'm
going
through
stuff.
We
may
end
up
hitting
some
hiccups.
A
It
was
a
little
bit
of
a
rush
to
install
upgrades
for
everything
because
I
upgraded
to
Catalina
I'm
working
from
home
today,
cuz
got
to
be
here
for
the
kids
and
stuff.
My
wife
is
off
doing
something
and
then
I
got
a
new
monitor
and
camera
and
all
that
stuff.
So
it's
been
a
little
bit
of
a
little
bit
of
a
trick
to
get
everything
up
and
working,
but
hopefully
we
won't
hit
too
many
too
many
snags
here.
So,
okay,
so
and
well
ly
good
to
see
you
from
Saudi,
alright,
so
I
love.
A
A
So
a
couple
of
things
to
look
at
is
that
there's
this
release
note
site,
which
is
just
getting
better
and
better
every
release
going
through
a
whole
bunch
of
the
stuff
that's
happening
here.
Feedback
on
this
is
useful,
but
I
think
lots
of
really
cool
stuff
coming
in
here,
and
this
is
a
good
way
to
sort
of
pull
this
out
of
github
and
make
it
consumable
there's
also
a
spreadsheet
used
for
tracking
sort
of
which
of
the
caps
and
issues
and
stuff
like
that
is
going
on.
A
A
These
are
some
really
cool
stuff,
so
the
first
thing
is
server
side
apply,
and
this
is
for
those
who
have
ever
looked
under
the
covers.
When
you
do
Cube
control
apply,
it
should
be
as
easy
as
just
slamming
up
some
new
sort
of
like
yamo,
converted
to
json
or
whatever
to
the
server
and
having
the
server
interpret
that,
but
it
turns
out
that
it's
more
complicated
than
that,
because
there
ends
up
being
ideally
speckies
back
as
status
of
status.
A
A
lot
of
that
logic
is
being
rethought
and
moved
to
the
server
with
the
idea
of
having
sort
of
different
views,
different
versions
of
resources,
so
that
you
can
actually
do
that
merging
in
a
more
in
a
more
structured
way
on
the
server.
And
so
this
has
been
in
progress
for
a
long
time
and
it's
making
some.
It
was
developed
on
a
branch
and
it's
making
making
some
good
forward
progress
of
getting
in
so
that's
really
exciting
and
then
and
then
sidecar
container.
A
So
we
talked
about
sidecars
a
ton
and-
and
the
reality
is,
is
that
kubernetes?
When
you
have
a
pod,
it
has
a
list
of
containers
and
all
of
those
containers
are
considered
equal,
which
means
that,
if,
if,
if
you
know,
if
you
know
for
that
pod
to
exit
cleanly,
all
the
containers
have
to
exit
cleanly
and
that
can
be
problematic
when
some
of
the
containers
are
something
like
a
side
car
running
envoy
for
a
service
mesh.
Or
what
have
you
now?
You
you
shut
down
your
main
workload.
A
That
envoy
is
left
running
there,
because
you
know
you
have
to
bring
down
both
of
the
containers.
The
idea
with
like
calling
outside
guard
car
containers
explicitly
is
the
okay
one
exception
is
the
NIC
containers
is
what
Scott's
saying,
but
the
idea
was
sidecars
is
that
you
can
identify.
Here
are
the
primary
containers
for
my
workload
and
then
the
side
cars
come
along
and
they
don't
control
the
life
cycle
of
the
pot
like
they
currently
do
when
you
have
a
sort
of
a
set
of
equal
container.
A
So
it's
exciting
to
see
that
stuff
come
along
too
alright.
So,
let's
see
some
deep
from
polling
good
to
see
you
and
Ramesh,
and
we
have
Scott
who's
a
one
of
our
colleagues
on
the
K
native
team,
also
working
with
Coe
so
excited
to
see.
You
know
Scott
and
Matt
along
here,
so
you
can
click
through
and
dig
into
some
of
the
details
on
those.
If
you
want
to
those
are
some
of
the
issues
in
the
proposals
going
on.
A
Ok,
the
CNC
F
accurate
were
annual
report.
You
it's
it's
useful
to
think
about
sort
of
like
what
is
all
the
stuff
the
CNC
F
does
I
think
this
is
a
good
summary
of
what
they've
done,
how
the
community
is
growing.
How
there's
engagement,
there's
a
you
know,
there's
always
more
to
be
improved
here,
but
I
think
it's.
It's
really
useful
to
call
out.
A
And
it's
great
to
see
the
the
annual
report
really
go
into
a
lot
of
detail
there,
so
something
you
might
want
to
check
out
alright,
so
more
stuff,
that's
going
on
so
some
interesting
articles
that
Duffy
and
George
pulled
out.
Toder
Sebastian
here
talks
about
right-sizing
Kafka
clusters
on
top
of
kubernetes.
So
this
is
the
bonsai
cloud
folks
and
they
ended
up
writing
their
own
operator
for
Kafka,
there's
also
scrim
Z,
which
is
a
CN
CF
CN
box
project.
A
For
doing
this,
and
talking
about
sort
of
how
do
you
actually
allocate
resources
and
so
interesting
to
see
this
stuff
working
in
the
context
of
kubernetes
and
and
for
me
this
is
really
really
exciting,
because
we're
essentially
moving
from
hey
look.
What
I
can
do
to
here's
real
world
experience
with
respect
to
running
this
stuff
in
production
and
so
I
I
love,
seeing
more
in-depth
articles
like
this,
even
if
I'm,
not
a
Kafka
export.
A
It
really
is
a
good
sign
to
me
that
the
we're
starting
to
mature
in
terms
of
of
people
using
this
stuff
for
more
advanced
use
cases,
here's
more
of
a
one
on
one
on
one
scenario:
blog
post
on
rolling
updates
roll
backs,
multiple
environments,
essentially
like
a
lot
of
the
features
with
deploy,
but
how
to
actually
route
to
those
things
with
ingress.
And
how
do
you
actually
start
viewing
this?
A
From
the
point
of
view
of
having
you
know,
dev
staging
production,
multiple
environments,
super
super
common,
so
that
is
an
interesting
cool
article
there
from
ernesto
folks
from
Cystic,
are
have
an
article
here
that
goes
into
some
of
the
details,
around
requests
and
limits
and
how
those
works.
I
did
a
TGI
K
on
this
quite
a
while
ago,
but
it's
great
to
see
more
more
detail
of
folks
playing
around
with
this.
A
Some
really
interesting
cool
diagrams
that
actually
show
all
this
stuff
breaks
down
very
cool
stuff
there
to
see
that
coming
from
Cystic
other
stuff,
if
you're
using
AWS
eks,
they
dropped
the
price
of
eks
from
20
cents
an
hour
to
10
cents,
an
hour
which
is
I,
think
really
interesting.
It
makes
me
think,
like
you
know,
have
they
changed?
A
How
they're
hosting
the
control
plane
for
eks
in
the
background,
I
wouldn't
be
surprised
if
they're
figuring
out
how
to
use
some
of
their
lightweight
VMs
to
be
able
to
host
this
stuff
for
smaller
clusters,
and
that
enables
them
to
do
this
price
drop.
Here
it's
going
to
be
interesting
to
see
you
know,
as
they
add
more
few
features
to
eks
whether
they
continue
to
keep
that
as
a
paid
thing
or
whether
they
just
think
hey.
You
know,
you'll
get
enough
with
the
usage
of
the
DMS.
A
Some
cool
app
releases
coming
out
here,
I
hadn't,
seen
this
until
I,
don't
know
if
it
was
Duffy
or
George
that
pulled
it
up,
cube,
NAB
and
I,
and
this
be
something
fun
to
play
with
it's
a
a
mobile
app
for
accessing
and
managing
kubernetes,
which
looks
pretty
cool
and
it's
open
source.
So
you
can
come
check
it
out
a
long
time
ago,
Sebastian
goesan
did
an
iOS
app
for
managing
kubernetes
and
it
kind
of
sort
of
fell
by
the
wayside
a
while
ago.
A
A
Okay
native,
because
it's
six
weeks
since
the
last
one,
all
right-
Evan,
if
you
want
to
put
that
in
the
note
7-
is
another
colleague
working
on
keh
native
stuff,
so
octants,
making
its
way
forward,
features
being
added
Wayne's
driving
the
bus.
There
now
really
great
to
see
that
there's
a
release,
prog
blog
post
but
I-
think
that
for
me,
the
most
interesting
stuff
is
container
exec.
A
This
idea,
you
can
have
an
interactive
way
to
sort
of
launch
in
and
debug
and
manage
containers
from
within
octant
super
cool
and
then
a
workload
viewer
which
is
essentially
an
overall.
You
know
sort
of
at
a
glance
the
health
of
all
of
your
different
workloads,
so
very
cool
to
see
that
stuff
coming
along.
A
One
of
the
interesting
things
here
and
I
was
thinking
about
this
this
a
while
ago,
is
that
you
know
we
have
this
concept
for
developers
called
an
integrated
development
environment
like
an
IDE
and
those
things
really
bring
together.
All
the
tools
curated
experience
make
it
super
easy.
What
would
a
sort
of
integrated
opt
environment?
Look
like
what
would
it
look
like
to
take
the
application
ops
tools
move
those
together,
make
that
be
extensible,
make
it
be
something
that
you
can
own
make
it
be
something
that
really
focuses
on
an
experience
and
I.
A
Think
that
might
be
something
that
octant
actually
turns
into
over
time,
and
so
that's
one
of
the
things
that
that
I'm
super
excited
about
all
right.
So
there's
that
and
Nautilus.
So
this
is
something
that
I
I
know
that
the
fusion
folks
had
been
working
on.
This
I
didn't
know
that
they
were
so
ready
for
close
to
announce
it
and
go
to
release.
So
I
haven't
had
a
chance
to
play
with
this,
but
it
looks
super
cool.
A
You
know.
Vmware
Fusion
is
a
product
with
a
ton
of
history
about
bringing
virtualization
to
the
desktop,
and
you
know
it
was,
and
it
was
really
one
of
the
products
that
VMware
got
started
with
it's
been
fascinating
to
see
you
know,
as
virtualization
has
been
mainstream.
You
know
how
Fusion
is
age,
had
sort
of
faded
to
the
background,
but
I
think
looking
at
this
in
the
of
the
need
to
have
a
production
like
environment,
on
your
desktop.
That's
where
stuff
like
this
comes
in.
A
So
this
is
really
great
to
see
these
folks
taking
fusion
with
all
of
its
history
and
finding
a
way
to
start
mixing
in
containers
and
kubernetes
to
create
a
really
great
developer.
Focused
environment
and
I
know
that
that
that
team
has
some
big
plans
here.
So
I'm
really
looking
forward
to
seeing
what
comes
next
with
this,
as
this
makes
its
way
out
of
I.
A
I
need
to
corn
or
Evan
and
get
some
some
details
around
that
whether
this
actually
does
stuff
instead
of
things
like
cert
manager
or
use
a
certain
manager
or
how
it
compares
to
a
cert
manager,
because
I
think
that
there's
definitely
some
overlap
there,
but
I
love,
seeing
like
the
support
for
contour,
there's,
also
support
for
ambassador
and
glue
and
it's
great
to
see.
Okay,
you
use
a
Serb
manager.
Is
what
I've
been
saying.
It's
great
to
seek
a
native,
create
that
level
of
choice
in
terms
of
you
need
some
more
advanced
routing.
A
Then
you
get
out-of-the-box
with
kubernetes,
but
not
tying
that
to
something
like
Sto
is
really
really
cool
all
right
now,
so
that's
sort
of
kubernetes
stuff,
now
some
more
fun
stuff
here.
Well,
this
isn't
fun,
but
the
Red
Door
in
Seattle
is
closing,
and
this
may
not
seem
like
a
big
deal,
but
this
is
very
very
sad.
A
This
is
like
when
we
moved
into
the
free
man
Fremont
office,
Fremont
Seattle.
This
was
like
essentially
across
the
street,
and
so
this
became
our
bar
and
I
know
you
can
see
I'm
getting
ads
for
shoes
here.
I
know
that
you
know
Craig
and
I
whenever
we
had
to
do
okay,
ours
or
reviews
and
stuff
like
that,
we
would
soften
the
blow
of
sort
of
corporate
hood
by
going
and
grabbing
a
beer
a
lot
of
the
times.
The
teams
would
go
there
after
work,
and
so
this
was
really
like.
A
You
know
an
extension
of
the
Google
office.
It
was
kind
of
like
a
conference
room
for
us
and
so
really
and
they
had
this
beautiful
patio
in
the
summer.
So
really
sad,
so
we're
gonna
probably
try
and
throw
some
sort
of
goodbye
event,
shindig
they're,
sad
to
see
that
happen,
and
then
okay
and
then
I
was
just
complaining
about
with
the
upgrade
to
Catalina.
They
want
you
to
switch
to
Z.
A
Shell
and
George
was
pulling
out
this
great
guide
that
Justin
garrison
did
on
Z
shell,
which
might
get
me
to
to
move
over
there,
but
I,
don't
know
I'm
kind
of
old
and
crusty,
so
I'm
kind
of
with
Duffy
update
on
the
episode
100
shirts
George
is
working
on
getting
those
out
there.
If
you
live
outside
the
US
and
may
take
a
while,
but
but
he's
gonna
make
sure
it
happens,
all
right,
so
that's
sort
of
news
of
the
week
or
so.
If
anybody
has
any
other
things
that
they
want
to
add.
A
Oh,
my
Z
shell
is
pretty
rad,
yeah
I
know
I
heard
you're
good
things.
I
know,
I
just
feel
like
every
time
you
mess
with
that.
That's
gonna
be
like
two
or
three
days
out
of
my
life
that
I
can't
spare
to
do
that
stuff.
So
we'll
see
we'll
see
if
I
can
find
the
time
to
make
it
happen,
all
right,
so
I
was
gonna.
Take
these
one
by
one
I
think,
let's
start
with
Co.
Okay,
we're
going
to
start
with
co.
A
The
build
and
deploy
aspects
when
using
go
and
I
think
go
is
special
in
this
context
because
go
produces
these
these
these
you
know
static,
binaries,
the
you
know
when
you
look
at
a
docker
file
for
a
go
project.
It
generally
is
like
copy,
you
know,
build
which
is
heavily
go
tool
chain,
do
a
build,
get
a
single
file
copy
it
over
to
the
runtime
container
and
then
and
then
that
runtime
container
ends
up
being
a
very
thin
wrapper
around
that
static
binary.
A
In
fact,
if
the
entire
world
worked
like
go
and
you
were
shipping
static,
binaries
like
Google
does,
then
we
probably
wouldn't
need
containers
in
the
way
that
we
need
them
now,
and
so
that's
that's
something
that
you
know
I
think
we're
we're.
Definitely
you
know
it's
it's
it's
interesting.
When
you
look
at
something
like
go
in
the
context
of
containers,
the
whole
container
image
thing
seems
feels
oftentimes
a
little
bit
silly,
but
the
idea
here
is
that
yeah
generally,
you
do
a
go
build.
A
You
know
maybe
in
a
docker
build
and
then
you
do
a
push
and
apply,
and
you
have
to
have
your
local
docker,
daemon
and
all
that
stuff.
And
what,
and
if
you
have
a
bunch
of
micro
services,
then
there's
a
lot
of
stuff
that
gets
repeated,
and
then
you
wrap
that
with
something
like
scaffold,
yeah
Robert
says
two
or
three
days
out
of
my
life.
Yeah
I
know
every
time
I
muck
with,
like
my
you
know,
Emacs
Emacs,
that's
definitely
an
afternoon.
A
So
the
idea
with
go
is
that
you
pointed
at
something:
that's
go
gettable
and
it
just
makes
it
happen
and
it
handles
both
the
build,
the
packaging
of
the
container
and
the
uploading
of
that
to
a
registry
and
I
think
that's
ends
up
being
super
super
interesting.
What
you
end
up,
so
let's
go
ahead
and
what
can
try
this
out,
so
I
think
I
have
be
where
some
of
these
import
paths
changed.
A
Okay,
so
let's
see
I
was
before
you
have:
okay,
okay,
so
this
before
you
add
your
own
repo
okay,
so
so
some
of
the
instructions
here
are
a
little
bit
out
of
date,
because
this
was
quite
a
while
ago.
So
instead,
what
we'll
do
is
we'll
follow
the
instructions
in
the
readme
for
Co
as
much
as
I
like
it.
It's
a
it's.
A
you
know,
the
SEO
for
Co
is
kind
of
crap.
I
got
to
be
honest,.
A
A
Somebody
gave
me
at
one
point:
a
shrug
sticker
like
here's,
the
I'm
trying
to
figure
out
what
I
wanted
where
I
want
to
I.
Think
you
know
what
I
moved
is
from
putting
stickers
on
my
laptop
I
put
them
on
my
laptop
stand,
because
I
feel,
like
the
laptop
stand,
is
gonna
last
longer
than
the
laptop
all
right,
cool,
okay,
so.
A
A
Build
it
and
then
throw
it
in
a
specific
path
and
so
they're
sort
of
a
convention
around
go
where
the
place
you
can
download
in
the
name
of
the
thing,
all
that
stuff
really
just
sort
of
lines
up,
and
so
Co
really
sort
of
plays
on
that.
So
the
idea
here
is
that,
because
building
a
go
repo
when
it's
go,
gettable
is
so
easy.
A
All
you
can
do
is
actually
just
say
you
know,
have
a
repo
instead
of
an
image
name
here,
you
actually
give
it
a
path
to
the
to
the
github
repo,
and
then
it
takes
care
of
everything
else
around
that
which
is
really
really
interesting,
and
so
we'll
go
ahead
and
we'll
try
that
Matt
does
this?
Does
this
example
work?
Is
this
actually
a
thing?
A
Alright,
so
you
don't
have
that
repo,
alright,
so
yeah
man,
if
your
links
aren't
showing
up
just
put
them
in
the
put
them
in
the
internal
slack
and
we'll
get
them
on
there.
Youtube
gets
rid
of
those
things.
Okay,
so
let's
see
how
our
install
is
going
here.
We,
okay,
so
we're
installed.
I
can
do
Co
Oh
phone
ringing
shut
up
phone.
A
Okay,
but
there's
no
instructions
feel
like
you're
you're
starting
but
like
what
what
do
I
looking,
config?
Okay,
all
right,
I'm,
going
to
do
this?
Okay,
so
oh!
This
is
old,
though
so
this
is
all
okay,
but
it
should
be
go
gettable.
So
let's
actually
check
it
out
so,
like
the
command
that
we're
actually
doing
here
is
echo,
so
I
should
be
able
to
do
if
I
do
go,
get.
A
A
Okay,
that's
amazing!
Okay,
oh
look
at
how
look
at
that,
so
I
actually
created
and
then
and
then,
when
I
did
cuz.
Okay,
Wow,
alright
I
know
what's
going
on
there,
but
it's
crazy!
Okay!
Oh
let's
see!
So.
If
we
go
to
config
here
do
vs
code
here,
okay
and
let's
see-
hopefully
you
didn't
upgrade
and
break
stuff
too.
A
A
This
is
not
a.
This
is
not
actually
an
image
right,
because
github
doesn't
host
images
now,
I
think
right
now
we
need
to
in
the
deployment
here.
We
need
to
change
that,
to
v1
will
fix
the
this
ones
at
v1,
core
services,
v1
type,
equals
load,
balancer
sure,
whatever
I'm
gonna
use,
I'm
using
kind,
and
then
we
have
a
service
account
for
whatever
reason
for
the
echo
controller,
okay,
longest
dinner,
okay,
cool
all
right,
so,
and
so
so
what's
gonna
happen
here
is
if
I
just
Yolo
this
in
so
I
can
do
what
is
it?
A
Co
apply
this
Oh?
What
do
I
got
to
do?
What
did
I
do?
Kodaka,
repo,
enviro
and
variable
is
unset.
Oh
I
have
to
tell
it
where
I
actually
want
to
okay,
it's
gonna
create
some
containers.
It
needs
to
upload
them.
You
have
to
tell
them
where
you
want
to
stick
the
things.
Let's
see
do
we
want
to,
and
so
you
can,
you
can
stick
that
end
up
up
in
a
real
repo
like
GCR
or
or
whatever,
and
then.
A
A
A
A
A
A
A
A
The
match
labels
or
does
that
work
I,
know,
okay,
see,
look
at
this
I,
don't
even
know
what
I'm
doing
selector
table
match.
Labels
said
like
another
I,
just
it's
been
a
while
since
I've
done
this
stuff,
and
this
is
why
what
so
we'll
get
to
this.
You
know
in
the
when
we
start
looking
at
things
like
config
EULA
boom.
A
So
that
was
actually
really
cool,
so
I
can
do
docker
images,
LS
or
images,
and
we
can
see
that
we
have.
It
gives
it
a
name
with
code
out
local
and
all
that
and
latest,
and
all
that
50
years
ago,
explain
what's
going
on
there,
which
is
really
fun,
but
that
was
I
mean
there
was
some
voodoo.
There
was
some
magic
going
on
there.
That
was
actually
really
cool,
so
I
think
now,
if
we
do
Cube
control
and
for
the
coupon
get
pods
Oh
image
pull
back
off.
Okay,
so.
A
Okay,
so
this
is
a
kind
load
image
name:
okay,
okay,
yeah
cuz
kind
has
its
own
daemon
and
this
stuff,
okay,
so
here's
what
we're
gonna
do
is
is
we're
going
to,
and
hopefully
what
we'll
do
is
we'll
bounce
us
off
a
docker
hub
cuz?
Why
not
I?
Think
probably
you
know
this
is
something
I
think
would
be
worthwhile.
Getting
co-working
with
kind
would
be
great,
because
kind
is
great,
because
it's
a
Multi,
multi
node
thing
and.
A
A
All
right,
actually
what
I'm
gonna
do
is
my,
let's
make
sure
okay,
so
the
fascinating
thing
here
and
I
think
this
is
what's
what
would
it
which
is?
Okay,
it
didn't
actually
show
anything
few
okay,
so
this
did
a
container
image
build,
but
it
didn't
use
docker
right,
so
I
only
had
to
do
docker
login
there,
so
that
I
could
actually
sort
of
initialize
all
the
credentialing
stuff.
A
This
is
not
actually
using
docker
behind-the-scenes
to
do
the
bill,
so
what
Thoth
usually
happens
with
a
build
when
you
have
a
docker
file,
is
that
roughly
each
line
to
the
docker
file
says
start
up.
A
docker
container
run
some
command
in
that
container
and
then
save
the
state
of
that
filesystem
and
turn
that
into
a
layer
in
the
image,
and
so
that
ends
up
being
like
the
thing
happens.
A
What
ko
does
and
I
think
what
we're
seeing
a
new
class
of
tools
doing
where
it
can
actually
build
docker
images
without
actually
running
sub
containers,
to
be
able
to
do
these
things
and
there's
a
couple
advantages
that
number
one.
You
can
be
really
fast
number
two!
You
can
be
very
thoughtful
about
what
goes
into
each
layer
of
your
image
and
then
number
three
is
that
you
don't
need
any
privileges
to
be
able
to
do
this
stuff.
You
can
do
this
stuff,
you
can
make
it
fast.
A
You
can
do
it
locally
and
you
don't
have
to
use
docker,
and
so
the
the
the
the
trade-off
Rico
is
that
Co
works
with
go.
It
doesn't
provide
a
bunch
of
the
sort
of
customization
sort
of
like
open-ended
run.
Any
commands
you
want,
but
it's
very
focused
on
sort
of
like
building
a
go
binary,
getting
it
in
a
docker
container,
and
then
you
can
decide
which
base
container
you
want
and
all
that
stuff
without
bringing
without
bringing
docker
into
it.
A
A
A
A
The
idea
that
you
have
to
have
any
sort
of
elevated
privileges
to
build
a
container
is
really
an
accident
of
history,
of
the
way
that
docker
worked
and
I
think
that
you
know
as
an
industry,
things
work
a
lot
better
if
you
can
actually
create
a
bill
to
create
an
artifact
without
having
any
elevated
privileges,
I
mean
like
I'm
gonna
use,
my
C++
compiler
I.
Don't
need
root
right.
Why
do
I
need
room
to
actually
build
a
container
image?
Okay,
so
essentially
what's
happening
here.
Is
that
we're
giving
it
a
bunch
of
manifests?
A
It's
looking
for
certain
patterns
in
here
like
github,
like
blah
blah
blah.
It's
then
going
through
and
actually
now
I
in
correct
me
if
I'm
wrong,
I
believe
it's
like
it
looks
in
your
go
path
to
see.
If
you
have
this
locally,
it
doesn't
actually
pull
this
thing
down
from
github
out
the
gate,
so
I
think
it.
It
looks
locally
to
be
able
to
do
this
stuff
and
then
for
each
one
of
those
things
that
are
a
command.
A
It
essentially
builds
an
image
on
that
thing
and
then
uploads
that
to
your
registry
and
then
so
that's
the
the
publish
right
and
then
it'll
actually
go
through
and
every
place
where
it
sees
the
that
github
repo.
It
does
a
textual
replacement
with
the
name
of
the
image:
okay,
docker
dot,
IO
/j,
Beata,
okay,
so
that
was
it.
A
Alright,
that
worked
too
I
think
was
already
up
there.
So
I
think
we
were
good.
And
now,
if
I
do
you
control
get
pods,
okay,
yeah
we
did
did
an
upgrade
and
it's
terminating
and
we're
all
up
and
running
so
that
things
up
and
running
yeah,
so
composes
an
image
without
having
to
without
having
to
actually
run
docker.
A
To
do
that
because
you're
not
starting
up
a
docker
because
you're
not
sort
of
like
doing
filesystem
diffs
and
all
that
stuff,
it
can
move
a
whole
whole
lot,
faster,
okay
and
so,
and
the
SHA
the
this
thing.
It
ended
up
creating
a
new
image,
but
the
SHA
was
the
same.
So
so
this
is
another
interesting
thing
is
that
it's
a
totally
reproducible
build,
and
that's
why
like,
if
we
look
at
dr.
A
images,
will
see
that
this
thinks
that's
50
years
ago
and
that's
because
they
essentially
set
all
of
the
UNIX
timestamps
for
all
the
files
and
everything
to
zero,
because
when
you're
trying
to
build
reproducible
things
where
it's
like,
hey
I,
want
to
build
something
now
and
then
I
want
to
build
something.
Ten
years
from
now
and
I
want
to
make
sure
I
get
the
exact
same
bit.
So
I
have
to
understand
everything
that
goes
into
it
any
place
where
you
see
something
like
a
timestamp
in
your
binary
or
in
your
artifact.
A
It
actually
creates
changes
that
aren't
really
changes
that
hinder
reproducibility,
and
so
that's
why
we're
seeing
you
know
all
the
dates
being
wrong
and
there's
something
in
the
readme
that
actually
goes
into
that
stuff.
So,
essentially,
what
it
does
is
finds
those
github.
It
builds
those
images
without
using
docker
it
pushes
those
to
a
registry,
it
rewrites
the
amyl,
and
then
it
applies
the
ammo,
and
so
that's
actually
really
cool.
A
So
how
later
do
you
do
updates
or
roll
backs?
Where
are
the
image,
tags
and
I?
Think
one
of
the
interesting
things
here
is
that
this
is
and
I'll
let
the
guys
on
the
on
the
chat
help
with
this,
but
like
this
is
really
helpful
for
that
development.
Fast
loop
type
of
flow,
when
you're
doing
a
release,
you'll
probably
want
to
go
through
and
give
this
thing
tags
and
sort
of
long
term
identity.
For
this
stuff.
A
A
So
it's
going
to
build
it
and
what
it
actually
did
does
here
is
it
you
can
see
it
replaced
it
with
this
thing
here
with
the
full
Shaw
hash
right
and
one
of
the
interesting
things
that
we
actually
see
and
then
is
that
any
place
where
it
sees
that
string
it'll,
do
a
build.
It'll
actually
do
the
push
on
this
stuff,
and
so
this
doesn't
have
to
be
in
like
a
image,
:
blue
tag.
A
This
could
be
an
environment
variable
or
it
could
be
a
ya
know,
file,
that's
never
uploaded
to
kubernetes,
and
so
you
can
use
this
to
actually
save
the
hat.
The
hash
and
stuff
like
that,
and
that's
what
Matt
was
talking
about
there.
You
can
also
add
tags
now
when
I
saw
this
I
was
a
little
bit
skeptical
of
the
fact
that,
like
any
string
that
looks
like
github
and
my
understanding
is
that
there's
a
strict
mode
and
it's
not
well
documented
and
the
strict
mode.
A
Essentially,
you
have
to
go
through
and
every
place
where
you
have
one
of
these.
These
things
you
have
to
give
it
a
sort
of
code
like
that.
That,
essentially,
is
a
is
a
real
sentinel
saying
this
is
the
code
thing
that
I
want
you
to
build
and
actually
do
it
so
that
that,
if
you're
afraid
of
sort
of
accidental
building
of
stuff
as
you're
doing
your
processing,
this
will
actually
help
with
that
also.
So
that
is
an
interesting
thing
to
see
there.
Oh.
A
So
I
like
that
I'd
like
being
explicit,
that's
just
the
way,
I
roll,
it's
like
I'd,
rather
have
things
be
explicit
than
implicit,
and
so
that's
pretty
much
go
in
a
nutshell:
I
mean
there's.
You
know,
there's
probably
a
few
options
here
and
there.
Oh
there's
this
Acco
apply
slash,
watch
which
essentially
says
anytime
anything
changes
reapply
it.
So
this
starts
getting
like.
You
know
some
of
those
interloop
automatic
deploy
types
of
stuff
which
is
really
cool,
yeah
I'm,
a
big
fan
of
like
let's
actually
not
overload
the
image
field
in
some.
A
There
is
a
there's,
a
replacement
of
it.
Oh
there's
like
this
FS
watch
thing
that
has
similar
semantics,
that
you
could
probably
plumb
in
okay,
cool
all
right,
Duffy,
saying,
there's
another
web
service
out
there.
I
can't
recall
the
name
where
you
point
the
image
string
at
a
web
service,
github
repo
and
we'll
build
the
image
just
in
time
for
you,
yeah
that'd
be
cool
too,
okay,
so
cool,
so
that
is
Co.
Super
interesting
and
I.
Think
it's
it's!
A
A
Okay,
but
I
do
think
we
need
to
like
get
some
instructions
on
how
it
to
so
so
advice.
For
you
guys
instructions
on
how
to
make
this
work
with
kind
would
be
useful
and
then
having
a
sample
that
actually
works
versus
pointing
at
the
repo
that,
like
just
having
a
tutorial
going
ABC,
because
these
things
don't
work.
Matt
Moore
doesn't
actually
have
an
examples.
Repo
contain
me.
A
Serves
docker
container
images
generated
on
demand
at
the
time
they
are
requested,
so
you
can
okay
that
looks
really
interesting.
Docker
pull
Co
contain
D'amico
serves
an
image,
so
this
will
actually
do
the
ko
at
the
time
when
you
pull
it
I'm
very
confused
by
the
whole
thing.
This
is
cute
I'm,
not
sure
you'd
want
to
run
this
like
having
some
random
a
service
hosted
somewhere
building
the
stuff
that
you
run.
This
is
a
good
way
to
get
out.
A
A
Yeah
bill
pecks
are
another
interesting
area
where
they're
viewing
the
building
The
Container
image
as
a
composable,
explicit
thing
versus
this
implicit
thing
with
with
docker
files,
which
is
cool,
yeah,
Nick,
Suri,
Devore
CTR
on
okay,
those
sound
interesting
all
right
cool
all
right,
so
that's
Co!
That's
about
all!
There
is
to
it.
Hopefully,
y'all
get
a
better
idea
of
how
it
works
is
kind
of
wraps
cube
control
to
some
degree.
For
some
of
this
stuff,
you
can
specify
your
base
image.
A
You
can,
you
know,
there's
ways
to
actually
add
some
static
assets
and
stuff
like
that
in
there,
so
some
fun
stuff
going
on
there.
Okay,
let's
move
to
our
next
project
in
our
twofer
here.
Unless
people
have
more
questions
about
Co,
which
is
config
EULA,
so
this
is
so.
This
is
like
the
the
number
of
variations
on
how
to
solve
this
problem
and
and
the
creativity
applied
to.
It
is
absolutely
fascinating
to
me
because,
a
while
ago
we
have
this,
the
I
showed
off
this
project
called
ytt.
A
Which
is
part
of
the
suite
of
projects
from
a
couple
of
folks,
you
know
one
at
I,
believe
IBM
and
then
one
at
pivotal,
Dimitri,
who
may
be
joining
us
or
not
and
and
ytt,
is
interesting,
because
it's
a
yamo,
templating
approach
where
you,
it
kind
of
feels
like
PHP
to
some
degree
where
you
have.
You
can
sort
of
wrap
things
with
with
yam
all
right,
and
so
it's
it's
it's
it's
I
mean
you
have
yam,
oh
and
then
you
can
sort
of
embed
Python
into
it.
A
A
Mohs
effort
says
was
a
yko
is
not
fully
integrated
with
kubernetes
I
was
defecting
to
see
something
like
Co
get
pod
star
lark.
It
was
formerly
Schuyler
yeah,
so
so
Koga
I
think,
like
you
know
it's
one
of
these
things
where
it
does
a
little
bit
of
sort
of
reemployment
about
cube
control,
but
I
think
trying
to
totally
wrap
cube
control.
You
know
they'd
be
interesting
to
think
about
what
that
would
look
like.
So
it's
only
the
applied
create
stuff
that
it
does
and
delete.
A
I
guess:
yeah,
okay,
so
so
here
what
you
can
do
is
you
can
go
through
and
take
a
mole
and
then
just
like
add
a
little
bit
of
Python
type
stuff
in
there,
but
it's
Nemo
first
augmented
with
Python
is,
is
YTD
and
I.
Think
when
we
think
about
templating
Python.
This
is
generally
the
type
of
thing
that
I
think
about
I.
Think
there's
some!
You
know,
there's
some
you
know
questions
around
sort
of
like
does
it
have
to
be
valid?
A
Python
and
I
mean
valid
yamo
and
it
does
and,
like
you
know,
you
can
so
so
there's
some
some
sort
of
structural
awareness
here.
So
it's
not
I,
don't
think
ytt
is
pure
textual,
but
what's
fascinating
is
that
what
Brendan
did?
And
he
took
a
page
from
the
react
world?
Is
he
said?
Okay,
this
thing
is
Python
first
and
yamo.
A
Second,
so
right
now,
one
of
the
things
that
we
find
is
that
any
time
when
you
want
to
embed
something
like
like
even
JSON,
like
the
best-case
scenario,
is
when
you're
embedding
JSON
and
JavaScript
right,
because
you
can
essentially
just
copy
and
paste
it.
But
Jay
sounds
a
pain
in
the
ass
to
actually
write,
because
it's
so
personally
about
stuff
and
and
but
even
doing,
something
like
JSON
in
in
Python
ends
up
being
a
little
bit
complicated
to
be
able
to
do
that
translation
there,
and
so
what
Brendan
do?
Yes,
he
actually
said.
A
Well,
if
you
end
up
with
he
augmented,
he
essentially
a
preprocessor
for
Python
that
goes
through
and
provides
a
way
to
have
sort
of
llamo
literals
inside
of
Python,
where
you
can
go
through
and
you
can
actually
go
through
and
embed
gamble
directly
into
Python
and
and
then
actually
call
out
with
a
special
syntax
back
into
Python.
So
you
can
switch
back
and
forth
to
Python
in
a
way
where
you
can
essentially
just
copy
and
paste
your
your
yamo
you
in
there,
which
is
actually
I,
think
really
really
cool.
A
So
even
saying
are
the
literal,
structured
content
or
text
I
believe
a
the
literals.
You
know
that's
a
good
question.
He
has
a
render
thing
here,
so
my
guess
is
based
on
the
render
that
implies
to
me
that
it
ends
up
being
sort
of
maps
and
lists
and
sets
and
sort
of,
like
native
Python
things
that
you
can
continue
to
continue
to
deal
with,
but
that's
something
that
we
should
totally
dig
into
a
little
bit.
A
A
A
A
A
Let's
see
what
happens
there,
but
then,
if
I
go
to
secure
Ian's
privacy,
yeah,
that's
well,
no
I,
don't
think
I
don't
want
to
turn
it
off
for
everything.
I
just
want
to
be
able
to
like
bless
that
binary.
This
ends
up
being
general.
Okay,
I
can
do
allow
anyway
there
and
that'll
actually
do
it
for
once.
I
want
to
dig
into
this
at
some
point,
but
now's
not
the
time.
Okay,.
A
A
A
A
A
A
Let's
see
what
happens
there:
okay
from
runtime
import,
blah
blah
blah,
okay
yeah!
So
here
you
can
see
sort
of
how
it
expands
it.
So
it
takes
that
thing,
that's
in
line
and
then
it
creates
essentially
a
bunch
of
classes
called
the
ammo
variable,
amyl
expression,
all
that
stuff.
That's
in
that
runtime
thing
the
question
here
and
then
it
says,
render
and
then
it
has
a
maybe
render
at
the
end,
because
I
think
that
lets
you
sort
of
allied
the
render
is
what
I'm,
guessing
and
then
do.
A
A
A
I
had
the
command-line
tools
installed.
Sorry
all
I'm
gonna
build
Python.
While
we
sit
here.
Okay,
but
I,
think
this
gives
you
an
idea
here
of
what's
happening
and
I
think
this
is
actually
fascinating
and
so
I'm
not
gonna
I'm
not
going
to
necessarily
rebuild
Python
while
we
wait,
but
I
think
that
this
is
really
really
fascinating.
A
So
what
he's
doing
under
the
covers
here
is
that
if
we
look
at
you
know,
package
config
EULA
here
you
know
it's
a
pretty
simple
parser
I'm
guessing
so
there's
a
Python
generator
here
and
it
looks
like
he
has
some
interfaces
for
being
able
to
do
different
languages
and
stuff.
Oh
yeah.
Maybe
a
docker
image
would
be
the
way
to
go
to
actually
demo
this
stuff
off.
But
the
idea
here
is
that
you
know
it's
nothing
more
than
generating
looking
through
the
lines
you
know.
A
A
A
So
yeah
so
I
think
it's
a
really
really
cool
hack
and
I
love
this
sort
of
being
inspired
by
JSX.
Because
if
you've
used
react,
you
can
use
react
without
JSX,
but
it's
works
a
heck
of
a
lot
better.
If
you
do
because
it
lets,
you
have
your
code
and
your
data
is
sort
of
HTML
stuff,
totally
inner.
You
know
intertwined
in
a
way
that's
actually
scalable,
because
it's
it's
not
like.
You
know,
PHP,
where
PHP
it's
the
HTML
on
the
outside
and
PHP
on
the
inside.
A
Here
it's
you
know
Python
in
this
case,
but
in
JavaScript
with
JSX,
it's
the
the
real
language
on
the
outside,
but
you're.
Actually,
you
know
bringing
the
ideas
around
the
the
a
special
type
of
format
on
the
inside.
That
thing
gets
pre-processed.
It
turns
into
a
set
of
classes
that
you
can
then
work
with
even
further,
which
is
really
really
cool.
A
A
There
was
a
name
for
this:
it's
not
sequel,
but
it's
a
sequel,
link,
yeah
the
link,
stuff
yeah
so
like
c-sharp
link,
is
fascinating
in
that
now.
This
actually
goes
a
lot
deeper,
but
they
have
sort
of
special
syntax.
Here,
that's
extensible
that
actually
turns
into
sort
of
classes
that
get
executed
under
the
covers
not
exactly
the
same
thing
as
this,
but
this
idea
of,
like
we're
going
to
be
taking
sort
of
you
know
these
types
of
special
types
of
syntaxes
and
being
able
to
actually
do
interesting
things
with
them.
A
A
I,
don't
know
if
you
could
do
the
sort
of
back
and
forth
that
that
Brendon
does,
and
that
happens
with
a
lot
of
react,
which
is
essentially
the
Aria
scaping
back
into
Python.
That's
something
that
I,
don't
think
is
well
supported
in
C++,
but
yeah,
but
I
think
link
is
another
example
of
where
you
actually
see
the
blurring
of
these
lines
and
obviously
in
the
functional
language
world.
This
is
you
know,
very,
very,
very
common,
but
I
think
seeing
this
mixed
into
imperative.
Languages
is
really
cool.
A
A
Maybe
ok,
but
I
think
you
know
I
think
this
highlights
sort
of
the
brittleness
of
Python
installs,
because
clearly
I
have
sort
of
that
Frank
and
installed
going
on
right
now
and
debugging.
Python
paths
is
never
fun
but
I
like
really
like
the
stuff
that
Brennan
is
doing.
It's
gonna
be
interesting
to
see
where,
where
it
goes
from
there,
ok,
so
PI
ml.
You
think
that's
what
we
want
to
do.
A
It's
it's
busy
installing
this
other
stuff,
the
command-line
tools.
Oh
we're
like
five
minutes
all
right,
yeah,
I'm,
gonna,
pass
on
this
I
think
you
all
get
to
get
the
the
flavor
of
it
there's
not
much
to
it.
This
is
why
I
felt
like
I
could
do
a
twofer,
because
it's
really
pretty
simple.
It's
very
much
a
I
think
a
proof
of
concept
here.
The
interesting
thing
here
is
that
you
know
he
does
build
out
sort
of
this.
Yamo
object
model,
and
this
is
something
that
to
me
is
is
interesting,
is
and
I
think.
A
Maybe
part
of
that
is
the
expression.
Okay.
This
is
this
is
fascinating.
Is
that
print
unrendered
bits?
You
have
EML
variables
and
stuff,
so
he
had
to
do
some
hacker
AMA
around
that
to
actually
make
this
sort
of
reinventing
work.
The
I
was
clear.
It
was
is
like
over
the
Christmas
project,
the
it's.
Let's
see
it
so
he's
using
dumper
node,
representer,
okay,
so
the
yeah
mo
the
mo
library
for
Python.
A
A
Raw
types
by
default,
and
then
you
can
actually
overload
sort
of
the
different
types
that
you
want
to
think,
but
there's
no
sort
of
generic
sort
of
Yamla
object
model
similar
to
like
when
you're
say,
parsing
XML
back
in
the
day,
and
so
it's
interesting
that
he
has
to
do
a
little
bit
of
that
to
be
able
to
make
this
stuff
work.
So
alright,
cool
I
mean
just
like
a
recursive
descent
to
render
the
thing
which
is
pretty
cool,
so
yeah
I
think
I
am
going
to
call
it
there.
A
A
A
You
know
a
tighter
inner
loop
for
devs,
but
it's
very
much
focused
ago
and
the
go
build
process
that
type
of
thing
versus
something
super
generic.
You
know
we've
already
seen
that
with
stuff
like
jib,
you
can
do
similar
types
of
things
with
Java,
but
I.
Don't
think
that
we
see
a
absolutely
you
know
generic
solution
here.
A
But
it's
interesting
to
see
sort
of
how
you
actually
bring
sort
of
that
different
point
of
view
here
and
I
love
the
the
influence
from
the
react
world
with
JSX
I
think
that
that's
really
cool
all
right.
So,
finally,
you
know
if
you
made
it
this
long,
you
probably
already
subscribed,
but
you
know,
I'm
on
YouTube,
so
I
gotta
say
subscribe
and
hit
the
hit.
The
bell
button,
and
all
that
and
and
then
matt
has
a
you
know,
says
that
there's
a
co
channel
in
the
K
native
slack.
A
So
I
couldn't
avoid
doing
a
TGI
K
on
it,
but
with
that
I'm
gonna,
sign
off
and
I'm
gonna
wish
you
all
a
great
weekend,
I
hope
if
you're
in
a
different
time
zone,
you're
already
enjoying
your
weekend,
if
not
have
a
great
rest
of
your
Friday
and
we'll
see
you
all
next
time
here
on
t
GI
kubernetes.
Thank
you.