►
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
Hello
and
welcome
everybody
welcome
to
cloud
native
live
where
we
dive
into
the
code
behind
cloud
native,
I'm
taylor
dolezal,
head
of
ecosystem
at
the
cncf,
where
I
work
closely
with
teams
as
they
navigate
their
cloud
native
journeys.
Every
week
we
bring
a
new
set
of
presenters
to
show
how
to
work
with
cloud
native
technologies.
A
In
today's
session
we
have
several
folks
from
the
argo
community
howdy
everybody
they
will
be
covering
argo's
vibrant
ecosystem
and
some
community
in
maintainer
q
and
a
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
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
excellent
to
one
another
and
respectful
of
all
fellow
participants
and
presenters
with
that.
I
would
love
to
hand
it
over
to
the
team
to
kick
off
today's
presentation.
B
All
right,
thank
you
yeah,
so
just
maybe
we
could
do
a
brief
introduction
and
go
around
and
if
you
want
to
put
up,
I've
got
the
slides,
so
you
can
see
who
we
are,
but
my
name
is
dan
garfield,
I'm
a
co-founder
and
chief
open
source
officer
at
code
fresh
and
very
proudly
an
argo
maintainer,
though
a
very
minor
one.
If
that
the
real,
the
really
got
to
talk
to
is
honk
because
you've
been
around
since
the
beginning.
C
Thank
you
dan.
Thank
you,
then.
So
my
name
is
hong
wong,
so
I'm
the
co-founder
and
ceo
at
acuity,
so
I
and
with
other
teammates,
we
started
the
argo
project
about
six
seven
years
ago
and
such
an
amazing
journey
and
really
happy
to
be
here
and
happy
to
share.
What's
our
current
progress,
thank
you
and
hand
over
to
julie.
D
Hi,
I'm
julie,
I'm
a
staff
software
engineer
at
intuit
and
I
am
working
on
argo,
workflows
and
argo
events.
I
am
you
know
the
least
senior
argo
person
here,
but
I
will
do
my
best
and
I've
got
some
support
from
my
colleague
here.
D
B
Thanks
brother,
well,
you
do
you
do
a
lot
of
the
heavy
lifting
on
the
project.
That's
for
sure.
So,
just
you
know
for
we're.
Gonna
do
some
we're
gonna
talk
about
some
project
updates
that
are
going
on
today.
We're
gonna
do
some
demos
today,
but
you
know
this
being
the
cncf
live
stream.
There
are
maybe
some
people
that
don't
know
what
the
argo
project
is
so
we'll
do
a
very
brief
introduction
for
those
people.
B
Argo
project
is
consists
of
four
main
tools:
performing
projects,
essentially
argo
workflows,
which
is
a
general
purpose,
workflow
engine
for
kubernetes,
and
it's
used
very
popularly
for
a
lot
of
data
science
and
we'll
talk
a
little
bit
more
about
that
project
and
who
is
using
it
argo
events
which
is
primarily
for
working
with
argo
workflows.
It's
triggering
events
and
triggering
actions
that
take
place
and
it
works
really
well
as
sort
of
an
event.
B
B
All
of
these
projects
can
be
used
completely
by
themselves
or
they
can
be
used
together
with
some
integration
between
our
cd
and
our
rollouts
and
some
integration
between
our
workflows
and
our
go
events.
But
if
you're
not
using
argo
cd,
you
can
still
do
canary
releases
using
argo
rollouts.
You
don't
need
to
use
argo
cd.
If
you're
using
argo
cd,
you
don't
have
to
be
doing
progressive
delivery.
You
don't
have
to
be
doing
the
workflows
if
you're
using
workflows.
You
don't
have
to
be
using
argo
events
to
trigger
your
workflows.
B
You
could
be
using
cron
or
other
things
like
that,
so
these
are
really
architected
in
such
a
way
to
be
very
flexible
and
you
can
pick
it
up
and
use
it
for
the
purpose
that
it's
designed
for.
We
joined
the
cncf
as
a
project
in
2018
and
we
moved
into
sandbox
we've.
We've
migrated
now
into
what's
the
next
level
above
sandbox.
I
just
just
escaped
my
head,
but
incubation
incubation.
Thank
you
and
then
we're
moving
forward
towards
graduation.
B
The
project
has
been
incredibly
popular
and
we
we
actually
are
now
one
of
the
fastest
growing
and
most
popular
projects
in
the
cncf.
There
was
a
momentum
report
that
just
came
out
with
the
cncf
that
showed
how
much
development
activity
there
is,
and
argo
was
just
behind
two
projects,
kubernetes,
and
I
think
it
was
so
it's
an.
B
Yeah,
it
was
open,
telemetry
yeah.
It
was
very,
very
close,
so
a
very
popular
project.
When
we
look
at
github
stars
over
20,
000,
github
stars
and
growing
very
rapidly,
the
project
is
maintained
in
a
primarily
by
five
corporate
sponsors
acuity,
which
hong
represents
blackrock.
B
We
don't
have
a
representative
from
them
today,
code
fresh
who
I
represent
into
it,
and
we
have
bala
and
and
julie
joining
from
intuit
and
then
red
hat
and,
of
course,
there's
a
huge
sea
of
community
maintainers
that
have
been
independent
and
operating
on
the
project
for
a
very
long
time
and
and
so
they're
critically
important.
So
we
have
this
wonderful
partnership
between
these
companies
as
well
as
all
these
independent
contributors
and
argo
is
trusted
by
google
nvidia
capital.
One
tesla
I
mean
the
largest
companies
in
the
world
are
using
argo.
B
Largest
companies,
but
also
the
smallest
companies,
are
using
argo
effectively.
You
don't
need
to
have
you
know
a
huge
degree
and
we've
got
a
really
exciting
event
coming
up
argo
con
and
I
think,
all
of
our
pretty
much
all
my
slides
have
it
sitting
up
in
the
top
right
corner.
It's
going
to
be
next
month
september,
19th
to
the
21st,
and
we
have
a
huge
number
of
speakers
that
are
coming
to
speak
at
that
event
and
share
their
use.
Cases
share
what
they've
been
doing
and
you
don't
want
to
miss
it.
B
So
if
you,
you
know,
while
the
live
stream
is
going
on,
go
google
argo
con
go
register
if
you're
attending
online.
It's
a
free
event.
If
you're
attending
in
person
there's
a
small
fee,
we're
all
going
to
be
there
in
person.
We
would
love
to
see
you
here
and
and
meet
you
in
person
if
you're
able
to
make
it,
but
that's
like
the
reason
for
the
season.
That's
what
we're
that's.
Why
we're
like
getting
together
to
talk
today
is
because
we
do
have
argo
con
coming
up.
It's
very
exciting
one.
B
One
other
thing
I
was
just
gonna
mention
about
the
argo
project.
Many
people
aren't
familiar
with
net
promoter
score,
but
basically
it's
a
measurement
of
how
much
your
users
like
or
dislike
your
product,
and
when
we
ran
this
survey
for
argo
workflows
and
argo
cd,
they
were
both
over
60.
and
a
good
nps
score
is
like
over.
20
is
considered
very
good.
Anything
over
like
30
is
considered
excellent.
Over
60
is
like
you
could
start
a
religion
off
of
the
love
for
the
product.
B
That's
like
the
level
that
argo
is
out,
so
the
community
is
just
incredibly
passionate.
They
love
using
argo,
whether
they're
using
argo,
workflows
for
doing
data,
science
or
or
other
kind
of
general
purpose
workflows
or,
if
they're,
using
argo
cd
to
deploy
their
software
it
just
it
really
simplifies
day-to-day
operations
with
kubernetes
and
makes
life
a
lot
easier.
So
in
summation
you
know,
go
register
for
argo
con.
We
want
to
see
you
there
there's
going
to
be
cool,
swag
there'll,
be
cool
speakers.
B
There's
going
to
be
some
interesting
announcements
going
on
we'll
be
talking
about
the
project
and
it's
going
to
be
really
really
exciting.
So
with
that
brief
intro
out
of
the
way,
I
think
we
wanted
to
maybe
start
with
argo
workflows,
so
julian
bala
I'll
pass
over
to
you.
D
Thank
you
dan.
Let's
see,
do
you
want
to
stop
sharing
your
screen
and
I'll
share
mine.
B
D
Right
yeah,
so
I'm
just
going
to
talk
a
little
bit
about
argo
workflows
and
what
some
of
the
new
things
are
that
we're
releasing
as
part
of
version
3.4,
which
I
guess
we
are
targeting
that
for
argo
con
itself.
So
I
think
that's
september
19th,
just
some
github
stats
here.
Argo
workflows
has
now
had
2400,
forks
and
11
600
stars
just
for
a
little
more
bragging.
D
I
think
probably
most
of
the
audience
is
pretty
familiar
with
workflows,
but
I
just
want
to
start
with
a
simple
example
here
you
know.
Basically,
it's
a
pipeline
of
steps
that
are
where
each
step
is
basically
a
different
pod
running
in
kubernetes,
and
you
could
have
either
linear
a
linear
pipeline
of
steps
or
it
could
be
a
directed
acyclic
graph.
D
Like
is
shown
here
and
you
can
have
you
know,
pods
that
run
that
basically
pass
outputs
to
other
pods
to
use
as
inputs,
and
then
you
can
have
the
whole
thing
triggered
on
a
cron
schedule
by
a
web
hook
or
if
you
integrate
argo
events
in
then
you
actually
have
access
to
21
different
potential.
D
Okay,
so
some
of
the
new
features
that
are
coming
out
as
part
of
version
3.4
involve
artifacts.
I'm
going
to
talk
a
little
bit
about
those.
So
artifacts
are,
you
know,
basically
files
produced
by
the
steps
of
your
workflow
that
you
put
in
cloud
storage
generally,
so
those
could
be.
You
know,
temporary
files
that,
where
maybe
you
know
one
pod
produces
a
file
and
it
gets
consumed
by
other
pods,
or
maybe
it's
some.
D
You
know
final
artifact,
you
know
produced
by
your
workflow
that
you
want
to
hold
on
to,
and
so
this
can
be,
you
know
all
sorts
of
different
types
of
files.
You
know
including
database
dumps,
or
you
know,
spark
files
in
addition
to
text
files,
etc,
etc.
D
D
So
let
me
just
show
you
some
of
the
new
visualization
capabilities.
So
basically,
this
is,
you
know
showing
in
the
ui
a
workflow,
that's
been
run,
and
so
what's
been.
Added
here
is
to
this
graph
is
basically,
you
know
all
these
artifacts
that
were
produced
by
this
particular
step
in
the
workflow.
D
D
Yeah,
okay,
so
now,
basically,
if
you've
got
a
file
produced
with
a
well-known
extension
like
a
text
file
for
example,
then
now
there's
an
iframe
that
opens
up
where
you
can
see
what
that
file
looks
like
a
json,
a
ping
file
and
then
also,
if
you
have
a
if
you're,
if
your
workflow
step
is
actually
producing
like
a
web
directory.
D
Now,
that's
basically
like
fully
navigable
over
here.
So
in
this
example,
you
know.
Basically
the
step
actually
produced
this
graph
image
and
then
put
it.
You
know
embedded
into
an
html
page
and
so
we're
actually
showing
that
here
and
then
this
html
page
actually
has
sub
links,
and
so
you
can
actually
navigate
through
those
over
here,
too
yeah.
So
that's,
basically
the
the
new
visualization
capability,
let's
see
and
then
so.
The
other
feature
related
to
artifacts,
that's
coming
out
as
part
of
3.4
is
artifact
garbage
collection.
D
So
the
issues
that
we
were
trying
to
address
are
basically
that
users
had
to
manually
delete
their
own
artifacts.
D
You
know
by
going
directly
to
s3
or
whatever
their
storage
engine
is,
and
then
you
know
if
they're,
not
if
they.
D
So
now,
basically,
we've
enabled
you
to
specify
in
your
workflow
that
you
actually
want
these
artifacts
garbage
collected
automatically
either
when
the
workflow
is
completed
or
when
the
workflow
is
deleted,
and
so
you
can
basically
define
that
either
on
the
workflow
level
up
here
or
on
the
artifact
level
down
here.
D
In
this
example,
let's
say
your
workflow,
you
know,
is
producing
a
whole
bunch
of
artifacts
that
maybe
you
don't
need
to
hold
on
to
those
long
term,
but
maybe
it
produces
some
final
artifact
that
you
do
want
to
keep.
So
you
know,
basically
you
can.
You
know,
set
your
overall
strategy.
D
You
know
to
basically
delete
delete
the
artifacts
when
the
workflow
is
deleted,
but
then
you
can
actually
override
it.
You
know
on
the
individual
artifact
level
to
say
you
know.
Actually
I
want
to
hold
on
to
this
one,
and
currently
this
is
just
implemented
for
s3
and
azure,
but
we're
hoping
that
there
will
be
community
contributions
to
augment
that,
and
that's
all
that
I
have.
B
D
D
But
the
release
candidates-
I
guess.
B
B
C
So
today
I
will
give
a
little
bit
of
demo
of
both,
and
here
is
the
plan
so
for
the
people
who
didn't
know
about
argo,
yet
I
think
it's
highly
unlikely,
but
I'm
still
going
a
very
basic
example
to
setting
the
core
functionality
and
what
that
looks
like
we'll
go
through
the
web
terminal
feature
which
is
already
shipped
in
the
2.4,
and
there
are
three
more
new
features:
brand
new
features
coming
on
the
street
2.5,
which
we
will
talk
about
it
and
also
do
a
quick
demo
on
one
of
them.
C
So,
first,
first,
let's
go
through
the
quick
demo
about
what's
the
core
functionality
of
rcd.
So
this
is
the
brand
new
empty
argo
cd.
So
what
you
do
is
you
need
to
create
a
new
application?
That's
easy!
So
you
can
see
demo
name
the
application.
This
is
a
new
feature.
I'm
not
going
to
go
beep
that
because
go
deep
into
this
concept,
it's
called
application.
Namespace.
I
will
mention
a
little
bit
in
my
in
the
feature
in
the
2.5
zoom
project.
C
We
go
with
the
default
and
we
want
auto
crank
namespace,
we'll
pick
a
repo
url,
so
I
will
just
using
my
personal
one,
which
is
on
the
github
and
you
can
using
the
guest
book
pass.
We
want
deployed
cluster,
we
just
deploy
into
the
same
cluster,
calling
cluster
we're
using
the
namespace
demo.
That's
it
we
catch
box,
everyone
and
we
create
a
namespace.
I'm
sorry.
We
create
the
application
here.
C
So
it
has
a
service
object,
has
a
deployment
object
and
you
can
see
the
hidden
object.
Also
the
replica
set
endpoint
and
those
things,
and
those
are
the
parts
one
thing
we
want
to
do
to
demo
is
the
ddos
concept
quickly.
I
think
a
lot
of
people
already
know
about
it,
but
I
will
just
quickly
do
it
so
here
from
the
repository
you
can
tell
the
configuration
for
this
deployment.
Replica
is
three,
so
I
want
to
change
it,
so
I
will
just
add
it
from
the
github.
C
C
But
here
we'll
still
do
the
manual
thing
so
right
now
it
has
three
so
when
we
sync
it
again
to
the
latest
change
and
then
we
are
c5
and
when
you
have
five,
but
maybe
you
feel
okay,
this
is
the
wrong
configuration
and
from
argo.
Cd
is
super
easy
to
roll
back.
You
can
pick
the
previous
version
and
click
on
the
rollback
and
we
could
do
the
time
travel.
So
this
is
what
we
before
we
deployed
the
new
version.
This
is
the
before
so
that
about
github.
C
So,
basically,
all
the
single
source
will
choose
all
sorts
of
choose
actually
in
the
git
and
argo
cd
is
trying
to
bridge
the
gap
is
taking
the
sausage
tools
from
the
git
and
deploying
to
your
target
cluster,
and
I
want
to
go
to
the
next
demo.
It's
talking
about
the
web
terminal.
This
is
an
optional
feature.
You
can
enable
that
in
two
for
in
and
future.
C
So
what
makes
life
easier
is
every
time
you
look
at
the
system
and
you
have
the
big
overview
about
what's
going
on
about
your
application,
and
you
want
to
do
a
quick
troubleshooting
about
your
your
part.
Nowadays,
you
can
do
click
on
the
part.
You
will
see
this
new
tab
called
terminal
and
you
can
directly
go
into
the
pod
and
be
able
to
basically
like
what
terminal
can
do.
You
can
run
the
command
here.
You
can
even
run
a
lot
of
things
about
understand
the
container
status.
C
This
is,
I
would
say,
the
flagship
product,
a
flagship
feature
in
2.4
which
already
been
available
everywhere,
but
you
need
to
enable
that,
following
the
steps
cool,
that's
the
demo
part.
So
I
want
to
go
back
to
talking
about
additional
features
in
2.5
server.
Side
apply
as
the
sync
option.
So
this
is
the
feature
has
been
supported.
I
think
in
120
kubernetes
version
and
reset
in
rdcd
in
the
2.5.
We
are
going
to
make
it
available
to
the
users.
C
Why
we
have
this
server
side
applied
for
three
biggest
reasons.
One
is
we
want
the
better
inter-operative
ability
with
admission
controllers
means
you
have
several
animation
controllers,
are
managing
the
same
object
and
how
you
figure
out
the
ownership
who
is
touching,
which
field
and
the
second
is
about
the
better
resource.
Conflict
management,
as
I
just
mentioned,
and
especially
the
last
but
not
least,
is
the
better
crd
support
and
we
want
to
do
a
quick
demo
about
what
does
that
looks
like,
and
what
does
that
mean?
So
we
already
created
one
application.
C
C
Before
the
project,
we
will
do
auto-click
namespace
and
enable
the
server-side
apply
this
time
and
I
will
deploy
the
exactly
the
same
version
of
the
app
so
copy.
From
my
repository
go
to
the
guest
book,
so
demo
dash
ssa,
we
want
to
create
a
new
name,
space,
create
it,
and
I
just
want
to
sync
it
and
when
you're
syncing
you
can
see,
the
server
side
applies
check
boxes.
Basically,
this
is
application
level
setting,
but
you
can
everything
you
can
change
it
if
you
want.
C
C
So
one
huge
difference
you
can
tell
you
are
using
the
thing
a
server-side
appliance
is:
do
we
have
the
last
applied
configuration
so
here
in
the
without
seeing
server
side
apply?
You
will
see
a
big
lens
string.
Basically,
talking
about
the
whole
spec
of
the
deployment
file,
but
when
we're
using
the
server
side
apply
that
disappear,
I
think
that's
the
symptom,
basically
that's
sort
of
like
additional
benefits
to
to
to
get
what's
the
server
side
apply
working,
but
it's
not
the.
C
C
So
I
will
talk
about
the
next
two
features.
We
don't
have
a
demo
yet
because
the
two
features
are
in
the
very
active
development
right
now.
So
there
are
a
lot
of
polish
has
to
be
done
before
we
can
release
it.
So
this
is
a
very
interesting
feature.
We
call
it
applications
outside
argo
city
namespace,
it's
very
weird,
but
I
can
tell
you
the
reason
so
nowadays,
a
lot
of
the
people
lives
are
lcd
because
they
are
using
the
very
advanced
features.
We
call
it
apple,
apps
pattern
or
application
set
pattern.
C
So
for
those
patterns
to
be
working,
you
have
to
deploy
the
object
to
the
control
plane,
namespace.
Basically,
you
are
doing
what
is
I
just
did
through
the
ui.
You
are
creating
applications
by
yourself
and
in
always
using
the
crd
to
create
applications.
So
the
target,
the
namespace,
is
actually
the
argo
cd
main
space
itself.
This
is
working
great
initially,
however.
Well
we
have
more
and
more
people
adopting
this
pattern
and
for
the
same
argo
cd,
you
may
have
two
different
teams
are
using
the
same
rlcd
to
manage
their
infrastructure
or
manage
their
applications.
C
Just
think
about
I'm
using
the
apple
x
pad.
You
are
also
using
apple's
pattern.
That
means
there
will
be
a
chance
we
are
colliding
with
each
other.
Basically,
I'm
naming
my
application
as
the
same
name
as
you
like
demo.
So
when
I
deploy,
I
will
overwrite
your
application,
which
is
pretty
bad,
so
this
is
kind
of
like
a
small
multi.
It's
advanced
the
multi-tendency
problem,
so
we
are
trying
to
address.
C
So
what
we
do
is
in
cellular.
You
can
just
getting
the
application
object
in
the
one
next
phase.
Argo
cd
will
allow
you
to
configure
to
monitor
multiple
namespace
as
the
control
plane
means
that
each
team
can
configure
their
app
of
apps
pattern
of
their
application.
C
Application
set
object
to
be
their
dedicated
namespace,
so
there
will
be
no
collision
possible.
So,
additionally,
there
will
be
additional
changes
in
the
project
concept.
I
know
people
understand
using
the
app
project
as
the
isolation
of
multi-tenancy,
so
that
will
also
be
able
to
mapping
to
the
management
spaces.
So
basically
you
everyone
have
their
dedicated
lane
to
use
this
advanced
pattern.
So.
B
Basically,
I
add
just
a
little
bit
to
that,
because
I
think
you
said
it
really
well,
I
the
the
the
common
pattern
that
we
see
people
doing
is.
They
will,
for
example,
do
when
we
talk
about
this
app
of
apps
for
people
that
aren't
super
familiar
with
it.
Basically,
what
they'll
say
is
anybody
that
adds
files
to
this
repo.
B
This
directory
gets
to
deploy
to
this
target
namespace,
and
so
what
that
means
is
you
can
configure
for
all
your
users,
you
basically
just
configure
the
kind
of
parent
app
for
them,
and
then
they
can
then
just
go
in
and
all
they
have
to
do
is
drop
a
file
into
github
or
their
git
provider,
and
then
it
will
be
automatically
synced,
and
so
this
this
is
a
pattern,
that's
very
popular
that
people
use
all
the
time
it
works
really
well,
so
this
adding
the
multi-tenancy,
so
you
can
just
have
a
dip,
so
they
don't
have
collisions
in
the
name
space.
B
That
really
simplifies
the
output
is
very,
very
highly
requested
feature.
C
C
So
I
would
like
you
guys,
if
you
guys,
really
need
it,
give
it
a
try,
but
this
will
take
time
will
make
it
very
mature,
but
this
is
a
feature
definitely
for
very
advanced
users
and
you
guys
can
consider
this
cool
moving
to
the
next
feature.
I
think
this
is
a
a
feature
has
been
asked
for
a
lot
because
there's
a
lot
of
github
discussions
like
talking
about
this
use
case.
C
So
argo
cd,
the
feature
name-
is
called
multiple
sources
for
applications,
so
it's
being
implemented
right
now,
so
the
whole
idea
is
for
one
application.
You
can
get
your
source
of
truth
from
multiple
sources,
as
name
imply,
so
why
we
need
that.
I
think
one
very
solid
use
case
is
for
the
health
chart
users.
So
when
you
have
this
helm
chart
it's
like
a
library
there,
but
you
may
have
value
files,
basically
you're,
trying
to
like
initial
instantiate
about
the
help
chart
to
be
a
manifest,
but
the
helm
chart
you
want
it
more.
C
Like
a
library,
but
you
may
have
multiple
value
files
here
and
there
and
you
want
to
keep
them
separate.
Why
and
one
one
use
case
is
a
lot
of
the
helm
chart
is
actually
published
by
the
official
like
elasticsearch
radis.
They
just
published
the
official
help
chart
like
you,
can
just
keep
your
value
files
in
your
personal
repository
and
reference
the
home
chart
as
a
library
and
combine
them.
C
Then
we
can
get
the
point
to
rlcd,
but
our
ocd
has
to
monitor
both
sides,
whether
the
official
helm
charge
change
or
whether
your
value
file
has
been
changed.
So
what
is
the
current?
Workaround
is
actually
using
a
concept
called
umbrella
helm
chart.
Actually
it's
workable.
It's
a
it's
a
workaround,
but
it
does
come
in
with
additional
overhead
means.
You
need
a
repository.
You
need
to
create
this
like
umbrella,
helm,
chart.
You
need
to
have
additional
repository
to
be
tracked
and
to
be
maintained
by
yourself.
C
I
think
that's
overhead,
so
this
is
a
a
feature
has
been
asked
by
the
community
for
quite
a
while,
and
we
are
taking
the
steps
to
get
there
and
it
will
be
coming
at
2-5
and
the.
I
think
the
main
reasons
we
are
going
to
be
cautious
because
by
the
original
design,
when
we
started
rocd,
we
have
this
strong
assumption.
Is
it
is
one
single
source
and
one
destination
to
breaking
that?
C
We
will
do
a
lot
of
changes
around
the
ui
backhand
and
also
how
we
put
in
the
information
how
we
merging
information,
but
after
all,
the
after
we
are
trying
to
digest
all
the
feedback
from
the
community
and
we
are
coming
to
our
proposal
and
we
are
doing
the
implementation
now.
So
looking
forward
to
this
feature,
I
think
this
will
definitely
help
a
lot
of
the
help
users
in
your
day-to-day
life.
I
think
that's
my
topic
today
and
thank
you
for
listening.
B
Yeah
thanks
tom,
that
was
something
that
share,
was
asking
about
right
when
you
started
the
update
he
was
like.
Is
that
helm,
values
coming
to
2.5
good
news?
Got
you
covered
yep?
I
I
actually
used
a
lot.
The
customize
work
around
where
you
can
use
customize
to
reference
a
helm
chart,
and
then
you
can
just
override
the
values
that
way
or
you
can
specify
a
local
file,
but
you're
right.
I
mean
it
requires
me
to
set
up
a
my
repo
and
set
up
this
additional
tooling.
B
Instead
of
just
saying
look,
I
just
I
just
want
to
use
this
helm
chart.
I
want
to
do
a
couple
values
locally,
and
and
do
it
that
way.
I
think
this
was.
This
has
probably
been
the
most
upvoted
feature
that
people
have
been
asking
for
for
the
last
eight
months:
nine
months,
maybe
maybe
the
whole
last
year,
so
appreciate
you
guys
taking
the
lead
on
getting
that
implemented,
because
it's
very
very
desired.
C
Yeah
credits
to
the
community,
so
so
I
think
we
really
appreciate
our
feedback.
I
think
that's
the
whole
reason
we're
making
the
whole
argo
ecosystem
to
be
better
because
of
most
of
features
driven
by
the
community
like
we
didn't
come
out
with
those
like,
for
example,
auto
sync
self
heal,
it's
just
all
from
the
real
use
case,
saying
like
that's
the
practical
problem
people
are
trying
to
address.
We
are
listening
to
those
feedback
and
we
are
incorporating
this
step
by
step
into
our
future.
C
So
I'm
actually
personally
proud
that,
after
three
four
years
development,
argo
is
still
a
such
a
vibrant
community,
so
I
mean
believe
it
or
not.
I
would
say
a
lot
of
the
open
source
community
can't
like
slow
down
like
stabilize.
I
mean
like
in
terms
of
contribution,
but
the
react.
The
reality
for
the
argo
is,
it
is
still
accelerate.
C
So
that
is
amazing
situation
for
us
and
truly
grateful
that
all
the
community
members
participate
and
are
giving
us
the
feedback
and
even
contribute
the
prs.
So
that
is
amazing.
Thank
you.
Thank
you.
Everyone.
B
Yeah
anybody
listening.
If
you
want
to
get
involved,
you
know
beyond
we're
in
slack
in
the
cncf
slack,
there's
an
argo
cd
channel,
there's
another
workflows
channel,
there's
our
new
events
channel
and
our
rolex
channel.
We
also
do
contributor
experience,
meetings,
bi-weekly
and
then
we
do
maintainer
meetings,
bi-weekly
and
the
contributor
experience.
You
know
they're
very
open,
so
people
come
from
the
community,
they
say
hey.
I
have
an
idea.
Could
we
solve
a
problem
in
this
way?
B
B
They
collect
feedback
we
get
through
the
architecting
and
then
people
can
get
to
you
know
getting
onto
the
implementation
and
helping
out
with
it
and
that
that
focus
on
contributor
experience
is
something
that
to
hong's
point
I
think,
has
been
really
successful
in
this
project
and
it's
one
of
the
reasons
that
we
have
maybe
the
most
maintain.
I
think
we're.
B
So
with
that
I
mean
those
are
the
those
are
the
project
updates,
that's
the
intro
to
the
project.
I
think
we
can
kind
of
move
into
the
discussion
portion
right.
I
mean
we
can
just
kind
of
chat
about
the
project
and
love
to
take
questions,
and
you
know
you've
got
a
couple
maintainers
on
the
call,
so
we're
happy
to
take
any
any
discussion
and-
and
I
guess
taylor-
do
you
want
to
lead
us
out?
Maybe
how
do
you
want
us
to
arrange
ourselves.
A
Yeah
yeah
yeah,
so
so,
like
dan
said,
if
anyone
has
any
questions,
please
feel
free
to
surface
those.
I
I
just
had
a
couple
before
closing
some
things
out
and
and
just
give
some
people
times
to
time,
to
ask
some
questions
when
it
comes
to
you
know,
I've
heard
a
lot
of
folks.
I
used
to
work
at
hofstra
corp,
and
so
I
came
with
that
perspective
of
people
trying
to
instrument
things
or
set
up
infrastructure
as
code
for
folks
that
have
already
set
up
workloads
within
kubernetes
or
other
cloud
native
workflows.
A
Do
you
have
any
recommendations
for
folks
on
kind
of
how
to
adjust
or
start
to
implement,
get
ops
within
those
solutions?
Is
there
any?
You
know,
unfortunately,
there's
no
like
automatically
fix
this.
You
know
for
me,
or
do
this
for
me
yet
yet,
but
on
the
path
to
get
there.
Are
there
any
tips
or
tricks
that
you
have
for
folks
to
make
that
a
little
bit
easier
for
them.
B
I
I'll
speak
quickly,
but
I
notice
that
most
people
so
when
they
start
moving
into
a
get
ops
mindset,
they're
used
to
having
kind
of
a
manual
deploy
button
of
some
kind
or
a
manual
deployment
trigger,
and
maybe
they're
doing,
the
deployment
manually,
or
maybe
it's
running
a
pipeline
or
something
like
that,
and
so
what
I
see
a
lot
of
people
do
early
on
is
they'll,
create
their
applications
in
argo,
cd
and
they'll
leave
their
sync
policy
on
manual
so
that
they
can
manually
push
the
button,
and
that
feels
great
because
then
they
feel
like
they
have
the
control.
B
I
really
like
to
move
towards
getting
towards
just
full
automation.
So
it's
hey
once
I've
committed
to
git
the
gates
are
all
on
git,
and
so
it's,
if
I'm
merging
the
pull
request,
I'm
doing
it
and
the
biggest
thing
to
make
that
happen
is
moving
to
a
two
repo
structure.
You
have
a
repo
for
your
application
code.
You've
got
your
go
code,
your
java
code,
whatever
you're
rocking
and
rolling
you're,
releasing
new
versions
you're
committing,
and
then
you
have
your
get
ops
repo,
where
this
is
defining.
B
What
version
should
be
deployed
so
when
you're
ready
to
deploy?
You
just
are
making
a
version
change
in
this
repo
over
here,
and
that
makes
it
really
easy
to
control
and
delineate
between
changes
and
if
you
have
several
dependency
applications
or
things
like
that,
you
can
kind
of
version
them
together.
You
can
release
together
if
you
want
to
and
that
that
takes
a
lot
of
the
pressure
off,
because
I
think
some
people,
when
they
first
come
in
they
say
well.
B
Okay,
I'm
gonna
have
like
a
deployment
folder
on
this,
but
then
I'm
making
changes
and
then
I
don't
you
know
I
feel
like
I
don't
have
control
and
maybe
somebody
bumps
this
thing
on
accident.
You
know
I
don't
have
the
permission
structure
I
want
so
going
with
the
two
repo
structure.
I
highly
recommend
that
I
don't
know
what
would
you
say?
I
mean
hong
bala,
you're
you're,
also
argo
cd
users.
What
would
you
say.
C
From
my
perspective,
yeah,
it's
a
it's
a
basically
very
good
expression.
I
mean
we
are
in
the
cnc
of
landscape,
so
I
mean
a
lot
nowadays.
A
lot
of
the
infrastructure,
as
code
concept
is
getting
prevailing.
I
mean
the
terraform
is
a
good
example.
I
think
it's
still
a
very
solid
tool,
but
there's
other
tools
also
on
the
horizon,
like
I
think
the
cross
plan
is
actually
a
pretty
good
tool
like
we
use
that
in
our
company.
Also,
we
basically
the
whole
concept
is.
I
feel
on
the
philosophy
side.
C
Is
the
everything
tied
back
to
kubernetes?
Has
this
declarative
api?
So
you
can
leverage
their
declarative
api
to
do
whatever
use
case
you
want,
like
you,
want
to
imagine
infrastructure
manage
the
application.
In
the
end,
it's
kind
of
like
a
very
strong
contract
that
there,
like
you
set
at
the
expectation,
is.
I
gave
you
this
yamo
some
controller
of
the
kubernetes.
C
You
deliver
the
result
to
me
as
simple
as
that.
It's
not
I
mean
implementation
is
not
simple,
but
the
contract
is
very
powerful
to
make
that
promise.
So
that,
basically,
I
think
is
people
if
you
are
still
evaluated
about
kubernetes
or
thinking
about
a
lot
of
the
other.
Things
like
you
feel
is
complicated,
but
I
would
say:
go
back
to
the
very
bare
minimum
to
understand
what
does
kubernetes
mean
to
your
company
and
you
have
to
rethink
about.
C
Do
you
want
declarative?
If
the
answer
is
yes,
I
think
that
will
help
you
to
make
a
lot
of
decisions
much
easier.
So
argo,
cd
cross
plan
and
even
other
tools
is
just
like,
I
would
say,
a
great
solution
built
on
top
of
that
promise
and
makes
that
promise
to
be
achieved
much
easier
there.
But
I
think
for
a
lot
of
people
like
just
go
back
to
the
bare
minimum.
Bear
like
the
fundamental
of
what
does
kubernetes
mean
to
you
and
start
with
that
song
to
to
start
your
journey.
There
gotcha.
E
And
under
the
intuit
is
a
heavy
user
of
the
targo
city,
all
the
intuit.
All
the
services
are
using
the
targo
cd
to
deploy
under
all
the
different
environment
and
exactly
downside
techno.
That
is
the
same
pattern
in
tutorials
are
using.
There
is
a
core
repo
under
github
repo
and
addition
to
the
github
repo.
A
I
like
that,
and
and
even
I've
liked
folks
kind
of
pointing
out
too
that,
like
you,
don't
have
to
it's,
it
doesn't
seem
obvious
all
the
time,
but
you
don't
have
to
do
everything
all
at
once.
You
know
moving
some
other
things
in
life
might
happen
that
way,
but
you
don't
have
to
do
that
with
your
infrastructure.
You
can
kind
of
develop
that
confidence
and
take
those
learning
lessons
as
you
go
through
it.
A
B
While
I
think
argo
as
a
project
is
ambivalent
about
that,
and
I
don't
think
we
have
an
opinion
as
a
project,
I
would
say
personally
I
actually
really
try
to
avoid
that
model.
I
really
like
to
have
everything
in
my
main
branch,
my
production
branch
and
then
I
have
a
folder
for
production.
I
have
a
folder
for
staging.
B
I
have
a
folder
for
test
environments
and
it
really
like
one
of
the
one
of
the
big
issues
is
that
we
typically
have
some
kinds
of
differences
between
staging
and
production
and
so
modeling
those
differences
you
have
to.
If
you're,
using
multiple
branches.
You
then
have
to
kind
of
have
a
policy
around
like
don't
merge
this,
but
do
merge
that,
and
that
makes
it
really
confusing
and
it
gets
it
gets.
It
gets
very
messy
when
you're
using
folders
and
you
have
a
folder
for
production.
B
You
have
a
folder
for
staging
and
I
I
use
customize
pretty
heavily,
I
mean
you
can
do
this
with
home,
but
I'll
have,
for
example,
a
customization,
that's
labeled
staging
and
a
customization,
that's
labeled
production.
I
know
those
are
never
gonna.
There's
never
gonna
be
a
movement
between
those
folders
on
those
things,
it's
very
obvious
what's
happening
and
then
the
the
changes
that
you're
staging
out
and
then
moving
to
production.
That
progression
happens
very
straightforward
and
the
other
thing
I
was
thinking
about
as
we
were
talking
about.
B
This
is
most
people
when
they
first
start
using
argo.
They
install
argo
and
they
don't
realize
that
they
can
use
argo
cd
to
manage
itself.
So
you
can
add
argo
cd
as
an
app
and
then
you
can
actually
move
changes.
You
know
you
can
you
can
stage
out
which
version
of
argo
cd
you're
going
to
be
using,
and
so
that
way
everything
is
fully
get
ops
and
you
can
bootstrap
off.
Of
that
I
mean
that's.
That's
like
a
lovely
pattern.
A
That's,
I
think,
that's
been
one
of
the
great
developments
about
you
know
the
arc
community.
I
really
liked
the
app
of
apps
pattern
and
just
like
all
of
those
architectures-
and
you
know
really
the
thought
patterns
behind
how
those
got
set
up
seeing
those
evolve
has
been
something
that's
been
really
validating
and
helpful
in
kind
of
you
know,
figuring
out
and
unlocking
the
best
ways
in
which
to
use
this
workflow.
So
much
appreciated.
E
E
A
Thank
you
for
the
insight.
I
I
saw
a
couple
comments
and
things
like
that.
I
don't
see
any
new
questions,
but
but
yeah.
If
there
aren't
any,
then
I'm
more
than
happy
to
kind
of
get
things
wrapped
up,
just
to
kind
of
reiterate,
for
where
are
some
of
the
best
places
that
folks
can
find
you
if
they
have
questions,
I
know
I
had
you
had
mentioned.
You
know,
take
a
look
at
the
kubernetes
slack.
Take
a
look
at
the
cncf
slack.
Are
there?
Are
there
any
other
places?
You
know
github,
twitter,
etc?
C
A
Yeah
not
according
to
popular
conception.
I
can't
just
say
argo
argo,
argo.
Three
times,
then
you
appear
okay
for
the
next
person.
If.
E
D
C
C
So
I
have
to
show
up
to
answer
the
question,
but
in
some
tests
that
works.
B
A
B
A
You've
got
it
handled,
awesome,
awesome,
cool.
C
I
just
last
I
want
looking
forward
to
meet
with
all
the
argo
users,
so
please
join
us
at
argo
con
and
if
you
are
not
some
for
some
reason,
you
cannot
join
argo
cam.
I
won't
see
you
in
detroit
and
at
any
like
kubecon,
looking
forward
to
meet
you
in
person,
and
I
want
to
learn
about
your
article
story
and
share
your
feedback.
Even
it's
the
critics.
I
welcome.
We
welcome
critics
about
hey,
what
do
you
don't
like
and
we
eventually
won't
really
making
the
product
to
be
better
and
better.
So
thank.
E
You
everyone
yeah
I'd
like
to
give
like
one
last
one
like
if
you're
new
to
the
argo
you
like
to
explore
the
targo
product.
Please
come
to
that
argo
con
zero
day
into
it.
We
have
like
a
bunch
of
workshops
which
will
start
from
the
scratch
like
a
kubernetes
information
and
argo
cd,
101,
argo,
workflow,
101,
argo
event.
101
will
give
that
very
basic
use
case
where
you
can
use
this
all
the
tools.
A
Awesome
well,
thank
you
so
much
a
few
more
things
before
we
are
go
today.
Thank
you.
Everyone
for
joining
the
latest
episode
of
cloud
native
live.
We
really
enjoyed
the
interaction
and
questions
that
we
got
from.
You
like
everyone
said.
Please
check
out
argo
con.
If
you
can
either
in
person
or
virtually
we
would
love
to
we'd
love
to
see
you
there
or
not.
You
know
just
kind
of
know
that
your
packets
are
floating
around
and
the
ether
would
be.
It
would
be
good
too.
A
Thank
you
so
much
for
joining
us
today
and
we
hope
to
see
you
again
soon
and
have
a
good
one.
Everybody
thank
you
later.