►
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).
B
B
By
taking
a
look
back
at
2021
and
some
statistics
and
milestones
in
terms
of
project
activity,
this
year,
we've
continued
to
maintain
a
really
healthy,
commit
activity
rate
across
a
large
number
of
contributors.
And
when
I
compare
this
to
2020,
the
numbers
are
even
if
not
better
than
the
year
before,
and
also
keep
in
mind.
These
numbers
are
only
counting
the
argo
cd
and
rollout
repos,
but
there
has
been
a
lot
of
additional
activity
happening
in
the
ecosystem
projects.
B
But
the
statistic
that
I
think
we
think
is
most
interesting
and
telling
is
the
number
of
monthly
visitors
to
our
website.
Specifically,
our
documentation,
which
you
can
see
in
this
graph
below
and
the
blue
visitors
are
the
visitors
this
year
and
the
orange
line
is
from
last
year,
and
this
is
showing
that
we're
basically
doubling
the
number
of
visitors
to
our
website
year
over
year,
and
I
interpret
this
as
like
we're
gaining
actual
users
who
are
really
using
the
product.
B
But
we've
also
added
a
really
a
bunch
of
great
features,
including
like
a
ui
dashboard,
which
you
can
access
using
either
the
cli
or
you
can
run
it
actually
as
a
service
in
your
cluster
there's
a
alternative
way.
You
can
run
rollouts,
which
we
called
workload
references
and
the
idea
behind
this
is
that,
instead
of
replacing
your
deployment
object,
you
can
reference
something
existing,
and
this
just
provides
a
different
way
for
users
to
maybe
transition
to
rollouts.
B
B
And
if
you
haven't
been
keeping
up
we're
about
to
release
argo
cd,
2.2
and
one
of
the
major
highlights
of
this
release.
Is
that
there's
a
new
better
way
for
operators
to
plug
in
their
own
configuration
management?
Tooling?
And
if
you've
ever
tried
using
the
the
1.0
feature
of
config
management.
Plug-Ins
you'll
know
it's
a
little
bit
clunky
to
configure,
and
so
we
improved
this
so
that
plug-ins
are
really
just
container.
A
B
B
B
All
right,
so,
let's
see
what
we
have
in
store
for
2022.,
going
back
to
rollouts,
and
one
thing
that
we've
kind
of
realized
is
that
it
takes
a
lot
for
organizations
to
get
to
that
final
state
of
doing
progressive
delivery,
and
we
think
we
can
make
this
a
lot
easier,
which
I
call
our
goal:
robots,
enablement
and
one
feature
along
those
lines
which
you
can
look
forward
to
in
the
next
rollouts
102
releases.
The
ability
to
dry
run
your
analysis.
B
Using
this
feature,
you
can
perform
an
analysis
as
part
of
your
update,
but
it's
result.
It's
success
and
failure
is
not
actually
going
to
abort
your
rollout.
It's
just
kind
of
like
a
practice,
run
to
see
how
what
your
analysis
would
have
done
and
so
lets.
You
fine
tune
it
before
turning
it.
On
the
second
thing,
I
think
we
could
do
better
is
providing
users
with
a
catalog
of
analysis
templates
that
work
with
the
popular
ingress
controllers
in
service
meshes.
A
B
Comprehensive
guide
of
you
know
best
practices
and
patterns
and
strategies
on
how
to
implement
progressive
delivery
at
the
organization.
I
think
some
literature
around
that
would
be
helpful
and
finally,
we
could
use
some.
You
know
better
tooling,
to
help
users
migrate
to
rollouts.
For
example,
one
idea
that's
been
floating
around
is:
maybe
we
have
a
conversion.
A
B
But
one
development
in
particular,
which
excites
me
is
the
upcoming
kubernetes
gateway
api,
which
is
often
referred
to
as
kubernetes
ingress
v2
and
the
problem
is
today
anytime.
We
want
to
support
a
new
ingress
controller
or
mesh.
We
have
to
implement
a
vendor-specific
integration,
and
this
requires
us
to
like
understand
their
specific
crds
and
but
with
the
kubernetes
gateway
api.
B
B
Earlier,
I
mentioned
all
the
ecosystem
add-ons
that
are
available,
but
today
the
problem
is
that
it's
still
a
burden
on
the
operator
to
correctly
piece
together
all
of
these
projects
into
their
installation
and
now
that
these
projects
are
beginning
to
mature.
It's
now
time
to
start
thinking
about
how
to
merge
these
into
the
argo
cv
upstream,
so
either
they're
part
of
the
default
installation,
just
part
of
the
vargo
z
core
or
at
least
they're,
easily
enabled
so
that
you
operators
don't
have
to
worry
about
compatibility.
B
So
I've
been
with
the
argo
project
for
four
years
now,
and
argo
has
basically
had
the
same
kind
of
look
and
feel
for
those
four
years
and
it's
pretty
due
for
a
ui
refresh
and
so
right.
Now,
there's
a
lot
of
effort
happening
right
now
on
how
on
updating
the
component.
Libraries
do
something
more
modern,
and
so
you
can
look
forward
to
kind
of
a
refresh
in
the
look
and
feel
in
terms
of
usability
of
fargo
city.
B
B
And
so
now
we
get
to
some
of
the
even
more
forward
thinking
looking
things
which
I'm
personally
excited
about.
As
I
mentioned
earlier,
we
have
these
mechanisms
to
extend
argo
cd
and
start
customizing,
your
installation
and
starting
with
the
d2
config
management
plug-ins.
I
really
think
we
can
start
building
this
ecosystem
and
and
catalog
of
argo
cd
plug-ins,
which
can
be
then
shared
amongst
the
community.
B
So
maybe
you
know
there'll
be
a
grafana
tonka,
config
management,
plugin
that
is
maintained
by
the
grafana
team
or-
and
we
think
also
this.
The
same
could
happen
for
resource
extensions.
Today
we
have
this
reference
implementation
for
the
argo,
rollout
ui,
but
there's
nothing
stopping
you
know
the
community
to
start
developing
these
new
ui
extensions
for
all
other
kinds
of
custom
resources,
and
so,
if
you
want
to
get
involved
in
the
argo
project,
a
really
great
way
would
be
to
start
contributing
plug-ins
to
the
ecosystem.
B
Okay-
and
this
is
just,
I
think,
there's
a
lot
more
potential
to
do-
we
can
do
with
extensibility
and,
for
example,
this
is
just
we
want
to
do
things
like
sidebar
extensions.
If
you
want
to
extend
the
ui
in
different
ways
or
even
application
level,
ui
extensions
or
maybe
even
just
deep,
linking
to
specifics
about
the
infrastructure,
all
right,
so
I
think
we're
about
time
and
I'll
stick
around
in
the
chat
for
questions.
Thanks.
C
Yeah,
that
was
great
jesse
and
there
are
a
lot
of
questions
for
you
if
you
go
back
to
the
general
chat
or
meet
them
in
the
cncf
slack
channels,
if
you
haven't
already
filled
out
the
survey
and
give
feedback
to
us,
so
we
can
start
building
22
and
understand
how
you're
using
argo.
Please
do
that
now.
Thank
you.
So
much.