►
Description
CNCF Harbor's Community Zoom Meeting
A
Okay,
what's
up
hello,
everyone
welcome
to
the
first
of
may.
The
first
community
meeting
in
may
today
is
may
the
fourth
and
happy
star
wars
day.
Everyone
first
of
all
and
second
of
all,
welcome
and
please
keep
in
mind.
That's
the
official
community
meeting,
so
please
behave
follow
the
code
of
contact
and
overall
be
a
nice
person.
My
name
is
olympus
silith,
I'm
located
in
bulgaria.
I'm
saying
that
because
I
can
see
some
new
folks
in
the
call
I've
I've
pasted
the
community
meeting
link
for
the
notes.
A
So
I
I
changed
the
format
a
little
bit,
so
we
can
have
it
more
structured.
I
took
that
from
the
valero
project.
I
I
I
see
that
that
works
there,
because
we
can
see
who
attended
and
if
there
is
a
point
for
someone
who
wasn't
there,
it's
easy
to
to
address
them.
So
I've
changed
the
plan
a
bit
so
yeah,
that's
the
new
one
compared
to
the
to
the
old
one
over
here,
and
so
please
add
your
topics.
A
If
you
have
any,
if
you
don't
have
any
feel
free
to
introduce
yourself
right
now,
I
can
see
mark,
and
I
can
see
I'm
sorry,
but
I
don't
know
how
to
read
that
dior
guerra
is
it?
Is
it
right?
I'm
sorry
for
my
prince,
hey,
okay,
so
I
have
two
things
for
today
feel
free
to
add
yours.
First
of
all,
I
wanna
recognize
the
the
the
pr's
from
simon,
I
suppose,
is
his
name.
A
He
has
contributed
quite
a
lot
in
the
last
few
periods
and
especially
around
the
ui,
which
leads
me
to
my
next
topic
is:
if
you
can
take
a
look
at
the
refactoring
of
the
portal
language
code,
I've
asked
the
maintainers
to
to
review.
That
code
looks
pretty
good
for
me,
but
I'm
not
the
expert
here
so
young
one
and
the
rest
of
the
team.
Please
take
a
look
at
this
one
and
give
your
feedback
looks
pretty
good.
It
will
make
the
localization
a
bit
more
easy
to
swallow.
A
A
A
Radio
record
nice,
so
it's
already
up
there
and
ready
to
to
be
streamed
right.
Yeah,
nice,
nice,
nice,
okay,
okay,
yeah!
I
can
update
you
on
a
few
other
stuff,
the
stale
pr
that
have
opened
last.
I
don't
know
when
yeah
almost
a
month
ago
it
was
merged.
So
I
suppose
in
20
20
days
we
will
start
having
results
after
this
one.
So
we
can
get
rid
of
super
old
stales
and
you
can
see
the.
A
A
B
A
A
A
C
C
C
C
If
you
do
githubs,
because
then
you
have
to
go
in
and
manually
update
the
the
custom
resource
in
githubs
and
then
you
can
update
the
secret
separately,
so
I
propose
a
couple
different
solutions
there.
Most
of
them
include
moving
the
access
key
to
either
separate
secret
or
to
the
same
secret
as
the
as
the
secret
reference
for
the
secret
key.
C
But
really
the
goal
here
is
to
move
the
access
key
out
of
the
custom
resource
to
a
secret
where
we
can
automatically
rotate
both
at
the
same
time
using
some
other
tools
so
personally
or
or
at
cisco.
We
use
external
secrets
to
synchronize
secrets
from
hashicorp
vault
to
kubernetes
and
we
use
hashcardboard
to
issue
aws
credentials.
C
C
C
I
can
see
that
it's
scheduled
for
release
1.4
right
now,
which
is
two
releases
out,
I'd,
be
happy
to
work
on
if
that
speeds
up
the
process,
because
this
is
this-
is
this-
is
critical
for
us
because
right
so
we
we
have
a
policy
to
rotate
every
secret
every
60
days
and
doing
that
manually
is
a
is
a
bit
of
a
pain.
So
we
we
try
to
make
that
automatic
as
much
as
we
can.
C
There
is
the
reason
I
haven't
really
started
working
on
it,
because
there
are
a
couple
different
ways.
We
could
solve
this
problem
so
first
I
wanted
to
make
sure
that
we
settled
on
at
least
one
and
then
maybe
provide
a
pr
so
solution.
Part
itself
is
not
complicated,
in
my
opinion,
finding
the
right
solution,
that's
both
backward,
compatible
and
yeah.
It
makes
sense
for
from
the
problem
perspective.
That's
that's
kind
of
the
first
step.
A
A
C
A
A
C
I've
just
so
really
I'm
interested
in
general.
What
the
release
cycle
looks
like
for
the
operator,
including
both
minor
and
patch
versions,
because
yeah,
as
I
said
there,
I
think
there's
only
one
in
the
in
the
current
patch
branch
right
now,
but
yeah
I'm.
So
if,
if
he
could,
I
don't
know
it
might
make
sense
to
to
document
it
somewhere
in
the
redmi
or
somewhere
on
the
repo.
A
A
C
And
just
for
you
to
know
so
right
now
we
are
relying
heavily
on
the
operator
because
we
managed
to
few
different
hardware
instances
and
we
actually
kind
of
released
hardware
as
a
managed
service
internally
at
etni.
So
different
teams
can
ask
us
to
to
spin
up
new
hardware
instances
and
we
use
the
operator
for
that
to
manage
different
hardware
instances.
A
A
C
Yeah,
of
course
I
mean,
I
think
I
think
we
actually
have
a
pretty
interesting
use
case
because
at
ethiopia,
ethnic
is
a
business
unit
within
cisco,
where
we
have
a
bunch
of
different
project
teams
that
require
cardboard
for
their
their
own
projects.
But
we
also
use
hardware
as
a
means
to
distribute
artifacts
to
customers
and
we
actually
hit
a
couple
issues
there.
So
maybe
we
could
talk
about
those
especially
around
the
replication
performance,
but
I
think
we've
come
up
with
an
interesting
setup
for
distributivity
artifacts
to
two
customers.
A
D
D
And
what
can
we
do
here?
Because
it
was
quite
hard
for
us,
because
we
didn't
know
how
how
the
replication
was
working
so
discovering
going
through
the
database
and
deactivating
radius
so
that
we
could
actually
stop
this.
So
we
we
can
have
our
infrastructure
working
with.
By
also
is
there
any
provision
of,
because
we
feel
that
the
jobs
should
run
in
background
right
and
the
this
should
be
not
noticeable.
B
B
C
A
C
Something
that
just
we
just
solved
with
adding
more
cpu
to
the
nodes
for
now.
So
that's
fine,
the
other
a
little
bit
bigger
issue
that
we
recently
quite
recently.
Actually
so
it's
like
from
last
week
so
was
that
during
the
applications
when
there
was
a
lot
of
things
to
replicate
the
the
registry
with
the
registry
experience
some
some
connection
drops,
which
is
quite
unexpected,
and
I
can't
say
for
sure
that
it
was
because
of
the
registries,
but
but
it
was
definitely
occurring
during
the
replication.
So
this.
B
C
C
B
B
A
Okay,
if
there
are
no
more
topics
to
discuss
once
again,
I
want
to
bring
the
might
ask
for
everyone.
If
you're
planning
to
visit
kubecon,
stop
by
the
eu,
so
buy
the
kiosk
or
yeah
just
try
to
say
hi.
I
want
to
meet
everyone
who
is
part
of
the
community
and
also,
if
you're,
planning,
to
visit
kubecon,
north
america
and
you're
somehow
feeling
chatty,
and
you
want
to
do
a
hardware
presentation
or
any
kind
of
talk
about
harbor.