►
From YouTube: Argo CD review
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
That
really
are
silly,
but
before
we
go
there,
let's
switch
to
here
so
I
have
two
local
clusters:
one
running
in
local
desktop,
it's
kind
of
staging
or
back
office
cluster
and
the
other
being
k3s
cluster.
That
I
present
here
is
a
production
cluster
in
the
production
cluster
I
don't
want
to
install
anything
except
my
production
code.
A
As
a
result,
I
will
install
go
CD
on
the
staging
plaster
and
we
deploy
first,
my
amazing
hello,
good
app
to
staging
and
then
deploy
the
same
app
and
that's.
It
promotes
the
same
app
to
production
so
before
I
get
to
this
workflow.
What
did
I
do
to
set
all
of
this
up?
I
basic
just
followed
the
documentation
for
OCD.
It
was
super
simple.
It
was
really
really
pleasant.
Experience
that
everything
just
works,
the
whole
product,
I'll
go
CD
I
mean
I,
think
it's
a
great
one,
clearly
its
tenth
the
size
of
the
lab.
A
So
it's
it's
much
much
smaller
product
and
database,
but
what
it
does
it
does
really
well
and
I
would
like
to
learn
from
them
and
even
borrow
some
ideas
on
our
way
to
creating
a
great
tremendous
experience,
lead
lap,
so
I'm
running
two
clusters
here
locally
and
let's
get
started
for
Agostini.
Let's
see
the
UI
first,
because
it's
pretty
sad
descriptive,
you
can
see.
I
have
two
applications.
Applications
are
what
what
is
the
core?
The
main
resource
type
resource
object
in
our
Vasily.
A
It
is
actually
deployment
that
you
that
you
have
defined
to
a
specific
cluster.
As
you
can
see
here,
I've,
hello
and
hello,
prod
I,
will
speak
about
the
project
at
the
end.
So
let's
see
the
other
parts
here
healthy,
and
so
the
status
is
pretty
clear.
I
think
both
applications
deploy
from
the
same
repository,
one
uses
development
branch-
that
is
the
master
branch.
They
use
deployment
paths
inside
the
repository
and
the
first
deploys
to
my
local
desktop,
while
the
other
deploys
to
K
3
s
in
the
before
namespace.
A
A
A
One
deployment
and
deployment
has
two
pods
when
I
get
into
it
and
say
that
currently
we
are
running
this
image,
which
is
v1
actually
going
to
change
this
to
be
to
later
on
during
the
this
demo,
and
you
can
get
logs
and
evens
and
whatever
black
locks
don't
work
for
me.
So
for
some
reason
it
might
not
have
Knox.
A
So
this
is
how
it
looks
like
and
you
can
configure
everything
through
DUI
or
through
a
CLI
or
through
humanity's
manifests,
and
as
we
want
to
be
configure
everything
forget
lab
I.
Think
the
last
one
is
the
one
that
we
want
to
do
so
I
am
going
to
show
you
my
t,
yeah,
let's
start
with
the
production
yeah.
No,
so
this
is
my
production.
Yeah
Mel,
as
you
can
see,
just
described
the
same
same
things
that
I
spoke
about
before,
plus
they
sync
policy,
which
is
very
simple
here.
A
I
could
do
the
same
on
the
UI
and
everything
can
be
set
up
there
as
well
and
so
on.
So
that's
what
all
good
series,
basically
I,
didn't
set
up
any
kind
of
books
and
I
think
so.
Obviously,
basically
I
guess
pause
good
lab
for
code
changes
and,
let's
see
how
an
amazing
version
change
looks
like
in
August,
CD
I
already
created
these
images
before
so
I'm
just
going
to
to
deploy.
A
A
A
Yeah,
okay:
we
missed
this
again
because
of
the
port
forwarding
everything
that's
sing
already
2v2.
As
you
can
see.
The
last
commit
message
here
and
the
image
is
already
be
to
image.
Sorry
for
that.
We
will
be
able
to
see
how
the
equipment
works
for
the
production
version,
though,
because
there
we
will
need
manual
syncing.
A
A
A
It
looks
for
it
will
use
one
in
commands
manifest
and
if
it
finds
a
customization
yellow,
it
will
use
that
if
it's
find
value
similar
it
we
use
how
and
so
on
and
I
think
this
is
just
great,
and
if
we
want
to
really
be
production
ready,
then
I
would
strongly
argue
for
having
August
City
behind
us.
Actually.
So
thank
you
very
much
for
your
attention.
That
was
my
review
of.