►
From YouTube: Argo CD and Rollouts Community Meeting May 2022
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
All
right
welcome
everybody
to
the
may
2022
argo,
cd
and
rollouts
community
meeting.
I'm
your
host
for
today
jesse
soon
and
today's
agenda
will
be
looks
like
it's
pretty
light
alex
will
be
going
over
the
upcoming
argo
cd
2.4
release
and
before
we
get
started
just
a
reminder
that
the
argo
project
adheres
to
the
cncf
code
of
conduct.
A
So
please
be
courteous
and
respectful
during
this
meeting
and
also
please
note
that
this
meeting
is
being
recorded
and
will
be
uploaded
to
youtube
afterward
and
also,
if
you
do
have
any
agenda
items
or
issues
or
discussion
topics,
please
feel
free
to
add
them
to
the
the
google
google
doc
and
we
can
address
them
after
the
presentations
all
right.
So
our
first
agenda
item
is
actually
going
over
the
2.4
release
and
alex
has
prepared
a
short
kind
of
presentation
about
this
alex
yeah.
Thank.
B
You,
okay,
so
yes,
I'm
alex
and
I'm
a
software
engineer
and
actually
architect
at
acuity,
and
I,
as
jesus,
has
prepared
a
presentation
about
release.
Let
me
start
from
sharing
my
screen.
B
Okay,
and
can
you
please
confirm
you
can
see
it
yep
awesome.
Thank
you
all
right.
So,
as
you
know,
we
are
trying
to
relate
rbcd
every
three
months
and
it's
it's.
It's
been
around
three
months
since
we
released
2.3
release
so
just
time,
just
the
right
time
to
release
the
next
one,
and
I
want
to
start
from
just
giving
you
a
short
summary
of
what
was
of
the
number
of
changes
that
we
developed.
So
we've
got
around
300
commits
from
88
contributors,
and
this
is
we're
very
consistent.
B
We
get
around
that
number
of
commits
every
release
and
I
want
to
start
from
saying
thank
you
to
everyone
who
contributed
and
helped
to
get
us
to
this
to
this
point
and
develop
the
trellis,
and
so
in
those
300
commits
we've
got
around
20
features
and
41
bug
fix
and
a
lot
of
documentation,
improvement,
which
I
didn't
code
here,
and
we
also
had
three
major
features
that
I
want
to
cover
today
and
I
want
to
start
from
one
feature
that
was
anticipated
by
many
users.
B
B
They
can
get
detailed
information
about
some
resources
and
if
the
resource
happens
to
be
bought,
it
is
possible
today
to
get
the
live
logs
of
containers
emitted
by
containers
in
the
port
and
starting
with
2.4
release.
It
is,
it
will
be
possible
to
actually
get
ssh
access
to
the
port
right
from
the
web
user
interface,
and
this
feature
is
very
like
it's
really
interesting
to
see
it
in
action
and
that's
why
I
decided
to
just
quickly
show
it
to
you.
B
So
let
me
exit
the
full
screen
and
quickly
switch
to
the
argo
cd
instance
that
I
run
locally,
and
so
this
is
the
application
details
page
that
I
described
just
now,
and
I
have
a
port
here
and
so
to
use
that
feature.
You
just
need
to
click
on
any
port
in
your
application
and
you
will
get
a
new
tab
called
terminal,
and
so,
if
you
click
on
terminal
tab,
it
immediately
starts
basically
exec
into
the
port
into
the
first
container.
You
should
be
able
to
select
from
the
containers
list.
B
If
you
have
many
containers
and
that's
it
basically,
you
can
just
run
any
command.
You
can
explore
the
file
system.
You
can
read
files
like
I
just
did
so
it's
a
fully
functional
terminal,
and
hopefully
it
will
be
very
useful
to
to
many
engineers-
and
we
are
very
quite
excited
about
that
feature
and
let
me
switch
back
to
the
presentation.
B
B
In
which
order
shells
are,
you
know,
being
being
choose
and
another
information
about
that
feature
that
worth
knowing
is
that
it
leverages
web
circuits
and
that
makes
applies
some
restrictions.
Basically,
if
you're
exposing
argo
cd
behind
the
load
balancer,
it
needs
a
web
socket
connection,
and
hopefully
it's
not
a
big
problem.
Most
of
the
modern
load
balancers
supports
web
circuit,
but
just
be
aware
of
it.
B
The
web
sockets
must
be
enabled,
and
last
but
not
least,
I
want
to
thanks
ben
why,
from
from
by
dance
and
his
colleagues
who
developed
that
feature
and
yeah,
that's
a
really
great
contribution,
and
I
see
some
chat
messages.
I
believe
we
will
address
it
shortly.
Okay-
and
there
is
a
question
from
from
then
about
arbuck,
it's
a
very
good
question
and
I
am
going
to
talk
about
it
in
the
next
slide.
So
both
features
both
logs
and
the
new
web
terminal
feature
definitely
give
a
lot
of
power
to
developers.
B
We
heard
about
it
from
the
community
about
logs
and
that's
why,
in
the
new
version,
we
are
introducing
a
role-based
access,
control
rules
that
cover
logs
and
the
web
terminal
feature,
so
basically
that
this
little
gamble,
snippet
kind
of
gives
you
a
high
level
understanding
of
how
those
rules
are
going
to
look
like.
Basically,
we
are.
B
Hopefully
you
can
see
the
flag
name
on
my
screen
and
that
this,
so
there
is
a
new
flag
in
the
argo
cg
cm
config
map.
Yes,
so
to
start
leveraging
rbac
for
logs.
You
must
set
this
flag
to
true
for
a
web
terminal.
Basically,
it's
available
by
default
and
I
believe
in
the
next
version
we're
going
to
switch
default
for
logs
to
true
as
well.
So
everyone
will
get.
B
You
know
our
bug
kind
of
enabled
out
of
the
box
yeah
and
that
feature
was
developed
by
regina
thanks
a
lot
to
jenna
for
building
it
and
for
going
through
the
review
process.
B
Oh
sorry,
for
yeah
for
for
peer
review,
okay.
Hopefully
that
answer
the
question
about
role-based
access
control
and
I'm
ready
to
move
on
to
the
next
one.
So
a
next
few
changes,
hopefully
a
good
news
for
argo
cd
operators.
B
So,
basically,
if
you
are
running,
if
you
are
an
operator
who
run
a
big
argo
ct
installation
that
manages
thousands
of
applications,
you
will
have
to
you
know
fight
your
fine
tune,
resources
of
your
argo
cd
instance.
You
might
have
to
give
more
memory
more
cpu
and
you
really
need
visibility
to
see
if
the
changes
that
you're
making
helping
to
improve
performance.
B
B
Yes,
and
that
feature
was
developed
by
ben
from
binance
again,
which
is
awesome
thanks
a
lot
ben
for
staying
for
the
very
useful
contribution
right.
The
next
change,
the
next
big
change.
I
would
say
that
we
are
making
is
again
a
good
news
for
argo
cd
operators.
So
we
are
expanding
a
list
of
supported
architectures.
B
So
starting
from
2
to
4,
you
can
run
argo
cd
on
a
power
pc
and
ibm
x,
and
that
feature
is
that
the
very
last
commit
that
introduced.
It
is
not,
maybe
so
big,
but
it
took
a
lot
of.
It
took
us
a
lot
of
preparation
to
get
rid
of
all
the
possible
all
the
binaries
that
were
bundled
to
reduce
the
number
of
binaries
that
we
bundle
into
argo
cd
image,
so
that
made
it
possible
to
actually
support
additional
architectures
and
a
nice
additional
side
effect
is
the
image
size
was
reduced
significantly.
B
So,
on
the
on
the
right
side
of
this
slide,
you
can
see
a
screenshot
of
the
most
recent
state
of
our
clay
repository.
So,
as
you
can
see,
we
have
now
four
tags
and
each
image
is
around
120
130
megabytes
before
it
was
close
to
175
megabytes,
so
we
reduced
the
image
size
significantly
and
that
the
feature
the
feature
that
actually
introduced
the
additional
architectures
came
from
external
contributor
again.
B
B
A
I
just
want
to
answer
the
question
from
sri
about
the
you
had
a
question
about.
If
the
terminal
is
blocked
on
the
cluster,
what
would
be
the
argo
cd
behavior
for
the
the
terminal
feature
so
well?
I
think
I
know
the
answer,
but
maybe
you
can
answer,
but.
B
Okay,
yeah,
I
basically
I
didn't
think
about
yeah.
I
I'm
not
sure
if
I
have
the
best.
You
know
if
I
know
the
right
answer,
but
I
believe
if
terminal
is
blocked,
argo
cd,
will
you
know
it
will
act
like
an
any
other
terminal?
You
will
just
you
know
you
won't
be
able
to
type
anything,
but
as
soon
as
you
close
the
terminal,
you
know
argo
cd
will
close
the
connection
and
it
will
basically
the
binary
will
die
in
the
kubernetes
itself.
So
it
should
not.
A
Right,
so
I'm
not
sure
if,
if
it's,
if
they're
blocking
it
through
just
normal
kubernetes
are
back
then
no,
I
don't
know
the
answer
like
it
depends
on
how
they're
blocking
it.
If
it's
normal
could
use
the
exact
blockage,
I
don't
know
like
kyren
or
is
doing
something
magical.
B
C
B
It
is
blocked
by
kubernetes
yeah.
You
will
just
get
an
error
message.
I
guess
saying
that
yeah,
it
is
blue.
A
But
if
they're
blocking
it
through
some
more
trickier
ways
like
I
know
blocking
system
calls
at
the
os
level
or
something
then
then
I
think
it
basically
has
the
same
exact
behavior.
It
keeps
you
feel
exact
because
that's
what
is
leveraged
in
the
implementation.
B
Okay,
yeah-
and
I
wanted
to-
I
noticed-
a
comment
from
from
michael,
so
he
mentioned
that
that
the
snippet
here
is
not
actually
accurate.
So
we
are
changing
the
verb
that
you
have
to
give
from
for
exact
from
get
to
create,
because
this
is
what
is
in
the
kubernetes
and
so
michael
improving
it
to
to
make
it
consistent
with
the
kubernetes
arbuck
yeah.
B
Thanks,
michael
all,
right,
I
so
any
questions
about
images
and
platforms.
D
Yeah
the
tilex
one
question
on
the
terminal
thing
so,
for
example,
if
the,
if
the
pod
the
container
running
inside
the
pod,
doesn't
have
any
terminal
available
like
distress
or
anything
like
that,
what
will
be
the
behavior?
I
guess
that
will
try
to
call
that
binary
inside
the
container.
B
Correctly,
our
literally
trying
to
guess
the
thrill
starting
from
the
most
advanced
ones
it
if
it
gets
nothing
it
it's.
You
know
the
ui
will
show
an
error
message
saying
that
sorry,
no
shells
available
okay,
yeah
and
I
I
know
that
I
think
it's
a
basically
we
can-
that
feature-
can
be
improved
in
the
future
right
now.
The
api
itself
allows
you
to
just
specify
the
shell.
You
need,
and
we
just
don't
have.
We
didn't
think
about
user
experience
for
that
and
definitely
can
be
done
as
improvement.
B
Okay
right,
this
is
actually
the
last
big
feature
and
I
still
I
have
one
more.
Oh
sorry,
yeah
yeah.
I
have
a
slide.
I
I
that
the
full
list
includes
around
20
features
and
it
was
just
impossi
impossible
to
list
all
of
them.
So
I
just
prepared
a
short
sample
of
other
notable
contributions
that.
B
Useful
for
you
know
for
for
every
rc
user,
and
you
will
find
more
information
in
that
release
blog,
but
this
is
the
sample.
Just
you
know
to
to
to
say
thank
you
for
people
who
contributed
the
changes.
So
we've
got
several
interesting
contributions.
One
is
ability
to
disable
deployment
to
the
control
plane
cluster.
That's
the
important
feature
for
installations
where
argo
cd
is
used
mostly
to
develop,
to
deploy
two
remote
clusters
and
control
plane.
B
B
If
you're
managing
gke
cluster,
we
had
support
for
aws
and
a
lot
of
people
use
it
for
aws,
and
a
lot
of
users
wants
to
get
the
same
feature
for
gk
clusters
in
google
cloud.
So
now
it
is
possible.
You
can
craft
a
declarative
definition
of
this
cluster
secret.
B
B
Next
improvement
is
again
for
operators
who
uses
maybe
managed
basically,
who
run
radius
themselves
and
typically,
that's
the
managed
radius
in
the
cloud,
and
now
it
is
possible
to
get
to
secure
that
connection
between
argosy
and
regis,
using
username
and
password,
and
in
that
release.
We've
merged
application
set
code
into
the
rvcd
itself.
Now
the
changes
in
applications
that
are
more
visible-
and
this
is
one
of
such
changes.
B
B
B
Both
tools
were
deprecated
long
time
ago,
probably
two
or
three
releases
ago
and
specifically
customize
is
pretty
much
dead
for
a
couple
years,
and
now
we
are
removing
both
tools
from
argo,
cd
yeah,
so
just
be
aware
of
it,
and
this
is
it
that's
the
end
of
presentations,
presentation
yep
feel
free
to
ask
any
questions.
If
you
have
any.
A
Thank
you.
Any
questions.
People
have
in
the
room
about
the
argo
cd
2.4,
either
with
alex
showed
or
in
general.
B
Oh,
thank
you.
Yes,
so
the
plan
so
far
is
to
basically
discuss
it
tomorrow
with
contributors.
I
know
we
have
few
peers
already.
That
has
to
be
that
are
waiting
to
be
merged,
but
those
pairs
will
be
merged
most
likely
today.
Tomorrow.
We're
going
to
give
another
call
ask
every
contributor
if
they
really
want
to
get
something
in
before
the
release,
and
hopefully
if
we
don't
find
anything
blocking,
we
can.
We
can
create
a
list
candidate
tomorrow
as
well,
and
then
let
and
then
typically
we.
A
Great
yeah,
I
echo
dan
sentiment
great
work.
Everyone
on
on
this
release,
yeah,
it's
actually.
When
I
like
to
compile
the
list,
I
was
like.
Well,
that's
actually
impressive
list
of.
A
That
was
done
in
just
a
short,
a
short
period
of
time,
so
yeah
thanks
everyone
all
right,
any
after
topics
you
know,
and
just
our
grocery
rollouts
in
general.
You
know
not
necessarily
related
to
2.4
that
people
have.
C
C
Yeah
sure
so
the
rollouts
extension
right
there
is
a
file
given
extension.power
file
to
be
specified.
So
in
our
organization
we
cannot
store
our
files
in
the
github.
So
we
want
this
one
to
be
this
to
be
placed
in
the
nexus
and
read
it
from
there,
but
in
the
manifest
we
don't
see
any
provision
to
specify
the
secret
to
get
it.
From
the
I
mean
nexus.
A
So,
oh
okay,
so
the
the
limitation
is
that
you
want
this
to
be
behind
some
password
protected
http
server
and
the
the
implementation
doesn't
provide
a
way
to
specify
like
the
fact
that
this
can
be
extracted.
C
A
I
think
this
is
a
current
limitation,
but
I
can
suggest
a
workaround,
so,
at
the
end
of
the
day,
extensions
are
basically
taking
this
tar
ball
and
extracting
it
to
some
some
subdirecting
in
there
like
tmp,
that
just
kind
of
holds
it
in
a.
I
think
in
a
convention
format
that
I
I
alex
might
know
better
and
so.
A
I
believe
it
should
be
possible
to
to
work
around
this
limitation
by
extracting
it
yourself,
either
as
a
in
the
container
that
extracts
it
beforehand
and
then,
as
long
as
the
file
is
in
place
by
the
time
argo
cd
server
is
running,
the
extension
will
work.
So
it's
not
a
solution.
I
mean
it's
a
workaround
to
this
limitation,
but
it's,
I
think
the
proper
solution
is
that
we
support
credential
based
access
to
http
servers.
B
Yeah,
I
I
think
I
will
I
will
comment
on
the
ticket
and
I
will
just
provide
you
exact
instructions
to
kind
of
unblock
you
quickly
and
also
I'm
going
to
move
the
ticket
from
reload
extension
into
another
repository,
argo,
cd
extensions.
Basically,
we
have
two
repos
and
a
reload
extension
is
an
implementation
of
rollout
specific
and
the
other
repo
I
put
it
in
in
in
the
chat,
argo,
cd
extensions.
This
is
like
a
proper
place,
so
yeah
I
it
will
increa.
B
A
By
the
way,
does
anyone
happen
to
know
if
we
have
the
same
limitation
for
git
access?
Do
you
do
do
we
support
credentialed
access
for.
B
I
don't
think
spec
has
it
right
now.
I
think
we
spoke
about
it.
We
have
room
for
the
spec
and
then
we
and
internally
it
uses
go-getters.
So
there
is
no
problem
too.
Basically
the
backend
supports,
but
we
expected
that
most
likely
extensions
will
be
available
externally.
So
we
didn't
know
anyone
is
going
to
yet.
So
basically
short
answer
is
no.
I
mean
git
right
now
do
not
support
credentials,
it
has
the
same
problem
and
but
it's
really
easy
to
edit
to
add
support
for
conditions.
C
Thank
you,
so
I
mean
do
we
have
a
plan
in
queue
to
I
mean,
provides
sometime
in
future
right,
yeah.
B
And
then
just
to
clarify,
like
aggressive
extensions,
is
not
tied
to
argo
cd
release
cycle
this.
The
project
this
project
can
move
much
quicker,
yeah
and
so
pretty
much.
A
Release
process
from
argo
cd,
so
what
alexis
is
saying
like
if
this,
if
it
gets
fixed
earlier,
then
you
know
three
months
from
now,
then
you
know
it's
not
like.
You
have
to
wait
until
then
for
it
to
be
fixed,
like
you
can
build
from
tip
and
then
run
the
the
fixed
version.
B
I
I
want
to
just
yeah.
I
promise
to
continue
discussion
in
the
issue
itself
like
I
will
provide
a
workaround.
Hopefully
it
will
unblock
you
immediately
and
then
I
will
learn
from
you
as
well.
We
can
document
the
requirements
kind
of
more
carefully
yeah.
You
should
be
able
to
move
it
right
now.
It's
our
cd
extensions.
B
By
the
way,
rollout
extensions
just
got
a
recent
release,
so
it
was
updated
to
use
our
gorilla
1.2.
You
know
use
interest,
oh
okay,
yeah
good.
I
think
it
was
done
like
last
week.
C
Just
one
last
thing
I
think
kendrick
for
the
chat
as
well.
So
are
we
actually
trying
to
release
as
a
pot
of
cube
corner?
Is
it
bit
tight.
B
A
A
The
incoming
bugs
after
the
rc's
are
out
to,
if
there's
you
know,
important
fixes
that
need
to
just
be
in
there
before
we
make
a
g8
and
then
that's
takes
priority
and
then
keep
on.
A
But
for
sure
I
think
the
the
announcement
of
like
rcs
should
happen
before
coupon.
I
agree.
A
All
right,
so
I
think
that's
it
for
today.
E
I
added
one
thing:
just
for
those
that
are
available
to
attend.
Argo
contributor
summit
is
on
the
monday
of
kubecon.
I
put
a
link
in
to
register.
I
think
it's
almost
full.
We
have
a
few
presentations
planned
if
you're
interested
in
potentially
pr
presenting
at
that.
Please
let
me
know
just
hit
me
up
on
slack.
E
A
Thank
you
dan,
and
the
link
that
he
mentioned
is
in
the
the
doc
the
shared
google
doc.
So
you.
A
A
All
right,
I
think,
that's
it
for
today.
Thank
you,
everyone
for
attending
this
month's
community
meeting
and
like
always,
we
have
weekly
contributors
meetings
on
thursdays
and
the
workflow
meeting
will
be,
and
a
community
meeting
will
be
in
two
weeks
all
right.
Thank
you.
Everyone
have
a
nice
day.
A
I
think
I
think
the
the
workflowment
is
probably
gonna
be
canceled.