►
From YouTube: Argo Contributors Office Hours Feb 24th 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
Hi
everyone
welcome
to
the
contributors
meeting,
I'm
leo
and
let's
get
started.
Let
me
share
my
screen.
First.
B
Just
just
a
quick,
quick
thing:
I
see
we
have
someone
on
the
list.
Maybe
new
rh.
C
B
C
A
Cool
all
right,
I
hope
everybody
can
see
my
screen
today
february
24th
and
getting
started
with
the
triage
discussion,
so
I
was
in
the
triage
for
for
last
week,
so
I
was
looking
at
korean
argo
cd
issues,
this
one
I
was
discussing
with
the
user
this
morning.
A
It's
a
little
bit
strange,
maybe
a
bug,
maybe
a
bad
configuration
in
in
on
his
side,
but
I'm
not
sure
the
the
thing
is
he's
saying
that
he's
changing
the
desired
state
of
the
replicas
replica
count
in
gear
and
by
the
time
he
syncs
the
live
state
reflects
the
state
in
git,
but
the
diff
is
showing
difference
as
as
you
can
see
here,
it
shows
like
50,
which
is
the
previous
state,
even
though
it
was
just
apply.
A
I
never
had
that
behavior
before
not
sure
if
somebody
already
have
seen
this
as
in
the
past,
but
I'm
not
sure
if
this
is
really
a
bug
or
a
bad
configuration.
So
this
is
something
yeah.
Some
someone
has
something
to
say.
A
Guess
not
so
this
is
a
an
open,
I'm
gonna
leave
it
open
and
yeah
do
further
investigation.
A
Another
issue
that
is
at
the
top
of
the
of
our
issues
is
someone
complaining
about
the
cve
that
we
already.
A
List
of
patched
versions,
so
the
user
is
using
two
to
five
and
we're
saying
two
to
four
is
patched.
So
I
just
reply
back
to
him,
saying
that
you're
you're
you're
using
a
patched
version-
and
this
is
the
blog
post
but
yeah-
not
sure
if
I
should
just
go
ahead
and
close
this
one.
A
And
that's
it
going
back
to
the
document.
I
guess
the
next
step
is
selecting
the
the
the
who's
going
to
be
on
on
the
three
edge
for
the
next
week.
Any
volunteers.
D
D
A
D
D
B
I
think,
as
a
member
of
the
of
the
organization,
you
should
have
the
proper
privilege.
I
think
we
changed
that
recently,
but
we
we
do
have.
I
don't
know
if
it's
attached
to
the
membership
of
the
ag
approach
organization
or
if
we
have
a
team,
that's
being
allowed
to
do
that,
but
yeah
you.
You
definitely
should
have
the
the
permissions.
If
you
don't
have,
then
we
we
need
to
grant
them
to
you.
B
A
Thanks
y'all,
thank
you
so
yeah
going
back
to
the
to
the
plan.
If
anybody
has
some
last
minute
topic,
please
feel
free
to
to
add
in
the
document.
E
Oh,
I
I
do
have
one
small
topic,
maybe
it's
more
too
young.
I
won't
see
your
opinion,
so
the
kivaro
team
just
pinged
me
like
regarding
they
won't
do
some
code
blogging
opportunity
and
I'm
just
thinking
whether
there
will
all
be
something
interesting.
Regarding
the
security
side
we
can,
we
can
do
together
results.
E
Yeah,
so
I
I'm
not
sure
whether
it's
valuable,
because
we
are
trying
to
build
up
more
blocks
of
posture
regarding
the
security,
my
co-authors
and
blogs,
with
the
kivaro
team.
Will
that
be
helpful?
I
know
flux
team
did
something
they
are
we're
talking
about
verify
the
signature
of
the
docker
image
of
the
flux
image
by
adding
a
cluster
level,
verification
like
a
good
certificate
to
sign
the
signed
image
and
verify
the
signature
of
the
image
to
ensure
some
level
about
the
supply
chain
security.
B
Yeah
I
I
guess
it
would
make
sense
to
integrate
cosine
into
into
our
so
to
use
cosine.
We
we
just
need
to
see,
probably
because
everything
is
right
now
automated
in
github
right.
We
need
to
see
how
we
can
make
that
happen.
E
B
Whether
whether
it
makes
sense
to
sign
it
in
the
ci
right,
because
usually
I
mean
the
signing
process
should
be
something
it
should
not
be
automated,
because
then
it
has
no
value
right,
because.
C
B
We
can
see
how
we
can
do
it,
how
how
we,
I
I'm
not
sure
how,
if
it's
possible
to
to
have
the
ci,
build
the
image
and
then.
B
Have
a
developer
sign
it
or
whether
it
makes
sense
or
whether
it
makes
sense
to
have
like
a
I
mean
it
all
boys,
don't
trust
right.
B
E
A
Nope,
okay,
so
I
guess
we're
gonna
have
a
short
meeting
this
week.
Thanks
everybody
for
attending
and
see
you
all
next
week,
thanks
everybody
take
care.