►
From YouTube: CNCF Harbor's Community Zoom Meeting - Dec 14, 2022
Description
CNCF Harbor's Community Zoom Meeting
A
Foreign
today
is
December
14th
and
that's
the
official
community
meeting
for
project
Harbor.
My
name
is
manager,
it's
official
cncfmitting.
So
please
follow
the
code
of
conduct
and
just
be
nice
to
each
other
I've
pasted
in
the
chat.
The
link
to
the
community
meetings
notes
for
today
feel
free
to
do
yourself.
Add
your
topics
and
we
can
kick
off
alrighty
I'm
gonna
share
what
we
have
for
today.
A
Okay,
I
hope
everyone
can
see
that
nice,
okay,
I'm
gonna,
refresh
first
didn't
change
much,
but
anyway,
all
right.
I
have
two
things
for
today:
first,
one
to
update
you
that
almost
ready
with
the
block
427,
which
would
be
next
week
right
I'll,
put
it
out
for
review
in
the
website
repository.
So
if
you
can
take
a
look,
I'll
paste
it
in
the
maintenance
or
in
the
dev
Channel,
so
you
can
put
your
recommendations
there.
A
A
D
Yeah
sure
hi,
something
like
that.
It's
a
nourish
knowledge,
European
knowledge
name,
it's
every
everywhere
from
something
different
I'm
sitting
in
the
north
of
Journey
I'm
working
for
a
company,
doing
mostly
Road,
optimization
stuff,
and
we
are
using
Hardware
as
our
registry
for
container
yeah
for
our
container
stuff
and
I
I'd
like
to
contribute
to
open
source
because
I've
used
it
myself
very
much
and
I
have
another
side
project
running
somehow
on
on
GitHub.
It's
a
library
for
doing
zipper
stuff.
D
D
A
D
A
B
A
D
A
Okay
or
you
have
a
very
small
chain
of
reporting,
that's
great
I,
I
work
for
VMware
and
and
and
we
have
like
a
I-
don't
know
a
thousand
lines
of
reporting.
So
if
I
go
to
the
CTO,
I
should
go
through
several
people
anyway,
so
yeah.
So
if
you
feel
like
it
and
if,
if
you
have
the
willing
to
to
share
it's
going
to
be
great,
otherwise
yeah
also
great
super
happy
to
have
you,
but
then
once
you
I
can
see
in
the
things
that
he
wants
to
ask
something.
B
A
C
C
A
F
B
C
B
And
the
thing
is
that
I
would
rather
not
lose
it.
You
know
yeah,
so
so
I
would
rather
not
lose
it
and
try
to
to
work
with
I
think
Lassa
is
or
someone
else
from
bestseller
we
can
work
with,
and
we
had
an
already
discussion
in
the
past.
I
know
I
need
to
check
my
my
emails
and
helping
I'll
ping,
also
a
bestseller
to
see
if
they
can
transform
the
repository
to
us
or
if
they
are
not.
Let
me
check
how
many
projects
are
using
on
registry.
B
Okay,
they
use
a
harbor,
netbox
and
Luis
okay.
They
have
multiple
instances
there
yeah
so
I'll
ask
again,
but
apart
from
me
asking
we
also
need
to
set
up
a
process
for
you
that
you
can.
Maybe
you
know
kind
of
release
to
to
the
registry
already
you
know,
and
then
we
can
maybe
either
take
it
down
or
merge
it
together.
Somehow
we
can
find
a
way
how
we
can
then
make
it
work.
Okay,
but
yeah.
Thank.
C
A
A
F
C
A
G
D
G
B
A
B
Harbor,
you
know
which
is
responsible
for
installing,
and
configuring
Hardware
this
operator
will
be
more
for
managing
hover.
You
know
you
can
of
course
configure
it,
and
maybe
one
day
the
harbor
operator
can
use
this
operator
as
well.
I'm,
sorry
before
the
operator
names,
but
I
I
call
the
one,
the
the
one
that
we
have
currently
in
Harbor
I
call
it
the
install
operator
because
it
installs
a
harbor
and
configures
it,
and
the
other
one
is
like
the
the
operator
that
the
managing
operator,
you
know
the
application
managing
operator
to
go.
B
You
know
current
working
with
those
people
together
to
see
how
we
can
align
on
the
on
the
roadmap
on
the
timeline
and
the
functionality
that
should
be
in
such
an
operator
and
then
we'll
plan
to
do
in.
You
know:
January
February,
a
proposal,
a
community
proposal,
a
presentation
how
to-
and
you
know
how
to
move
forward.
D
B
C
B
B
Then
we
had
here
the
harbor
automation,
4K
8s,
and
this
is
now
part,
so
the
functionality
here
contained
here
is
now
part
in
the
go
Harbor
Hub
operator.
So
it's
part
it's
now
part
here.
So
it's
that's
why
it's
not
maintained
anymore,
because
it's
moved
in
the
operator.
Then
we
have
the
the
mid
Cloud
operator.
B
Yeah
this
is
the
the
mid
Vault
Hub
operator.
This
is
this
one.
It
is
up
to
date.
It
is
used
and
I
talked
to
the
Midfield
guys
and
they're
eager
to
you
know,
move
their
project
into
Harbor
and
collaborate
on
that.
So
we
can,
you
know
you,
you
know,
unite
our
work
together,
like
from
from
the
diner
Trace
people
from
giant
sworn
people
and
from
from
our
community
from
us
to
create
a
proper
official
operator
out
of
maybe
out
of
this,
but
we
need
to
investigate
it
further
yeah.
B
G
C
G
Those
operations-
yeah,
yeah
I,
know
they
are
doing
similar
scenes,
but
we
do
have
a
official
operator
there
and
we
do
have.
Maintenance
are
working
on
that
yeah.
So
so
so
I
again
I
I
like
to
hear
what
they
want
and
and
what
we
want.
They
want
to
contribute
to
this
project,
but
not
to
merge
their
project
into
hours.
B
B
C
G
B
In
common,
so
giant
swarm,
mid,
World
and
also
dynatrace,
and
we
as
well
have
requirements
on
an
operator
that
are
not
covered
here,
and
we
can
yes
do
it.
We
can
do
it
in
two
ways.
One
way
is
you
know,
making
you
know
a
pull
request
here
and
and
make
it
then
make
it
work
here.
The
problem
is
that
this
operator
here
fulfills
two
tasks
at
the
same
time:
first,
it
installs
Harbor.
B
You
know
it's
responsible
for
installing
and
maintaining
a
harbor
installation,
yes
and
configuration
hardware
and
those
other
operators
is,
is
not
for
installing
it's
just
for
managing.
However,
you
know-
and
the
overlap
here
is
just
on
the
config
object
right.
So
this
is
the
only
overlap.
There
is
so
and
that's
why
I
would
like
to
have
the
kind
of
this
operator.
B
Maybe
one
day
it's
not
now,
but
maybe
one
day
it's
split
in
two
one
is
the
the
installation
part
that
is
already
there
and
it's
you
know,
should
keep
maintained
and
should
be
there
and
then
just
for
the
configuration
part.
You
know
without
installing
installing
Harbor
just
for
operating
hover,
and
this
can
be
done
in
in
many
in
different
ways,
so
it
can
be
merged
together.
It
can
be.
B
We
can
contribute
to
this
project,
it
depends,
but
first
we
need
to
kind
of
get
a
common
common
understanding
about
what
this
the
managing
operator
should
do
and
then
seconds
getting
the
requirements
correctly
and
and
implement
it
and
I
think
we
have
a
lot
of
Manpower
here
that
is
eager
to
contribute,
and
if
we,
you
know
push
them
into
this
repository.
This
is
not
clearly
what
there
are
they
need,
because
otherwise
they
would
contribute
already.
You
know
so
I
think
we
need
to.
You
know,
make
a
step
towards
them
and
see.
B
G
B
B
C
A
C
A
Okay,
that's
that's
huge!
Okay,
by
the
way
something
similar
happened,
I'm,
not
sure
if
you
follow
that,
with
with
contour
and
Envoy
when
they
introduced
the
the
envoy
Gateway
pretty
much
this
crap
not
scrap
that
they
adopted
some
best
practices
from
contour
and
they
they
started.
A
new
project
called
get
void,
Gateway,
which
stepped
on
the
already
existing
Contour
code
base.
A
A
C
A
B
B
Cases
the
operator
do
two
different
things
and
like
one
is
like
the
one
that
we
have
has
a
has:
a
focus
on
the
installation
and
configurational
Power,
and
those
things
are
at
the
moment.
At
least
you
know
are
difficult
to
separate
if
we
can
make
it
work
that
we
have
just
one
operator
that
has
two
functionalities
and
you
can
clearly
decide.
I
want
to
have
this
functionality
or
I
have
I
want
to
have
this
functionality
totally
totally
perfect
I'm.
It's
the
ideal
use
case.
B
C
B
A
Normally
it's
achieved
like
this
I
mean
not
two
separate
operators,
because
by
definition
operator
means
exactly
what
we
are
describing
in
the
second
portion
of
it,
not
not
only
installation
but
like
data
operations
and
long-term
configuration
and
management.
So
if
we
decided
to
introduce
a
new
one
I'm,
just
asking.
C
A
Also
that
all
that
discussion
should
be
like,
including
the
say
it
did-
the
commitment,
long-term
commitment
of
maintaining
and
developing
this
stuff
yeah.
If
all
the
different
parties
like
in
this
case
companies
decide
to
put
effort
on
it
on
it,
and
then
that
applies
their
the
use
case.
We
should
all
agree
on
on
the
the
long-term
commitment
to
the
project.
A
E
Is
that,
second
time
yeah
yeah,
hello,
everybody
yeah?
My
name
is
cage
I'm
in
like
a
new
end
user,
the
harbor,
I,
guess
and
I
hope
I
kind
of
joined
today,
because
implementing
and
I
had
some
issues
with
Helm
charts
and
istio.
So
I
just
want
to
clarify
a
couple
things
if
this
is
the
right
kind
of
audience.
For
that.
A
It's
it
cannot
be
more
appropriate
to
discuss
this
stuff,
that's
community
meeting
office
hours
because
we
don't
do
office
hours
separate
office
hours.
So
when
we
finish
discussion
on
the
project
updates
and
and
overall,
like
ongoing
maintenance
and
maintenance
topics,
we
can
we
can
do
discussion
on
on
issues
if
someone
joins
like
you,
so
welcome
and
sorry
for
Miss
for
asking
your
name
is
Sage,
but
it's
page.
It's
okay,.
E
Yeah
so
I
don't
know
if
necessarily
a
problem,
maybe
just
like
a
lack
of
understanding.
So
I
guess
my
my
first
question
was
I.
Looked
at
both
a
bit
Naomi
and
the
go
Harbor
charts
and
it
looks
like
you
need
either
proxy
or
Ingress.
So
when
you're
with
using
istio
is
it
is
it
still
required
to
use
one
of
those
or
can
you
do
none
and
kind
of
do
like
the
routing
yourself?
E
B
And
I
can
maybe
answer
or
help
you
answer
it.
So
istio
hasn't
built-in
Ingress
right,
correct
yeah.
So
what
you
can
do
is
you
can,
you
know,
set
up
the
let's
say
the
official
egress,
the
official
Ingress
workflow,
that
is
there
and
then
you
just
copy
and
paste
the
the
settings
that
the
Ingress
would
generate
into
your
Ingress
into
your
istio
settings,
and
this
should
work.
B
B
E
B
E
B
Yeah,
so
they
they
I
mean
the
hardware
does
not
support
the
Gateway
or
the
virtual
service
right,
so
it
just
supports
the
classical
Ingress
type.
So
if
istio
does
support
the
classical
linguist
type,
then
you
can
generate
it
this
way.
If
not,
you
can
just
generate
a
classical
Ingress
and
then
just
copy
and
paste
the
settings
from
there
into
your
sto
and
virtual
service
type,
and
then
it
should
work.
E
G
B
E
Yeah
we
we
actually
kind
of
just
came
over
like
we
came
across
so
normally
we
bitnami
for
most
things
and
we
actually
just
found
the
harbor
chart,
and
that
was
our
thought
was
right.
Use
like
the
directly
kind
of
built
and
supported
one
from
you
guys
so
we'll
probably
end
up,
switching
or
I'll
end
up
switching
and
using
it
this
week.
So.
G
On
for
the
is
still
integration
or
of
charge,
so
you
can
just
file
issues
or
not.
We
do
have
received
several
queries.
Queries
on
this
on
and
actually
we
haven't
verified
that
yet
so
maybe
we
do
have
some
issues
on
that,
but
you
can
just
fill
issues
or
feature
requirement
on
that,
and
then
we
can
do
some
investigation
on
the
Easter
so
but
so
far,
based
on
our
experience,
I'm
I'm
not
sure
it's
fully
work
always
is
still
well.
E
Yeah
I
was
just
wondering
if,
like
if
it's
possible,
like
I,
don't
know
if
it
works
right,
I'm
kind
of
new
to
this,
but,
like
I,
don't
know
if
you
could
do
like
an
exposed
type
of
none
and
then
just
set
up
your
own
networking
or
like
how
like,
however,
you
wanted
to
talk
to
the
services
like
or
if
in
the
code
base
like
either
Ingress
or
in
genetics
like
if
it's
a
requirement
in
some
way,
some
dependency.
You
know
what
I
mean.
C
G
B
E
B
B
C
A
E
E
Yeah
I
just
joined
this
project,
so
a
lot
of
the
stuff
I'm
picking
up
just
what
they're
doing,
but
it's
like
kind
of
like
a
research
kind
of
project
like
they're,
trying
to
do
something
like
on
on
the
on
the
edge
I
guess
so
yeah.
This
is
like
kind
of
like
a
first
time
thing
for,
for
this
particular
agency.