►
From YouTube: Cloud Native Live: Use your favorite programming language to build your dream cloud native platform
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
all
right,
hello,
everyone
and
welcome
to
cloud
native
live
where
we
dive
into
the
code
behind
cloud
cloud
native.
I
am
itai
shakuri
and
I'm
director
of
open
source
at
aqua
security,
I'm
also
a
cncf
cloud
native
ambassador
and
will
be
hosting
today's
show.
So
this
is
cloud
native
live.
Every
week
we
bring
a
new
set
of
presenters
to
showcase
how
to
work
with
cloud
native
technologies.
A
They
will
build
things,
they
will
break
things
and
they
will
answer
your
questions
so
join
us
every
wednesday
at
11
a.m.
Eastern
time
this
week
we
have
matty
straton
here
to
talk
with
us
about
pulumi.
He
will
introduce
himself
in
a
second
just
a
quick
disclaimer
that
this
is
an
official
live
stream
of
the
cncf
and
as
such
is
subject
to
the
cncf
code
of
conduct.
Please
don't
add
anything
to
the
chat
or
question
that
will
be
in
violation
of
that
code
of
conduct,
basically
just
be
respectful
of
your
fellow
participants
and
presenters
so
matthew.
B
Sure
yeah,
my
name
is
maddie
stratton,
I'm
a
staff
developer
advocate
at
palumi.
I've
been
here
for
a
couple
months,
so
we'll
we'll
see
how
expert
I
can
just
be.
I've
been
in
the
devops
space
for
a
long
time.
I
host
a
podcast
called
the
rest
of
devops
and
run
devops
days,
and
I'm
excited
to
kind
of
do
a
little
exploring
about
gloomy
and
what
we
can
do
to
play
around
and
have
some
fun
with
kubernetes
with
it.
A
B
It's
very
easy
in
whatever
programming
language
you're
using
for
your
portal
to
just
consume
the
libraries
and
then
it
all
happens
there.
So,
like
there's
a
tutorial,
we
do
where
basically
go
ahead
and
do
pod
deployments
by
clicking
on
a
button
in
a
python
web
app
and
but
the
thing
that's
really
powerful,
with
pollumi
and
among
other
things,
is
that
all
of
your,
your
pollumi
programs,
which
is
the
thing
you're
going
to
write,
to
reason
about
your
cloud
infrastructure,
whether
it's
kubernetes
or
aws
or
gcp
or
whatnot,
you're.
B
Writing
it
in
the
programming
language
of
your
choice.
So
you
can
write
polumi
code
in
javascript
and
typescript,
which
is
what
I'm
going
to
be
doing
today.
You
can
write
it
in
python.
You
can
write
it
in
net
or
you
can
write
it
in
go
and
the
reason
that
that's
there's
a
couple
of
reasons
that
resonates
to
me
and
again
kind
of
coming
from
the
background
of
working
with
chef,
where
you
had
the
goodness
of
being
able
to
write
in
ruby.
B
But
the
problem
was,
if
you
didn't
like
ruby,
you
probably
weren't
gonna
like
chef
too
much,
and
the
goodness
of
this
is
among
other
lines
like
hey.
If
you
already
know
one
of
those
programming
languages
cool,
you
don't
have
to
learn
a
new
language,
but
because
it's
expressed
that
way,
everything
available
to
that
language
is
available
to
you
as
you
build
your
paloomy
code.
Things
like
you
know
simple,
as
just
auto,
complete
stuff
in
your
ide,
but
testing
tools
all
that
good
stuff.
B
B
I
wonder
if
there's
a
pollumi
plug-in
well,
of
course,
actually
there's
not
because
you
don't
need
it,
because
pollumi
is
just
typescript
or
it's
just
go
and
you'll
see
that
as
I
kind
of
go
through
this
stuff,
where
we're
getting
that
stuff
for
free
and
the
the
last
sort
of
thing,
I
think
about
is
there's
a
couple
different
types
of
reasons
you
might
be
thinking
about
polumi.
It
could
be
if
you're
like
me,
and
you
spent
your
life
in
ops
and
you're,
maybe
on
a
platform
team.
B
This
is
a
way
to
be
able
to
provide
these
resources
in
an
automated
and
trackable
way
in
the
way
that
makes
sense
to
you,
but
also,
if
you're,
a
software
engineer
that
doesn't
really
know
cloud
infrastructure
that
well,
but
you
know
you
need
to
get
stuff
there.
This
is
giving
that
window
to
the
cloud
to
that
ability
to
to
create
that
get
the
stuff
that
you
need
and
where
that
goes,
that's
the
stuff.
A
B
That's
the
the
intent,
because
there's
a
couple
different
ways
that
you
can
consume
providers
with
polumi
there's
the
ability
you
can
absolutely
wrap
an
existing
terraform
provider.
So
if
there's
not
a
native
pollumi
provider,
but
there
is
a
terraform
provider,
there's
there's
those
bridges
but
where
it
gets
powerful
is
what
we
call
the
native
providers
where
we're
talking
directly
to
the
apis
from
that
platform,
and
so
as
long
as
that.
B
So
back
in
my
chef
days,
one
of
the
things
people
always
wanted
is
they
said:
hey
I've
got
my
apache
server
here.
Can
I
just
point
chef
to
it
and
generate
the
cookbook
that
will
make
it
look
like
that
and
we
said
well,
no,
because
there's
hundreds
of
thousands
of
configuration
things
that
could
possibly
exist
on
a
linux
operating
system
plus
apache,
plus
whatever
there's
no
way
for
us
to
know
all
the
things
that
might
have
a
configuration.
B
Well,
then
you
go,
and
you
start
talking
about
things
like
because
when
you're
reasoning
against
an
api
versus
that
all
that
stuff
is
consumable,
so
you
absolutely
can
point
pollumi
to
your
fargate
cluster
to
your
kubernetes
cluster
that
exists
and
say
generate
the
pollumi
code.
That
will
make
this
happen
and
that
actually
can
happen.
And
it's
because
we're
reasoning
about
everything
at
an
api
level
and
that's
just
as
the
world
has
changed
right.
You
know,
linux
servers
weren't
meant
to
be
reasonable,
like
apis
they're,
just
a
bunch
of
files
right
right.
B
I
had
kind
of
thought
about
running
this
on
mini
cube
on
my
machine,
but
I
also
have
apple
silicon
and
I
haven't
had
a
good
experience
yet
making
sure
that's
100
good,
so
the
kubernetes
cluster
that
we're
going
to
do
is
we're
going
to
use
polumi
to
spin
up
an
eks
cluster
in
amazon.
You
could
do
this
with
aks.
You
could
do
this
with.
However,
you
wanted
to
that's
just
how
I'm
choosing
to
do
that
to
kind
of
show
the
ideas.
B
The
other
thing
is
like
I
said
you
can
write
pollumi
code
in
typescript
or
python,
or
go
or
or
c
sharp
and
and
dot
net
I'm
gonna
be
using
typescript.
Because
that's
where
my
examples
were,
I
also
usually,
I
actually
like
to
write
pollumi
code
and
go,
but
I
had
a
couple
things
I
wanted
to
steal
from
that.
I'd
done
before
that
were
in
typescript,
so
that's
where
we'll
go,
but
all
of
this
stuff
is
available
in
all
the
other
other
languages.
B
We
can
go
ahead
and
get
started.
The
one
thing
I'm
give
a
quick
background.
Before
I
bring
up
my
code,
then
I
think
I'll
just
go
ahead
and
do
it.
This
way
there
we
go
okay,
so
polumi
is
an
open
source
project.
Pollumi
itself
doesn't
cost
you
a
dime,
go
ahead,
use
it
knock
yourself
out
the
what
pollumi
needs
is
it
needs.
It
needs
a
back
end,
a
place
where
it
stores
state
and
you
can.
The
the
preferred
way
is
through
the
palumi
service
pollumi.com
and
for
individuals.
B
Stuff
like
this
doesn't
have
any
cost
to
it.
The
the
paid
offering
involves,
if
you're,
if
you're,
creating
teams
and
organizations
and
you're
doing
things
with
needing
a
lot
more.
That
trip
being
said,
you
can
use
s3
as
a
back
end.
You
can
use
almost
anything,
but
you'll
have
probably
a
little
bit
of
a
better
experience
using
poloomi.com.
So.
B
Absolutely
so
the
thing
the
thing
to
remember
is
palumi
the
service,
the
plumi.com,
it
doesn't
actually
talk
to
any
of
the
cloud
providers
are
doing
any
of
that
stuff.
So
we
don't.
We
don't
talk
to
the
cloud
provider
on
your
behalf
on
our
sas.
But
what
happens
if
I'm
going
to
do
a
deployment?
For
example,
I'm
going
to
say
spin
up
this
cluster,
which
we're
doing
paloomi,
has
to
know
the
state
that
the
cluster
is
in
so
that
it
is
able
to.
B
When
you
run
to
say,
do
I
need
to
do
anything
right
like
I
need
to
understand,
what's
happening,
and
so
that
has
to
be
stored
somewhere
right.
There
has
to
be
a
way
for
palumi
when
I
run
my
paloomy
program
to
say
well
maddie
you
asked
for
this,
but
this
is
the
current
state
of
the
thing
you
want,
and
this
is
the
change
I'm
gonna
make
right
and
then
also
and
that
lets
us
in
addition
to
so,
it's
just
sort
of
the
common
central
structure
to
under
to
reason
about
your
infrastructure.
B
Okay,
so
you
can
store
that
as
a
state
file
wherever
you
want.
It's
just
a
you
know,
works
out
a
little
bit
better
if
you
can
use
the
the
service,
because
you
get
to
see
a
little
bit
more
put
it
this
way.
If
you're,
not
gonna,
use
the
service
and
you
throw
it
in
s3
or
something
like
that,
you
probably
have
to
build
some
stuff
around
it
yeah
to
show
you
this
stuff.
So
the
idea.
B
Yes,
the
only
the
only
place
where
you're
gonna,
you
know
start
running
into
you
know
the
the
cost
is
is,
if
you
want
to
create,
like
our
bat,
you
know
who
has
rights
to
what
stack
who's
doing
that,
if
you're
doing
larger
collaboration
type
features
is
where,
where
the
paid
offering
comes,
but
I
mean
for
me
just
right
now,
I
just
rock
this
thing.
It's
totally
like
I,
when
I
started
I
was
like.
Oh
do.
B
I
have
to
get
some
kind
of
you
know
special
key
for
my
blooming
account
like
everybody
who
works
at
polou's
like
we
just
use
a
free
one.
It's
fine
yeah,
you
know
it's
totally
good
and
the
idea
you'll
see
a
little
bit.
I've
got
a
couple
in
here
and
we're
going
to
create
these
projects
the
the
thing
with
a
project,
for
example,
we
can
go
look.
B
And
the
thing
that's
important
to
think
about
is
you
have
when
you
think
about
how
you
organize
your
pollumi
projects
and
your
way
you
reasoned
about
pollumi
and
there's
lots
of
different
ways
to
do
it,
depending
on
how
your
team
works.
But
fundamentally
I've
got
a
pollumi
program,
that's
like
a
project,
probably
maps
to
a
git
repo
and
then
within
a
project
you
have
stacks
which
to
me
I
always
reason
about
them
as
like
environments,
but
they're
really
different
instances
of
this
type
of
program
that
might
have
things
different
about
them.
B
So
we're
going
to
just
be
using
a
stack
that
I
call
dev
for
the
stuff
we're
building,
but
you
might
have
a
dev
stack.
You
might
have
a
prod
stack
and
or
you
might
break
them
up,
based
on
like
availability
zones
or
something
because
those
are
all
different
configuration
parameters.
You
might
pass
into
that.
So
you
can
use
the
same
pollumi
code.
I
like
to
think
about
them
as
environments
which
may
or
may
not
be
the
right
way
to
talk
about
it
in
pollumi
speak.
But
it's
what
made
sense
to
like
what.
B
Absolutely
right
like
so,
for
example,
let's
say
I've
got
this.
You
know
workshop
club,
this
cluster,
that
we're
going
to
build
this
eks
cluster,
and
then
I
know
this
is
maybe
not
a
great
example,
but
for
some
reason
my
development
cluster
that
I
like
to
build
is
in
us
west
too,
but
we
run
prod
in
us
east
because
we
don't
like
ourselves.
I
guess
I
don't
know,
but
so
what
I
can
do
is
my
program.
B
Does
that
but
you'll
see
when
we
kind
of
pull
in
there's
a
place
we
can
pull
in
from
the
config
and
every
stack
has
its
own
sub
config
so
that
I
can
say,
and
the
part
one
maybe
I'm
gonna
say:
where's
the
availability
zone,
or
maybe
even
the
size
right.
How
many
or
how
many?
How
many
replicas
do?
I
need
for
this
application,
maybe
in
test
I
only
need
one
or
two
but
proud.
B
We
know
we
run
a
hundred,
so
those
are
all
variables
that
can
be
set
at
the
stack
level
and
stacks
can
actually
output
to
each
other
as
well.
We're
not
going
to
really
go
into
that
today,
but
if
I
have
a
stack,
it
can
maybe
again,
if
you're
thinking
about
how
things
move
along
through
your
workflow,
maybe
something
outputs
from
an
earlier
stack
and
then
that
has
to
get
consumed
by
a
later
one.
So
there's
a
lot
of
ways.
We
can
reason
about
this
about
this
data.
A
B
I'm
going
to
go
ahead
and
sorry
I
kept
that
if
I
want
to
change
my
windows,
you
all
don't
want
me
sharing
my
whole
screen,
because
it's
a
49
inch
monitor.
So
I
still
have
to
go
window
by
window.
So
a
couple
things
I'm
not
going
to
I'm
going
to
explain
through,
but
not
going
to
show
because
it's
boring
to
watch
me
do
so.
The
thing
is,
though,
the
for
this
whole
work.
You
need
the
palumi
command
line
tool
right,
so
you
know
you
can
just
sort
of
see
there.
B
It
is
installed
with
homebrew
easy
enough,
it's
a
simple
little
cli
and
then
you
will
in
this
case
what
I've
already
done.
Is
I've
already
offed.
Excuse
me
polluting
me
to
the
plume
service
and
there's
a
step.
There's
poloumi
login
you
go
through
it's
just
like
every
other
type
of
thing.
You've
done
like
this,
which
says
that
way.
It
stores
your
credential
and
knows
that
when
I'm
running
paloomy
it
should
talk
to.
B
It
should
use
my
account
to
talk
to
the
palomi
service,
so
we've
already
sort
of
got
that
got
that
started
and
what
we're
going
to
do
is
we're
going
to
start
and
create
a
plummy
program.
That's
going
to
spin
up
an
eks
cluster
for
us
on
amazon,
which
we
could
then
use
for
a
lot
of
the
other
stuff
that
we're
gonna
do.
A
B
So
that
uses
my
normal
aws
cli
config
all
right
right,
so
you
know
you
could
use
environment
variables,
use
whatever.
Whatever
is
the
way
that
you
would
manipulate
aws,
so
you
could
use
an
enviro.
You
know
use
an
aws
profile,
so
what
you
can
do
is,
I
could
say,
for
example,
polumi
config
set.
I
can
set
the
config
as
you'll
see
when
we
set
we're
going
to
set
a
couple
parameters
in
the
config
and
one
of
the
things
I
could
do
in
there
is
say
what
aws
profile
to
use.
B
B
B
B
Yeah
yeah,
that
was
a
tada
mtvs
code
screen,
so
the
yeah.
It
follows
it's
the
because
it's
talking
to
the
apis
the
way
that
the
api
wants
to
be
talked
to
so
you'll
see,
for
example,
when
we
go
to
the
part
where
we're
manipulating
the
cluster
pollumi
doesn't
use
cube
cuddle,
but
it
uses
kube,
config,
yeah
right
so
and
there's
various
ways
you
can
get
that
access,
that's
the
format
of
that
that
it
consumes.
B
But
you
don't
need
to
have
the
aws
cli
installed
to
do
that,
but
the
convention
of
of
where
the
credential
comes
from
so
cool
okay.
So
we're
going
to
go
ahead
and
create
our
first
paloomy
program
here.
So
we're
just
going
to
call
this
madi
cluster
maddie
cluster,
because
yeah,
let
me
see
if
I
can
make
that
a
little
bigger
for
you.
B
An
empty
typescript
program
you'll
see
later
that
there
are
templates
for
for
different
things.
So
if
I,
if
I
wanted
to
create
that
that
will
pre-create
get
kind
of
a
getting
started
piece,
but
we're
going
to
start
from
scratch
here,
so
we're
going
to
say
we're
going
to
create
a
new
typescript
and
it's
going
to
say
so:
it's
it's
creating
the
stack
for
me
on
the
paloomy
service
and
then
it
kind
of
set
up
the
the
beginnings
that
we
need
to
have
here
right.
B
So
it's
a
typescript
program,
so
we've
got
our
package.json
and
it's
go
ahead
and
it
says:
okay,
I
know
that
I
need
polumi
and
it
gives
me
and-
and
we
can
see
that
index.ts
is
our
main
program,
which
is
not
really
doing
anything
terribly
interesting
right
now,
so
we've
gone
ahead
and
initialized.
It
we've
started
it
and
we
can
see
that
we're
importing
the
pollumi
library.
But
let's
actually
do
something
interesting
here.
So.
A
B
Exactly
what
this
did,
and
also
because
it,
the
palumi
yaml,
is
telling
it
the
name
of
the
paloomi
project.
That's
connected
to
that
so,
like
you
could
have
done
all
that.
But
if
you
don't
do
the
paloomy
new,
you
would
have
to
go
and
then
create
that
project
on
the
plummy
side.
So
this
this
takes
care
of.
You
can
say
it's
creating
the
stack
and
then
but
then
it's
also
like
I
said,
pre-configuring
the
things
that
we
know
we
normally
need,
but
you
don't
necessarily
have
to
follow
this
in
this
way.
B
The
other
thing
a
little
more
advanced
way
to
think
about.
It
is
right
now
you're,
seeing
that
I've
got
the
pollumi
program
kind
of
by
itself,
it's
possible
and
sometimes
the
right
pattern.
If
you
want
the
infra
code
to
live
with
the
application,
so
you
might
have
in
your
repo
for
your
application,
you
might
have
a
subdirectory
called
infra
that
contains
your
actual
pollumi
program.
B
So
we've
got
our
our
initial
piece.
We
could
do
a
pollumi
up,
but
it
wouldn't
do
anything
interesting,
but
we
want
to
go
ahead
and
get
in
the
aws
packages
that
we
need,
because
we're
going
to
be
talking
to
aks
or
eks
sorry,
amazon,
people,
I'm
going
to
go
ahead
and
clear
my
screen
here,
so
we're
going
to
do
a
yeah.
Sorry,
I
see
the
correct
says:
I'm
a
python
developer.
Absolutely
you
can
write
paloomi
and
python
lots
of
people
like
to
write
pollumi
in
python.
B
You
would
be
able
to
do
in
python
and
one
of
the
things
that's
really
important
is
we
have
this
idea
of
plumi
packages,
of
which
this
aws
package,
I'm
about
to
add,
is
an
example.
So
there'll
be
packages
for
cloud
providers
and
kubernetes
and
things,
but
you
also
could
have
a
package
for
say
pagerduty.
Actually,
there
is
a
package
for
page
duty,
but
what's
cool
with
this
idea
of
multi-language
packages?
Is
you
might
create
this
package
that
either
you
want
the
community
to
use
or
within
your
organization
and
you're
like
okay?
B
Well,
the
thing
is
because,
if
normally,
if
I
want
to
write
this
package,
I
have
to
I'd
have
to
write
the
sdk
for
it
in
each
of
the
languages.
I
wanted
it
to
support
right.
So
let's
say
I
know,
go
and
I'm
like.
Okay,
I'm
going
to
write
a
package
for
page
duty
right.
Well,
I'm
going
to
write
it
and
go
and
that's
cool
for
anybody
who
wants
to
use
polumi
code
with
go,
but
the
sdk
wasn't
published
with
the
multi-language
packages.
B
A
B
A
B
B
Pretty
much
yeah,
it's
it's
based
on
how
you
build
that
particular
thing,
and
what
native
native
providers
are
really
the
way
where
things
are
going
and
there's
more
and
more
things
being
created
in
that
kind
of
the
terraform
bridge
was
a
way
to
say:
if
you
don't
want
to
rewrite
the
provider
in
palumi
and
have
it
have
all
that
goodness
you
can
consume
it?
You
know,
because
there
already
is
a
whole
bunch
of
great
terraform
providers
out
there.
That
can
be
a
stepping
stone
to
that.
A
B
So
when
you
say
can
we
use
terraform
and
polomi,
you
can
take
your
existing
terraform
and
turn
it
into
polumi.
The
question
is:
terraform
a
competing
solution.
Yeah
this
would
play
in
the
same
place
as
terraform
or
chef
for
that
matter,
you're
not
likely
to
use
both,
but
you
can
use
you
might
use
both
for
a
while.
The
only
thing
is
the
same
thing
back
from
my
chef
days.
You
don't
want
to
be
running
multiple
config
management
against
the
same
resources,
because
they'll
all
start
fighting
with
each
other.
B
While
your
organization
may
not
use
it
everywhere,
you
want
to
make
sure
within
projects
you're
not
trying
to
do
terraform
for
part
of
the
project
and
plummy
for
another
part,
because
then
you
get
kind
of
a
split
brain
thing
that
happens
like
when
people
wanted
to
run
puppet
for
some
stuff
on
their
servers
and
chef
for
other
things.
It's
just
not
a
not
a
pleasant
place
to
end
up.
B
I'm
also
installing,
what's
called
the
aws
x
package,
so
one
of
the
things
is
we
have
packages
that
we
call
crosswalk
and
what
these
do
is
they
abstract
away?
Some
of
the
things
you
might
need
to
do
that
are
according
to
good
practices.
So,
for
example,
if
I'm
creating
an
eks
cluster,
there's
a
lot
of
aws
resources,
I
have
to
create
as
well
that
happen.
B
Every
time
you
create
an
eks
cluster,
and
if
I
wasn't
using
the
crosswalk
package,
I
would
have
to
go
in
in
my
pluma
code
and
create
all
of
those
things,
whereas
that
package
wraps
what
are
common
good
practices
around
things
that
would
map
to
that.
It
makes
it
a
lot
easier
and
then
you
could
use
a
similar
idea
to
what
we
do
in
crosswalk
again
within
your
organization,
for
the
packages
that
you
might
want
to
share
with
people
to
say
like
okay.
B
This
is
what
how
we
build
eks
clusters,
you
know
and
we're
going
to
expose
just
the
parts
that
you
need
to
turn
the
dials
on
again.
It
goes
back
to
the
way
I
used
to
think
about
chef
where
I'd
say
like
okay.
If
I
want
to
spin
up
a
tomcat
server
and
I'm
a
developer,
there's
like
a
thousand
different
things,
I
could
do
in
tomcat.
I
care
about
three
of
them.
You
know
so
how
can
I
abstract
that
away
just
and
make
sure
that
everything
else
just
gets
done?
B
I
swear,
I
know
how
to
type
okay,
so
we've
got
those.
That's
that's
just
fun
typescript
stuff.
So
now
we'll
just
sort
of
let
that
sit
there.
But
what
we
want
to
do
is
like
I
talked
about
the
config
right,
so
I
need
to
set
a
couple
different,
config
things,
so
one
thing
is
going
to
be.
Where
do
I
want
to
put
this
right-
and
in
this
case
I'm
going
to
say
we're
going
to
run
in
us
west
2.?
B
B
Oh
so
it
so
it
see
it
created
this
paloomy
dev
yaml.
So
this
is
a
configuration
item,
but
it's
at
the
stack
level.
This
is
just
for
the
dev
stack
and
then
likewise,
we're
also
going
to
do
a
we're
going
to
set
the
aws
skip
metadata
api
check
and
that's
just
because
it's
running
in
an
im
role.
So
it
doesn't
need
to
do
that.
B
B
B
Let's
do
this,
I
think
that's
different.
Let's
call
it
just
to
make
sure
I
don't
have
something
with
that
name
already
and
but
then
what's
the
name
of
the
cluster
right,
so
this
is
going
to
be
so
I
can
pull
you
know,
name
and
then
say
it's
going
to
be
cluster
cool
fun,
exciting,
and
then
we
want
to
do
the
same
thing
with
our
cluster
tag
that
we're
going
to
use
and
since
because
we're
setting
these
variables
here,
this
is
letting
us
interpolate
them
and
kind
of
do
all
that
stuff.
B
Now
we
want
to
actually
create
this
vpc.
So
we're
going
to
do
we're
going
to
create
this
vpc
as
a
new
aws
object
and
it's
an
ec2
v,
and
so
you
see
how
the
type
ahead
I'm
getting
all
this
stuff
for
free
right,
vs
code,
doesn't
know
what
gloomy
is,
but
because
I've
imported
that
aws
x
package,
then
I
get
get
all
of
this
helpful
type
of
head
stuff
right,
so
go
ahead
and
give
ourselves
we're
going
to
name
it
after
our
name.
A
A
B
Yes
and
then,
if
you're
used
to
this
is
doing
with
typescript
typescript's
very
good
at
this
kind
of
thing,
but
you
see
these
similar
type
of
heads
and
autocompletes
and
stuff
if
you
were
doing
this
in
python,
because
you'd
have
brought
in
the
python
package
for
this.
That
provides
all
that.
So
it's
again
it's
sort
of
cheating.
If
you
will,
I
don't
know,
if
that's
the
word
I
want
to
use,
but
you
know
no
more
than
any
other
library
would
be
cheating
by
having
typescript
do
what
typescript
does
right.
B
B
B
A
B
B
B
This
is
what
happens
when
I
type
and
talk
at
the
same
time,
so
we've
got
type
is
public
yeah,
so
the
question
there
isn't
going
to
be
a
code
extension
for
palumi,
because
everything
that
palumi
does
short
of
typing
in
palumi
up
like
that
would
be.
The
only
thing
I
could
think
of
that
you
could
do
with
an
extension
would
be
that
I
could
right
click
on
a
file
and
say
run
pull
me
up,
but
pretty
much
everything
that's
happening
is
coming
from
the
the
programming
language
cluster
tags.
A
A
B
Okay,
I'm
gonna
copy
from
my
code
that
I
did
earlier
today
because
y'all
don't
need
to
watch
me
type
okay.
So
the
only
thing
that
I
just
copied
that
wasn't
there
before.
Is
that
also
we're
doing
this
overall
tag?
So
so
this
is
basically
getting
us
our
vpc
easy
enough
stuff,
and
then
we
want
to
go
ahead
and
define
this
cluster,
and
this
is
what's
kind
of
nice,
because
so
first
we
need
to
bring
in
the
eks
provider,
so
we'll
say,
install
halloumi.
B
B
And
we're
using
clustname
that
we
had
that
we
defined
before
and
then
we
we
can,
because
we
have
that
vpc
id,
because
we
created
that.
So
I
can
get
the
value
that
came
from
the
vpc
that
we
created
up
there
that
object
called
vpc,
so
the
id
that's
coming
back
from
when
it
gets
created,
I
have
available
and
then,
when
I
do
private
subnet
ids,
I
can
the
same
thing.
B
I
can
get
those
from
that
object
and
then
the
same
thing
will
happen
for
the
public
subnet
ids,
which
are
all
the
things
that
eks
needs
to
know
right
and
then
we
can
say
my
instance
type,
and
in
this
case
I'm
gonna
say
you
know
t2
medium.
So
this
is
the
size
for
the
you
know
the
cluster
nodes
that
need
to
happen.
B
I
want
to
have
two
of
them,
because
this
is
on
my
credit
card
and
I
can
set
min
size
to
one
max
size.
This
is
all
your
and
then
we'll
go
ahead
and
create
the
oidc
provider
who-
and
then
we
pretty
much-
have
that
so
this
code
right
there
was
everything
to
tell
palumi
what
I
want
this
cluster
to
look
like
and
we're
using
the
variables
that
we've
defined.
B
So
we
don't
have
to
keep
retyping
that
over
and
over
again-
and
this
is
even
stuff-
that
this
could
come
from
the
kulumi
config
from
that
bloomy
deviamila,
for
example,
the
cluster
name
was
something
we
wanted
to
be
done
dynamically
based
upon
the
stack.
So
now,
if
we
wanted
to
go
ahead
and
do
this
so
we
run
the
paloomy
when
we
run
pollumi
up.
What
that's
going
to
do
is
first,
it
does
a
preview
of
what
it's
going
to
do
and
it's
looking
at
the
plumi
program
and
saying:
okay.
B
B
If
you
want
to
apply
this
update-
and
in
this
case
we're
going
to
go
ahead
and
say
yes,
because
we
would
like
our
cluster
to
exist
now,
this
takes
a
little
bit
of
time
and
we're
not
going
to
sit
and
wait
for
the
15
to
16
minutes
that
it
takes
for
an
eks
cluster
to
come
up,
because
that
would
take
us
to
the
end
of
the
stream,
and
that
would
not
be
very
exciting.
So
when
this
is
chugging
away,
we
can
also
see
this
if
I
switch
over
really
quick
to
my.
B
B
That's
what
I
get
for
for
moving
things
around
there.
We
go
okay.
So
if
I
look
at
the
project,
so
we
created
a
new
project
called
madi
cluster
and
we
can
see
in
the
stack.
So
we
can
see
here
is
the
configuration
that
we
had
set
the
tags
that
that
that
exist
from
the
paloomy
side.
But
if
we
look
at
activity,
we
can
see
there's
an
update,
running
right
and
this
is
showing
me
the
changes.
These
are
the
things
that
have
happened.
This
is
the
changes
is
what
happened
it
created
these
things.
B
If
I
go
to
timeline,
we
can
see
that
right
now,
it's
working
on
these
pieces
and
parts.
This
is
also
what
we
were
seeing
in
the
cli,
but
giving
us
this
in
the
this
is:
what's
letting
us
see
this
from
the
the
web
perspective?
If
that
was
the
thing
that
was
interesting
to
us,
I'm
gonna
switch
screens
on
you
one
more
time.
Sorry,
but
I
won't
won't.
Do
it
again.
That's
the
last
time,
I'm
I'm
flipping.
B
So
one
of
the
things
we
can
do
so
I'm
going
to
switch
over
on
my
terminal,
so
this
is
on
the
cluster
that
I
had
created
before
and
what
I
want
to
do
is
if
I
there's
outputs
that
come
out
of
the
pollumi
program
and
so,
for
example,
if
I
were
to
say
palumi
stack
output.
These
are
the
things
that
my
paloomy
program
is
exporting,
which
you
and,
among
other
things,
it's
exporting
a
cube,
config
right.
So
what
we
can
do
with
that,
then
is.
I
can
go
ahead
and
use
the
polumi.
B
I
could
t
that
out
to
my
local
cube
config
as
it
happens,
my
local
coop
config
is
already
pointing
to
this
particular
cluster,
although
it
wouldn't
actually
hurt
to
do
that.
So
you
can
see
what
it
does.
So,
if
I
do
that,
it's
going
to
take
the
output
of
it's
going
to
dump
that
kube
config,
where,
where
now
I
have
that
available
to
me,
so
I
have
you
know
I
can
use
my
cube
cuddle.
If
I
want-
and
I
could
say,
get
nodes.
B
And
that
worked
because
of
that
coupe
config
that
it
that
it
dumped
out
of
that
and
that's
letting
us
go
ahead
and
and
do
those
things
so
real
quick.
So
if
we
want
to
go
ahead
and
deploy
something
because
it's
great
to
have
a
kubernetes
cluster,
but
not
if
it
doesn't
do
anything,
I'm
gonna
go
ahead
and
create
a
new
terminal
here,
because
that
other
one's
going
up
there.
So
now,
if
we
go
ahead
and
create.
B
There's
a
few
things
that
we
want
to
change
in
here,
because
what
I
want
to
do
is
you
can
see
the
replica
how
many
replicas
do
I
want.
This
is
hard
coded
in
my
code
here,
but
that
might
be
something
that
I
want
to
be
a
little
more
dynamic,
so
we're
going
to
use
polomi's
configuration
system
for
that,
so
we'd
say
let
config
we're
going
to
create
a
new
pollumi
config.
B
A
A
B
And
because
we
have
that
labels
variable
up
there,
we're
just
going
to
go
ahead
and
use
that
and
then
what
we're
doing
here
is
we're
saying
instead
of
replicas
is
one
we're
going
to
say,
config
and
we're
going
to
say
get
it's.
The
thing
we
want
is
a
number
and
the
value
of
the
key
value
pair
is
going
to
be
defined
in
our
config
as
replicas.
B
Yes
now
it
wouldn't
work
right
now,
because
we
haven't
created
that
that
config
yet,
but
we're
in
stainers.
What's
a
container
maddie,
that's
a
that's
a
container
that
that
container
is
what
happens
when
I've
got
like
my
my
lemonade
bottle
and
it
leaks
and
it
gets
all
over
my
pants.
That's
a
container.
A
B
B
B
And
then
the
big
thing
that
we're
going
to
do
here
is
I'm
going
to
take
this
export
and
what
I'm
doing
is
I'm
taking
that
nginx
deployment
and
I'm
exporting
it
to
an
output
in
paloomi,
so
I'll
be
able
to
get
to
it
later.
So
now,
if
I
go
ahead-
and
I
say
lumi
up
on
this-
this
particular
piece
here-
it's
going
to
actually
does
anybody
know
what
what
what?
What
how
many
replicas
is
it
going
to
create.
B
Four,
so
now
that
it's
set
there,
so
if
we
actually
were
to
go
ahead
and
do
paloomi
up
again
well,
let's
do
before
we
do
that,
because
we
should
see
two.
So
if
we
go
ahead
and
if
we
were
to
say
paloomi
if
we
go
to
describe
the
output
the
deployment,
but
it's
based
upon
that
stack
output,
you
see
how
I
did
the
interpolation.
I
was
able
to
say
substitute
in
and
then
we
can
see
the
actual
deployment.
B
B
B
Let
me
I'm
trying
to
think
about
the
fastest
way
to
do
this
without
changing
windows.
I
have
I
have
a
project,
I
did
that
deploys
a
helm
chart.
So
that's
the
short
answer
is
that
there's
a
provider
so
I
can
in
in
my
pollumi
code
I
can
write
a
plumi
program
or
my
plumi
program,
because
it
might
not
only
be
one
program
that
will
deploy
the
helm
chart
and
then
I
can
also
with
that
provider.
A
Cool
yeah,
I
really
like
the
demo.
It
was
really,
even
though
you
know
some
some
hiccups
here
and
there,
but
the
experience
of
writing
programming
language
to
set
up
stuff.
I
can.
I
can
see
how
it
fits
together
in
in
an
application
where
you
know
today.
The
boundaries
are
a
little
bit
blurred
between
what's
the
app
what's
the
infrastructure,
so
that
can
be
pretty
useful
thanks
for
the
demo.
B
Yes,
so
if
you
go
to
palumi.com,
there's
all
the
stuff
to
get
started,
if
you
go
onto
the
doc
site,
which
is
linked
in
all
sorts
of
different
parts
of
the
nav
there's
a
substantial
number
of
tutorials
getting
started.
So
some
of
the
things
that
I
did
today
there's
some
similar
tutorials
and
you
can,
you
know,
bring
your
own
kubernetes.
All
this
stuff
will
work
with,
like
mini
coob,
if
you're
trying
to
just
sort
of
test
things
out,
there's
just
of
course
a
few
things.
B
B
Maybe
we'll
see
we'll
see
so
we
I
do
have
theoretically
a
cloud
native
tv
show
that
should
be
going
live
next
week,
we're
seeing
we
might.
We
might
have
a
little
problem,
but
it's
okay,
but
if
you,
if
you
know
this
about
me,
I
also
run
an
online
game-
show
called
devops
party
games
and
so
we're
gonna
do
something
with
cloud
native
tv
in
a
similar
spirit
of
just
having
some
fun
in
some
games
and
stuff.
So.
B
A
B
And
actually
I'll
give
you
a
little
bit
of
a
shout
out.
There
is
a
very
cool
project
called
tinkerbell
for
bare
metal,
kubernetes
stuff
that
is
built
using
pollumi,
and
I
believe
in
a
couple
hours
right
here
on
cloud
native
tv
cat
cosgrove
show
we'll
be
talking
about
tinkerbell,
which
I
think
is
really
really
cool
so
and
it's
it's
a
couple
of
great
people
on
that
that
episode
too
so
tune
in.
For
that
one.
B
A
Yeah,
so
I
see
that
there
are
a
few
more
questions
came
up.
I
would
ask
those
people
if
you
could
please
write
them
in
the
in
the
slack
channel
that
we
have,
and
I
believe,
we've
posted
that
channel
name
before
now.
It
goes
live
on
the
screen.
Cloud
native
dot
live
under
the
cncf
slack
mati.
Thank
you
very
much.
It
was
a
pleasure.