►
From YouTube: Kubernetes YAML Manifests Made Easy - Open Source Friday
Description
Monokle lets you create, analyze, and deploy YAML manifests with a visual UI, and provides policy validation and cluster management. Join us at 1pm ET to learn how to get started!
A
A
A
A
Vibes
before
we
start
open
source
Friday
to
to
folks
who
are
just
tuning
in
thanks
for
joining
us.
If
this
is
your
first
time
watching,
this
is
called
open
source
Friday,
it's
a
stream
that
we
do
on
githubs
twist
and
github's
Linkedin
and
github's
YouTube
channel,
where
we
talk
to
open
source
maintainers
about
the
projects
that
they've
created.
A
It
helps
us
to
explore
and
discover
other
open
source
projects
that
we
can
get
into
and
if
we're
interested
in
becoming
maintainers
ourselves,
we
may
be
able
to
like
pick
up
some
tips
and
tricks
from
them.
So
I
want
to
start
turning
it
over
to
our
guest.
Introduce
yourself
tell
us
about
you,
we'll
start
with
Olay
and
then
go
down
the
line.
Awesome.
B
B
C
D
A
Nice,
thank
you,
I'm
glad
that
you
all
have
been
so
embedded
into
the
project
as
well.
I
want
to
say
just
highlight
a
couple
of
viewers
because
it
looks
like
we
have
people
from
all
over
the
world.
We
have
folks
from
Louisville
Kentucky,
but
we
also
have
folks
from
turkey
and
Algeria
and
Poland
and
looks
like
someone
said
and
from
Chile
as
well,
and
it
looks
like
someone
said
hello
eager
to
learn
about
this
project
and
somebody
else
I
missed
the
comment.
I
can't
find
it.
A
B
It's
really
really
tricky,
and
although
there
are
like
Ides
out
there
that
have
plugins
and
stuff
like
that
to
help
you,
none
of
those
are
really.
You
know,
got
everything
together
in
one
nice
set
of
two
set.
You
know
integrated
Suite
of
kind
of
things
to
help
help
me,
at
least
at
that
point,
get
those
map
those
configuration
files
right,
and
that
was
the
idea
behind
monocle
right.
B
Wouldn't
it
be
great
if
there
was
one
tool
that
had
all
that
intelligence
around
kubernetes
configurations
and
workflows
and
all
that
stuff
built
in
I,
don't
have
to
Cobble
together
on
my
own
tool
chain.
I
know
some
people
love
to
do
that
and
I
get
impatient
very
quickly.
I
just
want
to
get
stuff
done,
so
that's
kind
of
the
the
background
of
Monaco,
which
we
started.
Oh
well,
the
summer
two
years
ago.
So
it's.
A
B
Not
yet
two
years
old,
but
it
will
be
in
a
couple
of
months
and
can
clean
was
one
of
the
first
devs
on
the
project.
So
he
he
was
kind
of
tasked
with
the
with
taking
a
wild
idea
from
myself
to
act,
something
that
actually
works
and
he's
obviously
done
a
brilliant
job
together
with
radwan
and
others
on
the
team.
A
This
is
awesome.
This
is
awesome
because
I
agree
like
kubernetes
can
be
kind
of
hard
and,
as
someone
in
the
comments
said,
yaml
is
kind
of
complex.
It
can
be
frustrating
and,
like
you
said,
you
know
things
work
for
different
people.
Some
people
do
like
putting
together
that
Suite
of
tools,
but
I
really
like
I,
mean
not
Suite
of
tools
but
different,
like
tools
in
their
tool
chain.
A
B
Think
that's
really
it's
a
great
point.
It's
that's
really
one
of
the
things
that
can
be
hard
to
get
right
if
you're,
using
just
a
regular
IDE,
you
know
and-
and
you
start
working
with
yamo
for
kubernetes,
there's
so
much
that
you'll
be
missing
out
on
that
you
could
get
from
plugins
or
a
tool
like
monocle
right
to
help
you
and
get
all
these
things
right.
So
you
might
be
really
struggling
with
yaml
syntax
or
with
specific
configurations
configurations
for
the
things
you're
trying
to
do,
and
then
you
start
looking.
B
Is
there
a
plug-in
for
this?
For
my
ID
there's
a
plugin,
but
it
doesn't
work
with
that
version
of
kubernetes
that
I'm
using
and
it's
not
compatible
with
this
or
that
and
it's
it's
kind
of
a
an
unnecessary
kind
of
uphill
battle
is
kind
of
what
I
felt
I
felt
like
when,
because
I've
been
doing
this
for
a
while,
I
know,
they're
all
they're,
all
these
things
out
there.
Why
don't?
B
We
just
you
know,
put
them
together,
integrate
them
glue
them
together
and
put
them
in
an
environment
that
can
help
both
people,
who
are
new
to
kubernetes,
really
get
started
quickly
and
hopefully
not
make.
As
many
you
know,
mistakes
as
they
get
started,
but
also
experts
quickly
kind
of
be
productive
right.
B
So,
but
to
your
point,
love
people
who
talk,
who
kind
of
put
together
their
own
tool
chains,
I'm
one
of
those
in
certain
cases
and-
and
you
know
loving-
that
that
diversity
in
in
the
space
so
I'm
not
trying
to
say
everyone
should
be
using
Monaco,
but
there's
definitely
a
case
where
Monica
will
help
and
kind
of
will
get
you
over
some
of
the
hurdles,
specifically
kubernetes,
which
is
still
so
evolving
so
quickly.
It's.
B
A
B
I
think
it
was
at
that
time
where
I
was
kind
of
struggling
with.
You
know,
with
with
a
pretty
complex
setup
of
kubernetes
configurations
and
I
felt
like
oh.
Why
the?
Why
isn't
there
a
tool
that
just
visualizes
these
dependencies?
For
me?
That
shows
me
that
when
I
did
this
for
error
over
here,
that
show.
B
Would
it
kind
of
told
me
that
this
is
not
going
to
work
right
instead
of
me
having
to
deploy
my
stuff
and
then
you
know
finding
out
10
minutes
later
by
digging
through
some
logs
that
it
didn't
work,
and
it
just
felt
like
this
this
there
should
be
an
easier
better
way
of
doing
this
and
I
I
mean
obviously
I
was
a
beginner
at
kubernetes
and
had
I
been
better
at
kubernetes.
Maybe
I
wouldn't
have
had
that
initial
challenge,
but
I
do
think.
B
Although
the
command
is
is
pretty
prevalent,
I
think
most
of
the
people
with
kubernetes
are
still
beginners
and
still
going
through
that
struggle
and
a
lot
of
experts
out
there,
of
course
as
well,
but
but
most
of
us
are
still
early
in
the
in
that
curve
and
then
I've
from
my
personal
experience,
I've
had
the
fortune
of
of
building
open
source
projects
previously
that
worked
out
very
well,
so
I
felt
like
I've
done
it
before.
Let's
do.
B
Know
and
I
I
know
that
I
love
that
early,
you
know,
building
new
projects
for
users,
engaging
with
users
getting
feedback.
You
know
fixing
bugs
getting.
You
know
it's
kind
of
that
whole
Mojo,
that
you
have
around
an
open
source
project
which
is
which
is
so
enrichening,
and
not
just
the
coding
in
itself,
but
just
building
out
that
ecosystem
and
the
community
and
everything
around
an
open
source
project
is,
is
just
that's
why
you
know:
love
open
source,
yeah.
A
And
it
does
seem
like
a
shared
sentiment
among
other
open
source
maintainers
that
I
talked
to
when
they
create
an
open
source
project,
and
then
they
realize
how
helpful
and
like
it
is
for
their
contributors
or
or
users
they're,
like
oh
I,
really
love
this
and
like
I,
think
that
that
part
feels
rewarding
and
they
keep
going.
I
also
have
a
comment
from
my
friend
here
who,
like
to
me:
I,
look
at
him
as
an
expert
and
software
engineering,
but
even
he
says
like
when
he
started
with
the
Manifest
Falls
for
months.
B
Is
really
verbose,
especially
for
kubernetes?
You
know
you
can
have
these
files
can
get
pretty
large
and
it's
easy
just
to
get
lost
right
in
them
and
there's
so
many
options
configuration
options,
and
you
know,
and
when
you
kind
of
start
looking
at
through
with
the
aspect
of
security
and
performance
and
compliance-
and
maybe
you
have
some
so
there's
just
so
much
to
keep
track
of
so
having
some
tools
to
help
you
get.
B
B
You
what
help
ever
helps
you
kind
of
get
the
job
done
is
great,
as
I
said
earlier,
monical
being
a
more
alternative,
very
focused
on
kubernetes,
specific
tasks
and
workflows,
and
that
kind
of
stuff,
but
whatever
rocks
your
boat
right.
Whatever
makes
you
get
the
job
done
by
the
end
of
the
day,
and
you
know,
makes
you
sleep
good
at
night
is
great
right.
A
Like
you
have
tools,
whatever
tool
helps
you
get
to
the
end
goal,
doesn't
matter
yeah,
sure
and
or
whatever
tool
you
prefer
so
I
know
that
sometimes
beginners
watch
this
show
and
I
want
to
make
sure
that,
like
they're
not
lost
and
they're
not
like
what
are
you
all
talking
about?
Do
you
want
to
explain
kubernetes
to
me
like
I'm,
five.
D
B
You
know
whatever,
and
the
challenge
is
that
when
you
have
one
or
two
containers,
that's
not
you
don't
need
any
kind
of
system
to
manage
those
containers
for
you,
but
as
they
as
the
number
of
containers
grow-
and
you
start
you
know
struggling
with.
How
do
we
scale
these
containers?
How
do
we
make
them
secure?
How
do
we
make
sure
that
they
can
talk
to
each
other?
You
need
some
kind
of
infrastructure
to
do
that
and
that's
what
kubernetes
does
kubernetes
is
basically
a
container
not
around
time,
but
a
container
management
system.
B
A
No
I
think
that
was
I.
Think
that
was
a
great
description.
You
said
people
use
containers
to
to
develop.
It
helps
to
containers
help
like
if
you're,
like
switching
environments
or
something
like
that,
help
keep
things
consistent
and
then
you
might
need
a
container
management
system
to
help
make
this
process
smoother.
That
was
perfect.
Okay,
great,
let's
go
into
if
y'all
are
ready.
The
demo
I'm
really
excited
I,
think
it
sounds
like
Kathleen
is
going
first
and
then.
C
Yes,
today
we
want
to
demo
monocle
and
before
I
show
my
screen,
so
we
will
have
two
stories
that
we
want
to
show.
One
will
be
for
new
people
that
maybe
struggle
with
kubernetes
and
they
want
to
quickly
deploy
something
and
I'll
show
how
you
can
do
that
in
just
a
couple
of
minutes
with
monocle
and
then
res
one
will
have
another
demo
where
he
will
show
how
you
can
collaborate
with
your
team,
use,
git,
validate
your
resources
and
see
changes
between
branches,
even
I'm
gonna
share
my
screen
now.
One
second.
C
C
You
can
select
an
existing
folder
start
from
scratch
or
clone
GitHub
repository,
but
today
I
will
use
the
start
from
template
option,
because
I
will
use
a
template
that
will
create
some
resources.
For
for
me,
without
having
to
write
any
yaml,
I'll
have
to
set
a
project-
name,
let's
say
GitHub
demo
and
then
I'll
go
to
the
next
step.
Here.
I
will
see
a
screen
with
a
list
of
templates
that
I
already
have
available
in
Monaco.
C
So
right
now
we
can
see
what
a
monocle
template
is.
It's
basically,
a
visual
form
that
you
can
go
through
and
it
will
require
you
some
fields
to
enter.
Let's
say
the
name:
I
will
use
nginx
as
an
example
for
this
template,
so
I'm
going
to
call
it
nginx,
then
the
image
will
be
nginx
latest
and
I
also
want
to
set
an
environment
variable.
C
Maybe
let's
do
that
with
nginx
port
and
the
value
of
80.,
and
then
service
type
could
be
node
Port,
because
it's
just
a
demo,
Target
Port
is
80
again
and
then
I
can
submit
this
and
in
just
a
couple
of
seconds,
I
have
four
resources
that
were
created
for
me
and
I
can
save
them
to
the
folder
that
was
created
for
this
folder
and
now
after
it's
reloading
for
one
second
I
should
see
the
ID
UI
before
I.
Go
to
the
next
steps.
C
I
just
want
to
briefly
show
explain
the
UI
in
the
left
part,
you
have
a
menu
with
different
tools
that
you
can
use,
but
I'm
not
going
to
go
through
all
of
them,
because
then
it
will
be
on
a
one
hour.
Demo,
probably
right
now,
I
will
focus
on
the
files
only
and
then
in
the
middle.
We
have
a
navigator
as
we
call
it.
It's
basically
a
place
where
you
will
see
all
your
resources
in
the
different
modes.
C
You
are
in,
for
example,
right
now,
I'm
in
local
mode,
so
I
see
the
resources
that
were
created
by
my
template
and
they
are
saved
in
these
files.
We
can
see
a
relationship
with
these
highlights
between
the
resources
and
the
files.
This
is
the
part
that
all
I
was
talking
about
where
you
want
a
tool
that
helps
you
understand
the
relationship
with
between
your
resources,
and
you
can
see
that
with
these
links
here,
you
can
navigate.
So
let's
say:
I
want
to
jump
to
the
config
map.
C
I
can
only
click
on
this
link
and
then
I
jump
to
it,
and
this
functionality
will
also
show
you
if
you
have
a
wrong
link.
For
example,
if
I
modify
this
and
I
don't
have
a
config
Mark
with
that
name,
then
it
will
turn
yellow,
and
this
is
a
warning
but
I
want
to
fix
that
and
another
cool
feature
that
we
added
recently
is
the
graph
view
where
you
can
see
even
more
visually
your
relationship
between
the
different
resources
that
you
have.
C
Finally,
if
you
liked
the
templates
for
creating
the
resources,
you
can
also
use
form
editors
to
continue
editing
without
having
to
touch
yaml.
So
you
can
just
use
Auto
generated
forms,
collapse
and
modify
the
fields
that
you
want
and
all
the
changes
that
you
do
here
will
be
applied
directly
to
the
yaml.
But
now,
let's
continue
with
the
story
that
we
started
with,
so
we
wanted
some
resources.
We
created
them
with
the
template
and
now
we
want
to
deploy
them.
C
But,
let's
say
I'm
still
working
on
this
customization
monocle
has
a
customized
panel
here
and
if
you
are
still
working
on
a
customization
and
you're
making
changes.
Let's
say:
I'm
gonna
delete
these
two
resources
from
the
customization
and
now
I
want
to
see
what
resources
will
be
generated
from
this
one.
I.
Can
click
on
preview?
This
is
a
feature
that
monocle
has
where
you
can
preview.
C
Oh
sorry
about
this,
where
you
can
preview
the
output
of
a
customization
or
a
Helm
chart,
and
you
will
see
in
the
Navigator
the
resources
that
were
created
by
it
and,
for
example,
here
I
only
generated
the
deployment.
So
now,
even
here
in
the
editor
I
can
see
an
error
that
the
config
map
is
missing
and
it's
missing
because
I
just
deleted
it
a
couple
of
seconds
ago.
C
I
will
edit
back
and
the
next
step.
So
after
you
verify
that
it's
working
correctly
with
a
preview
you
can
deploy
it
so
I
can
select.
My
customization
I
can
deploy
it.
I
will
use
the
default,
namespace
I'll
click
on
OK
and
it
should
be
applied
successfully
here
now,
the
next
step,
let's
say
so.
This
is
the
development
part
of
Marvel,
but
we
can
also
help
you
after
this.
After
things
are
in
your
cluster,
you
want
to
inspect
them.
You
want
to
see
if
everything
is
working.
C
Okay,
here
at
the
top,
we
have
a
widget
which
shows
the
Clusters
that
you
have
configured
in
your
Cube
config
and
you
can
choose
to
connect
to
the
cluster.
When
you
connect
to
the
cluster,
you
will
see
this
cluster
dashboard
with
some
overview
information
and
then
on
the
left.
You
have
some
kinds
where
you
can
see
the
resources,
for
example,
I'll,
go
to
the
deployment
and
I
will
see
here
that
I
have
my
nginx
deployment
and
we
can
go
even
to
the
pods.
C
I
can
see
nginx
deployment
if
I
click
on
it
I
get
some
more
information.
I
can
see
the
Manifest
I
can
see
the
logs
and
I
can
even
go
to
the
Shell
and,
let's
say
I
can
curl
for
localhost
and
I
should
be
able
to
see
that
it's
working
or
not
okay,
but
this
is
the
flow
that
I
wanted
to
show.
Basically,
you
go
from
scratch.
You
don't
have
any
resources,
you
generate
some
of
them.
C
A
B
To
confirm
what
you
said
without
you're,
totally
right
Monaco
is
really
to
help
you
for
the
entire
life
cycle
of
your
kubernetes
configurations.
Right
from
that,
you
create
it
like
the
template
that
Kathleen
showed
it
helps
you
then
visualize
and
validate
and
make
sure
everything
lines
up,
and
then
it
helps
you
deploy
to
your
cluster.
If
and
then
it
actually
connects
to
your
cluster
and
helps
you
inspect
what's
running
in
your
cluster
right.
A
D
Thank
you
so,
as
Catalina
mentioned
I'm
going
to
show
you
how
you
can
actually
validate
your
resources
using
monocle
how
you
can
use
kit
related
actions
like
creating
a
new
local
branch,
for
example,
and
pushing
some
commits,
and
also
comparing
between
different
git,
commits
using
Monaco.
So,
first
of
all,
I'm
going
to
use
the
clonogi
triple
option
from
here
and
I'm
going
to
use
some
demo
report
that
we
have.
D
Perfect
so
after
cloning,
the
repo
I
can
see
all
the
resources
and
everything
that
is
found
inside
of
my
project
and
first
of
all,
I
see
that
currently,
my
project
has
no
errors
and
no
warnings,
but
that's
just
because
we
currently
have
deactivated
all
the
validations
for
this
project.
So
just
by
going
to
the
settings
pane
from
here,
I
can
quickly
see
the
validation
tab,
where
you
can
notice
that
we
have
different
options
for
validating
your
resources.
D
Also
going
to
enable
the
copyright
schema
validator
and
just
by
doing
that,
I
can
quickly
notice
that
here,
in
this
validation,
icon
I
see
that
I
have
seven
new
validation
errors
and
by
clicking
on
here,
I
can
see
all
the
new
errors
and
warnings
that
I
have
inside
of
my
project
and
also,
if
I
go
to
the
editor
view.
I
can
see
here
that
four
of
my
resource,
some
of
those,
were
updated
with
the
corresponding
errors
and
warnings.
So,
for
example,
for
this
blue
CMS
deployment.
D
I
can
see
here
by
hovering
over
this
icon
that
I
have
on
warning
and
also
an
error,
and
by
clicking
on
it,
I
can
see
here,
for
example,
if
I
go
and
hover
back
at
the
line.
19
I
have
this
error
because
on
this
image,
I
still
have
the
latest
tag
set
for
it.
So
what
I'm
going
to
do
right
now,
I'm
going
to
fix
this
problems,
because
I
don't
want
to
have
them
inside
of
my
project.
D
So,
if
I
quickly
go
back
to
my
validation,
pane
I'm,
going
to
filter
them
and
show
them
by
resource
and
for
this
resource
I'm
going
to
quickly
change
the
latest
tag
to
be
some
version,
for
example,
2.3.0
and
also
I,
see
here
that
I
have
one
warning
which
is
related
to
the
kubernetes
schema
validator,
that
the
replicas
should
be
on
a
number.
This
was
set
to
a
string,
so
we
should
change
it
and
make
it
as
a
number,
and
we
can
also
see
that
the
errors
disappeared
also
from
our
validation
pane.
D
D
We
can
see
that
we
know
we
no
longer
see
them
in
the
validation
pane
and,
of
course,
what
I
want
to
do
next
is
create
a
new
local
branch,
so
I
can
actually
commit
these
new
changes,
so
the
project
don't
doesn't
contain
the
the
errors
and
the
warnings
anymore.
So
if
I
go
here
on
the
top
on
the
top
of
the
application,
I
can
go
to
creating
a
new
Branch,
for
example,
fixing
errors.
D
So,
for
example,
for
this
deployment
file,
I
can
see
that
I've
changed
the
tag
of
this
image
to
another
version,
I'm
going
to
Stage
the
files
that
were
changed
and
also,
of
course,
I'm
going
to
commit
this
and,
let's
say
fixed
warnings
and
errors
going
to
commit
this,
and
the
committee
so
successfully
I
see
that
I
don't
have
any
more
changes
and
what
I'm
going
to
show
you
next
is
another
cool
feature
that
we
have
inside
monocle.
Is
the
compare
feature
which
basically
allows
you
to
compare
between
different
sets
of
resources?
D
This
feature
is
also
really
useful
when
you're,
comparing
maybe
against
your
cluster,
because,
for
example,
you
might
have
some
problems
in
the
production
or
of
your
cluster,
and
then
you
can
just
can
quickly.
Compare
between
the
git
git
commit
that
you
have
and
against
your
cluster
resources
and
then
see
exactly
what
changes
have
you
made
in
order
to
create
to
create
that
problem
so
yeah
that
that
would
be
my
demo
for
for
monocle.
A
B
Thanks,
there's
some
there's
some
really
awesome
stuff
in
there.
Thank
you.
Let
me
just
jump
in
I'm
get
so
excited
when
I
see
this
just
on
on
the
on
the
comparison
right.
The
possibility,
like
you
said,
like
you,
should
comparing
branches,
but
we
also
have
users
who
really
love
this
for
comparing
clusters
right.
So
you
might
have
a
like.
You
said
you
might
have
a
Dev
and
a
staging
cluster
and
you
want
to
and
it's
working
in
one
cluster,
but
not
in
the
other.
B
You
can
you
can,
can
you
know,
set
one
of
one
side
of
the
compare
to
point
to
one
cluster
and
the
other
side
to
point
to
another
and
just
compare
those
and
you
can
very
easily
see
without
having
to
download
or
you
know,
extract
or
anything
like
that,
so
this
this
kind
of
possibility
to
to
troubleshoot
across
branches
across
qubits
across
clusters.
Whatever
you
know
kind
of
ways
that
might
help
is
super
helpful
in
a
more
deployment
phase
or
in
a
troubleshooting
phase
right.
So
this.
C
B
Show
there's
a
lot
of
features
around
when
you're,
creating
your
your
manifests
and
and
editing
them
and
all
that
stuff,
and
rather
than
showed
all
the
validation
stuff,
we
did
go
into
that
you
can
create
custom
validation.
So
if
you
want
to
create
your
own
rules,
for
you
know
whatever
rules
you
might
have
in
your
teams
or
orgs
or
projects,
all
that's
possible
to
do,
and
so
there's
just
a
wealth
of
possibilities
and
it
it
it's
always.
You
know
we
want
to
cater
to.
We
want
to
make
everyone
happy
like.
B
Which
is
obviously
hard,
but
we're
trying
to
kind
of
find
a
ground
where
we've
at
a
level
where
we
feel
that
we
have
both
features
for
people
who
are
maybe
new
to
kubernetes
and
yaml.
All
these
things,
but
also
really
features
that
are
are
pretty.
You
know
low
level
when
it
comes
to
that
troubleshooting
or
the
the
creating
custom
validators
and
stuff
like
that.
A
A
C
Yeah
I
can
answer
this
one,
so
we
we
can
download
any
schema
for
any
version
of
the
kubernetes.
You
can
select
it
within
the
app
and
then
we
will
validate
based
on
that
schema,
and
we
also
want
to
give
the
user
some
warnings
when
maybe
they
have
a
schema
selected
in
the
tool
and
they
connect
to
a
cluster
that
doesn't
have
the
exact
same
schema.
We
will
notify
them
and
we
also
try
when
we
see
a
change
of
the
schema
in
the
validation
tab.
C
A
Okay,
thank
you
and
then
I
did
see
a
couple
of
questions
of
people
asking
what
project
is
this
or
they
came
in
like
well?
We
have
a
recording.
This
project
is
called
monocle.
It
helps
you
to
I
hope,
I'm
saying
this
right
like
manage
your
your
kubernetes,
manifest
files
or
yaml
manifest
files,
because,
like
there's
all
these
different
tools
that
you
have
to
put
together
to
make
it
easy,
you
can
do
this
All
in
One.
Yes,
there
is
a
recording
like
this
is
being
recorded
right
now.
A
A
C
I
can
answer
this
one
as
well.
Currently
we
have
a
CLI.
This
is
a
tool
that
it's
right
now
separate.
It
has
the
same
functionality
of
validation
that
Monaco
does,
but
we
also
captured
it
in
a
CLI
and
that
one
right
now
supports
custom
validators
as
well.
We
are
planning
to
add
them
to
the
desktop,
but
we
need
to
work
on
some
nice
UI
where
you
can
create
those
policy
validators,
but
until
then
you
can
already
create
some
custom
ones
in
the
CLI
and
those
ones
can
even
be
written.
C
B
A
B
I'm
thinking
kubernetes
in
in
Docker,
so
it's
a
way
of
running
kubernetes
inside
Docker
so
and
that
for
me,
is
a
place
where
you
deploy
your
manifests
right
to
to
run
your
kubernetes
applications.
So
you
would
definitely
you
can
definitely
use
kind
together
with
monocle
right.
So
just
as
as
both
Kathleen
and
rosvan
showed,
you
can
create
and
manage
your
manifest,
and
then
you
can
connect
to
your
kind
cluster
locally
and
deploy
it
to
kind
or
to
any
other
cluster.
B
C
Yeah,
the
short
answer
is
yes,
and
you
can
also
manage
multiple
clusters,
like
we
said
with
the
compare
feature,
if
you
want
to
maybe
sync
the
state
between
two
clusters,
you
can
actually
do
that
directly
in
monocle,
because
you
have
that
view
where,
with
two
columns
you
see
the
resources,
you
see
the
differences,
but
we
also
give
you
rasman
didn't
show
it,
but
we
have
some
actions
to
deploy
directly
from
one
cluster
to
another.
So
we
make
it
really
easy
for
you
to
work
with
the
Clusters.
A
A
C
I
would
say
it's
it's
only
cabernetes.
You
can
definitely
use
other
yamul,
but
then
the
the
UI
has
or
a
lot
of
features
around
the
resources
and
specifically
kubernetes
resources,
and
basically
the
resource
for
us
is
like
a
special
unit
in
the
app
and
we
use
it
everywhere.
In
all
the
panels
with
yaml
only
yaml
files,
then
you
will
lose
a
lot
of
capabilities
and
I'm,
not
sure.
If
maybe
you
can
write
some
typescript
validators
that
could
work
for
your
yaml
files.
B
Think
definitely
for
now
we're
focusing
on
kubernetes
related
configuration
files.
So
it's,
but
you
know
we're
an
open
source
project
and
we
want
to
make
our
users
happy
so
head
over
to
GitHub
open
some
feature
requests
or
you
know,
talk
to
us
on
Discord
and
happy
to
discuss
how
that
you
know
how
working
with
spring
boot,
yaml
files
or
any
other
yaml
files
could
fit
into
the
story
of
kubernetes
managing
kubernetes
applications,
and
it's
definitely
something
we
would
consider.
A
Cool
and
then
the
person
asked
the
question
earlier:
Marcia
she's
clarifying
more.
This
is
again
my
my
limitation
of
kubernetes
but
they're,
saying,
like
apologies
but
they're,
trying
to
figure
out.
If
there's
a
distinction
between
the
cloud
service
provider,
Hardware,
Azure,
AWS
and
other
I
think
they
earlier
were
asking
like
audit
capabilities.
Yeah.
Do
you?
Maybe
you
all
don't
have
that
yet?
Maybe
I.
C
Might
be
wrong,
I
could
I
could
mention
a
feature.
It's
still
work
in
progress,
but
we
plan
to
release
it
in
partnership
with
another
open
source
project
and
it's
related
to
the
hardware
in
a
sense
that
it
will
try
to
calculate
the
cost
of
running
your
kubernetes
in
the
cluster,
and
we
will
have
that
functionality
soon
so
other
than
that,
maybe
just
some
validation
on
the
requests
of
contact
containers
for
CPUs
and
the
RAM,
and
you
can
also
see
how
much
is
used
so
yeah.
A
B
Similar
capability
integrated
CI
to
validity
to
config,
yes,
so
the
monocle
CLI
that
was
mentioned.
It
can
definitely
be
integrated
into
your
CI
CD
workflows
on
GitHub
with
the
GitHub
action.
We
also
have
a
separate
project
where
there's
a
cloud
version
of
Monaco,
but
we're
not
going
to
talk
about
that
here.
That
also
has
a
GitHub
bot,
which
does
all
the
validations
that
you
saw
as
part
of
your
GitHub
workflows.
A
D
I
can
I
can
answer
this
question.
Well,
the
easiest
way
for
contributing
on
monocle
is
to
directly
go
to
our
repo
on
GitHub
and
on
the
issues
list.
We
label
the
most
of
our
issues
for
contributors
with
a
good
first
issue
label.
So
basically,
anyone
who
wants
to
contribute
to
Monaco
can
simply
just
go
to
an
issue
with
that
label
and
just
say:
hey
I
want
to
contribute
and
work
on
this
issue
and
from
there
some
of
our
some
of
the
developers
working
on
Monaco.
A
A
B
I
can
start
there
so
dude.
There's,
there's
plenty
of
challenges
when
you,
when
you're
starting
an
open
source
project,
I,
think
one
of
the
biggest
ones
I
think
for
early
projects
is,
is
just
getting
getting
people
to
notice
you
getting
people
to
use
the
project,
getting
feedback
engaging
with
users.
You
know
there's
so
many
tools
out
there
that
are
fighting
for
the
attention
of
developers
and
engineers
and
Engineers
are
super
busy
doing
all
great
stuff
and
they
especially
with
a
tool
like
this.
They
feel
like.
B
Oh
I,
already
have
an
IDE
I'm
good
with
that,
and
they
don't
maybe
invest
the
time
or
have
the
time
to
kind
of
explore.
If
this
could
be
something
that
you
know
delivers
on
its
promise
of
making
things
easier
for
you
so
it
and
it
is
an
uphill
battle
for
most
open
source
projects,
initially
just
unless
you're
kind
of
associated
with
a
big
company
right,
if
you're,
where
you
have
that
brand
behind
you
or
you,
have
other
open
source
projects
that
you
can
piggyback
off.
So
that's,
really
big.
B
A
big
Challenge
and
out
of
that
I
would
recommend
anyone
to
really
invest
time
into
I
know
if
you
call
it
devrel
or
whatever
you
know,
Advocate
Advocates
blogging
engaging
with
others
on
slack
on
in
other
communities.
Making
noise
about
your
project
is
much
more
important
than
building
the
project
itself
and
not
to
downplay.
You
know
all
the
creative
juices
out
there,
but
if
nobody.
B
Going
to
use
it
in
the
end,
so
it's
a
balance
right
and
it's
it's
this
this
balance
of
how
much
do
you
invest
into
the
project
itself,
coding
versus,
advocating
and
building
the
ecosystem?
And
it's
kind
of
you
know
one
pushes
it's
the
chi
chicken,
the
egg
problem
a
little
bit,
but
it's
definitely
something
that
I
I
think
I've
seen
a
lot
of
projects
to
underestimate
the
value
of
devrel
and
of
advocacy
and
and
the
need
for
that.
So
that's
been.
That
has
been
a
big
challenge.
B
Now,
we've
gotten,
you
know:
we've
come
to
a
place
where
I
think
we're
people
starting
to
recognize
the
name
and
they've
heard
about
it,
and
they
might
give
it
a
try
and
maybe
they
didn't
like
it
first,
but
then
they'll
come
back
six
months
later.
Try
it
again
so,
but
that's
really
one
of
the
big
challenges
then
there's
technical
challenges.
Of
course,
right
as
the
it's,
it's
growing
pains
right.
B
The
project
grows,
people
start
using
it
for
things
that
you
didn't
expect
or
in
for
clusters
that
are
much
larger
than
you
thought
or
then
and
that's
kind
of
where
we
once
again
we're.
So
grateful
for
people
reaching
out
and
telling
us
hey,
it
doesn't
work
with
this.
It
could
be
better
here.
Could
you
add
this
and
and
helping
us
improve
and
so
thankful
for
any
feedback
right
for
the
people,
and
so
that's
kind
of
something
that
another
challenge
we've
had
sorry
I,
just
continued
talking,
Kathleen
restaurant.
D
D
Sure
I
was
just
thinking
right
now
and
one
also
one
challenging
thing
that
we
have
is
keeping
the
our
documentation
up
to
date,
because
we
also
are
trying
to
deliver
new
features,
and
we
need
to
have
those
features
really
well
documented
in
order
for
the
user
to
know
about
them
and
know
exactly
how
to
use
them.
I
think
that's
an
important
thing.
D
C
Yeah
and
I
think
what
I
already
mentioned
it,
but
during
development
I
think
it's
challenging.
You
get
a
lot
of
feedback
which
is
very
valuable,
and
then
you
realize,
maybe
you
didn't
think
exactly
right
in
the
first
try
with
the
feature
and
then
you're
gonna
have
to
completely
change
what
you
worked
on
a
few
months
ago,
but
yeah,
that's
part
of
it
and
it's
always
great
to
get
feedback.
Yeah.
B
That's
really
a
great
Point
Kathleen.
It's
really!
You
know
it's
first,
when
you
you,
we
can
have
all
these
thoughts
and
ideas
about
how
we
think
this
problem
should
be
solved
based
on
our
own.
But
then
it's
first
when
you
talk
to
actual
users
that
you
can
understand
how
it
should
be
solved
right
or
that
we
get
you
get
a
more
holistic
picture
and
being
prepared
to
then
say:
oh
I,
guess
I
was
wrong
or
kind
of,
maybe
that's
not
the
perfect
way
of
doing
it,
but
also
sometimes
holding
your
course
right.
B
It's
kind
of
a
it's
a
middle
ground.
You
know
between
being
catering
to
the
needs
and
the
asks
of
the
users
versus
having
be
a
vision.
Kind
of
this
is
how
you
should
be
doing
it
and
and
then
trying
finding
that
middle
ground.
It
can
be
really
tricky,
but
I
think
the
key
is
is
once
again
talking
to
users
and
and
engaging
and
listening,
and
that
and
then
obviously
having
a
great
team
around
you.
A
I
never
thought
about
that
one
as
a
challenge
like
yeah.
You
could
go
on
a
path
and
you're
like
we're.
Gonna
make
these
features
and
then
the
users
are
like.
We
don't
want
that,
so
that
was
a
that
was
a
good
call
out
and
then
also
on
the
devrel
part.
I
always
try
to
tell
developers
about
that
because,
like
you
can't
I
thought.
A
B
A
B
A
A
B
People
who
come
in
the
number
of
people
I
think
for
us
as
an
early
project.
I
think
Reddit
is
what's
kind
of
maybe
given
us
the
most
immediate
kind
of
feedback.
Even
if
it's
sometimes
pretty.
You
know
you
know
Reddit,
so
it
can.
If
you
you,
never
know
what
you're
gonna
get,
but
it's
it's
at
least
a
way
of
getting
very
quick
interactions.
A
B
It
doesn't
have
to
be
Black,
Ops,
so
I
think
that's
been
good.
Then
meetups
is
great,
actually
meeting
people
in
person,
especially
early
on,
because
because
then
you
have
them
in
front
of
you
right
then,
and
they
you
can.
You
can
hold
on
to
them
a
little
bit
and
and
ask
them
more
about
their.
You
know
what
are
your
challenges
with
yeah
with
manifests
and
yaml
and
Etc,
et
cetera
and
I.
B
Think
the
important
part
I
think
always
when
engaging
with
users
earliest
is
to
listen
and
ask
questions
not
to
say
hey.
Look
at
this
feature,
we've
built
right.
That's
maybe
that's
the
second
part.
The
first
part
is:
what
are
your
problems
with
with
you
know:
yaml
manifests
and
kubernetes.
What
are
your
challenges
Etc
and
then,
once
you've
had
that
discussion,
you
could
say
well
why?
A
So
I
I,
it
sounds
like
you
like
forums
and
then
even
in
person
you
you
want
to
be
where
the
people
are.
So
you
can
hear
what
they're
what
they're
saying
so
that's
been
working
well
for
you,
okay,
cool
and
then
oh.
Actually,
there
was
one
thing
Rosman
mentioned.
Documentation
has
been
hard
and
I.
Think
there's
a
good
call
out
for
people
who
are
watching
and
want
to
contribute,
go
ahead
to
that
repository
and
help
them
keep
their
documentation
up
to
date.
A
A
So
I
guess
sorry
I
got
thrown
off
just
because
this
person,
actually
it
feels
like
it,
feels
like
they're
reading
the
list
that
I
have
like
I
asked
about
like
challenges
to
y'all,
and
then
they
also
said:
what's
the
most
rewarding
part,
that's
actually
the
next
question
I
did
after
y'all.
So
what
has
been
the
most
rewarding
part
of
maintaining
a
project
for
y'all.
D
Well,
since
we
also
talked
about
users
contributing
to
Monaco,
I,
think,
like
a
rewarding
part,
is
having
to
interact
directly
with
the
users
and,
for
example,
a
user
contributing
to
monocle
to
guide
him
and
see
exactly
what's
his
opinion
and
how
how
he
thinks
about
seeing
the
application
and
working
with
him
in
order
to
solve
the
issues
that
maybe
he
has
or
other
people
are
having
so
I,
think.
That's
that's
really
awesome
when
you
are
working
with
an
open
source
project.
D
C
Oh,
we
actually
solved
this
and
we
solve
it
in
an
easy
way,
and
then
it's
really
rewarding
for
me
to
point
that
to
the
user
and
when
I
get
some
feedback
back
from
that
user,
saying
that
it
really
helped
him
that
that's
really
a
great
feeling
so
I
would
recommend
people
working
on
their
own
libraries
or
products
to
just
be
part
of
the
conversations
and
then
indirectly
or
organically.
They
will
find
people
that
struggle
with
the
same
problem
and
they
they
can
point
them
to
their
own
product.
A
Awesome
yeah,
I,
I,
I,
love
that
open
source
maintainers
like
to
help
people
and
they
they
feel
like,
like
a
certain
level
of
like
satisfaction
when
they're.
Like
oh
wait,
my
idea
helped
you
out
like
this
is
something
I
was
struggling
with
for
for
folks
who
want
to
create
their
own
open
source
project
or
build
their
own
Library.
A
A
B
Problem
that
needs
to
be
solved
a
preferably
a
problem
that
you've
had
yourself.
If,
because
you
know
scratching
your
own
itch
is
kind
of
the
best
best
formula,
but
then
don't
try
to
go
too
deep
on
on
features
and
functionality.
Try
to
get
to
something
that
you
think
this
is
good
enough
to
start
showing
to
others
and
getting
feedback
right.
So
obviously
it
has
to
show
some
value,
but
it
doesn't
have
to
be
super
smooth.
It
doesn't
have
to
be
installed,
have
have
installers
for
all
platforms.
B
It
doesn't
have
to
you
know
it
just
have
to
has
to
be
something
that
gets
the
point
across
of
the
problem
you're
trying
to
solve
and
then
go
out
to
communities
like
like
razran
and
Kathleen
set
stack
overflows,
slack,
Reddit,
whatever
and
and
say:
hey
I.
Try
to
find
people
that
you
know
maybe
you've
had
the
same
problem
say:
hey
I've,
created
I've
had
the
same
problem.
Myself
I
created
this
library
or
this
thing.
A
A
Let
people
know
about
it
and
then
they'll
help
they'll
people
will
come
in
and
help
to
build
that
project
up
even
better
whether
they're
users,
whether
they're
people
like
sponsoring
financially
or
whether
they're
contributors
I'm,
going
to
quickly
move
to
the
last
two
technical
questions
and
then
go
into
the
non-technical
questions.
What's
an
open
source
project
that
y'all
admire?
C
Yeah
I
can
start
shortly,
I,
really
like
the
work
of
Tanner
Lindsley.
He
is
developing
libraries
related
to
react
in
the
beginning
and
I
liked
a
react
table
for
a
lot
of
time
because
he
really
adapted
to
the
changes
in
the
reactical
system.
He
started
with
a
version
that
was
using
class
components
just
to
be
a
bit
technical.
C
Then
hooks
came
out
for
react
and
there
was
a
new
wave
of
libraries,
but
he
refactored
the
entire
app
and
was
one
of
the
first
to
use
the
hooks
and
then
now
he's
even
building
an
abstraction
over
that
and
his
library
is
available
for
other
Frameworks,
not
necessarily
react
so
seeing
how
he
evolved
and
pivoted
to
other
areas.
It
was.
It
was
really
inspiring
for
me.
A
B
So
many
and
there's
so
many
that
I
think
are
I'm
just
so
impressed
impressed
by
like
the
team
behind
I'll
call
out
electron,
which
I
know
is
getting
some
bashing
nowadays,
but
I
still
think
it's
an
amazing
effort
trying
to
to
provide
a
a
a
framework
for
building
applications
desktop.
You
know,
like
applications,
I
think
that
that
project
has
also
evolved
immensely
over
the
years
so
kudos
to
them.
It's
one
of
many,
though
there's
so
much
out
there
that's
great
there.
A
Are
you
know
if
someone
asked
me
this
question?
I
would
have
a
hard
time
answering
as
well.
Okay,
really
quickly,
are
there
any
GitHub
products,
I've
seen
that
y'all
use
get
or
are
like
using
like
to
get
the
get
Concepts
to
like
do
diffs
and
stuff
like
that?
But
are
there
any
like
GitHub
products
that
have
empowered
you
as
an
open
source
maintainer?
A
C
Are
using
quite
a
lot
of
tools
from
GitHub,
so
with
GitHub
actions,
we
are
running
our
CI
CD
for
releasing
and
for
testing,
and
we
are
also
using
it
to
automate
deploying
our
documentation.
So
when
someone
does
a
PR
and
it's
much
to
menu
on
the
documentation,
we
deploy
it
to
GitHub
pages,
so
we
also
use
GitHub
pages
to
deploy
it,
and
then
we
use
GitHub
projects
to
do
project
management.
C
Basically,
we
use
the
milestones
and
then
we
we
have
a
project
with
some
nice
views
for
each
version
and
we
like
to
do
it
directly
in
GitHub,
because
we
want
it
to
be
public,
so
people
can
contribute
and
they
can
see
at
all
times
what
we
are
working
on.
They
can
give
feedback
and
it's
been
great.
It
has
all
the
features
that
we
need
and
yeah
also
co-pilot,
I.
Think
there
are
some
people
myself
included,
I
use
it
when
I,
develop
and
I
think
it
saves
a
lot
of
time.
B
C
A
Right
I'm
excited
that
y'all
are
using
so
many
GitHub
tools,
especially
on
GitHub
projects.
I
think
the
team
will
be
super
excited
to
hear
that
okay,
I
I
ended
up
enjoying
this
conversation
so
much
that
I
realized
we're
getting
really
close
to
time.
So
I'm
gonna
ask
y'all
like
speed
answers
or
speed
questions
in
their
non-technical
questions.
A
A
B
A
C
A
B
D
A
D
A
Good
choice,
all
right,
thank
you
all
so
much
I
know:
I
went
overtime.
I
just
really
enjoyed
this
conversation,
so
I
apologize,
but
thank
you
to
the
chat
as
well
for
tuning
in
I
want
to
just
highlight
a
couple
of
links
that
you
should
check
out.
The
first
one
is
monocle.io.
That
is
the
Project's
website
itself.
A
So
if
you
wanted
to
just
like
see
an
overview
and
like
I
guess
see
whatever
other
things
you
can
connect
to
there,
you
can
go
ahead
and
go
to
monocle.io
and
then,
if
you
wanted
to
contribute
to
the
repo-
and
you
want
to
help,
make
it
better,
whether
it's
the
documentation
or
the
actual
code
I
know
some
people
had
some
ideas.
Go
ahead
to
github.com
cubeshop,
slash
monocle.
A
Thank
you
to
the
audience
for
tuning
in
y'all
are
always
really
great
and
very
engaging
or
engaged
with
asking
questions,
and
then
also
thank
you
to
Olay,
Kathleen
and
rosbon.
It
was
lots
of
good
questions.
I
mean
good
answers.
I
I,
loved
y'all
answers
in
general
and
people
seem
to
enjoy.
They
said
it
was
so
fun.
Thank
you.