►
From YouTube: Argo Contributors Office Hours Jun 2nd 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
Are
several
topics,
and
that
was
me
who
added
all
of
them?
So
if
you
have
any
questions,
please
type
it
here.
Okay,
traditionally,
we
need
to
highlight
any
topics
that
bubbles
up
in
support
for
last
week.
Anything
alarming
and
we
need
to
find
who's
going
to
be
the
next.
B
Yeah
alex,
I
was
the
primary
last
week,
so
nothing
alarming
just
normal
discussions
here
and
there
there
is
the
pr
that
I
opened
to
remove
the
liveness
probe
in
argo
cd
controller.
B
That
is
well
there's
some
discussion
going
on
there.
This
is
something
that
may
be
worth
mentioning
because
removing
the
liveness
probe,
I
think
it
might
be
scary,
but
as
we
discussed
it
seems
that,
while
we
understand
that
that
liveness
probe
is
not
really
useful
for
for
for
the
controller
itself,
but
there
are
some
concerns
right,
so
I'm
mainly
bringing
it
up
to
maybe
ask
someone
if
you,
if
you
know
about
a
real
useful
use
case
for
the
current
lifeblood,
liveness
okay,
I
should.
A
Contribute
because
I
added
that
liveness
pro,
I
remember
we
in
my
as
I
know,
as
far
as
I
know-
we've
it
used
to
make
sense
and
then,
after
we
made
changes
in
actually
implementation
of
that
lens
probe.
As
far
as
I
know
it,
it's,
it
doesn't
make
sense
anymore,
but
that
and
I'll
just
comment
there.
You
know.
A
Maybe
there
are
different
opinions,
but
it's
basically,
I
think
now
it
turned
into
like
famous
kubernetes
antibiotics
to
have
exact
same
thing
in
both
lemons,
broken
earth
and
ray
transport
yeah.
Okay,
all
right!
So
we
need
a
moderator
I
want
to
volunteer
because
I
was
kind
of
upset
for
like
a
month.
That's
why
oh
attendance
in
the
community,
so
I
definitely
I
I
want
to
be
a
mother
primary
for
next
week
index
unless
someone
else
wants
it.
A
A
A
Okay,
all
right,
I
added
couple
topics
and
that
was
kind
of
not
much
so
one
is,
I
guess
we
really
delayed
2.4
and
then
I
was.
I
spent
like
a
couple
days
yesterday
before
day
before
yesterday:
testing
it
and
we
merged
few
bug
fixes,
I
know
for
sure
terminal
feature
works.
I
just
saw
you
know.
People
confirmed
that
several
users
confirmed
that
the
latest
latest
release
candidate
fixed
the
terminal
issues,
and
I
guess
that's
a
question
to
like
everyone.
Do
you
know
about
any
other
outstanding
bugs
something?
A
Maybe
we
can
use
this
document
to
actually
track
it
and
just
literally
mention
tickets
here
and
then,
if
not,
maybe
we
can
just
since
we
recently
published
release
candidate,
we
still
maybe
should
give
people
a
chance
to
report
bugs
and
test
it.
But
I
guess
maybe
it's
a
good
idea
to
schedule
release
on
monday,
unless
anyone
aware
of
any
bad
blocking
bug.
A
And
then
okay,
it
sounds
like
no,
and
I
actually
there
was
one
issue
that
I
I
just
wanted
to
discuss.
I
know
that
daniel
worked
on
124
kubernetes.
Basically
it's
impossible
to.
I
mean
it's
not
a
blocker
right
now,
but
the
cli
unable
to
register
2.4
cluster.
So
it's
a
big
usability
issue,
not
2.43
124
clusters,
and
I
guess
I
don't
know
what
are
your
thoughts
people
like?
Is
it?
A
Do
you
think
it's
okay
to
release
without
the
bug
fix
and
maybe
deliver
that
the
cli
improvement
as
a
patch
release
is
like
too
loud
for
them,
which
bug
are
you
talking
about
it's
impossible
to
like
in
kubernetes
124?
They
introduced
a
behavior
change.
Basically,
if
you
create
a
service
account,
there
will
be
no
secrets
with
the
service
account
token
automatically
created.
Now
this
secret
has
to
be
created
manually
and
our
cli
tool.
A
You
know
argo
cdcla
kind
of
expect
that
secret
will
be
auto
created
and
that's
why
it's
like
argo
cd
can
manage
124
clusters,
but
everyone
kind
of
have
to
manually
create
service
account
and
token
in.
If
you
know,
if
you
see,
if
you,
if
user
needs
to
connect
the
cluster
using
better
token,
it
has
to
be
done
manually
cla
won't
work.
A
D
Yeah,
I
I
guess,
if
it
were
me,
I
would
probably
say
that
we
should.
D
A
It
without
this
fix,
because
we
can't
link
to.
C
A
E
Yeah,
my
my
only
hesitation
with
it
is
that
one
thing
that's
kind
of
interesting
here
is
that,
basically,
I
think
k3s
does
not
have
a
stable,
1.24
version
released
yet
and
for
the
purposes
of
ci.
You
know
it
would
be
nice
to
basically
add
that
to
testing
moving
forward
so
that
maybe
the
it
would
be
good
to
have
some
runs
in
here
where
we
see
it's
working
properly
with
k3s.
A
Because
it
potentially
affects
so
many
people,
maybe
we
can
kind
of
split
it
basically
test.
You
know,
split
the
implementation
and
get
this
pr
in
and
test
it
manually
and
maybe
have
a
test,
but
the
test
can
be
disabled
because
we
cannot
really.
You
know
the
test,
won't
work
in
this
ui
and
then
once
kts
has
stable
version.
We
can
updates
here
to
start
using
the
stable
version
and
and
then
enable
the
test.
E
Possibility
sure
I
think
that
makes
sense
but
yeah,
I
think,
for
the
most
part
here.
I
can
elevate
it
from
draft
to
ready
to
review
and
get
people's
thoughts
on
it,
and
we
can
try
and
move
it
forward.
Okay,.
E
Yeah
so
the
way
that
it's
currently
implemented,
it
will
try
and
check
and
see
if
the
service
account
already
has
a
secret
associated
with
it
and
basically
use
that
as
the
or
it'll
check
for
the
specific
bearer
token
type
secret
to
make
sure
that
it
doesn't
essentially
like
create
duplicate
ones
or
anything
of
that
nature.
D
B
I'm
curious
to
to
to
understand
if
this
is
also
affecting
users,
where
they
have
already
argo
cd
installed,
and
then
they
upgrade
their
kubernetes
clusters
to
the
to
the
latest
version
or
if
it
just
affects
new
installations
in
the
newer
kubernetes
version,
do
you
have
a
guest
alex
or
daniel
or
anybody
else?
Well,.
A
A
Okay,
so
cool,
so
maybe
it
will
make
it
into.
You
know
final
release,
because
since
it's
a
cli
tool
and
I'm
kind
of
maybe
over
optimistic
but
looks
like
it's
hard
to
it's,
either
working
or
not
working
because
there's
not
so
many
moving
parts.
So
maybe
we
can
include
it
into
final
release
if
we,
if
it
makes
it
before,
like
monday,
tuesday,.
B
A
Hear
from
daniel,
if
what
he
was
thinking
is
it
you
know?
Is
it
too
big
for
push
or
not?
And
as
I
understand
it's
good
enough
for
patch,
basically
just
we
can
consider
it
as
a
bug
fix
so
yep
make
sense,
cool.
Okay,
I
didn't
see
any
like
new
topics.
Oh
one
new
topic
was
created
actually
by
someone
about
argo,
rollouts
approvals,
oh
yeah,
all
right,
so
really
quick.
I
wanted.
A
Is
there
anything
blocking
it
or
I
was
about
to
just
approve
and,
and
you
know
and
merge,
but
I
want
to
hear
if
there
was
anything
else
that
we
forget
and
then,
if
you
don't
know,
the
proposal
is
to
basically
give
an
option
to
use
server
side
apply
and
some
additional.
You
know
details
about
some
edge
cases.
B
Yeah
we,
I
wrote
this
proposal
alex
and
we
had
a
quite
a
few
discussions.
I
updated
almost
all
of
them.
I
think
there's
just
one
missing,
which
is
exceptional
scenario
provided
by
byte
dense
use
case.
B
So
what
I'm
gonna
do
I'm
going
to
add
that
to
the
to
the
goals
to
be
yeah,
it
goes
to
be
achieved
in
the
proposal
just
to
make
sure
we
don't.
We
don't
miss
that
use
case
and
I'll
ping
you
and
then
we
I
in
my
opinion
we
can
just
go
ahead
and
merge
it.
Okay,
cool.
A
B
The
one
in
get
ops
engine
is
already
merged,
and
now
we
need
to
make
it
more
flexible
and
implement
it
in
argo
city
code
base,
so
this
one
would
be
targeting
2.5.
I.
A
D
So
my
question
was:
just
I've
noticed
a
little
bit
of
a
slowdown
with
getting
approvals
into
argo
rollouts,
and
I
wanted
to
just
like.
I
have
a
pretty
good
set
list
of
people
in
my
head
for
argo
cd
stuff
that
I
can
go
to.
If,
if
something
needs
approval
you
know
posh,
is
there
alex
alexander?
You
know
just
a
lot
of
people
that
I
could
go
to
with
rollouts
I'm
a
little
uncertain.
D
A
I
know
it's
not
not
me
because
yeah
I
literally
like,
but
I
was
doing
sometimes
is
you
know
when
there
was
a
pull
request,
that
kind
of
related
to
maybe
old
parts
of
fallouts
that
I
was
familiar
with.
People
were
using
me
for
rubber
stump
progress,
but
basically
it
was
possible
to
do
it
only
if
the
change
was
kind
of
simple
and
and
then
kind
of
easy
to
review,
because
it
was
related
to
familiar
part
of
quote
familiar
to
me
so
for
now
I
just
cannot
help
much.
I
maybe
maybe
leo
knows
like.
B
I
guess
yeah
there
is
a
there
is
an
internal
discussion
ending
to
it.
Yeah,
because
we
are
facing
a
similar,
similar,
similar
issue
ourselves
so,
and
harry
is
leading
that
so
the
idea
is
to
have
more
approvals
for
our
rollouts
shortly
so
yeah,
something
that
is
going
to
be
discussed
in
the
next
approval
meetings.
D
Okay,
so
we're
just
we're
aware,
that's
an
issue
and
you
said
you
want
to
discuss
in
the
maintainers
meeting
or
you're
in
you're,
saying
you're
going
to
discuss
with
some
you're
in
the.
B
Maintainers,
I
think
the
next
yes,
sorry
in
the
next
maintainers
meeting
harry
is
going
to
bring
up
this
topic
for
discussion.
Okay,.
A
A
Okay,
all
right,
we
run
out
of
topics
any.
F
A
I
feel
like
we
have
this
kind
of
hack,
I
mean
we
can
consider
it
from
from
may
and
then
we
can
cut
the
release.
Candidates.
A
It's
just
basically,
I
mean
we
seems
like
we
do
it
all
the
time
like
we,
we
create
release
candidate
every
three
months
and
then
we
have
like
kind
of
months
of
of
bug
fixes
and
then
we
release.