►
From YouTube: Harbor - Enterprise Cloud Native Artifact Regi... Yan Wang, Chenyu Zhang, Daojun Zhang & Vadim Bauer
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Harbor - Enterprise Cloud Native Artifact Registry - Yan Wang, Chenyu Zhang, Daojun Zhang, VMware & Vadim Bauer, Container Registry
Project Harbor is an open-source trusted cloud native registry project that stores, manages, signs, and scans content, thus resolving common image or Helm Chart management challenges. It has been widely used by organizations large and small around the world to resolve both the container image and Helm Chart management challenges. In this presentation, we will cover some advanced features of using Harbor, such as image signature management(cosign), image management in a cloud environment, unified management of Helm chart and container images, and highly-available deployments.Furthermore, the team would love to get feedback from users and contributors to current features and future roadmap.
A
Hi,
everyone
welcome
to
harbor
nintendo
track
talk,
and
today
we
have
a
hardware
maintenance.
Here
we
have
quite
a
few
modern
euro
session.
Let's
have
a
quick
round
self
introduction.
First,
my
name
is
yan.
I'm
a
software
engineer
at
vimeo
in
modern
application
business
unit,
and
I
have
been
work
on
harvard
for
about
four
years.
Have
you
passed
to
your
stone.
B
C
Hi
everyone,
my
name
is
shunwan
and
I
joined
vmware
nearly
a
year
ago.
I
am
a
hubble
maintainer
and
I
also
take
the
responsibility
of
maintaining
the
hubble
ham
project
as
well.
In
today's
video,
I'm
going
to
present
the
hubble
2.5
recap
and
the
course
and
demonstration
and
redeem
please
introduce
yourself.
D
Yes,
hello,
everybody,
my
name
is
madin
bauer,
I'm
one
who
is
not
working
for
vmware,
I'm
working
for
a
company,
eight
gears
and
we
are
providing
harbor
as
a
service.
And
recently
I
became
a
maintainer
of
harbor
and
I'm
happy
to
give
an
introduction
about.
What's
coming
up
coming
next
in
harbor
for
the
2
6
and
beyond
releases.
A
A
Let's
take
a
look
at
our
core
tenants.
We
offer
a
lot
of
different
features.
Here
are
the
key
seams.
You
can
have
a
multi
tendency
with
using
hardware
project.
You
can
have
raw
face
the
access
control
with
reverse
rows
in
half
today,
and
you
can
control
this
with
authentication
best
back-end
service,
local
db
or
oitc
or
ldap.
A
Artifact
distribution
is
referring.
The
ability
to
move
artifact
from
one
registry
to
another
and
the
target
regulatory
could
be
another
harbor
instance
or
third
party
radishes
cloud
regulators,
so
you
can
set
the
replication
policies
for
those
privacy.
Cache
allows
you
to
use
hardware
to
process
and
catch
immediately
from
our
target
registry,
for
example
like
docker
hub
and
there's
a
big
theme
around
the
security
and
the
compliance.
A
C
Okay,
so
there
are
two
parts
regarding
hardware:
2.5
recap:
one
is
about
the
new
features
being
introduced
in
205
and
the
other
one
is
improvement
being
made
in
2.5
in
the
first
part.
Let's
start
talking
about
improvements
that
have
been
made
in
205.
First
to
improve
the
performance
we
implemented
concurrent
pro
requests
by
asynchronously,
updating,
artifacts
pool
time
and
repository
per
count,
and
then
garbage
collection
is
now
failure,
tolerant,
which
means
it
can
continue
to
deleting
subsequent
artifacts
when
removing
the
current
artifact
errors
out.
C
C
In
the
second
part,
let's
talk
about
the
new
feature
in
2.05,
which
is
mainly
about
integrating
copper
with
cosine.
We
will
have
a
demo
on
this
course
integration
later
in
this
session,
but
let's
talk
about
some
details
of
it
now.
Firstly,
our
users
might
be
interested
in
how
cosine
signature
is
stored
in
harbor,
the
cosine
signature
is
essentially
an
oci
compatible
artifact
stored
in
harbor
as
an
accessory,
which
is
associated
to
the
subject
artifacts
and
can
be
deleted
independently.
C
C
C
In
most
user
scenarios,
we
would
like
the
association
relationship
being
replicated
over
to
the
destination
registry
whenever
either
during
a
push-based
replication
or
a
pool-based
replication,
and
that
is
how
causing
accessory
integrates
with
hardware
replication
functionality.
In
other
words,
the
corsa
signature
will
be
automatically
replicated
over
to
the
destination
registry
as
an
accessory
of
its
subject.
Artifacts
next
step,
please.
C
Oh
yes,
this
one,
and
in
this
page
we
have
some
slides
in
terms
of
corsair
integration,
such
as
the
support
to
store
cosine
signature
as
an
accessory
in
harbor,
the
support
of
automatically
replicating
artifact
signature
to
another
harper
instance,
and
policy
enforcement
to
disable
poorly
and
unsigned
image
from
harbor.
Additionally,
we
have
an
image
on
the
right
to
illustrate
a
visual
conception
of
how
cosine
works
in
harbor.
B
B
We
found
that
there
are
many
inquiries
executed
repeatedly
in
a
single
poor
request.
These
queries
could
be
cast.
The
cache
layer
will
be
implemented
in
a
manager
layer.
Cache
data
in
manage
layout
make
it
easier
still
work
on
whatever
data
position
layer
it
used.
We
could
leverage
the
same
cache
layout
for
postgres
or
mysql.
B
B
B
B
B
We
have
image
scanning
service
which
could
scan
image
and
view
a
cv
report
because
it
might
contain
thousands
of
cves
we
found
the
report
might
be
huge.
Also,
should
we
move
to
the
previous
slides
about
the
season?
Artifact
yeah,
the
cv
report
download
the
prices
should
be
asynchronized.
We
adopt
the
job
service
to
wrong.
I
synchronized,
then
it
will
export
the
cv
report
in
a
file.
Where
should
we
store
this
file
so
that
we
could
consume
a
habit
hubble
core?
B
Performance
issue
to
the
database:
should
we
slow
in
position
volume
we
will.
It
will
also
impact
the
scalability
of
the
job
service
part.
Finally,
we
consider
use
the
redis
storage
to
store
this,
this
certain
files
and
name
these
sort
of
files
as
seasonal
effect.
In
future,
we
could
extend
it
to
any
file
needed
to
store.
B
The
third
item
is
the
audio
log.
Could
we
move
to
the
next
slide
now?
The
third
item
is
the
audio
log.
As
we
mentioned
before,
the
audio
log
grows
fast
in
high
concurrent
poor
request
environment.
Sometimes
it
might
reaches
15
gigabytes.
Any
operation
in
such
huge
table
will
be
slow
and
also
consume
the
hour
time
of
database.
B
B
B
A
C
C
C
C
C
C
C
C
C
We
know
that
there
are
two
types
of
replication
you
cover:
one
is
proof-based
replication
and
the
other
one
is
a
pool-based
replication,
essentially
the
course
and
accessory
will
be
replicated
over
to
the
destination
registry.
Together
with
the
subject
artifacts,
no
matter,
it
is
a
push-based
replication
or
a
pool
based
replication.
C
C
C
D
D
D
D
So
the
other
area
of
improvement-
and
this
is
something
also
for
the
community-
currently
harbor-
supports
only
postpress,
but
there
is
a
major
effort
going
on
to
support
other
databases,
not
just
the
postgres
and
the
next
you
know
desired
state
is
to
support
maria
tb
and
my
sequel.
So
there's
an
effort
going
on
in
the
community
and
if
you're
interested
in
participating,
we're
happy
to
to
invite
you
to
join.
D
As
I
said,
harbor
is
used
by,
you
know
hundreds
and
thousands
of
companies
worldwide
and
to
my
knowledge
there
is
over
20
000
instances
running
and
publicly,
and
there
is
even
more
instances
running
behind
firewalls
and
and
on-prem
environments.
So
it's
a
huge
huge
user
base
and
there's
a
huge
community.
D
As
you
can
see,
we
have
a
lot
of
contributions
from
a
lot
of
companies
and
and
there's
a
lot
of
issues,
a
lot
of
tasks
going
on
so
as
a
really
active
community,
and
we,
of
course
trying
to
improve
our
community
and
improve
working
with
the
community.
So
we
are
have
a
multiple
ways
how
you
can
engage
with
the
community.
D
So
if
we
go
to
the
next
slide
I'll,
so
there's
a
two
two
working
groups
currently
going
on.
One
is
the,
as
I
said,
the
database
working
group.
So
if
you're
interested
in
supporting
other
databases
than
just
my
sequel,
which
is
currently
worked
on,
you're
invited
to
join
the
working
group,
and
you
contribute
to
that
if
you're
interested
in
you
know
having
support
for
another
database
than
just
my
sequel.
D
There
is
another
working
group
going
on
regarding
supporting
other
formats
of
container
images.
So
there's
the
typical
format
of
container
images
that
you
know
everybody
knows
is
aware
of,
but
there
are
other
formats
that
are
more
compact,
for
example,
and
and
allows
allow,
for
example,
a
better
startup
type
of
container
images.
D
So
there
is
a
working
group
going
on
and
it's
quite
active
actually
to
support
this
this
format,
so
one
format
is
nidus.
For
example,
that
is
a
more
compact
format
of
image.
Storing,
so
you
could.
You
know
pack
pack
more
images
into
your
storage,
and
this
will
be
as
an
effort
to
integrate
this
functionality
into
harbor
last
step,
how
you
can
engage
with
the
community.
D
It's
gonna
be
the
next
slide,
so
the
there
are
four
ways
how
you
could
engage
with
the
community
of
harbor
and
the
I
think
the
most
easiest
one
for
all
developers
is
of
course
slack.
So
there
is
a
slack
channel
on
link
is
missing
here,
but
the
slack
channel
is
on
the
cncf
cncf
and
the
channel
is
harbor
and
haberdev.
D
So
if
you
have
questions
you
can
join
the
users
channel
on
harbor
and
if
you
would
like
to
contribute
to
the
project
and
if
you
have
developer
rated
questions,
you
can
join
the
developer
channel
on
the
cncf
and
there
is
also
a
cncf
mailing
list,
mostly
used
for
announcements.
So
if
you
want
to
stay
up
stay
up
to
date
with
harbor,
it's
advised
to
to
join
this
mailing
list
and
of
course
the
same
goes
for
the
twitter
handle.
D
It
is
mostly
used
for
announcement,
and
you
know
if
you
want
to
be
up
to
date
with
the
current
release
date
of
harbor
and
last
but
not
least,
is
our
regular
meetings
on.
I
think
it's
every
second
week
on
wednesday
afternoon,
central
european
time,
you're
welcome
to
join
the
meeting
as
a
user
or
as
a
contributor
or
as
a
potential
contributor.
D
You
can
join
them
during
the
meeting
and
you
know
see
for
and
learn
first
first
hand
where
harbor
is
currently
standing
at
and
there
is
also
a
special
working
group
meetings
that
are
happening
every
another
week
as
well,
but
when
they
are
happening
you
can
find
it
in
the
in
the
community
and
also
in
the
in
the
slack
channel.
So
this
is
the
the
best
way
how
you
could
engage
and
communicate
with
the
community.