►
From YouTube: CNCF Harbor's Community Zoom Meeting - August 10, 2022
Description
CNCF Harbor's Community Zoom Meeting
A
So
hello,
everyone
welcome
to
the
b
weekly
harbor
community
meeting.
So
let's
get
started
today
is
the
10th
of
august
2022,
and
we
have
already
a
few
topics
on
the
agenda.
Today
we
can
start
with
jolin
who
gonna
talk
about
the
current
state
of
harvard
2.6.
B
Charlie,
hey,
hey,
thank
you!
Randy,
okay,
yeah.
The
first
one
is
about
the
status
of
2006
and
in
last
community
meeting
we
have
mentioned
that
we
postpone
the
release
date
for
2006
to
august
15,
so
that
that
is
same
as
over
now
so
next
monday
we
will
gs
is
released,
so
we
would
suggest
community
to
try
this
version
and
the
feedback
for
any
any
feedback
that
will
come
to
us.
C
C
Yes,
yes,
oh
they
told
me
that
you
can
have
to
handle
that,
and
I
will
stick
with
you
about
how
we
talk
to
it,
release
in
the
github
and
we
should
probably
have
to
manually
edit
the
release
node.
C
We
have
some
automation
job
to
automatic,
automate
it
to
create
the
traditional,
but
we
have
to
reorganize
them
and
add
some
human
readable
comments.
Okay,
but
are
they
release
notes.
A
B
Yeah,
I
think,
for
this
node
previously,
we
have
some
only
have
substance,
provides
some
functionality
to
generate
all
release
nodes
and
follow
the
release
nodes
depending
on
the
label.
When
we
checking
the
request
and
then
yeah
this-
that
is
a
apollo
with
release
notes,
and
another
part
is
something
I
think
we
added
manually
to
describe.
A
B
B
Okay,
so
that's
great
and
thank
you,
yeah
and
I
I
want
to
add
more
information
about
2006.
I
think,
like
the
community
have
already
seen
the
release
release
information
in
the
rc
release.
I
just
want
to
echo
that
what
is
the
new
feature
we
have
in
this
release?
B
We
have
doing
some
improvement
for
performance
which
introduced
a
cache
layer
in
this
release,
so
that
is
very
helpful
for
the
enterprise
user,
which
has
a
lot
of
the
pool
and
and
the
push
request,
and
the
second
feature
is
the
cv,
vulnerability
export
feature,
I
think,
in
communities.
There
are
a
lot
of
ask
previously
for
export
the
cve
report,
to
I
mean
to
save
it
as
some
file
or
some
other
format.
So
this
is.
This
is
also
a
new
feature
in
2.06
and
the
second,
the
second
one
is
about
the
server.
B
Is
the
audit
log
or
redirect
and
purge
feature
so
because,
if
there
in
some
enterprise
instance,
if
you
have
a
very
large
usage
on
hubble,
there
will
be
many
many
audi
log
in
the
table.
So
we
have.
We
provide
this
functionality
to
allow
users
to
regulate,
redirect
the
log,
so
that
will
also
have
some
improvement
for
the
performance,
so
there
also
a
lot
of
some
small
enhancement
or
functionality
improvement.
So
I
will
not
go
through
each
of
this.
B
Anything
else
you
guys
want
to
add.
A
I
would
like
to
add
that
we
should
shout
out
to
the
community
to
for
the
translations
that
I
saw
already.
There
are
a
few.
A
Tags
on
the
release
that
are
on
the
close
pull
request
regarding
that
contains
e18n.
A
You
know
like
e8
and
n
translations
here
and
if
we
filter
about
those
there
are
already
a
few
issues
of
pars
with
area
internationalization,
and
we
should
shout
out
to
ask
the
community
to
help
with
the
translation
you
know
I
will.
I
can
do
this
later
after
this
meeting,
so
ask
the
community
for
different
help.
With
the
translation,
I
think
I
mean
we
have
a
few
translations
and
yeah.
A
A
B
Both
a
vote.
Yes,
so
I
think
this
top
this
topic.
We
have
discussed
in
previous
several
community
meetings
and
actually
for
the
first
one,
china
median
deprecation.
B
Yeah,
so
back
to
last
year,
I
think
they
allow
comments
coming
from
community
about
yeah
about
the
application
for
china
museum
at
that
time.
The
concern
is
saying
that
a
lot
of
we
use
usages-
I
mean
china
medium
usually
still
in
the
community,
and
at
that
time
we
re
research,
yes
to
migrate,
the
challenger
to
osi
capability,
a
compatible
artifact
so
actually-
and
they
are
also
a
concern
about
the
hem
chart
right
saying
that
it
is
not
stable
to
support
oci.
B
But
I
think
recently
back
two
months
ago,
there
is
a
new
hampshire
release.
Maybe
if
I'm
correct
it
is
3.7,
is
that
the
one
I
think
that
is
introduced
to
support
the
alsa
competition
in
hand
chart
three
seven.
A
B
Yeah,
so
I
think
that
is
a
good
news
for
community
to
change
these
use
their
site,
competitive
artifact,
so,
based
on
all
the
above,
we
we
now
would
re-launch
the
deplication
discussion
and
actually
roger
the
the
harper
pm
added
comments
yesterday
to
suggest
the
deprecation
process.
I
mean
it's
actually
process
for
this
discussion.
I
think
in
the
in
in
his
comments,
there
are
two
options:
actually,
actually
there
are
two
options:
one
is
he
write
down
here.
B
We
launched
the
discussion
launched
officially
introduced
a
deprecation
for
this
challenging
component
in
this
community
meeting
and
follow
with
the
application
process,
which
is
submitted
last
month
merged
last
month.
So
in
that
process
we
are
saying
the
second
community
meeting
I
will
continue
to
discuss
and
on
this
and
after
that,
that
around
september
we
will
counting
the
word
for
this
for
this
issue
and
to
decide
to
make
decisions
whether
we
will
deprecate
it
or
not.
So
there
are
some
details
in
these
comments.
B
I
would
suggest
community
users
and
the
maintainer
to
to
have
take
a
look
to
see
this,
so
that
is
optional
and
another
option
for
this
proposal
I
mean
the
application
proposal.
Is
since
we
we
know,
we
seized
gas.
B
This
discussion
was
launched
for
about
one
year
yeah
one
year
ago,
so
if,
if
the
maintenance
can
vote
this
by
end
of
this
week
and
if
we,
if
we,
if
this
gets
passed
in
by
the
end
of
this
week,
so
we
can
launch
the
application
in
2.6
so
target
to
remove
it
around
start
from
2008
release
so
that
that
is
option
two.
B
So
there
are
two
options
here,
so
we
will
see
in
the
in
blender
this
week
so
based
on
that,
we
will
make
the
choice.
A
We
should
we
should
vote
then
so
yeah,
here's,
the
link
correctly.
So
just
write
your
comment.
If
so,
should
we
do
the
fast
track?
I
mean
or
or
not
I
mean.
A
Yeah
I
mean
we've
been
discussing
it
for
quite
long
and
I
well.
I
personally
would
vote
for
a
fast
track
because
yeah
fast
tracking
deprecation
and
then
maybe
remove
it,
you
know
keep
it
deprecated
until
yeah,
I
would
maybe
not
say
a
2.9.
I
would
maybe
say
3.0
so
that
we
could
remove
it
in
3.0,
which
make
would
make
sense.
But
you
know
2.0
is
because
2.9
is
because
there's
like
two
deprecation
is
after
two
releases
right.
So
this
is
our
in
our
in
our
policy.
B
C
A
A
B
So
ready,
I
just
want
to
to
be
clear
about
what
you
are
saying,
I
think
in
this
proposal
and
follow
the
application
process.
B
A
B
B
Yeah,
so
I
think
that
is
the
policy.
What
we
are.
C
B
B
C
D
Okay,
yeah,
so
so
so
from
from
from
my
perspective
as
mercedes-benz,
it
would
be
good
to
remove
it
in
2.7
earliest,
because
we
have
around
2
000
charts
in
charge
museum,
so
we
have
to
migrate
them
or
our
customers
have
to
migrate
them
and
yeah
206
is
way
too
early,
so
for
us
so
but
yeah
2.7
is
then
I
got
it
totally.
Fine.
B
Yeah,
but
you
know
usually
for
hubble,
we
have
four
monsters
released
cycle
for
a
mana
release,
so
you
can
say
start
from
now
before
it
it
could
be
removed
from
2.8.
There's
still
eight
monsters
right
yeah.
So
I
think.
C
D
D
So
yeah
we
already
started
or
we
will
start
the
communication
in
september
after
all
the
vacation
in
germany,
so
to
inform
our
customers
that
they
should
migrate
from
from
child
machine
away
to
the
helm,
oci
supported
version,
and
then
hopefully
this
will
be
done
beginning
next
year.
So.
C
B
D
B
Thank
you
very
much
and
so
yeah
vadim.
I
think
another
order,
nintendo
kind
of
like
in
this
meeting.
Maybe
we
we
need
to
one
one
one
way
we
can
do
it
to
add
the
maintenance
to
to
let
them
know
about
this
and
to
to
to
vote
for
this
proposal.
B
B
A
B
And
I
think
before
I
would
add
sorry
sorry
waiting
to
interrupt.
I
would
add
some
background
here.
You
know
notary
one
is
the
first
is
the
first
image
sending
tool
which
is
integrated
with
the
hardware,
and
it
is
worked
for
about
years
and
where,
but
I
think,
since
maybe
latest
three
or
two
years
and
the
notary
one
is
not
that
activity.
You
can
see
what
only
statement
here
when
he
opens
this
issue
discussion
uh-huh
it
is,
it
is
almost
no
commitment
about
about
one
year
right.
That
means
yeah.
B
That
project
is
not
active
and
also
for
the
upstream
northwest
too.
We
still
not
seeing
any
deliver
till
now
and
so
consider
that
hubble
have
we
introduced
another
imu,
sending
functionality
in
2.5,
which
is
called
send
to
standard
image.
I
think
that
could
be
a
good
choice
for
art
and
for
community,
so
based
on
that,
we
now
propose
to
deprecate
the
noto
v1
in
hubble.
So
that's
a
background
hope
this.
Hopefully
this
can
give
you
some
useful
information
about
this.
B
C
B
So
so,
well,
I
think
that's
all
to
topic
from
my
side
all
right!
Oh
sorry,
I
remember
I'm
not
saying
about
the
kukkum
nga.
I
think
there's
something
maybe
we
need
to
follow
up.
I
think
one
year
maybe
can
provide
some
detailed
information
about
this.
C
Yeah,
hey:
I
have
forward
your
email
about
the
nintendo
track
session,
exactly
yeah.
A
C
Add
our
option
to
the
cc
app
whether
we
want
to
host
a
kiosk
or
whether
we
want
to
host
office
hours
and
whether
we
want
to
do
an
in-person
session
or
virtual
recession.
So
there
was
only
two
more
days
to
to
make
it
down
so,
but
here
is
now
on
location.
I
cannot
contact
with
him.
C
A
A
A
It's
called
I'm
interested
in
the
pr
support
for
upcoming
release
and
feature
announcement,
and
I
think
this
is
related
to
the
announcement
feature
announcement
of
harbor
in
in
the
global
on
the
global
conference.
In
the
main
stage.
Am
I
right.
A
A
C
Yeah
yeah
this,
the
china
team
cannot
attend
information
so
yeah.
So
so,
if
you
are
online
can
host
that
we
can
provide
the
slice
and
or
demo
for
you,
but
you
guys
have
has
to
host
that
session.
Okay,
yeah.
C
Your
yeah.
A
B
C
C
B
C
B
C
A
C
A
A
The
thing
is
that
there
were
a
few
things
that
we
have
found
and
but
nothing
you
know
nothing
critical
and
what
I
will
do
is.
I
will
create
tickets
out
of
it
so
that,
like
four
or
five
issues,
I
will
create
a
ticket
out
of
it
and
we
can
then
address
them
inside
the
as
a
project.
But
there
is
no
nothing.
A
You
know
nothing
critical
was
found,
which
is
good
news,
but
there
are
a
few
things
that
were
found
like
regarding
cookie
security
and
then
cash
cash
and
cash
problems
and
a
few
few
other
issues,
but
nothing
and
nothing
scary,
I'll,
create
an
issue
regarding
that.
There's
like
four
or
four
things,
one
I
already
created
this
was
regarding
nginx.
A
As
you
remember.
Maybe
we
could
discuss
this
one
as
well
like
is,
there
is
no
I
mean
there
is
regarding
nginx.
There
is
currently
a
very
old
version
of
nginx
running,
which
is
not
supported
anymore,
as
I
created
the
ticket
for
that,
and
the
reason
for
that
is
that
photon,
which
is
you
know,
deployed
with
the
harbor,
is
based
on
it's
using
photon
based
layer
base
image,
and
the
question
is:
if
there
is
no
mandatory
to
use
photons,
can
we
switch
it
to
plane
engine
x?
A
C
So,
but
the
currently,
why
we
actually
choosing
the
photon
as
the
base
image,
because
that
we
can
have
the
support
from
the
wooden
team
to
help
us
to
fix
the
cv
for
any
building
library
like
ngx.
But
if
we
choose
the
engines
and
official
base
image,
we
probably
cannot
ask
them
to
help
us
to
fix
the
cve
and
then
align
the
fixed
with
our
release
cycle.
C
A
A
B
Think
if
it
is
some
security
issue
based
on
the
my
understanding,
maybe
I'm
around
based
on
the
hubble's
governance,
I
mean
yeah.
B
Process
we
should
not.
We
should
use
the.
B
C
B
Should
not
create
issues
before
before
communicating
in
the
security
email
distributed
listing
right.
A
Yeah
I'll
I'll
do
because
yeah,
I
think
most
of
those
issues
are
not
security
relevant.
So
it's
okay
to
create.
It
just
create
an
issue
so,
but
I
will
I'll
do
anyway.
First,
the
the
official
way,
and
then
we
can
see
the
rest
yeah.
C
A
Yeah
then
that's
that's
it
from
from
my
side
I
mean
I
have
much
more
points,
but
that's
for
now
any
other
discussions
or
topics.