►
From YouTube: CNCF Harbor's Community Zoom Meeting - May 17, 2023
Description
CNCF Harbor's Community Zoom Meeting
B
Okay,
let
me
let
me
start
this.
Today's
meeting
welcome
to
the
Hubble
community
meeting
today
is
2023
on
May
17th
and
today
let
me
open
I,
wish
they
community
meeting
being
in
the
chat,
so
everyone
can
open
it
and
I'm
going
to
share
my
screen.
B
So
here
here
is
a
few
agenda,
at
least
here
for
today's
meeting.
So
also,
if
everyone
can
log
can
write
down
your
name
to
the
attendees.
That
will
be
very
helpful
to
Native.
Community
know
who
are
joined
today's
meeting
and
the
first
one
here
is
a
I
want
to
talk
a
little
bit
about
the
2A,
2.9
release,
planning
and
the
current
status.
B
We
have
a
milestone,
which
you
name
the
feature
phrase
milestone
for
each
other.
It
is
start
from
2007
and
remember
so.
B
This
National
means
before
we
get
the
I
mean
to
reduce
plan
finalized.
We
can
move
in
or
move
out
some
atoms
or
issues
from
this
release.
So
after
that,
we
will
have
a
concrete
plan
for
this
release
and
the
team
will
focus
on
what
has
been
planning
for
this
release.
So
that's
the
match.
That
is
the
meaning
for
this
master.
I
mean
speech
for
it,
so
we
have
reached
I
mean
two
thousand
lines
have
reached.
This
feature
free
state,
and
now
we
have
I
think
sorry.
B
I
need
to
look
so
I
have
up.
There
is
a
project
reporter
and
put
the
major
I
mean
anchor
feature
ticket
here,
so
everyone
can,
it
will
be
visible
for
everyone
from
the
community.
So
previously
we
have
communicated
with
two
dollar
land
plan,
maybe
one
months
ago.
So
the
major
feature
in
this
release
is
it's
a
you.
We
will
provide
a
UI
to
to
to
get
the
vulnerability
more
visible
for
the
for
the
mutual
or
the
other
users
will
hover
and
the
and
another
one
is
about.
B
We
will
continue
to
improve
the
performance,
so
we
create
this
epic
and
Link
some
issues
created
by
Community
or
by
the
maintenance,
and
next
we
will
continue
the
efforts
I
mean
to
adopt
the
distribution
v1.1
I.
We
we
have
noticed
that
there
is
a
distribution
we
want
to
have
reduced
after
two
recently,
even
though
we
do
not,
we
don't
know
the
exact
data
they
will
release
this
one
or
one,
but
I
think
it
it
pretty
much
stable
now,
so
we
will
have.
B
We
have
some
follow-up,
a
task
plan
for
to
to
fully
support
that
and
another
one
is
also
very
important,
is
about.
We
will
totally
remove
the
notary
and
this
one
we
will
totally
removed
in
notary
V1
from
this
release,
and
that
has
been
discussed
for
a
very
long
time
since
2006
and
the
last
one
we
have
I
mean
discussed
with
the
another
V2
maintenance.
So
we
have
built
some
connection
and
try
to
do
some
cooperation
at
the
harbor
side
to
support
supporting
notional.
So
that's
something
we
are
interesting
to
doing
this
release.
B
B
So
if
you
are
interested
in
this,
you
can
go
through
this
one.
B
So
I
will
not
took
all
all
this
items
so
just
give
give
the
community
a
Ward
status
update
for
to
the
online.
So
any
comments
or
questions.
A
I
have
a
question
regarding
the
vulnerability
dashboard.
Is
there
a
kind
of
a
already,
let's
say
a
design
and
what
information
and
how
it's
going
and
how
you're
going
to
display
this
information?
Is
it
already
defined,
or
is
it
still
in
progress.
B
Yeah
I
think
it's
a
design
you
still
in
progress
and
the
maintenance
I
think
a
stone
is
working
on
the
proposal
and
I
believe
it
will
be
available
for
discussion
review
in
the
community
in
next
couple
weeks.
So
at
that
end
we
will
have
a
I
mean
detailed
information
around
this
feature.
What
we
plan
to
do
and
how
it
will
be
improved
and
we'll
discussed
with
the
community
and
maintenance.
A
And
also
who
is
working
on
that
Dow
Jones?
Yes,
okay,
and
because
we
need
to
talk
with
the
maintenance,
with
the
maintenance
with
the
trainees,
the
LFX
trainees,
because
the
there
is
a
train
training
working
also
on
the
dashboard
right.
A
B
Sure
sure
I
think
I
think
we
will
discuss
on
that
part
on
details,
so
I
think
stone
is
also
in
this
code.
Do
you
have
any
commas
regarding
redeems
questions.
C
Yeah
I
think
we
can
discuss
it.
You
know.
Currently,
we
are.
We
investigate
the
kind
of
previous
implementation
of
the
database
and
basically,
we
have
two
feature.
C
One
is
the
search
such
as
one
repeated
by
by
project
by
artifacta,
and
also
we
can
search
the
availability
information
by
ceid
and
also
we
can
maybe
we
can
search
it
by
Target
and
we
also
should
display
some
summary
information,
for
example,
in
in
a
project,
Harmony
want
to
be
reformed
and
they're
harming
the
stability
such
as
such
as
how
many
high
facilities
three
or
low
or
media
law.
Let's
say
you
can
summarize
by
project
or
by
necology
yeah
yeah.
This
is
the
we
are.
C
We
are
going
to
investigate
our
country,
incremented.
A
Okay:
okay!
Yes,
we
need
to
sync
also
Loop
in
the
the
trainee
or
the
the
mentee
for
that
from
the
Olympics
program.
Who
is
working
on
that
specific
task
and
she
is
designing,
you
know,
dashboards
and
uis.
How
this
might
look
like
and
I
think
should
be
good
if
we
get
her
arms
on
board
as
well.
There,
yes,.
B
And
then
I
think
for
you
have
had
I
think
it's
a
stream
is
we're
working
with
that
part,
so
both
dojo
and
the
string
assist
to
maintenance
will
major
the
focus
on
this
feature
in.
B
A
A
Yeah
this
is
mine.
Yeah
I
can
share
this
with
you.
B
A
I've
mentioned
it
already
a
few
times
and
and
we're
building
a
proxy
and
I
would
like
now
to
share
this
with
the
community
as
it's
a
bit
more
mature.
Now
there
is
more,
you
know
we
made
some
some
progress
and
I
added
some
documentation
so
that
we
can,
you
know,
kind
of
a
publicly
share
this
this
project
and
also
provide
the
community
with
a
solution
to
a
problem
that
will,
you
know,
be
quite
common
in
Beyond
to
the
date
of
Harvard,
and
it's
called
the
helm,
chart
oci
proxy
and
basically,
how
it
works.
A
Is
that
it's
a
you
know
it's
this
application
that
is,
is
working
as
a
proxy
and
also
as
a
Transformer,
so
it
will
proxy
the
charts
in
this
chart
repository
styled
format.
You
know
with
the
index
demo
file
and
this
target
file
it
will
transform
any.
You
know
any
chart
repository
that
you
that
has
those
styled
charts
and
proxy
and
transform
them
into
oci
oci
artifact
and
you
can
consume
those
oci
artifacts
directly
from
the
proxy
or
you
can
create
and
harbor
a
replication
and
the
replication
in
Harbor
will.
Then
you
could
use
two.
A
You
know
proxy
or
to
replicate
charts
into
your
local
registry
that
are
not.
You
know,
they
don't
exist
as
oci
artifacts.
Yet
you
know
so
it's
like
two
use
cases.
You
could
use
it
directly
as
a
user
right,
the
proxy
or
you
can
use
it
as
a
via
hardware
and
in
Harbor
you
could-
and
this
is
how
it
looks
like
you
know,
when
you
try
to
pull
an
image.
A
D
It's
you
know,
depending
on
on
how.
A
You're
using
Helm,
so
this
is
the
direct
use
case
and
you
can
use
it
also
with
Hardware,
but
the
only
thing
that
you
need
to
do
is
you
need
to
create
an
endpoint
and
the
limitation
that
we
have.
Is
you
need
to
create
an
end
point
not
not
to
the
proxy
itself,
but
also
to
the
you
know,
to
the
chart
that
you
want
to
replicate
so
for
each
charge?
Sort
you
need
to
create
an
endpoint,
for
example,
for
jets,
taking
you
to
create
an
endpoint
for
at
vietnami
and
so
on.
A
That's
only
you
need
to
create
endpoints,
and
then
you
can
create
an
replication
Rule,
and
then
you
can
apply
the
filters
and
things
that
that
you
would
normally
use
to
your
application.
You
can
apply
it
here
as
well,
and
then
you
can,
you
know,
replicate
charts
as
oci
images
or
import
SDI
images
you
could
even
you
could
even
proxy
those
you
know
if
you
wanted
to.
This
is
also
possible
article
to
create
a
proxy
So.
A
Currently,
it's
just
replication,
but
you
could
also
create
a
proxy
and
then
you
could
just
proxy
it
from
via
Hardware
as
oci
and
can
consume
it
directly.
Yes-
and
this
is
basically
the
the
application
you
can
run
it,
you
can
run
it
locally
right
or
you
can
run
it
in
in
your
new
infrastructure.
There's
a
help
chart
that
we
have
built
that
you
can
use
I'll
update
in
the
documentation
a
bit
how
to
install
it.
This
part
is
missing
here
right,
but
I'm,
adding
it
and.
A
Yeah,
so
this
is
basically
the
Hampshire
oci
proxy
and
if
you
would
like
to
use
it,
you
can
you
know
spin
it
up
locally
or
you
can
use
our
public
one
Chuck
proxy.
This
will
go,
live
in
you
know.
Maybe
today
and
you
can,
you
know,
create
issues,
pull
request
if
you
need
to
extend
it
in
a
way
that
that
fits
your
requirements
and
the
whole
thing
is
basically
based
on.
D
Hi
yeah
so
last
week
we've
tested
it
our
team
and
our
environment,
so
this
deployed
the
proxy
on
our
own
infrastructure.
It's
the
same
cluster,
where
our
Hardware
instance
is
running.
So
we
are.
The
endpoint
is
just
an
internal
service
for
us,
it's
really
easy
and
direct
and
slim
so
to
say,
and
it's
just
working,
so
we
used
the
hand
chart
to
deploy
the
service.
D
The
handshards
need
need
some
improvements
here
and
there,
but
I
will
I
will
create
a
pull
requests
once
this
is
public
at
a
repository.
So
no
no
big
things,
but
just
just
some
details,
but
after
we
deployed
it
while
the
Hem
chart
it
just
worked
really
really
well
so
no
problems
there,
and
this
is
for
us
a
really
good
way
forward
to
go
to
Harbor
2.8
and
still
provide
old,
styled
handshards
for
our
internal
teams.
D
So
this
was
the
solution
we
are
looking
for
and
we
are
using
it
in
a
scenario
where
this
is
just
a
proxy
and
not
a
mirror
or
replication.
Just
an
endpoint
deployed
in
a
proxy
project
with
this
endpoint.
So
we
used
the
docker
registry
type
for
that
in
order
to
make
this
as
a
proxy
available
for
the
team
so
and
then
it
it
works.
A
D
D
B
Great
ready,
thank
you,
I
think
it's
that
we
have
benefited
Community
right
to
do.
Ninja
migration
phase
from
the
2007
to
bury
it
yeah,
that's
great.
A
E
D
Yeah
so
most
of
our
teams
are
working
in
an
aircraft
environment
and
have
no
direct
access
to
external
Registries
or
oci
Registries
or
child
vendor,
and
they
have
to
go
through
Harbor
but
and
no
yeah,
but
not
everything
is
it's
at
oci
right
now,
so
we
need
a
way
to
transform
it.
Yes,.
C
D
E
D
D
E
Today
possible
that
you
can
write
a
blob
for,
for
this,
I
mean
that
the
integration
with
Harbor
and
this
process-
and
maybe
some
someone
like
Stefan
and
who
is
using
harboring
heavy
and
looking
for
some
some
tool,
can
help
them
to
to
finish
the
transform.
So
for
them
we
can
link
The
Blob
with
our
official
Twitter
account.
E
In
our
migration
wiki
page,
so
do
you
know
the
the
migration
wiki
page
yeah
there
we
have
I
have
already
updated
that
we
refactor
the
tool
and
reflected
the
the
staffs
for
the
trans
migration.
So.
A
A
Thank
you
yeah,
while
I
have
to
say
that
using
this
tool
for
migration
is
I
mean
it.
It
is
possible.
You
know
like
if
you
have
an
old
Harbor
running
and
a
new
Harbor.
You
could
use
it
for
migration,
but
it's
not
designed
primarily
for
migration
right,
because
you
need
to
set
up
everything.
If
you
do
want
to
do
migration,
you
need
to
set
up
right
where
application
Rule
and
you
need
to
point
it
to
your
old
registry
and
things
like
this.
So
you
know
if
you
would
migrate.
A
E
Yes,
can
you
also
send
up
a
message
to
the
sub
Channel
I
mean
the
cncf
harbor
sectional
to
to
let
more
people
know
this
tool,
and-
and
maybe
you
can
give
a
short
description
and
this
usage
on
yeah
I-
think
a
lot
of
people
are
seeking
for
this
kind
of
tool
to
have
them
to
transform
the
wholesale
charts.
C
A
Not
even
reverse
proxy,
so
like
yeah,
it
could
be
yeah,
it
could
be,
but
it
I
think
it
may
be
easier
to
have
another
tool
that
does
this.
The
thing
is
the
the
old
style
chart.
Format
is
basically
an
index
yaml
file.
You
know
the
index
yaml
file
plus
a
place
where
the
Stark
Z
files
are
stored
and
you
could.
Basically,
if
you
read
the
API
you
could
you
know
you
could
assemble
it
quite
easily
right.
So
it's
it's
not
complicated
to
write
this
yaml
file.
A
It's
just
a
index
yaml
file
that
contains
the
URLs
where
the
target
Z
file
is
plus
the
metadata
and
the
names
so
I
mean
you
cannot.
You
cannot
use
this
for
this
purpose,
but
it
would
not
be
very
complicated
to
create
one
that
does
it,
but
the
reverse
process
right
yeah,
but
for
which
use
case,
do
you
think
it
makes
sense?
It
would
make
sense
to
have
a
to
proxy
from
oci
into
you
know.
The
traditional
Helm
chart
format.
A
Okay,
yeah
because
I've
I've
been
thinking
about
this
as
well
as
well,
but
I.
You
know
there
was
no
use
case
that
came
up
to
my
mind
that
that
that
made
sense,
maybe
I'm
missing
something.
That's
why
I
was
asking
if
you.
C
Have
something
in
the
in
a
discussion
of
the
hollow
GitHub?
Maybe
some
of
the
users
still
using
the
other
format,
because
the
prefer
to
use
the
ham
search?
Commander,
okay,
does
not
provide
this
feature
exactly.
E
But
but
I
think
we
should
open
the
ticket
for
the
help
client
to
yeah
push
them
to
implement
the
Hub
search
to
support
the
OCS
compatible
charts
the
distribution
V2
API
to
have
them
so
the
dodging.
Can
we
can
we
do
this,
I
mean
that
we
can
open
the
GitHub
issue
at
the
ham
report
that
the
number
you
can
use
that
to
discuss
with
the
maintenance
from
the
ham
chart,
the
ham
team.
B
Okay,
that's
a
really
good
discussion.
I
think
thank
you.
Thank
you
madine
to
present
this
to
the
community,
so
any
any
more
questions
or
comments
on
this
topic.
A
D
But
I
was
I
was
immune.
Sorry,
so
if
you
go
on
public
with
this
hand
proxy
server,
so
this
will
be
some
somewhere,
the
1.0
from
your
perspective,
okay,
so
production
release,
yeah.
A
So
the
other
topic
I
would
like
to
discuss
is
the
deprecation
of
notary,
and
you
know
it.
It
caused
some
problem
when
we
upgraded
from
two
seven
to
eight.
You
know,
people
migrated
migrated
the
applications
and
they
found
out
that
hampshires
wasn't
there
and
it
didn't
work
out
as
they
expected
the
upgrade
and
I
think
it
would
make
sense.
If
we,
when
we,
you
know,
remove
notary
that
we
upgrade
the
harbor
version
to
3.0.
A
C
A
E
Have
to
design
some
V3
API
yeah
like
some
New
Year
Monumental
Improvement,
like
performance
like
yeah,
but
but
for
the
the
current
Master
minority
started
the
2.9.
E
It
is
a
routine
update
like
with
with
some
anchor
new
features,
but
but
we
are
not
ready
for
the
nest
and
major
release.
A
E
So
yeah
we
I
think
we
can
claim
like
we
are
deprecating
the
notary
in
the
NASA
release,
and
everyone
knows
that
and
and
from
signature
perspective.
We
do
not
provide
any
migration,
because
that
Harbor
has
already
supported
the
cosine
and
the
signature
tool.
But
we
cannot
transform
the
signature
signed
by
not
free
to
the
cosine
signature
right,
so
we're
just
deprecate.
The
network
and
user
can
choose
cosine
as
alternative.
A
To
addition,
I
mean
we
have,
you
know
kind
of
a
we
stating
in
our
community
or
in
our
repository
that
we
are
following
this
romantic
versioning
right
and
it
because
we're
stating
that
we're
following
the
semantic
versioning
I
mean
we
should
we
should
follow
the
semantic
versioning
and
the
semantic
versioning
is
not
about
features.
You
know,
perversion
that
are
added
or
removed.
It's
basically
semantic
versioning
is
about
API
and
compatibility,
and
the
the
API
is
is
changing
all
the
functionality
and
the
API
is
changing.
A
When
we
remove
notary,
because
we
have
our
API
changes,
we
have
less
API
than
we
had
before,
right
and
I
think
from
the
semantic
versioning
perspective.
If
we
want
to
be
compliant
with
the
semantic
versioning
specification,
we
we
have
no
other
choice,
it's
not
something
if
it's
a
feature
ready
or
feature
Worth
to
upgrade
to
3-0
or
not
it's.
Basically,
if
you
break
the
API,
you
change
the
version
or
if
the
API
changes-
and
this
is
how
people
like
who
are
using
automated
update
tools
like
Argo
CD
and
things
like
this.
A
They
follow
this
semantic
versioning
and
they
that's
why
a
few
of
them
had
problems
when
they
upgraded
automatically
to
to
date,
because
they
were
expecting
no
API
breaks
and
they
have
been
API
Pricks.
No,
so
I
think
we
should
yeah
or
we
or
we
change
the
the
description
in
our
repository
that
we're
not
following
the
semantic
versioning
right.
So
we
have
two
choices,
but
we
should
be,
you
know,
decide
on
one
or
the
other
choice.
E
E
E
A
B
I
may
have
some
different
opinion
here.
You
can
see.
Actually
the
kubernetes
Community
is
also
saying
to
follow
the
semantic
version.
But
if
you
look
at
the
release
of
kubernetes,
it
is
still
1..
1.X
continue
and.
B
I
think
we
can
follow
the
kubernetes
as
a
best
practice
as
an
example
and
do
what
we
our
currently
follow
right
and
even
we,
when
you
open
the
semantic
version,
introduction
I
cannot
clearly
see
they
said
you
cannot
deprecate
a
feature
in
your
release.
Right.
A
No,
it's
not
about
deprecating
a
feature.
The
Thematic
versioning
is
saying
if
you're
changing
the
API
to
make
it
incompatible
to
the
previous
version,
you
need
to
update
the
major
version
like
incompatible.
Api
changes
and
deprecation
is
an
incompatible
API
change
right.
So.
B
Api
change,
I
think
that
is
some,
maybe
some
difference,
understanding
from
from
different
perspective
right.
If
we
see
API
changes.
What
does
that
mean?
Medicine
is?
There
is
a
API
already
here
and
it
is
continuous
provided
in
the
future
release,
but
the
behavior
change.
So
that
is
a
API
change
which
is
incompatible
right,
but
the
application.
Maybe
it
is
some
difference,
the
API.
We
are
not
there
right,
it
is
removed.
We
we
actually
do
not
change
the
API
Behavior,
which
we
just
replicated
or
launch
the
featured
application
right.
C
E
B
Sorry
in
Harvest
release
in
the
previous
release.
If
there
are
any
API
change
we
will.
We
actually
will
I'm,
not
sure
if
that
already
have
happened,
but
I
remember.
If
there's
some
break
changes,
we
were
clearly
pointed
out
right,
so
I
think
from
API
perspective.
B
My
understanding
is
it.
It
is
something
Behavior
change,
not
another
verification
right,
but.
A
A
Yeah
but
yeah
I
mean
people,
people
yeah
I
mean
I'm
I'm
open
for
any
change
right
but
I
think
for
me
the
important
part
is
to
be
consistent
and
if
we
suggest
that
we
do
something
like
semantic
versioning
and
the
and
the
community
is
expecting
it
from
something
from
it
right
how
they
interpret
the
semantic
versioning
specification
and
we
interpret
it
differently.
Maybe
we
should
not
call
it
semantic
versioning
in
our
site.
That's
it.
E
B
A
E
For
the
not
for
it
application
where
we
are
now
never
not
API
change,
if
you're
not
definitely
any
API,
just
remove
the
the
Notre.
Add
the
signature
tool
to
support
Hardware
to
sign
the
image
so.
A
A
A
E
Yeah
I
agree
with
you.
So
can
you
read
the
discussion
within
the
maintenance
group?
So
then
we
can
discuss
this
topic
so
yeah
so
that
that's
quite
we
we
have.
We
should
have
concrete,
clearly
a
message
to
the
community.
So
what
we
do,
what
we'll
do
in
major
or
minorities
so
do
not
to
break
their
expectation.
Yeah
lucky,
like
you,
said
that
they
they
just
upgrade
Harbor
with
the
automated
automatically
the
in
the
the
agriculture
cicd.
There
may
be
some
breaking
change
so
so
we
should
clarify
the
the
our
policy.
A
I
have
maybe
a
question
to
Florian
he's.
Yes,
I
am
the
hello
Florian
hello.
There
have
been
a
few
terraform
provider
updates
I
like
pull
request,
yeah.
F
C
A
Few
few
pull
requests
piling
up,
yeah.
F
I
saw
them
that
I
did
another
time,
because
I
was
not
available
last
month.
A
A
Okay,
thank
you
very
much
yeah.
Otherwise,
I
don't
have
any
questions
or
topics
to
discuss.