►
From YouTube: From Code to Docs to Marketing: How to Contribute -
Description
From Code to Docs to Marketing: How to Contribute - Jesse Suen, Alex Matyushentsev, and Remington Breeze, Akuity; Dan Garfield, CodeFresh; Regina Voloshin- Bank Hapoalim, Michael Crenshaw & Julie Vogelman, Intuit
Have you contributed to the Argo community yet? Interested but not sure where to start? Get an overview of the Argo community and the key areas where your contribution is needed. Covering SIGs and sub projects, identify your next move in the community.
B
B
D
Thank
you
all
right,
I'm
just
here
to
kick
things
off,
but
this
session
is
about
how
to
get
started,
contributing
to
Argo.
So
we'll
go
over
what
it's
like
to
make
a
code
contribution.
I
know
it
can
be
pretty
daunting,
and
so
hopefully
this
will
make
things
a
little
less
scary.
But
if
you
do
take
one
thing
away
from
this
session
is
that
you
don't
have
to
be
a
developer
to
contribute
to
Argo.
D
You
know
we
have
folks
just
focusing
on
documentation,
marketing
security,
so
there's
a
lot
of
different
areas
to
contribute,
and
so,
as
you
know,
Argo
has
two
tracks
like
CD,
rollouts
and
workload
of
events.
So
every
week
there
is
a
cargo
City
rollouts
meeting
on
Thursdays
this
for
this
technical
discussions
and
similarly
on
workflow
French,
it's
not
every
week
but
workflows,
has
a
I,
think
bi-weekly
meeting
on
workflow
related
issues
and
Technical
discussions,
there's
and
I.
D
Don't
you'll
have
to
look
on
the
calendar
for
all
of
these,
but
there's
meetings
focused
specifically
on,
like
the
UI.
Of
course,
we
have
like
the
monthly
Community
meetings,
which
is
kind
of
more
targeted,
for
you
know
more
general
public
and
less
maintainers
and
other
things
like
marketing
committee
and
even
when
focused
on
security.
D
Just
like
you
know,
Reach
Out
speak
to
us
and
say
Hey
What,
Can,
I
Do
to
contribute
so
I
think
some
some
other
tips
I
know
it's
hard
to
get
attention
of
maintainers,
so
I
find
it
effective
to
kind
of
show
up
to
some
of
these
contributors
meetings
and
and
just
get
in
our
face
and
actually
raise
issues.
Add
things
to
the
agenda,
especially
that
will
they'll.
You
know,
bring
things
to
the
Forefront
that
meets
discussions
and
we
do
try
to
tag
issues
as
good
first
issues.
D
Think
the
last
part
of
contributing
and
I
think
you'll
have
I'll
have
to
defer
to
Henrik,
but
we
do
have
like
the
whole
corporate
track
right
corporate
contribution,
but-
and
so
you
know
the
people
code
fresh
and
red
hat
and
Acuity
like
Black
Rock,
if
you're,
if
you
have
a
organization,
a
corporate
and
that
wants
to
get
involved,
we
have
you
know
ways
to
join
us
there.
So
I
think
that's
all
I
had
Alex
is
going
to
start
introducing
the
various
people
presenting
today.
I
think.
E
Thank
you
Jesse,
so
one
more
time:
I'm,
Alex
and
I'm,
a
maintainer
of
Fargo
ocg
project,
and
so
we're
going
to
have
five
speakers
today.
That's
why
I
have
a
job
to
introduce
all
of
them
and
first
speaker
is
Regina
Evolution.
She
actually
is
not
here
but
she's
going
to
present
virtually
we
have
a
video
recorded
and
Regina
she
a
long
time
user
of
Fargo
CD
and
she
was
so
excited
about
the
features
that
LG
provides
So.
F
Hi
everyone,
my
name,
is
Regina
and
I'm.
A
huge
githubspan
I'm,
also
a
cloud
platform
team
leader
in
bangali
since
I
was
a
child.
I
was
always
the
only
female
somewhere.
The
only
girl
in
class,
one
of
the
few
women
lecturing
in
devops
areas
and
lately
I,
have
become
one
of
the
few
female
open
source
contributors.
F
F
F
F
But
that
didn't
happen
for
quite
some
time
and
let's
see
why
contributing
looked
scary
and
beyond
my
level,
I
had
Windows
on
my
laptop
I
had
Windows
on
my
laptop
I
used
virtualbox
and
installed
a
VM,
but
that
VM
wouldn't
start
with
some
weird
error
and
I
found
nothing
about
how
to
fix
it.
So
I
said:
I
need
to
do
instance
in
an
AWS
account
and
then
I
managed
to
build
the
codes,
but
then
I
had
to
spin
an
IDE
I
tried
to
install
the
ID
on
the
same
ec2
instance.
F
F
F
Live
in
Comfort
Zone
in
time
zone
I
wrote
a
proposal
for
the
future
and
put
it
up.
The
shared
community
meeting
agenda
documents,
I
checked
the
date
of
the
meeting
four
times
and
the
time
different
five
times
when
I
entered
the
meeting.
I
was
two
hours
late.
Nevertheless,
luckily
they
still
discussed
it
without
me
and
decided
they
want
this
picture.
F
So
this
is
contribution
reality.
We
asked
how
it
looked
like
in
my
mind.
In
the
beginning,
working
with
four
people
took
longer
than
I
expected.
I
was
forgetting
to
sign
off
the
commits
and
had
to
recreate
my
Branch,
often
I
also
didn't
work
efficiently,
with
pulling
changes
from
Master
and
so
I
had
to
reply.
My
changes
frequently
the
environment
setup,
took
longer
than
I
expected.
F
F
Asking
stupid
questions
on
slack
was
also
a
much
smaller
problem.
I
assumed
that
Argo
City
maintainers
deal
with
Junior
contributors
all
the
time,
and
so
beginner
questions
were
normal
when
I
was
stuck,
I
explored
the
problem
and
tried
various
Solutions
on
my
own
and
I
also
used
the
debugger
a
lot,
but
once
those
were
done
and
things
were
still
not
working,
I
asked
for
help
in
the
slack
contributors,
Channel
and
people
were
very
responsive
and
very
welcoming.
F
F
Oss
projects
had
covered
long
before
we
had
even
heard
that
word.
It
means
that
they
had
to
deal
with
people
being
remote
to
each
other,
working
in
different
time
zones
and
hardly
sharing
an
office
while
the
rest
of
the
world
started
dealing
with
the
remote
challenge
of
sharing
knowledge
and
design
decisions
and
common
context
effectively.
Only
in
2020
OSS
projects
already
have
a
mature
methodology
for
that
this
can
be
argued.
F
F
The
logs
Arabic
feature
was
definitely
not
a
good
first
issue
that
innocent
change
turned
out
to
be
a
breaking
change
unless
explicitly
allowed.
It
would
have
disabled
overall
UI
accessed
podlocks,
and
so
a
transition
release
with
a
feature
gate
was
needed.
The
change
management
at
configuration
upgrade
instructions
and
release
log
levels
has
stopped
me
a
lot.
F
F
F
E
G
G
Okay,
yeah
so
I'm
from
workflows
and
events
and
I
was
asked
to
talk
because
I
have
the
Newbie
perspective,
because
I've
basically
been
working
on
work,
clothes
for
the
last
five
months
and
then
for
three
months
before
that
on
event.
But
disclaimer
like
if
anything
I
say,
is
wrong.
Please
feel
free
to
interrupt
me.
Hopefully
not
okay,
so
you
know
basically
you'll
find
that
all
the
Argo
projects
I
think
are
under
github.com
Argo
proj,
and
that
includes
one
for
Argo
workflows,
one
for
Argo
events.
G
So
if
you're
looking
to
contribute,
maybe
you're
somebody
that
already
has
your
own
need
right,
you're
using
it
and
there's
either
an
enhancement
that
you
want
to
see.
That's
not
getting
addressed,
or
maybe
there's
a
bug
that
you
need
fixing.
So
please
we
welcome
all
the
contributions.
If
you
do,
but
if
you
don't,
then
you
know
there
are
plenty
that
you
can
find.
If
you
go
to
GitHub
issues,
just
find
one,
that's
unassigned!
G
We
ask
people
to
put
a
thumbs
up
on
any
issue
that
they're
interested
in,
so
the
popular
ones
have
more
thumbs
up
and
then
consider
a
good
first
issue,
I'm,
not
sure.
If
everybody
knows
what
that
is,
but
basically
there's
a
tag,
you
know
which,
if
you
go
to
a
label,
I
should
say
so.
There's
a
good
first
issue
label.
There.
G
So
yeah
I
mean
there
are
plenty
of
code
fixes,
bug
bugs
and
enhancements
that
could
be
addressed,
but
documentation
too.
You
know
we
have.
Our
documentation
is
also
on
those
same
repos
and
that
gets
published
to
a
site
that
that
shows
all
the
documentation.
So
if
you
wanna
help
us
improve
that,
that's
definitely
welcome.
G
That's
also,
you
know
on
the
repo
here
is
this
list
of
discussions
here,
so
you
can
start
a
discussion
or
even
bring
it
to
one
of
those
workflows
and
events
to
developers,
meetings
that
Jesse
mentioned
just
because
you
know
I've
seen
people
submit
PRS
for
features
and
then
the
response
they
get
is
basically
oh
well,
it
would
have
been
better
if
it
were
done
this
other
way
right.
So
I
don't
want
anyone
to
you
know
waste
time.
If
it's
something
significant
enough,
you
may
want
to
go
that
route
first,
okay.
G
So,
while
you're
making
the
changes,
what
you'll
find
is
in
our
documentation,
we
actually
have.
We
have
this
developer
guide
here,
developer,
guide,
tab
and
then
you
know,
there's
a
page
here
called
Running
locally.
So
this
gives
you
you
know,
basically
the
instructions
for
for
how
to
run
things
locally.
G
So,
like
our
workflow
controller
and
our
autograph
server
actually
run
just
bare
metal
on
your
machine
instead
of
in
a
a
separate
pod,
it
just
makes
the
development
easier
right.
Okay,
let's
see
so
yeah.
If
you
have
questions
which
I'm
sure
you
will,
then
you
know
feel
free
to
bring
those
up
in
the
GitHub
discussions
that
I
mentioned
before
or
in
these
cncf
slack
channels,
and
then
please,
you
know,
if
do
add
unit
tests
and
then,
if
applicable,
end-to-end
test.
G
G
First
of
all,
pull
requests
should
start
with
the
keyword
either
feet
fix,
docs
or
chore,
and
then,
if
there's
an
issue,
that's
either
a
bug
or
an
enhancement
that
your
PR
is
tied
to
then
you
know
usually
writing
fixes,
and
then
the
the
number
of
the
issue
is
good.
So
then
it'll
automatically,
you
know,
link
them
together,
sign
the
commit
as
well.
G
And
then
also,
we
have
a
lot
of
things
that
get
auto-generated
based
on
changes
and
then
things
that
get
checked
as
well.
So
by
running
this
make
pre-commit
Dash
B.
You
can
do
all
of
that
stuff.
If
you
don't.
What
tends
to
happen
basically
is
the
CI
will
run
in
GitHub
on
your
PR
and
you'll
just
see
that
there
are
various
things
that
have
failed,
so
you
can
always
go
and
look
and
see
well
what
did
fail
and
and
try
to
address
any
issues
in
there.
G
G
G
G
G
G
And
then
yeah,
so
this
diagram
kind
of
just
shows
the
main
flow
of
operation
within
the
workflow
controller.
I
mean
basically
what's
happening.
Is
there's
a
cue
or
I
guess
a
couple
of
cues
that
the
controller
is
is
working
on
just
like
you
know,
processing
all
of
these
workflow
changes
that
have
occurred.
So,
okay,
let's
see
all
right,
just
some
key
files
to
be
aware
of
sorry,
this
is
getting
pretty
detailed,
but
workflow
types.
This
is
kind
of
where
you're,
where
the
workflow
spec
is
defined.
G
Operator.Go
is
called
by
controller.go
to
basically
process
a
workflow
and
then
down
here
argoserver.go
is,
you
know,
basically
setting
up
the
HTTP
listener.
You
know
that's
listening
for
messages
coming
from
the
UI
or
or
from
the
rest,
API,
and
then
sorry.
This
is
the
last
slide
I.
These
two
slides
will
probably
be
more
useful
for
anybody.
G
That's
looking
at
the
slides
later
than
right
now,
but
this
is
kind
of
just
you
know,
sort
of
the
key
directories
within
our
go
workflows
and
by
the
way
yeah
I'm,
mentioning
Argo
workflows
a
lot
here.
I
haven't
really
talked
much
about
Argo
events.
I
think!
That's
because
there's
a
lot
more
work
to
do
on
Hardcore
class,
but
yeah.
So
key
directories.
G
G
E
I
Reviewing
blog
posts,
all
these
kinds
of
things,
and
so
this
is
a
really
great
area
to
get
involved.
If
you're
interested
in
devrel
or
a
lot
of
I
mean
I.
Think
most
of
the
people
here
are
very
technical,
but
you
may
have
people
on
your
team
that
are
less
technical
that
are
interested
in
contributing
to
open
source
and
in
the
Sig
Marketing
Group.
We
have
a
mix
of
very
technical
people
and
very
non-technical
people.
I
For
example,
one
of
the
people
that
helped
put
on
argocon
from
the
code
fresh
team
is
Sharon
and
Sharon
is
not
a
programmer.
She
doesn't
know
anything
about
programming,
she's,
an
events
manager,
and
so
she
helped
organize
to
make
sure
that
we
had
the
right
buildings
worked
with
the
cncf
all
of
these
kinds
of
things.
So
the
opportunity
is
there,
no
matter
what
kind
of
contributions
you
want
to
do,
if
you
can't
do
if
you,
if
you're
watching
that
last
talk-
and
you
were
thinking
this
is
too
hard.
I
If
you
were
unconvinced
by
the
ease
of
use
of
that
experience
and
you're
thinking
still
want
to
contribute,
but
maybe
I
can
contribute
in
a
different
way.
Maybe
I
can
do
more
blog
posts.
Maybe
I
can
go
out
and
talk
about
Argo.
Maybe
I
can
help
with
Events.
Maybe
I
can
help
run
a
Meetup
any
of
those
kinds
of
things.
Sig
marketing
is
the
place
to
be,
and
so
to
get
into
Sig
marketing.
All
of
the
Sig
information
is
on
the
on
the
Argo
calendar.
I
The
Argo
maintainer
meetings,
the
contributor
experience
meetings,
as
well
as
the
Sig
meetings,
Sig
marketing,
meets
twice
monthly,
I,
believe
I
think
it's
like
every
other
week
and
then
Sigma
Securities
like
every
other
week,
and
someone
else
will
talk
about
Sig
UI
but
at
any
rate,
that's
the
basic
pitch
any
questions
about
Sig
marketing,
no,
no,
in-depth
technical
review
of
that.
Okay.
Great.
So
with
that,
do
you
want
to
introduce
the
next
speaker?
Okay,
thank
you.
L
K
K
So
I
want
to
start
off
with
saying
that
there
are
two
main
ways
that
you
can
contribute.
As
Dan
said,
it's
not
always
just
code.
You
can
contribute
in
a
lot
more
ways
than
just
code
so
on
the
left
here,
I
have
the
react
logo.
So
if
you
know
any
react,
which
is
code,
that's
going
to
be
the
main
way
with
which
you
contribute
to
the
rdui,
but
you
can
also
contribute
on
GitHub,
which
is
why
I
have
the
GitHub
logo.
K
So
you
can
contribute
by
opening
GitHub
issues
by
contributing
to
discussions
by
creating
proposals
and
then
further
in
the
community
meetings.
You
can
come
to
the
Sig
UI
meetings.
You
can
come
to
the
general
contributor
meetings
to
talk
about
your
UI
ideas
and
complaints
as
I'm
sure
there
are
many
all
right,
so
I'm
going
to
talk
a
little
bit
about
the
current
state
as
well.
K
So
first
we
have
the
cdui
Argo
CDs
UI
is
fairly
mature
and
fairly
stable
as
well.
We
also
have
the
workflows
UI,
which
has
had
quite
a
bit
of
features
you'll
see
later
in
the
presentation.
I'll
show
you
a
little
bit
of
the
state
of
workflows,
UI,
but
I
think
workflows
is
where
we
need
a
lot
of
help.
K
So,
if
you're
looking
to
contribute
to
Argo
UI,
please
help
us
in
workflows
and
then
the
role
sui,
which
has
this
dashboard,
which
is
relatively
new
as
of
about
a
year
and
a
half
ago,
and
it's
continuing
to
improve
and
evolve.
Jesse
spoke
earlier
about
how
the
dashboard
is,
we
hope
to
add
a
login
feature
or
authentication
rather
and
then.
Finally,
this
is
maybe
the
most
important
area
in
which
you
guys
can
contribute.
K
So
moving
on
to
the
first
of
my
three
key
points,
so
Argo
workflows,
as
I
said,
it
has
many
features:
I
included
the
screenshot,
so
you
can
see
you
know
this
is
almost
a
dozen
sections
of
the
UI
and
it's
becoming
very
complex
and
we
need
contributions.
So
if
there's
one
takeaway
from
this
talk,
please
help
with
our
go
workflows,
UI
and
I.
Think
it's
especially
important
to
consider
polish,
because
there
are
a
lot
of
new
features
that
are
on
the
bleeding
edge.
K
You
could
say
we
need
to
sort
of
bring
it
to
a
similar
state
that
CD
is
in
where
it's
relatively
mature
and
stable,
so
yeah
workflows.
We
would
appreciate
help
with
workflows
and
then
for
CD,
as
I
mentioned,
it's
pretty
mature
and
it's
important
to
consider
that
massive
changes
are
going
to
be
jarring
to
users.
So
I
think,
while
visual
modernization,
we
need
to
do
it.
K
And
if
you
guys
are
not
aware,
we
introduced
extensions
relatively
recently,
and
this
is
a
powerful
new
way
to
add
functionality
to
argosys
UI.
So
essentially,
I'll
show
you
a
screenshot
in
the
next
slide,
but
you
can
extend
the
UI
with
your
own
subsets
of
the
UI.
So
your
own
components,
your
own
react
components
and
it's
pretty
easy
to
to
get
started
with
it.
It's
easy
to
develop
them
and
there's
no
need
to
wait
for
PR
reviews
and
releases
I.
Think
Bala
mentioned
plugins
for
Argo
workflows.
This
is
similar.
K
K
This
is
where
CDs
is
headed,
because
it's
so
extensible,
because
it's
future
proof
and
I
will
mention
too,
that
Argo
rollout's
dashboard
it
was
created
as
an
extension
and
again
I'll
show
you
a
screenshot
in
just
a
second,
but
we're
also
going
to
be
adding
application.
Level
extensions
or
that's
already
introduced,
I
think
if
it's
not
introduced
already,
it
will
be
soon
and
then
sidebar
extensions
as
well.
K
This
is
something
in
progress,
so
multiple
areas
of
extension
and
then
Leo
also
has
a
PR
open
for
introducing
reverse
proxy
functionality
to
extensions.
So
this
should
make
it
a
lot
more
powerful
as
well-
and
this
is
the
QR
code
for
that
proposal.
If
you
guys
want
to
take
a
look
at
that
reverse
proxy
proposal-
and
here
is
a
screenshot
of
the
Rolex
extension.
K
So,
as
you
can
see,
it
looks
almost
identical
to
the
Rolex
dashboard
and
that's
because
it
is
essentially
the
rollouts
extension
is
a
repackaged
version
of
the
Rolex
dashboard,
and
this
is
the
primary
example
of
an
Argo
CD
extension.
So,
as
you
can
see,
you
click
on
a
resource
in
your
resource
tree
in
one
of
your
Argo
City
applications,
and
there
is
an
extra
more
tab
at
the
top
right.
K
K
K
But
again
we
do
welcome
new
features
and
new
feature
ideas,
even
if
you
don't
want
to
implement
them.
Somebody
else
probably
will
so,
please
feel
free
to
open
an
issue,
and
then
you
could
always
help
review
existing
PRS.
Even
if
you're,
not
a
official
maintainer
that
can
go
ahead
and
approve
a
PR
to
be
merged.
Feedback
is
always
welcome,
so
feel
free
to
pitch
in
your
two
cents.
This
is
especially
easy
with
UI.
K
It's
usually
good
practice
to
include
a
screenshot
if
you
open
a
uipr,
so
you
can
always
take
a
look
at
the
screenshots
and
if
you
like,
what
you
see
give
it
a
thumbs
up.
If
you
don't,
then
feel
free
to
leave
a
comment,
and
then
we
also
have
the
Argo
Sig
UI
channel
in
the
cncf
slack,
so
feel
free
to
join.
K
E
M
M
D
M
Yes,
so
if
you
click
this,
you
can
load
the
Argo
proj
calendar
into
your
calendar.
For
me,
it
was
a
bit
of
a
trick
to
get
it
into
Outlook,
but
very,
very
worth
it,
because,
if
you're
having
a
slow
day
at
work
or
whatever,
you
can
hop
into
one
of
our
meetings
and
usually
there's
something
interesting
going
on.
M
We'd
love
to
talk
with
you.
Second
thing
write
documentation
right
now,
particularly
Argo
CDs
documentation,
and
that's
mostly
what
I'm
going
to
focus
on
is
CD,
it's
written
in
in
a
here's,
how
you
get
your
Argo
CD
set
up,
here's
how
you
create
a
project,
here's
how
you
create
an
application!
I
think
that
we
would
really
benefit
from
documentation
that
is
okay.
You've
got
all
this
set
up.
How
do
you
retroactively?
M
M
M
M
It
said
you
have
a
default
project
that
most
people
leave,
as
is
in
their
Argo
CD
instance,
but
that
default
project
isn't
locked
down
and
he
describes
how
to
lock
it
down
so
simple
stuff
like
this
write,
it
up
feel
free
to
slack
it
to
me
tweet
about
it.
I'll
see
it
I
want
to
see
how
people
are
thinking
about
Security
in
their
Argo
CD
instances.
M
It
really
helps
us
if
you're
more
into
code
unless
in
the
docs,
a
couple
places
where
you
can
start
are
with
this
project
in
the
Argo
CD
repo
Ada
Logics
recently
did
a
security
audit
for
Argo
CD
and
actually
for
all
of
the
Argo
products,
and
as
part
of
that
they
identified
some
cves.
We
got
the
cves
fixed
and
the
fix
is
pushed
out,
but
they
also
identified
just
some
like
room
for
improvement
areas
and
we've
written
all
those
up
into
issues.
Some
of
them
are
kind
of
big.
M
So,
even
if
you
don't
want
to
write
code,
that's
all
available
for
you
and
there's
also
a
security
label
for
issues
that
you
can
narrow
down
and
look
at
what's
available,
one
particular
kind
of
issues
issue
that
I'd
like
to
see
if
folks
are
interested
in,
we
created
a
new
issue
template
in
the
Argo
CD
repo
for
security
logs,
so
we're
going
to
try
to
identify
areas
of
the
code
where
the
logging
could
benefit
from
highlighting
hi.
This
is
security
related
and
here's
how
closely
you
should
look
at
this
logging
event.
M
So,
for
example,
we've
started
adding
logging
for
when
Argo
CD
fails
to
close
a
file.
You
can
just
ignore
that
error
and
move
on,
but
you
could
run
into
issues
where
your
controller
is
running
out
of
resources.
So
we
want
to
log
that
event
and
give
admins
the
opportunity
to
monitor
that
and
tell
if
they're,
potentially
a
security
issue.
So
if
there's
something
that
happens
in
Argo
CD
that
you're
like
I'd,
want
to
know
about
that.
M
If
there
aren't
any
issues-
and
you
think
I
just
have
a
really
awesome,
Argo
CD
security
set
up,
then
please
write
how
you're
doing
that
and
blog
about
it,
because
companies
are
going
to
secure
their
stuff
in
completely
different
ways.
And
it's
really
helpful
for
us
to
know
what
those
different
ways
are,
so
that
Argo
CD
can
provide
first
class
support
for
all
those
different
methods
of
securing.
So
that's
all
I
have
for
security,
I'll,
pass
it
back
to
Alex
for
Q
a
and
then
I
think
we're
going
to
Henrik
after.
H
E
H
E
I
A
Infrastructure
is
there
any
way
to
I,
see,
there's
a
way
to
integrate
home
and
Target
CD?
Is
it
the
first
class
system,
the
home,
because
it
seems
that
you're
describing
deployments
in
in
kind
of
your
own
custom
way
and
applications,
but
we
really
use
how
to
pack
and
show
our
application?
Is
that
that
post-class
citizen
again.
I
H
E
E
H
E
A
And
speak
up
a
bit
Yeah,
so
I
I
am
by
the
way
from
EA,
which
is
electronic
cars.
So
we
do
package
our
applications
as
a
home
chart
and
of
course,
currently
we
are
doing
just
simple
pipelines
to
deploy
them.
Just
run
simple
Helm
apply
and
it
goes
to
kubernetes
right.
So
we
want
to
keep
the
same
feature
just
package,
all
the
applications
but
switch
to
our
as
a
cicd
yeah.
E
Let's
support
it
has
two
ways
to
support:
Health
First:
you
can
just
have
your
home
chart
in
git
depository
production
chart
and
it
will
figure
out
what
parameters
you
can
specify
it
lets
you
give
parameters,
values
in
the
Argo
CD
UI
itself,
without
even
connecting
it
back
to
git
and
also
like
you
can
use
Helm
repository
directly.
It
doesn't
have
to
be
connected
to
git
and
then
2.5
release.
That's
coming.
Hopefully
you
know
soon
in
like
a
week
or
two.
I
E
E
M
And
then
it
uses
those
it
uses,
Cube
CTL,
to
apply
those
manifest
to
the
cluster.
If
your
developers
are
super
used
to
like
using
the
helm,
installer
command
and
I
think
there
are
advances
of
list
releases
Etc,
that's
not
available,
because
we
don't
use
talent
to
actually
install
releases.
We
just
use
it
to
build,
manifests,
and
then
that
goes.
M
I
But
luckily,
once
they
have
Argo
CD,
all
the
applications
would
be
listed
as
well.
So
you
just
do
Argo
CD
Plus
app
list,
but
this
is
true
of
the
entire,
like
approach
to
manifests.
Argo
CD
at
the
end
of
the
day
is
just
going.
It's
going
to
end
up
with
manifests
to
apply
through
whatever
config
management
tool.
You're
using
and
Argo
CD
is
not
really
opinionated
about
that.
Helm
is
the
one
that
has
the
most
opinion
because
it
has
like
in
the
UI
like
Helm
repo.
C
Has
there
been
any
consideration
of
expanding
the
functionality
of
Argo
rollout
to
more
resource
types,
not
president,
be
able
to
use
the
metrics
of
the
analysis
templates
to
be
able
to
do
things
like
oh
I've
rolled
out
any
damage
set,
let's
say,
and
this
on
the
metrics.
Now
that
that
thing,
that's
generating
roll
back
to
the
previous
image,
but
that
game
and
set
was
running
that
type
of
functionality.
Yeah.
I
D
So
stateful
set
is
I.
Think
the
second
most
requested
Argo
feature
after
the
off
bash
report.
It's
it's
gonna.
It
would
be
nice
to
support
it.
It
is
gonna,
be
pretty
challenging
because
if
you
think
about
the
way
rollouts
work,
it's
actually
implemented
as
a
drop-in
replacement
for
a
deployment
resource.
So
it
creates
and
manages
replica
sets.
D
But
we
would
have
to
kind
of
repeat
that
the
other
consideration
about
this
is
that
their
rollout
is
equivalent
to
a
deployment.
But
those
two
other
resources
are
actually
you
know
different
resource
clients,
and
you
don't
want
to
say
a
rollout
can
do
both
like
the
functionality
of
a
Daemon
set,
a
staple
set
and
a
deployment
because
you
know
demon
sets
are
much
more
impactful
to
a
cluster,
so
we
would
have
to
introduce
a
a
demon
set
equivalent.
D
So
with
all
that
said,
it
I
think
it
is
kind
of
a
stretch,
goal
I
would
say,
and
there
is
some
effort
to
extrapolate
some
of
the
reusable
components
that
we
did,
that
to
kind
of
lay
the
groundwork
for
eat
more
easily,
being
able
to
support
those
type
of
stateful
workloads.
But
it's
I
would
say
it's
it's
going
to
be
a
long
road.
I
Investment
money
not
directly
related
to
that
question,
because
it's
not
actually
an
article
rollouts
thing,
but
there
is
a
really
interesting
feature
coming
from
the
community
that
hasn't
been
accepted.
Yet
the
proposal
hasn't
been
accepted
but
to
support
rollouts
across
application
sets,
which
would
be
more
like
Fleet,
Management,
yeah.
H
E
So
basically
algosity
you
don't
have
to
understand
if
it's
customized
or
Helm
to
write
changes
back
to
git,
because
it's
all
now
encapsulated
in
a
single
file.
Yeah.
So
I!
Guess,
if
you,
if
you
like
the
idea
to
teach
rusiji
to
do
that,
maybe
create
an
issue
and
see
how
many
thumbs
up,
but
we're
kind
of
close
to
to
support
it.
Yeah.
That's.
E
So
kind
of,
like
some
people,
thinks
it's
controversial.
A
way
to
manage
manifests
because
yeah
you
get
like
two
source
of
Truth.
So
on
one
hand
you
have
maybe
a
customization
config
plus
bunch
of
hammer
files
and
it
produce
your
set
of
manifests.
But
Argo
CG
will
take
the
same
set
of
you
know,
configurations
and
apply
this
magic
file
on
top
and
reduce
your
Capital
difference.
D
I
can
imagine
a
world
where
someone
writes
an
argosity
extension
with
the
back
end.
That
introduces
a
button
in
the
in
the
interface
that
says,
like
sync,
this
live
state
to
back
to
get
and
then
so
I
think
to
me
I
think
those
type
of
you
know
some
maybe
more
controversial
features
are
things
that
maybe
to
kind
of
keep
the
the
Argo
CD
from
getting
bloated.
I
feel,
like
extensions,
is
like
the
right
mechanism
in
the
future
to
handle
these
type
of
things.
N
N
My
voice
is
quite
loud:
cool
yeah,
workflows
are
usually
easier
for
users
to
use
a
plug-in
is
intended
to
be.
Allow
you
to
avoid
running
pods
effectively
as
part
of
your
workflow.
So
when
a
plug-in
executes
a
task,
it
spins
up
a
single
container,
I
think
that
lives
with
the
Pod
with
the
agent
pod
and
that
container
executes
those
tasks
in
sequence.
So
it
uses
less
resources
than
a
template.
It
doesn't
spin
pods
up
and
down
to
complete
each
task.
N
J
Are
more
things
like
what
floor
template
is
like
a
namespace
code,
cluster
template?
You
can
use
it,
but
you
cannot
give
like
a
privilege
to
that
all
the
namespace
like
accessing
across
the
template.
If
you
install
that
the
plugin
in
your
controller,
it
will
be
available
for
all
the
namespaces
with
the
multi-tenant
organs.
L
N
L
N
L
L
L
L
L
O
I
E
Okay,
yeah
I
can
update
you
about
the
progress,
so
there
is
at
least
look
at
the
plan,
which
is
kind
of
like
struggles
to
execute
it,
but
the
idea
was
that
we
introduced
the
charging,
which
is
a
way
to
try
to.
You
know,
have
many
controller
serving
a
bunch
of
clusters.
It
was
just
scary
to
we
just
learned
that
it's
kind
of
expensive
to
reach
out,
because
every
time
you
change
the
way
you
assign
clusters.
E
In
most
cases,
all
controllers
has
to
stop
and
restart
from
like
from
zero.
That
takes
like
a
couple
minutes.
So
what
we
did
was
we.
We
developed
a
command
that
go
through
all
the
Clusters
and
tries
to
decide.
What's
the
best
way
to
show
it,
and
the
idea
was
to
have
this
shellac
command
available
in
agricity
binary
itself,
and
then
we
were.
E
We
were
hoping
to
offer
people
just
a
call
to
have
a
control
that
you
can
run
the
school
job,
maybe
like
once
a
day
because
class
person
won't
get
edited
frequently,
and
hopefully
the
command
would
just
do
nothing
most
of
the
time.
If
you
add
a
new
cluster,
it
would
be
shared
and
you
know
provide
a
better
balancing,
so
the
current
state
is
this:
pull
request
is
pretty
much
ready
to
get
merged.
It's
just
missing
tests
and
I
guess.
The
main
reason
is
not
that
many
people
in
the
world
need
it
like.
E
O
My
current
problem
is
that
I
have
maybe
like
a
dozen
applications
applicators
and
they
use
a
very
lopsided
amount
of
resources,
because
not
everything
is
balanced.
Equivalently
across
all
the
Clusters,
so
I
have
to
like
I
have
size
them
all
for
the
largest
application
and
I
would
much
prefer
it
if
the
application
controllers
could
balance
among
themselves
what
food
needs
to
be
passed
out
and
also
allow
them
to
scale
up
and
down
dynamically.
Based
on
how.
E
Many
applications
are
running
basically
I.
Think
I
can
just
I
can
promise
to
finally
finish
it
because
it's
so
so
close
to
here
right
here
and
then
as
soon
as
it's
yours,
I
think
you
can
just
give
it
a
try.
You
know
like
you
will
get
so
once
it's
north
there
will
be
an
image
command
and
it's
kind
of
detail
to
use.
You
just
need
to
package
it
into
a
ground
drop
that
has
permissions
to
make
to
manage
status.
It's
also
is
not
safe.
E
It
needs
permissions
just
to
like
if
it's
in
Argo,
CD,
namespace
and
that's
I,
guess
the
biggest
it's
really
difficult
to
test.
If
it
is
used,
you
know
if
it's
effective
or
Not
So
in
theory,
it
should
work.
You
know
if
you
test
it,
that
will
be
a
bit
Yeah
and
then
we
can
document
how
people
should
use
it,
and
we
can
refer
to
your
example
and
say
that
yeah
it
did
help
and
then
another
thing
to
know
about
it.
Currently
it
it
uses.
Basically,
the
first
attempt
to
implement
proper
charging
or
balancing
was
to.
E
You
know
dynamic
programming,
algorithm
that
tries
to
iterate
for
all
possible
ways
to
distribute
clusters
and
and
provide
the
best
one.
It
works
on
like
10
clusters.
If
you
have
like
400
clusters,
it's
it
takes
one
hour
which
it
just
doesn't
worth
it
so
right
now
there
is
a
kind
of
primitive
way.
It
just
tries
to
assign
clusters
and
pick
the
best.