►
From YouTube: CNCF SIG App Delivery 2021-03-17
Description
CNCF SIG App Delivery 2021-03-17
A
B
B
C
A
So
yeah
then
device
for
today
we
have
three
main
topics
update
from
the
operator
working
group,
especially
on
the
white
paper
around
operators-
cornelia,
I
also
reserved
once
not
for
the
github
working
group
in
case
you
want
to
share
something.
Obviously,
there's
the
the
voting.
That's
going
on
that
you
posted
on
the
mailing
list
and
then.
B
A
The
argo
project
update
presentation
for
for
today
I
think
we
should
be
fine
timing
wise,
given
that
for
about
20
minutes.
A
A
D
This
is
my
first
time
going
to
one
of
these
meetings.
My
name
is
matt
clark
and
I'm
a
senior
engineer
in
spotify
in
the
deployments
team.
So
we
manage
all
of
our
deployment
infrastructure
tools
and
yeah
nice
to
be
here.
E
B
Hi,
I'm
regina,
I'm
I
work
at
red
hat
also
with
dejuan
too.
We
use
our
go
cd
so
here
to
watch
their
pitch.
So
thanks
nice
to
be
here.
E
A
That
all
right,
it's
five
minutes
past
the
hour.
So
let's
get
started
here.
First
up,
that's
always
a
quick
update
from
the
operator
working
group.
I
think
you
have
some
exciting
news
to
share.
F
Okay,
yes,
so,
let's
start
just,
let
me
share
my
screen.
F
Okay,
so
can
anybody
hear
me
hopefully?
Yes,
I'm
perfect,
so,
yes,
we
have
exciting
news,
so
we
are
about
to
to
get
our
first
draft
done.
F
So
currently,
the
last
pull
requests
are
getting
into
our
repository.
We
are
currently
reviewing
everything
and
yes,
what
did
we
want
to
achieve
with
our
with
our
white
paper,
so
the
reader
should
get
an
idea.
What
an
operator
is
we
wanted
to
find
use
cases
for
an
operator
so
as
an
end
user,
we
wanted
to
describe
what
an
operator
could
do
for
an
end
user
so
which
tasks
could
an
operator
fulfill
and
yes,
how?
F
How
could
he
be
supported
by
this,
but
also
for
a
developer,
which
things
could
I
provide
with
an
operator
so
which
capabilities
could
an
operator
have
and
yes
to
get
and
to
get
really
an
idea
what
an
operator
can
provide
for
for
anyone?
F
We
also
wanted
to
create
some
awareness
for
the
security
of
operators,
so
there
were
such
things,
which
were
already
defined
better
by
the
security
working,
especially
in
tourist
group
in
the
white
people,
but
we
also
tried
to
describe
what
what
wouldn't
operate.
F
F
F
So
how
will
this
will
the
table
of
content?
Look
like
so
we'll
have
an
executive
summary,
not
not
really
surprising,
which
will
be
finished
after
the
after
the
comment
period.
F
We
have
some
foundation
topics,
so
we
described
what
an
operator
is,
how
a
design,
how
the
design
pattern,
not
only
what
you
need.
This
control
operators
could
look
like,
and
we
also
described
the
design
pattern
on
the
on
an
example
of
kubernetes
control
of
kubernetes.
F
Then
we
described
some
capabilities,
so
there
were
some
capabilities
which
are
pretty
obvious,
such
as
installing
and
upgrading.
In
some
points
we
have
such
things
as
auto
remediation
and
what
what
you
can
think
of,
but
we
didn't
want
to
use
the
capability
model,
which
is
sorry,
the
maturity
model
which
is
currently
more
or
less
the
standard.
For
this
we
wanted
to
get
more
in
a
capability
based
way
to
not
say
that
an
operator
which
has
a
kind
of
a
capability
is
more
mature
than
another
one,
because
this
must
not
be
the
case.
F
Yes,
then
we
described
some
some
the
security
and
risks.
As
I
said
before
in
this
place,
I
want
to
thank
the
seek
security.
If
someone
is
there
because
they
wrote
it
afterwards,
we
described
some
kind
of
operator
framework.
So
currently,
I
think
we
have
the
cube
builder.
We
have
the
operator
framework.
We
have
to
meet
the
controller
and
I
think
we
have
kind
of
cop
there.
F
F
Yes,
we
tried
to
add
some
use
cases
such
as
we
had
we
had.
We
had
one
use
case
for
key
tops,
for
example,
because
this
could
also
be
a
task
of
an
operator,
but
we
also
have
a
simple
use
case
on
on
top
of
the
of
the
prometheus
operator,
and
we
are.
We
are
also
trying
to
find
some
additional
use
cases
until
the
final
publishing.
F
We
define
some
best
practices,
but
we
also
get
this
from
the
from
the
currently
literature
and
at
least
last
but
not
least,
we
summarized
up,
and
yes,
this
was
it
more
or
less
so
we
had
some
related
work,
because
there
is
a
lot
of
further
reading
about
operators
and,
last
but
not
least,
we
have
the
country
we,
we
spent
the
section
for
the
contributors
so
that
everybody
gets
the
credit
he
he
deserves.
F
Yes,
but
now
it's
your
turn.
So
currently,
after
all,
pull
requests
are
there
and
accepted,
which
will
be
most
probably
tomorrow.
F
We
will
open
one
pr
with
a
with
a
really
large
document
which
will
include
all
of
the
all
of
the
sections,
and
then
we
hope
that
every
one
of
you
reads
this
document
and
if
you
have
some
comment,
suggestions
or
something
which
is
not
really
in
the
document
at
the
moment-
feel
free
to
open
a
pr
make
comments
or
suggest
something.
On
the
on
this
pull
request.
F
If
there's
something
to
change,
we
will
coordinate
this
with
our
origin
authors
and
if,
if
these
are
really
really
simple
changes,
we'll
make
the
changes
by
ourselves
and
the
color.
This
review
phase
will
end
on
the
first
april
and
this
is
no
joke.
So,
yes,
and
afterwards
after
this
color
review,
we
will
write
the
executive
summary
around
this
or
around
this
up
and
try
to
get
this
published.
F
So,
yes,
this
was
our
update.
Are
there
any
questions,
comments
and
so
on
from
your
site?
F
Can
you
send
it
out
to
the
mailing
list
once
you've
done
the
merging?
Yes,
so
we
will
do
the
we
will
send
it
out
in
the
mailing
list.
We
will
send
it
out
on
slack
on
twitter
and
wherever
so.
We
want
to
get
as
many
comments
as
possible
from
as
many
people
as
possible.
A
Topics-
okay,
girls,
looking
forward
to
it,
so
we
have
something
with
the
white
audience
to
share.
Then
I
would
now
pass
over
to
the
githubs
working.
G
Group
cool
well,
that
is
a
hard
act
to
follow.
I
do
not
have
a
grand
announcement
of
like
principles,
document
being
published
or
anything
like
that,
but
I
will
give
you
sorry.
The
sun
just
came
through
my
window.
I
will
give
you
a
an
update.
We
have
been
busy
nonetheless,
so
one
of
the
main
things
that
we're
working
on
one
of
the
first
things
we're
working
on
in
the
get
ups
working
group
is
the
get
ops
principles
document.
G
G
We
are
also
scheduling
some
synchronous
sessions
with
the
to
work
on
the
principal's
documents,
so
there's,
of
course,
a
lot
of
value
in
doing
things
from
an
asynchronous
perspective,
but
then
there's
also
you
can
push
things
forward
more
quickly
with
the
synchronous.
We
will,
of
course,
record
those
sessions
and
reflect
anything.
That's
done
in
the
synchronous
sessions
will
be
reflected
back
into
the
git
repository
for
those
of
you
who
cannot
participate.
A
A
You
get
them
on
the
ctf
calendar
because
it
might
be
easier
for
people
to
win.
G
And
they
are
for
those
of
you,
you
know
until
we
have
something
in
the
calendar,
you
can
find
those
things
discussed
in
the
slack
channel.
So
do
take
a
look
at
the
slack
channel
and
you
can
find
out
when
you
can
join
those
things.
G
I
do
not
have
at
this
point
a
a
set
of
milestones,
so
I
cannot
tell
you
I
mean
we
are.
I
can
give
you
an
order
of
magnitude.
G
We
are
not
looking
to
publish
the
principles
a
year
from
now
we're
looking
to
publish
them
closer
to
a
month
from
now
and
then
of
course
iterate
on
them,
so
whether
it
ends
up
being
a
month
or
two
months.
I
don't
know
yet
and
we
will
see
about
maybe
getting
a
calendar,
I'm
inspired
by
what
you
just
did
thomas
in
describing
the
schedule
for
your
the
white
paper.
G
The
second
work
stream
that
we're
working
on
is
a
website
workstream.
So
to
really
start
to
kind
of
articulate
and
gather,
you
know
links
and
things
like
that.
That's
been
a
little
bit
slow
getting
going,
but
we
do
have
a
number
of
individuals
who
have
volunteered
for
that
work
stream.
G
The
newer
work
streams
since
two
weeks
ago
is
that
the
get
ops
working
group
is
going
to
be
putting
on
a
zero
day
event
at
kubecon,
the
the
upcoming
kubecon
in
may.
I
think
it
is,
and
that
is
we're
doing
a
get
ops
con.
G
It
is
being
co-sponsored
by
red
hat
and
weave
works
simply
from
the
mechanics
perspective.
So
red
hat
is
in
fact
going
to
be
providing
all
of
the
infrastructure
for
the
streaming,
and
you
know
the
platform
for
putting
on
the
event
and
is
working
together
with
we've
worked
on
kind
of
putting
together
the
materials
from
a
marketing
perspective
and
so
on,
and
then
in
terms
of
the
the
event
itself.
That
is
very
much
going
to
be
run
by
the
get
ups
working
group.
G
We
have
about
three
people
who
have
volunteered
to
help
with
that.
We
are
putting
together
a
schedule
where
we
are
going
to
be
issuing
a
call
for
papers.
I
think
that's
going
out
today,
or
maybe
already
did.
We
will
have
about
three
weeks
of
allowing
folks
to
provide
their
submissions
to
that.
Then
we'll
have
about
a
week
of
selecting
from
those
submissions.
G
So
you
can
see
that
it's
very
much
a
community
event.
This
election
is
going
to
be
done
by
that
work
stream.
That's
selecting
the
the
talks
for
that.
We're
aiming
for
about
a
four
or
five
hour
event,
including
some
social
time
and
kind
of
hallway.
We'll
do
our
best
to
have
a
bit
of
a
hallway
track
within
that,
and
then
we'll,
of
course,
publish
the
this
schedule,
and
it
will
be.
G
I
we,
I
believe,
are
not
going
to
be
charging
anything
for
this,
so
anybody
who
wants
to
participate
can
sign
up
through
their
kubecon
registration,
so
it
it.
G
I
don't
know
if
it's
already
there,
but
they
should
be
showing
up
as
the
list
of
zero
day
events
that
you
can
sign
up
for
and
then
finally,
you
mentioned
eloise
when
we
first
came
on
that
some
of
you
may
have
noticed
if
you're
paying
attention
to
the
mailing
list
for
the
sig
app
delivery
is
that
we
are
in
the
process
of
electing
co-chairs
for
the
get
ops
working
group.
G
It
doesn't
mean
that
the
co-chairs
do
all
of
the
work,
but
we
do
want
the
co-chairs
to
have
enough
domain
knowledge
to
be
able
to
help
coordinate
the
different
work
streams,
keep
things
moving
forward
and
those
types
of
things
that
the
nominations
for
the
co-chairs
closes
at
midnight
friday
night,
so
11
59
p.m.
Friday
night,
then
we'll
have
a
one-week
voting
period
and
then
we
will
announce
the
co-chairs.
A
That
is
actually
a
lot
going
on
there.
It's
great,
so
I
I
thought
that
two
people
already
brought
back
on
the
the
co-chairs
like
what
we
also
try
to
generally
do
now,
more
especially
in
the
app
delivery,
but
overall,
so
hopefully
we'll
also
find
some
end
users
or
people
from
ending
the
companies,
obviously
to
join
in
as
well.
So
maybe
strongly
encourage
somebody
there
to
participate.
A
A
I
Give
me
a
thumbs
up.
If
you
see
the
see
my
screen
perfect,
see
ya,
perfect
thanks
everyone,
so
hi
everyone.
My
name
is
henry
blixt,
I'm
a
product
manager
at
inted.
I
was
going
to
give
a
fairly
quick
update
on
where
we're
at
with
with
the
graduation
that
we
filed
for
the
pr
I
think
was
filed
submitted
a
few
weeks
ago
now,
I'm
gonna
give
a
shout
outs
to
all
the
contributors
and
and
users
and
vendors
that
have
helped
get
us
to
this
point.
I
So
just
a
argo's
been
around
now
for
a
while,
but
I
wanted
to
take
you
know
a
minute
or
so
just
to
give
a
quick,
quick
overview
of
where
we're
at
and
where
we've
been
so
far.
So,
as
you
probably
know,
argo
is
a
set
of
kubernetes
kubernetes
tools
for
running
and
managing
jobs
and
applications.
I
Each
of
these
tools
can
be
run
independently,
but
as
these
tools
mature-
and
we
see,
users
have
use
cases
that
that
that
can
bridge
the
the
gaps
between
them.
We
see
more
and
more
users,
picking
up
more
of
the
projects
and
we're
also
working
on
getting
them
more
closely
integrated
so
that
the
users
that
you
use
more
than
one
can
get
additional
benefits
of
of
running
all
these
together.
I
I
I
So
I
look
quickly
just
on
the
history
before
I
go
into
more
data
on
on.
What's
happened
in
the
last
year,
so
argo
was
was
incubated
at
a
startup
called
the
atlantic's
about
two
and
a
half
years
ago
now
and
fairly
shortly
thereafter,
they
were
acquired
by
by
intuit
to
build
a
internal
self-service
cloud
native
platform
for
service
delivery
and
for
the
developer
community.
I
As
that
platform
was
being
built,
there
was
a
need
that
was
realized
that
we
needed
some
continuous
delivery
tool
and
that's
how
argo
cd
was
was
born
just
a
few
months
after
after
that
blackrock
who
was
a
fairly
long-term,
a
long-time
work.
I
Argo
workflow
user
submitted
argo
events
to
the
to
the
project
and
then
another
couple
of
months
later
argo
cd
rolled
out
in
production
at
intuit
and
as
we
used
argo
cd
internally,
we
also
came
to
the
realization
that
we
needed
some
way
of
doing
progressive
delivery,
doing
some
canary
and
blue
green
testing
and
and
hence
argo
roll
out.
So
it
was
incubated
and
launched
a
few
months
later.
I
So
this
is
a
committee
of
a
number
of
of
contributors
and
companies
that
have
helped
with
argo
and
they're
tasked
with
with
working
with
the
with
the
community
and
making
proposals
and
and
guiding
the
governance
of
the
the
argo
project,
and
this
is
a
very
active
committee-
meets
every
week
to
discuss
how
to
move
argo
forward
and
and
grow.
The
community
feel
free
to
jump
in
anytime.
If
you
have
any
any
questions
so
so.
I
So
if
you
look
at
the
dotted
line,
that's
incubation
less
than
a
year
ago,
argo
workflows
now
is
is
is
nearing
8,
000
stars,
they've
added
50
stars
just
in
in
less
than
a
year
and
argo
cd
has
almost
doubled
the
number
of
stars
since
the
incubation
in
in
just
in
just
a
year,
and
that
was
something
I
was
mentioning
in
incubation
as
well,
that
cncf
wanted
to
see
cd
grow
as
well.
I
So
so,
together
we
have
15
000
stars
in
the
project:
3
000
forbes
and
looking
at
the
dev
stats
on
cncf
we're
up
to
3
800
contributors
in
total,
of
which
just
over
900,
are,
are
actually
contributing
code
to
the
project,
and
we
have
a
couple
of
very
active
slack
channels
with
a
total
of
5
000
members
that
have
also
seen
very
good
growth
here
in
in
the
last
in
the
last
year
and
and
and
just
on
argo
cd,
we've
seen
the
the
contributors
grow.
I
Very
strongly
as
well
and
and
on
on
github,
we
actually
now
have
more
contributors
on
argo
cd
than
we
do
on
on
workflow
they're,
pretty
even
but
but
argo
cd
is
seen
a
large
influx
of
contributors
that
are
evenly
spread
across
vendors
users
and
and
individuals.
It's
good
to
see
you
know
a
mix
of
various
contributors
coming
in
here
as
well,
and
we're
seeing
a
strong
growth
of
contributors
and
members
outside
of
of
intuit.
I
I
think
last
week
there
was
there
was
a
maintainers
meeting
and
I
think
that
12
12
new
members,
core
members,
were
accepted
into
the
project
and
two
promotions
and
of
those
14
new
members
and
two
promotion.
I
think
there
was
only
one
new
member
and
one
promotion
that
came
from
into
it,
so
we're
seeing
a
lot
of
contributors
come
into
the
projects
from
from
outside
from
outside
from
outside
into
it.
I
I
I
Of
course,
we've
also
added
a
large
number
of
new
users.
We
have
over
200
official
public
references
now,
I
think
they're
250-ish
in
total
200
unique
companies.
I
So
we
have
some
around
40
or
50
of
the
companies
that
are
self-reported
are
using
more
than
one
argo
project
and
we've
seen
some
of
the
some
of
the
new
notable
ones
that
we've
seen
here
lately
nikki
from
japan
who
publishes
the
world's
largest
business
daily
financial
times
based
in
london,
we've
seen
new
rally,
consumer
logic
here
from
the
u.s
swisscom
european
telecoast
electronic
arts
and
as
of
yesterday,
I
think
also
have
paypal
reporting
that
they
rolling
out
argo
rollouts.
I
So
a
lot
of
new
users,
a
lot
of
various
verticals
spread
across
the
world,
a
really
good
good
mix
of
usage
and
users
across
the
various
projects.
I
But
in
addition
to
all
the
uses,
we've
also
seen
a
lot
of
integrations
with
argo.
As
a
component,
where
we
have
projects
that
have
been
around
for
a
while
like
cube
flow
and
sql
flow
and
zeldan
using
argo
workflows
as
an
orchestration
engine,
underneath
we
have
cooler
a
little
more
recent,
which
is
a
unified
interface
for
for
managing
workflows
with
different
workflow
engines
that
also
support
argo
and
and
then
fairly.
Recently.
I
We
also
have
the
developer
portal
platform
backstage
now,
also
supporting
argo
roll,
that's
looking
for
progressive
delivery
in
in
on
that
platform,
and
then
in
in
addition
to
the
open
source
project.
There
was
also
an
announcement
by
by
red
hat
a
couple
of
weeks
ago
about
the
get
ops
agent,
sorry,
the
git
ops
operator
that
they're
releasing
that
that
that
uses
argo
cd.
So
we're
excited
to
get
a
fully
supported
vendor
solution
here
with
argo
as
well
and
and
on
the
vendor
side.
I
In
addition
to
that,
we
also
have
a
number
of
vendors
that
have
integrations
either
lists
on
the
website
or
or
integrations
of
argo
that
they
support.
For
example,
there's
code
fresh:
that's
taken
a
a
more
active
role
in
the
organ
community
as
well
and
helping
out
and
contributing
it
a
lot,
and
then
we
have
more
passive,
more
passive,
like
like
vmware
and
digital
ocean.
That
still
have
argo
integrations
documented
on
there
in
their
official
documentation,
but
not
not
necessarily
being
too
involved
in
the
project.
So
so,
overall,
it's
it's
been
a
great
year.
I
We've
also
seen
a
lot
of
a
lot
of
chatter
on
on
twitter
on
slack
and
that's
how
we
know
that
this
the
actual
number
of
users
is,
is
quite
a
lot
larger
than
the
200
that
that
that
officially
supported,
because
you
know
that
the
number
of
companies
that
aren't
allowed
to
you
know
officially
proclaim
what
what
they're
using
internally.
I
But
we've
seen.
We've
seen
uses
that
that
aren't
listed
with
companies
in
in
the
users
file
to
that
post
on
on
twitter.
How
excited
they
are
about
the
project
we've
seen
people
post
about
training,
they're
doing
meetups
and
webinars,
and
it's
also
really
exciting
to
see
some
more
local,
meetups
and
local
presentations
in
just
the
last
couple
of
weeks,
I've
seen
meetups
and
presentations
in
spanish
and
japanese
and
in
argos
it's
good
to
see.
I
You
know
how
how
it's
spreading
spreading
around
around
the
world,
but
in
general,
there's
a
lot
of
just
great
positivity
around
argo
and
not
just
argo
itself,
but
also
around
around
git
ops,
and
it
seems
like
the
the
audience
is,
is
maturing.
You
can
tell
that
the
community
and
users
are
maturing.
There
are
less
questions
around
what
is
argo
and
and
what
is
git
ops
people,
people
get
it
now,
users
get
it,
there's
more
real
use
cases.
How
do
how
do
I
take
these?
How
do
I
take
these
components?
I
I
We
also,
I
also
mentioned
the
user
surveys,
so
in
in
february
we
ran
user
service
for
the
argo
projects
and
we
got
about
120
or
so
unique
responses
across
the
surveys
and
though
there
is
a
little
bit
of
selection
bias,
of
course,
and
since
since
these
were
solicited
from
you
know,
from
from
the
current
argo
users,
the
the
resulting
nps
course
came
in
at
68
and
66,
respectively
for
cd
and
workflow,
so
even
with
some
selection
bias,
those
those
are
some
pretty
incredible
and
some
incredible
nps
nps
data-
and
you
know,
as
in
my
in
my
previous
life
as
a
vendor,
even
some
selection
bias,
and
I
would
be
incredibly
proud
over
over
those
and
and
equally
here
you
know
those
are
some
pretty
impressive
numbers
that
show
how
excited
the
users
are
and
how
happy
they
are
with
with
what
has
been
done
by
the
community.
I
So
far,
it
showed
there
was
a
pretty
good
mix
of
of
experience,
level
and
use
cases
in
the
community.
It's
not
it's!
It's
a
good
mix
of
better
seasoned
veterans
and
new
users,
some
that
have
just
put
argo
in
production.
Some
have
run
and
production
for
a
long
time
and
almost
90
percent
of
the
people
that
responded
are
using
it
in
production.
I
So
it's
so
it's
not
that
there's
a
lot
of
science
projects
going
on
here
that
these
are
actually
users
and
companies
using
argo
in
production
and,
like
I
said
earlier,
about
25
percent
used
more
than
one
arga
project
all
already
and
what's
what's
what's
almost
even
more
exciting
than
the
nps
scores,
and
the
reflection
of
the
nps
score
is
that
almost
50
of
the
people
that
responded
said
that
they
were
willing
to
to
share
what
they're
using
argo
for
evangelize
argo
and
do
case
studies
provide,
quotes
or
write
some
blog
posts
to
do
to
do
some
presentations
on
argo
and
that's
another
good
testament
to
you
know
how
how
how
excited
the
user
community
is
and
how
confident
they
they
are.
J
J
So
otherwise,
there's
something
on
any
questions
on
chat.
There
are
a
few
expressions
on
chat,
no
questions,
yeah.
I
No
expressions,
no
questions,
okay,
I'll
I'll,
keep
going
and,
like
I
said,
feel
free
to
interrupt.
If,
if
you
have,
if
you
have
any
questions
the
four
projects
we
have
released
independently,
so
it's
just
a
timeline
of
when
the
the
release
is
so
far
that
we've
we've
had
we're
not
on
a
fixed,
fixed
cadence.
I
But,
like
I
said,
it's
been
pretty
regular.
It's
been
pretty
hectic
with
the
350
releases
in
total
and
with
three
350
releases
from
350
releases
from
the
start
of
which
almost
half
is
is
from
around
here.
I
So
it's
been
a
very
intense
release,
cadence
here
in
in
the
last
in
the
last
year,
but
even
even
so,
we
haven't
had
any
major
releases
since
incubation,
so
so
I'm
very
excited
to
announce-
and
some
of
you
might
have
already
seen
that
that
we're
aiming
to
have
major
releases
of
argo,
workflows,
argo,
cd
and
argo
rollouts
here
in
the
next
in
the
next
month,
or
so
so
we'll
get
up
to
the
first
1.0.
Release
of
argo
workflows
will
rev
argo
cd
to
2.0
and
argo
workflows
to
g3.0.
I
So
there's
a
lot
of
good
stuff
coming
in
here,
argo
workflows
has
a
brand
new
ui,
there's
integration,
better
integration,
more
integration
with,
with
with
argo
events,
that's
frequently
used
together
with
argo,
workflows,
there's
more
enterprise-grade
functionality
like
controller
high
availability,
making
sure
that
we
reduce
the
timing.
In
case
something
happens,
the
controller
we
don't
have
to
wait
for
kubernetes
to
start
up
the
new
pod.
We
can
just
do
a
hot
swap
and
get
up
and
back
up
and
running
faster
and
in
argo.
I
Cd
there's
also
been
a
lot
of
new
cool
ui
work.
The
log
visualization
has
been
rewritten
and
improved
to
make
sure
that
it's
easy
to
troubleshoot
and
figure
out.
What's
what's
what's
going
on
with
with
your
deployments,
we've
also
found
and
fixed
a
number
of
security
issues
in
in
argo,
cd
and
there's.
Also
now
a
argo,
proj
security
advisory
page
on
github.
I
We
can
go
and
see
you
know
any
and
and
subscribe
and
see
any
anything,
anything
that
we
find
anything
that
gets
gets
fixed
and
then
last
but
not
least,
getting
argo
rollouts
to
1.0
I'll
show
that
in
a
little
bit,
we've
started
rolling
it
out
internally
at
at
into
it
and
we'll
do
more
roll
outs
at
into
later
this
year,
but
based
based
on
our
experiences
based
on
what
we've
seen
from
the
community
and
heard
from
the
users
it's
time
to
get
it
up
to
1.1.0.
I
So
we
completed
that
last
week
and
they
did
basically
two
different
two
phases:
a
threat
model,
which
is
more
high
level
component,
focused
review
where
they're
going
to
design
and
architecture
actors
and
just
try
and
and
see
and
and
evaluate
if
there
are
any
any
issues
in
in
the
modeling
in
the
architecture
of
the
product
and
then
the
second
phase
was
a
a
code
review
more
focused
on
using
static
analysis
tools
and
manual
review
of
code
to
really
drill
in
and
see.
I
You
know,
what's
what's
going
on
and
see,
what's
what
potentially
could
be
could
be
an
issue,
so
the
the
threat
model
found
22
issues
ranging
from
informal
to
high
and
the
code
review
found.
35
issues
from
informal
to
medium,
which,
given
the
size
of
the
project
is,
is,
is
a
really
good
result.
Most
of
the
issues
are
low
or
informational,
meaning
that
they're
things
that
we
just
need
to
document.
Something
to
report
maybe
maybe
switch
to.
I
I
The
the
really
good
news
is
there
were
no
critical
issues
found,
which
is
the
degradation
criteria
to
meet,
but
even
so
a
number
of
these
issues
are
already
being
triaged.
Some
of
them
have
already
been
fixed,
even
so
we're
triaging
and
prioritizing
this
to
to
to
get
as
many
as
possibilities
fixed
here
quickly
and
include
in
the
in
the
upcoming
releases
and
even
the
ones
that
are.
I
And,
and
even
so
for
for
the
medium
and
high
issues
that
were
found,
the
vast
majority
of
these
were
also
rated
with
a
high
difficulty,
which
means
that,
even
even
if
the
there's
a
medium
or
high
impact,
the
ability
to
to
actually
exploit
these
would
be
very
tricky
and
very
hard.
I
Another
thing
that
we've
been
working
on
to
to
to
make
the
project
you
know
easy
to
use
and
more
polished
is
a
new
website,
design
and
content
content.
So
a
shout
out
to
to
code
fresh
that
has
has
helped
a
lot
in
in
getting
this
going.
I
So
currently,
the
the
four
projects
have
slightly
different
website.
The
the
information
is
is
scattered
slightly
differently
and
they
have
slightly
varying
degree
of
maturity
of
the
content,
so
so
we're
building
a
new
website.
I
And
I
think
have
I'm
nearing
the
end
here.
I
just
wanted
to
the
high
level
bit
into.
It
is
still
one
it's
not
the
largest
users
of
of
argo
and
we've
grown
quite
a
lot
since
incubation.