►
From YouTube: CNCF Harbor's Community Zoom Meeting - June 15, 2022
Description
CNCF Harbor's Community Zoom Meeting
A
A
B
Yeah
yeah
sure
yeah
recently,
the
team
is
working
on
one
patch
release
2.2.2,
which
will
include
some
security
issue,
fixing
and
bump
up
some
third
part
component
to
fix
some
cvs.
Also,
we
have
a
few
important
issues
fixing
in
z3ds.
B
B
B
The
development
work
for
these
major
features
are
complete.
We're
currently
focusing
on
some
testing
and
a
few
other
small
features
development
tasks
so,
but
because
in
the
last
week
and
this
week
the
team
have
spent
many
efforts
in
2.5.2
patch
release,
so
we
probably
will
delay
a
few
days.
I
mean
for
the
fc
for
2.6
release
yeah.
So
that's
there
all
was
status
status
for
these
two
release.
A
Do
you
have
an
time
frame
when
2.6
will
be
available
plus
you
know
yeah.
B
The
original
yeah,
the
original
schedule
for
2006,
is
plan
to
release
that
back
into
july
yeah,
that
is
original
plan,
so
giving
the
current
status.
I
think
we
can
check
the
latest
in
the
next
round
of
the
community
meeting,
so
that
will
be
more
accurate.
I
think.
B
A
All
right
good,
thank
you
very
much
for
the
update
on
the
release
anything
else,
or
should
we
go
to
the
next
agenda
topic.
C
D
Yeah,
let
me
use
the
logo
today
feature.
The
feature
is,
as
we
know,
the
audio
log.
We
are
allowed
image,
push
poor
and
delete
operations
for
high
concurrent
environment.
You
will
lock
huge
amount
of
audio
log
in
the
database
and
consume
a
huge
amount
of
disk
space.
In
order
to
save
the
disk
space.
The
administrators
have
to
manually
delete
the
record
periodically,
for
example,
in
the
current
testing
environment.
D
There
are
a
lot
of
audio
log
here
and
in
hubble
2006
we
introduced
a
new
visual
autolog
approach
and
we
are
help
to
create
the
job
service
to
schedule
to
purge
the
audio
log.
Let's
check
it
in
the
ui.
There
is
a
cleanup
section
and
the
previous
damage
collection
section
was
replaced
with
a
cleanup
section.
In
this
section.
There
are
two
sub
items.
One
is
the
garbage
collection,
it
was
as
interest
and
the
there
is
another
is
the
log
notation,
the
log
rotation
we
are
user.
D
If
we
select
you
know
if
we
select
seven
days
and
we
will
approach
the
audi
logo,
we'll
keep
the
analog
in
one
week,
for
example,
in
the
current
body
log,
most
of
them
most
of
the
autolog
are
created
in
june
9..
D
D
And
there
is
a
yeah,
it
is
already
complete
and
we
can
check
the
logs.
That
is
actually
we
have
deleted
all
the
logs
in
autolog
table
and
we
can
check
it
in
any
log
table.
D
D
This
configuration
is
that
located
in
the
configuration
system
settings
and
then
we
can
check
the
audi
log.
We
can
input
our
audio
log
forward
and
point
yeah.
This
is
that
to
find
the
right
previous,
the
input
value
yeah
when
we
forward
the
other
log,
we
can
save
it
and
then
we,
when
we
delete
an
operation
of
push
image
or
deleting
image,
it
will
log
an
audio
log
event
like,
for
example,
we
tried
to
delete
a
repo
that
was
available.
D
D
Let's
take
a
look,
we
can
delete
the
another
repo
we
delete
the
oo2
and
select
one
of
the
ring,
for
he
should
create
a
set
of
event
unlock
in
other
log.
D
And
we
check
the
logs
and
we
found
that
there
is
no
other
logo
in.
D
You
can
refresh
it
only
11
items,
but
we
can
check
it
in
new
moda
as
this
logo
and
this
logo.
D
D
In
the
audio
log
of
the
moda
scissors
we
have,
we
can
get
that
to
get
this
event,
that
project
o2
right.
This
is
the
this
repo
artifact
that
was
removed
and
he
was
logged
in
audio
log.
D
This
option
is
a
the
deserve.
This
give
audiolog
database
option
is
only
available
when
you
have
already
configured
the
law,
audio
logo
forward
and
pond.
If
you
did
not
configure
the
audio
logo
forward
and
point,
this
option
is
not
available.
D
A
This
looks
very
good
and
I
do
have
a
question
so
the
the
forwarding
end
point,
so
you
you're
sending
the
data
to
the
forwarding
endpoint.
My
question
is:
what
is
the
format
you're
sending
the
data
and
yes,
what
is
the
format
and
how
can
the
other
side
receive
this
this
data?
So
is
it
how
how
to
implement
the
receiver
site.
D
I
think
a
standard
assist
logo
can
receive
this
in
render.
Now.
This
is
the
format
of
the
audiolog,
it
will
log
the
action
and
the
resource
and
the
user
operator
in
the
user
and
the
time
yeah.
A
A
Okay,
okay,
is
it
somewhere
documented,
because
this
was
not
clear
that
it's
syslog
forwarding
now
there
is.
A
That
I
will
okay,
because
in
the
in
the
in
the
in
the
text
in
the
ui,
you
don't
see
it
also,
if
you
click
on
the
ui
on
the
on
the
admin
admin
console
of
hardware,
there's
just
audit
lock,
forward,
endpoint
and
also
in
the
info
in
the
input.
There
is
also
no
no
no
on
the
configuration
for
the
lock
forwarder
yeah.
So
if
you
click
on
the
info
here
on
the
info,
icon,
yeah.
E
D
If
you
are
installed
with
the
compose,
then
you
will,
you
can
forward
it
to
the
local
syslog
event.
Endpoint,
the
local
syslogger
and
the
pointer
is
1
105
1
4.
F
But
I
have
one
more
question:
is:
can
the
endpoint
be
an
https
url,
because
I
would
want
to
forward
this
to
let's
say
some
centralized
log
for
centralized
log
aggregators,
like
you
know,
we
have
loggly,
or
you
know
even
vmware's
login
site,
so
it's
possible
to
provide
a
url
so
that
I
can
use
that
to
invoke
the
rest
apis
in
the
forwarder.
F
Okay
got
it
so
so
that's
all
for
login
site
and
what
about?
If
I
want
to
send
it
across
to
a
cloud
subscription
of
let's
say,
loggly
or
something
which
is
which
is
more
like
a
more
like
an
http
based
endpoint
I
mean
asking
like
I
mean:
can
we
consider
like
implementing
that
as
an
enhancement
if
it
is
not
available
right
now,.
F
A
Suggested
is,
if
you
want
to
implement
something
another
endpoint
you
know
except
of
syslog.
Is
there?
Is
there
an
interface
already
for
create
another
implementation?
You
know
like
you,
can,
for
example,
select
a
schema.
You
know
like
this.
A
This
log
forwarding
schema
is
you
you
write
schema,
for
example,
syslog,
then
slash
slash
and
then
the
ip
address,
and
then
you
write,
I
don't
know
another
system
endpoint
and
then,
based
on
the
schema
you
can
decide
which,
where
the
the
the
locks
are
shipped
to,
is
there
a
kind
of
a
standardized
interface
where
this
or
is
there
already
interfacing
harbor
that
we
could
maybe
implement
another
endpoint
easily
or
extended
so
that
the
complexity
of
extending
supporting
another
endpoint
or
another
syslog
forwarding
endpoint.
D
D
C
A
Okay
understand
yeah.
Of
course
I
mean
there's
a
lot
of
system
support,
syslog
out
of
the
box
receiving
data
in
syslog
format.
Okay,
are
there
any
other
questions
regarding
lock,
rotation
and
lock,
forwarding.
A
Okay,
not
then
I
have
another
topic
as
well.
It's
not
you
know
by
me.
It's
roger
asked
me
to
discuss
this
in
in
the
community,
and
this
is
regarding
the
deprecation
policy
inside
the
project
harbor.
So
as
as
you
remember,
we
had
quite
a
few
questions
from
people,
especially
regarding
our
helm.
A
Chart
support
the
like
the
the
chat,
museum
support
that
supports
helm,
charts
versus
oci,
and
then
the
next
topic
would
be
probably
a
notary,
server
and
roger
asked
me
that
we
should
come
up
or
within
some
sort
of
a
duplication,
standardization
or
deprecation
policy.
B
Yeah,
I
think
a
rodeo
maybe
already
have
a
proposal.
Did
he
share
something
with
you.
A
No
well,
he
asked
me
just
to
bring
this
up
in
his
community.
B
A
Today
and
see
that
if
we
can
come
up
with
something.
B
Yeah,
I
think,
yeah,
maybe
the
best
way
to
do
this
yeah.
I
think
you
make
a
very
good
point
there
right.
We
have
some
features
like
hem
chat
and
going
forward
the
northern
v1
right,
something
like
that
special
we
are
going
to,
I
mean
planned
to
deprecate
them,
and
actually
we
have
initial
some
discussion
in
the
github
industry.
B
So,
but
what
is
the
gap?
Is
we
actually
do
not
have
a
project?
Do
not
have
a
application
process
for
the
stable
feature
so
yeah,
I
think
the
better
way.
Maybe
we
need.
We
need
a
proposal
summit
on
the
github
so
based
on
that
we
can
review
and
discuss
and
do
some-
and
I
think
the
nintendo
and
the
the
community
can
comments
on
that.
A
Yeah
definitely
yeah
yeah,
so
we
should
come
up
with
a
deprecation,
deprecation
policy
and
standard,
and
you
know
how
we
can
communicate
this
deprecation
policy
to
the
outside
as
well
yeah.
I
think
we
can
yeah
orientate
ourselves
on
kubernetes,
maybe
on
kubernetes
or
other
cncf
projects.
B
On
the
process,
I
think
we
can,
I
think,
as
a
maintainer
and
the
community
can
discuss
together
a
conclusion
on
a
process
that
we
think
the
maintenance
communities
think
that
is,
that
is
a
property
for
project
harvard,
I
think,
there's
a
goal
right.
We
don't
need
to
have
something
very
similar,
either
other
projects.
I
think,
just
in
my
opinion,.
E
A
B
C
I
just
wanted
to
say
if
folks
had
any
ideas
about
this,
that
that
comes
to
mind.
We
do
have
an
issue
about
creating
a
deprecation
policy.
I
just
put
the
link
in
the
chat,
so
if
you
have
thoughts
or
anything
that
comes
up
you
know,
hopefully
roger
is
able
to
put
together
a
proposal.
I
think
this
will
be
something
that's
really
awesome
to
have
for
the
community,
and
so
that's
just
wanted
to
say
that
we
do
have
an
issue
too.
C
If
people
had
thoughts
afterwards
and
hopefully,
roger
can
put
together
a
proposal.
So
we
can
talk,
continue
talking
about
this.
A
That's
that's
important,
that's
good
yeah,
so
we
can
build
upon
that.
A
Are
there
any
other
topics,
besides
the
duplication
that
we
should
work
on,
then
topics
that
we
should
discuss
today.
A
I
see
there
is
nobody
added
something
on
the
agenda
today.
Maybe
we
can
so
if
we
have
some,
we
have
some
time.
Maybe
we
can
go
over
a
bit
on
the
on
the
community
proposals
that
we
what
we
had.
I
think.
A
Maybe
he
he's
also
am
I
right,
you're
also
working
on
the
on
some
of
the
community
or
some
features
of
for
harbor
right.
F
Right
right
for
them,
but
so
the
I
have
not
been
able
to
update
the
proposal
because
I
was
busy
with
something
else,
but
just
to
give
a
quick
background.
I'm
working
on.
So
I
worked
on
the
system
artifact
manager,
which
was
around
storing
non
oci,
compliant
artifacts
with
the
registry
as
the
back
store
backing
store,
so
that
that
effort
was
complete
and
I'm
leveraging
that
to
develop
a
complete
csv
export
functionality
for
scan
data.
F
So
that's
work
in
progress
like
I
mean
I'm
working
closely
with
the
vang
for
that
and
it
should
get
hopefully
like.
I
will
be
able
to
update
the
proposal
as
well
as
provide
a
demo
in
the
next
community
meeting
and.
F
Like
it's
all
about
like
allowing
the
user
to
export
all
the
scan
scan
data
data
that
has
been
that
has
been
obtained
for
the
images
so
yeah.
That's.
A
F
Sorry
I
was
on
mute,
yeah,
that's
right,
buddy
and
the
system
artifact
manager
thing
is
the
the
first
proposal
related
to
storage
of
system.
Artifacts,
that's
complete.
I
mean
the
implementation
has
also
been
completed.
There
are
a
couple
of
bugs
that
were
being
identified,
but
it's
more
or
less
it's
done,
and
it
is
now
being
leveraged
as
a
foundational
piece
to
develop
the
csv
export
feature
which
I'll,
which
I'll
provide
an
update
and
demo
in
the
next
community
meeting.
F
A
A
Because
there
is
perhaps
already
you
know,
created
a
pr
and
I
think
it's
clear
that
we
gonna
accept
his
pr
once
it
meets
the
requirement.
So.
A
See
that
yeah
it's
currently
working
work
done,
so
I
would
suggest
that
we
so
that
we
accept
this
request.
A
A
Because
otherwise
I
mean
we
will
have
the
feature
merged
in
in
the
in
the
master
and
then
community
is
still
not
accepted
here.
Got
it
for
them,
okay,
okay,
so
shoot.
Should
we
then.
A
And
there
is
another
topic
that
we
should
also
take
action
on,
and
this
is
the
you
know,
move
daniel
into
emeritus
and
we're
still
missing
a
few
few
reviews
from
the
community
from
the
maintainers.
You
know
if
you
would
give
it
give
it
a
go
immediately
and
we
can
close
this
topic
as
well.
F
Hey
I'm
on
my
phone,
can
you
is
it
about
the
csv
export?
That
is
what
that
that
requires.
That
requires
my
input.
A
No,
no,
no,
your
input
is
not
required
here.
This
is
like
the
community
approval
topic
for.
A
Yeah,
so
while
we
were
talking
about
the
deprecation
and
policy
features,
I
see
that
roger
did
already
made
a.
C
A
A
And
here
we
go
here's
the
link
to
the
chat,
please
review
and
comment,
and
most
importantly,
then,
approve,
and
so
this
one
as
well.
So
you
know,
let's
move
a
bit
a
few
topics,
because
because
there
are
a
lot
of
topics
as
well
in
the
community
that
needs
to
be
approved,
because
you
know
we
technically
agreed
agreed
on
them.
The
only
thing
that
is
missing
is
like
moving
forward
with
them
and
and
approve
them.
A
You
know
kind
of
technically
approve
them,
but
because
we're
or
theoretically
approve
them,
because
technically
we
already
committed
to
this
saying
the
same
as
like
with
this
code
code
owners.
This
is
also
open
for
quite
some
time,
and
this
is
also
more
of
a
technical,
technical
proposal
from
orlan.
A
Okay,
then,
I
would
say
if
there
is
no
other
topics
to
discuss.
Please
update
your
your
username
in
the
attendance
list
of
today
and
thank
you
very
much
for
attending
and
I'll
see
you
for
everyone
else.
In
two
weeks
on
the
next
community
meeting
same
time
same
place.
Thank
you
very
much
goodbye.