►
From YouTube: Argo CD and Rollouts Community Meeting Jan 2023
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).
C
D
B
D
All
right
so
we're
a
couple
minutes
past
time,
so
we
can
get
going
so
yeah
welcome
everybody
to
The,
Argosy
and
rollouts
community
meeting
I'll
be
your
host
for
today
my
name
is
Remington,
so
yeah
we
can
go
ahead
and
get
started.
A
quick
reminder
if
everybody
here
could
just
add
their
name
to
the
list
of
attendees
on
the
Google
Document
I
will
go
ahead
and
throw
this
link
in
the
chat.
D
If
you
don't
have
it
already,
there
we
go
and
with
that
I
will
hand
it
off
to
our
first
presenter
for
today.
So
our
only
agenda
topic,
it
looks
like
at
the
moment
is
going
to
be
monocle,
demonstrating
some
improvements
to
the
argosity
yaml
editor,
so
yeah.
Let's
take
it
away.
Thank.
B
You
thanks
I'll,
just
frame
it
a
little
bit
and
then
I'll
hand
it
over
to
veto
to
do
the
actual
demo.
Yeah,
basically
Cube
shop,
we're
an
open
source
company
and
we
have
one
of
our
projects.
Monaco,
which
is
a
tool
for
working
with
kubernetes,
manifests
and
yamos,
and
we
started
engaging
with
the
Argo
team.
B
I
think
at
kubecon
and
figured
out
a
good
way
for
us
to
contribute
to
Argo
would
be
to
inject
some
of
our
yamo
magic
or
love
into
the
yaml
editor
that
you
currently
have
in
argue
interface
and
video's
been
working
hard
on
getting
that
done.
So
we
can
get
that
contributed
in
the
next
release.
So
it's
around
validation,
it's
around
syntax,
highlighting
it's
around
a
bunch
of
things
to
make
it
easier
to.
B
You
know,
work
with
your
yamos
and
get
them
right
if
you're
editing
them
it's
from
inside
Argo,
so
I
think
that's
probably
enough
framing
for
me.
I'll
just
hand
it
over
to
Vito,
obviously
happy
to
answer
any
questions
before
or
after.
E
All
right,
thank
you
for
the
introduction
Ole.
Let
me
try
to
share
my
screen
here,
so
we
can.
You
can
ask
questions
about
the
implementation
after,
but
I
always
like
to
show
first
what
exactly
we
we
tried
to
make,
and
so
we
saw
a
few
places
where
you
have
the
editor,
and
one,
of
course
is
when
you
open
like
a
resource
here,
so
you
can
go
to
the
live
manifest
and,
as
you
see,
some
curly
yellow
lines
have
appeared
and
those
are
for
validation
that
we
run
on
resources.
E
So
we
we
have
like
a
a
whole
area
of
rules
that
are
related
to
security.
That
can
be
be
used
to
to
find
small
mistakes
in
this
case.
I've
enabled
all
of
them,
but
you
can
configure
it
and
you
see
that
some
of
them
are
missing
here.
If
you
go
to
the
security
context,
and
you
see
that
there
is
a
runner's
group
and
run
as
for
non-root,
but
for
example,
the
runners
group
is
missing,
and
that
is
indicated
by
this
rule
here
you
could
also
drop
all
the
capabilities
for
the
rest.
E
Because
of
this,
the
deployment
actually
is
is
quite
well
up
to
date.
There
is
some
small
thing
here,
for
example,
this
should
be
a
string,
so
we
also
do
schema
validation.
E
The
nice
thing
is
that,
once
you
have
the
schema
validation,
it's
when
you
want
to
edit
is
we
can
use
the
the
intelligence
of
that
schema
to
provide
autocomplete
like
you,
you're
used
to
in
any
editor
like
Visual
Studio
code
or
something
it
gives
you
like,
a
sample
value
if
I
would
write
something
wrong
here
again,
you
get
the
curly
line,
that
it
should
be
an
integer,
and
you
can
correct
this
to
make
sure
that
there
are
no
mistakes
while
you're
quickly
trying
to
edit
the
the
resource.
E
But
that's
one:
that's
for
the
the
resources
and
there
there
are
plenty
of
tools
that
can
validate
for
deployments
and
so
on,
but
where
monocle
gets
really
interesting
is
when
you
try
to
work
with
custom
resource
definitions,
and
if
you
go,
for
example,
to
the
app
info,
then
you
also
have
the
Manifest
pane,
where
you
could.
Edit
I
have
to
cheat
a
tiny
bit
here,
because
for
this
to
work,
I
actually
have
to
make
it
a
complete,
compliant
kubernetes
resource.
E
So
if
I
would
edit
this
and
quickly
add
in
metadata,
so
that
would
look
like
this.
Then
we
can,
from
this
information,
extract
the
schema
again
and
we
get
the
same
benefits
so
here
we
can
now
start
working
and
play
with
automated
I.
Don't
know
these
things
quite
well,
because
I
I
don't
work
with
the
obviously
the
resources
so
often,
but
I
can
hear,
try
to
to
really
get
things
done.
E
We
we
talked
a
bit
about
security
validation
on
top
of
this,
but
what
is
also
very
nice
about
monocol
is
that
you
can
write,
are
Community,
plugins
or
plugins
that
anyone
can
use,
and
they
are
interesting
for
a
project
like
ago.
We
went
quickly
through
your
docs
and
we
saw
that
if
you
write
a
destination,
you're
not
allowed
to
combine
using
both
the
property
of
server
and
name.
E
So,
as
you
see
here,
otherwise,
applications
destinations
are
mutually
exclusive,
so
you're
not
allowed
to
do
this
if
I
would
again
remove
the
server
this
works
well
again,
and
vice
versa.
So
it's
quite
easy
for
if
you
have
this
custom
resource
definitions
at
your
validation,
we
could
show
the
code
in
a
bit,
but
this
was
like
10
lines
of
code
to
do
in
our
framework
to
add
this
kind
of
validation
rules
and
that's
the
the
main
visit
of
the
improvements
to
the
editor.
B
Here,
let
me
I
can
just
add
a
couple
things,
so
the
the
the
the
policy
related
rules
are
the
same
as
in
trivi,
which
you
might
be
familiar
with,
so
we're
using
the
they've
open
sourced
their
whole
rule.
Library,
obviously
tribute
itself
is
open
source,
so
we're
kind
of
using
that.
So
it's
these
aren't
rules.
We've
come
up
with
ourselves,
so
they're,
you
know
well
well
trusted
Etc.
B
We
could
obviously
have
these
kind
of
validations
and
rules
also
for
other
rollouts
crds
for
any
crds
that
you
would
like
to
you
know,
support
more
or
less
natively
and
I
think.
Lastly,
we
talked
about
this.
Also
previously
we're
looking
to
you
to
maybe
help
us
and
implement
the
rules
that
you
think
would
be.
B
You
know
relevant
for
you,
users,
you
guys,
obviously
know
Argo
much
better
than
we
do
and
just
like
Vito
said
we,
you
know,
went
through
the
documentation
and
and
kind
of
extrapolated
some
basic
rules
from
there,
but
maybe,
if
you
feel
like,
if
you
see
kind
of
a
common
mistake,
that
users
of
Argo
are
making
or
something
that
they
come
often
get
wrong,
or
you
know
policies
that
they
should
be
doing
things
in
a
certain
way.
Let
us
know
and
we're
happy
to
add,
add
corresponding
rules
to
the
editors.
B
It's
as
video
said,
it's
really
easy
and
they're
open
source.
Anyone
could
kind
of
go
in
and
modify
them
and
improve
them
if
they
wanted
to
so
that's
kind
of
an
Ask
path.
Back
back
to
you,
guys
to
make
this
you
know,
is
really
as
rich
and
Powerful
as
possible.
For
your
end,
users
will
provide
all
the
plumbing
under
the
hood.
C
E
This
one,
this
will
Now
fail
because
it's
under
the
hood
it
takes
the
it
expects
it
to
be
a
spec,
so
this
will
fail,
but
because
it's
not
the
correct
aspect
but
I
think
if
I
would
do
it
like
this
and
remove
this
again.
I
would
expect
this
to
work.
A
My
my
point
is:
the
lines
of
everything
is
pulled
from
git
right.
So
in
this
case,
if
I,
if
I
change,
if
a
if
the
Manifest
in
the
in
my
git
Repository,
you
know
still
have
whatever
wrong
spec
that
I
have
there
and
if
I
edit
in
Argo
City
directly
and
save
here,.
D
I
think
he's
asking
a
little
bit
more
of
an
Argosy
question
so
that
editor,
basically
it
edits
the
live
state
of
your
cluster
rather
than
the
state
and
git.
So
it
will
save
to
your
cluster,
but
it
will
not
go
and
commit
not
to
get
that
answer.
Your
question.
D
A
Now
this
I
mean
I
I
liked
it,
but
my
point
is:
will
it
not
be
against
our
rule
that
you
know
everything
goes
from
the
git
right,
so
everything
is
audited
from
git.
Every
change
that
goes
into
the
cluster
is
done
in
the
git
repository
and
it
is
audited
in
the
git
repository.
So
if
we
say
in
that
now
we
are
bypassing
it
and
doing
the
changes
directly
in
Argo
CD
right.
D
So
this
is
more
of
a
convenience,
for
you
know
quickly:
debugging
resources
or
adding
an
annotation,
for
example.
So
you're
you're,
absolutely
right
that
if
you
do
go
into
Argos,
dsui
and
edit
a
manifest
directly
you're,
bypassing
all
of
the
benefits
that
you
get
with
Git
Ops.
D
But
this
is
a
feature
that
exists
in
Argo
CD
today
to
be
able
to
edit.
These
manifests
and
the
guys
at
Monaco
are
basically
adding
more
validation
on
top
of
it
to
avoid.
If
you
are
going
to
go
in
and
debug
a
manifest
by
editing
it
directly
through
the
Argos
DUI.
D
The
enhancements
that
the
guys
at
Monaco
have
added
now
are
adding
another
layer
of
protection.
On
top
of
that,
so
you
can
validate
that
your
your
schemas
are
correct
before
you
actually
go
and
push
them
to
the
cluster.
But
you
are
right.
This
that's
a
risk
that
you
have
to
take
when
you're
editing
manifest
directly.
In
obviously,.
A
Okay,
so
my
follow-up
question:
if
no
one
has
questions
so
is
there
a
way
to
you
know,
release
this
feature
or
to
take
away
this
feature
from
the
from
the
end
users
say,
for
example,
if
I'm
implementing
Argo
CD
Now
in
my
R
back,
is
there
a
way
for
me
to
suppress
this
feature
from
releasing
it
to
my
production
environments,.
E
Yeah,
so
with
about
how
the
implementation
works,
the
nice
thing
about
it
is
that
the
the
way
that
Monaco
works,
so
we
use
the
Monaco
editor,
which
is
what
Visual
Studio
code
uses
under
the
hoods,
and
so
actually
all
these
changes
that
I
showed
you
it's
just
like
five
lines
of
codes.
The
only
thing
that
I
did
was
install
this
yeah.
This
has
a
bit
of
indentation
that
changed,
but
all
I
did
was
install
or
dependency,
which
is
Monaco.
Kubernetes
should
be
in
here
somewhere
in
the
dependencies.
E
So
this
one
I
added
and
we
made
a
small
tweak
to
the
webpack
configuration,
and
so
it
would
be
I
I
think
possible
to
to
tweak
this
out
or
to
be
able
to
change
this
worker.
So
it's
not
that
we've
been
adding
or
adding
a
lot
of
bloat
to
the
arbor
CDA
projects.
We
thought
it
was
important
that,
indeed,
should
you
not
want
this,
that
you
could
change
it
around
a
bit
or
not?
Yes,
only
I
see
you
raised
your
hand.
B
Yeah
I'm
guessing
three
that
you
want
to
maybe
disable
the
editing
altogether,
not
just
specifically
the
features
that
we
showed
here
so.
B
Of
the
editor
okay
question
for
Remington,
I
guess.
A
And
one
follow-up
question
and
I'll
leave
the
the
flow
to
others
so
easily
argosity
notification
that
I
can
get
or
is.
Is
this
event?
Is
it
something
that
I
can
get
in
to
my
notifications
so
that
I
can
understand
if
there
are
it's
happening
in
the
system?
D
Not
as
it
stands
today
unless
Michael
erleo,
if
you
guys
correct
me
if
I'm
wrong,
but
as
far
as
I'm
aware,
no
that
that
doesn't
exist
at
the
moment,.
F
F
The
thing
is:
there's
no
feature
to
disable
the
button,
so
users
will
still
see
the
button,
but
as
soon
as
they
click
save
this,
this
won't
be
allowed
to
be
done
in
the
cluster.
So
that's
how
we
currently
is
implemented.
G
F
A
F
A
few
words
from
my
from
my
side
glad
to
see
you
guys
around
hiole
happy
to
see
yeah
yeah
excited
to
see
this
feature
in
Argo
CD.
My
question
is
mainly
basically
how
it
works.
I
just
want
I'm
just
curious
to
understand
how
it
works
for
managing
crds
right,
because
this
is
not
provided
by
by.
G
F
E
That's
a
good
question,
so
I
think
it's
a
custom,
research
definitions,
there's
two
aspects
to
it:
it's
like
the
the
validation
and
it
is
the
the
schemas
since
your
question
is
more
oriented
towards
the
schemas
I
can
answer
that
first.
So
at
this
point
in
time,
it's
indeed
correct
that
you,
you
need
to
to
get
the
the
schema
itself
right
so
for
this
demo,
I
made
it
available
for
Auto
City
exactly
for
this
crd,
but
it
becomes
more
interesting
once
you
want
other
crds
as
well.
E
E
Also
working
with
is
that
you
have
like
plugins.monicle.com
I,
don't
know
the
exact
Parts,
but
here
we're
working
on
like
collecting
a
database
of
schemas.
We
we
know
already
like
gather
them
for
the
standard
ones.
I
think
this
might
work
if
I
don't
like
no
okay,
I.
Guess
it's
wrong,
but
it's
it's
something
like
this.
F
So
and
then
the
editor
okay
and
then
the
editor
will
come
and
access
this
URL
and.
E
Yes,
exactly
so
the
way
that
that
works
is
quite
similar.
Again
we
took
inspiration
from
how
red
hat
does
it
with
the
visual
studio
code
extension,
which
is
slightly
different
than
Monaco,
but
we
took
inspiration
from
that
and
the
way
that
it
works
is
that
you
have
the
language
server
of
yamul
running
within
the
web
worker
and
that
web
worker
can
then
request
a
schema.
E
Now,
if
you
have
like
a
normal,
more
yaml
based
tools
that
are
unaware
of
kubernetes,
then
you
can
just
fetch
the
resource,
but
what
we
were
able
to
do
then,
is
actually
we
have
our
resource
parser,
we
inspect
the
content
and
we
can
determine
which
kind
and
API
version
it
is
from
that
identifier.
Try
to
get
it,
and
and
for
for,
like
all
the
Argos
CD
custom
resource
definitions,
we're
going
to
add
them,
then,
to
that
CDN
that
I
just
showed
before
we
might
find
other
ways
to
do
that.
E
Make
it
configurable
I
think
that
configurability
use
case
is
not
so
interesting
for
Argos
CD.
It
might
be,
but
at
least
then
you
have
the
option
to
configure
it.
And,
of
course,
you
have
the
fallback
of
our
own
CDN
that
will
hopefully
grow
over
time.
F
E
So
it
is
it's
actually.
If
you
go
to
the
sources,
then
so.
B
We're
using
we're
using
the
same
editor
component
as
vs
code
Monaco,
not
confused
with
monocle
and
a
Monaco,
has
a
concept
of
language
servers
which
it
uses
to
process
different
languages,
and
so
basically,
we've
created
our
own
language
server,
which
is
a
you
know,
Monaco
concept.
These
are
not
servers,
as
you
know,
grpc
or
remote
servers
there.
It's
more
of
an
abstraction
to
language
processing
and
the
communication
protocol
is
I,
don't
know
I'm
hoping
we
took
an
answer
that
so
just
to
the
the
term.
A
F
E
Yes,
but
I
I
think
it's
important
to
highlight
there
that
it's
in
a
web
worker,
so
it
will
not
impact
the
performance
of
rocd.
You
will
notice
that
this
is
ongoing.
All
the
the
processing
is
done
elsewhere,
so
you
you
get
the
best
of
both
worlds.
Actually,
because
you
don't
have
the
hassle
of
having
a
separate
server,
but
you
do
have
to
benefit
that
it
does
not
impact
the
performance
and
keeps
your
your
main
render
threats
like
free
for
Auto,
City,
stuff
itself,.
C
G
Does
monocle
surface
field
descriptions
or
just
field
names
when
you
get
like
the
little
autocomplete
pop-up.
G
So
our
Argos
CD
application
types
have
like
golang
comments
above
each
field
and
it
describes
what
the
field
is
and
does
we
strip
out
all
of
that
information
when
we
generate
the
crd,
because
the
crd
is
massive
and
we're
trying
to
make
it
smaller,
but
Argo
workflows
has
two
versions
of
their
crds
one
that
is
just
dedicated
to
like
IDE
support.
So
it
retains
all
the
descriptions
if
monocle
surfaces,
those
descriptions,
I
think
we'd
want
to
follow,
Argo,
workflows
pattern
and
create
two
crds.
B
I
think
the
descriptions
is,
what
are
what
you
see
in
the
pop-up,
this
descriptions
pulled
from
the
schemas
for
each
property,
so
if
you
could
keep
them
in
there,
that
would
kind
of
provide
extra
help
for,
for
you
for
people
editing
or
working
so
yeah
cool.
F
But
basically
you're,
saying
Michael
that
the
one
we
publish
are
having
this
descriptions
stripped
out
from
the
crd
is
that
right
definitely.
G
For
application
set
and
I
think
maybe
for
application,
and
we've
had
like
folks
kind
of
want
those
for
Ides
already
for
like
visual
studio
and
IntelliJ
products,
and
it
just
we
haven't,
had
a
use
case.
That
was
compelling
enough
to
justify
the
time
to
re-add
those
descriptions
and
do
what
Argo
workflows
has
done.
But
if
we
have
something
built
into
Argo
CD
that
could
take
advantage
of
those
fields,
I
think
it
would
be
worth
it
cool.
D
C
B
E
Almost
I'm
working
today,
the
only
thing
I
have
to
tidy
up
is
that
the
the
resource
schema
downloading
so
I
did
it
like
a
bit
hacky
I
would
say
where
some
schemas
are
still
embedded
in
the
library.
Of
course,
we
want
to
download
that
from
our
own
CDM
so
that
your
bundle
doesn't
blow
up,
but
I
mean
no
big.
Show
Stoppers
should
be
there
anymore.
The
the
concept
is
proofed,
basically
cool.
F
C
G
Something
that
just
occurred
to
me,
what,
if
I,
have
like
Opa
policies,
am
I
gonna
have
to
duplicate
those
rules
in
order
to
see
those
like
little
yellow
lines
in
the
desired
manifest
page
or
can
monocle
somehow
take
advantage
of
the
OPA
rules.
G
So
I
I'm
not
I'll,
be
honest.
I'm
not
super
familiar
with
Opa
I've
never
set
it
up,
but
I
know
that
there
are
rules
that,
like
prevent
you
from
doing
certain
things.
B
I
think
you'd
probably
have
to
wrap
those
in
a
plug-in,
a
validation,
plugin
and
then
add
them
to
our
public
Community
repo
happy
to
help
you
with
that.
So
if
you
have
rules
that
you
would
like,
as
I
said
a
while
back,
if
you
guys
know
about
rules
either
Rigo
or
Opa
or
you
know,
whatever
format.
Well,
maybe
not
whatever,
but
you
know,
Common
formats
will
definitely
try
to
help
and
make
sure
you
know,
because
we
they
are
used
and
honored
by
this
editor.
E
Cool,
so
the
the
thing
there
I
understand.
The
question
now
is
that
the
legal
policies
that
we
have
ourselves
are
compiled
to
webassembly
and
we
we
use
them
for
our
own
validation,
but
we
do
not
yet
have
the
ability
to
at
your
your
own
policies
that
are
compiled
webassembly
the
custom
validation
that
I
showed
you
before
it's
with
a
framework
built
with
typescript
that
has
the
ability
to
generate
code
from
our
custom
resource
definitions.
E
So
if
you
have
August
today
custom
resource
definitions,
then
we
generate
like
type
guards
and
the
whole
schema
so
that
you
can
use
it
there,
which
provides
quite
a
good
developer
experience.
E
And,
of
course
we
we
in
the
long
term
want
to
add
other
strategies
where
you
could
also
work
with
Trejo.
But
for
now
these
are
with
typescript
I.
Would
I
can
send
you
a
link
to
the
repository
where
we
Define
the
plugin,
so
you
can
check
it
out.
It's.
G
E
B
B
Artists,
sorry
go.
G
Ahead,
I
think
there
would
be
a
lot
of
those
rules
that
the
Argo
CD
team
would
write.
That
would
be
common
for
all
users
and
then
folks,
who
have
like
some
Opa
rule
that
maybe
they
want
to
show
in
the
UI
date
app
to
find
the
proper
way
to
make
that
happen.
G
C
B
It
it's
on
GitHub,
you
could
just
show
the
rule
there.
I
guess
yeah.
B
C
E
For
example,
say
it's
still,
that's
a
bit.
It's
still
read
only
right.
I
have
to
toggle
the
feature
flag
as
well.
B
Yeah,
just
posted
the
link
to
the
blank
GitHub.
E
Yeah
and
then
had
I
known
I
could
have
prepared
this
a
bit
better.
One
second.
E
There's
yeah:
it
will
be
a
bit
too
much
work
to
set
up
now
in
three
minutes,
but
what
you
can
do
is
we
have
a
development
server.
I
can
maybe
describe
it
a
bit
in
words
quickly,
so
we
have
a
development
server
and
if
you
want
to
develop
these
plugins,
what
you
actually
just
do
is
open
a
resource
like
that
in
monocle
itself,
and
then
you
can
open
a
developer
mode
and
what
this
developer
mode
does
is.
E
Actually,
whenever
you
type
well
you're
making
the
plugin,
it
will
bundle
it
as
just
with
es
builds
and
it
will
send
it
over
the
wire
with
an
event
stream
to
or
application.
And
since
we
work
with
the
latest
version
of
JavaScript,
we
can
dynamically
load
your
code
in
our
application.
E
So
you
can
in
real
time
see
the
validation
rules
that
you're
writing
I
have
a
demo
video
about
it,
though,
that
we
can
share,
maybe
only,
but,
if
you're
interested
in
writing
a
plugin,
it's
actually
extremely
easy
because
you
can
just
play
around
as
you're
typing.
You
see
the
line
appear
in
the
editor
of
monocle
itself,
and
then
you
know
that
you're
right
or
wrong
because,
like
if
you're
not
so
familiar
with
the
crds,
it's
easy
to
make
a
type
or
something.
But
you
immediately
catch
it.
That
way.
B
Yeah
I
suggest,
if
you
wanna,
happy
to
maybe
have
a
breakout
session
if
you're
interested
in
just
how
to
create
plugins.
But
if
you
look
at
the
GitHub
repo
that
I
shared
there's,
there
are
the
Argo
rules
and
then
you
can
use
the
tooling
that
we're
just
describing
to
to
make
it
really
smooth.
G
Okay
yeah:
my
main
concern
is
where
the
code
will
live,
because
I
think
we'll
definitely
want
to
write
plugins
additional
rules.
Then
we
just
need
to
put
that
somewhere
and
make
sure
folks
can
contribute
rules,
but.
B
E
You
see
my
screeners,
so
we
have
here.
This
is
just
the
only
thing
is
that
they
are
at
this
point
public
because,
like
I
said
they're
running
your
browser,
we
have
a
sales
application,
so
we
also
want
to
make
sure
that
it's
secure.
We
are
working
for
private
plugins
as
well,
for
people
who
are
authenticated,
but
for
now
they're,
just
like
more
Community
Based.
And
if
you
see
here
this
is
the
Argo
plugin.
E
If
you
go
to
the
source
codes,
then
we
can,
for
example,
see
the
the
rule
that
you
asked
about
at
destination.
So
it
looks
like
this
to
implement
it.
You
have
develop
dates.
What
you
do
is
you
have
a
resource.
You
filter
out
all
the
known
applications.
You
can
see
here
that
this
is
generated
from
the
custom
resource
definition.
So
it's
not
that
you
have
to
Define
anything
manually
here.
You
just
drag
and
drop
the
custom
resource
definition
in
the
directory.
E
I
think
I
have
it
here
in
crds,
so
there
I
put
this
one
in
the
moment
that
you
then
run
coach
and
then
that
becomes
available,
and
after
that,
all
we
do
is
just
check
whether
it
has
a
name.
It
has
a
server
if
it
has
like
either
of
the
other,
then
it's
not
valid,
and
otherwise
you
just
give
the
pods.
If
you
use
this
spot,
then
that
is
sufficient
for
us
to
know
where
it
is.
E
It
also
works
for
arrays,
so
you
can
just
put
like
a
number
in
here
and
we
will
probably
properly
extract
the
the
region
of
where
it
goes
wrong
and
to
demonstrate
that
in
the
thing
I
actually
have
the
plugin
here
open
as
well.
If
you
run
npm
run
Dev
start
this
desk
server
that
we
created
it's
still
in
beta
because
we're
working
out
the
kingsplit
kind
of
works
already.
If
you
then
go
to
our
application,
so
this
is
just
app.monaco.com.
I
have
a
resource
here.
E
E
Here,
for
example,
I
just
put
this
on
the
kinds,
then
you
will
see
that
this
in
real
time
jumps
away
to
there,
because
the
the
code
is
immediately
loaded
over
the
wire
all
right.
So
that's
a
bit
the
concert
where
you
can
very
easily
like
like
experiment
with
what
works
for
your
resource.
You
have
one
that
was
a
had
a
problem
in
it.
The
workflow
is
done
a
bit
that
you
take
that
faulty
resource
you
put
it
in
monocle,
you
write
a
rule
and
it
never
happens
again
after
that.
G
E
For
example,
this
is
now
a
development
plugin,
but
you
can
also
install
them.
I
can,
for
example,
take
the
NSA
rule
sets
open
the
network
tab.
So
what
you
will
see
now
here
is
that
these
are
built
in
from
the
CDN.
If
you
go
here,
then
you
see
that
this
is
that
hosted
on
plugins.monaco.com
validation
and
is
the
latest.
E
So
if
we
merge
a
pull
requests
to
Main
in
that
Community
repository
a
pipeline
runs
that
actually
makes
the
build,
and
it
puts
it
then
on
our
CDN
I
think
that
Oli
also
made
now
a
contribution
to
to
be
able
to
put
them.
The
plugins
then
that
you
built
I,
mean
I,
could
also
perfectly
just
go
here
and
run
npm
run,
builds
that
build
output.
You
could
also
perfectly
put
that
in
a
directory
of
the
the
kubernetes
resources
that
you
want
to
validate
and
then
we'll
read
it
from
there.
E
E
Yeah,
it's
actually
for
I,
I
think
for
the
first
version,
because
we
also
to
to
not
spend
we
might
just
embed
the
rcd
plugin.
That's
also
perfectly
possible.
If
you
make
a
separate,
builds,
that's
actually
what
I
did
now
so
that
just
shows
to
the
flexibility.
If
I
go
here
back
to
this,
then
the
plugin
that
you
actually
saw
in
the
demo
I
have
a
tier
as
a
separate
plugin.
You
can
just
this.
Plugin
can
just
be
be
loaded
in
the
validation
service.
E
So
here
you
see
if
the
the
the
configuration
has
argue
parameter,
then
this
is
the
the
custom
validator
that
we
have
you
give
it
that
object,
because
that's
all
it
is
in
the
end,
what
we
bundle
is
just
an
object
and
that
object
is
then
used
for
validation.
D
All
right
any
last
questions.
D
Okay,
well,
thank
you
guys
very
much.
That's
super
exciting
I'm.
Very
thank
you
excited
to
see
that
PR,
but
yeah.
Thank
you
guys
for
your
time
and
for
the
demonstration.
We
really
appreciate
it
and
yep,
of
course,
with
that.
If
there
are
no
last
minute
agenda
topics,
any
anybody
want
to
bring
one
up
all
right
with
that
I
think
we
can
go
ahead
and
conclude
this
month's
meeting.
Thank
you,
everybody
for
attending,
and
we
will
see
you
next
month.