►
From YouTube: Simplify Application Deployment at the Edge with Harbor - MICHAEL MICHAEL, Harbor Don’t miss out!
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
Simplify Application Deployment at the Edge with Harbor - MICHAEL MICHAEL, Harbor Don’t miss out!
Harbor offers a lot of capabilities as a registry in the datacenter. Recently, we have focused our energy on better image distribution and Edge scenarios. You can't operate Kubernetes at the Edge without a registry and Harbor is making it easier and simpler to co-locate your workloads with your cloud native artifacts. Integrations with P2P providers like Uber’s Kraken and Alibaba’s Dragonfly and Proxy Cache capabilities are key features that make image distribution at the Edge possible.
https://sched.co/fGWK
A
My
name
is
michael
michael
and
I'm
one
of
the
hardware
maintainers,
I'm
actually
very
involved
in
the
cmcf
community,
I'm
also
maintainer
for
contour,
and
I'm
also
one
of
the
chairs
in
the
kubernetes
community
responsible
for
seek
windows.
I'm
idea
right.
I
am
a
director
of
product
management
at
vmware
and
you
can
find
me
under
the
alias
m2
on
slack.
A
So
what
is
harbor
harbor
is
a
cncf
graduated
project.
We
graduated
this
past
summer
and
we're
super
excited
to
be
part
of
the
cncf
highest
level
of
ecosystem
set
of
projects.
Our
mission
is
to
be
the
trusted
cloud
native
repository
for
kubernetes,
so
we
want
to
be
very
fast,
very
efficient,
very
secure
and
the
de
facto
way
that
you
use
for
storing
all
of
your
cloud
native
artifacts
that
you
use
with
kubernetes.
You
can
find
us
on
twitter
at
project
hardware,
as
well
as
on
our
website.
Gohardbird.Io.
A
A
So
you
can
rest
assured
that
the
images
and
the
applications
you're
putting
in
production
don't
have
any
vulnerabilities
and
we
sign
images
as
trusted.
So
you
know
where
these
images
are
coming
from.
With
that
hardware,
delivers
compliance
performance
and
interoperability
to
help
you
as
a
user
as
an
enterprise
consistently
and
securely
manage
your
artifacts.
A
A
So
for
the
past
almost
five
years,
we
have
a
steady
contribution
across
the
board
on
hardboard
and
we
have
40
maintainers
across
five
companies
and
pretty
much
every
continent
imaginable.
So
our
community
is
thriving.
What
a
welcoming
and
open
community
if
you
want
to
come
in
and
help
us
achieve,
and
further
the
vision
of
harbor
come
and
join
us.
We
have
bi-weekly
community
meetings,
we're
active
on
slack,
we're
active
on
twitter,
come
and
engage
with
us,
we'll
love
to
hear
your
scenarios
and
enable
your
requirements
with
hardware.
A
Now
kubernetes
is,
and
has
been,
the
standard
for
container
orchestration
in
the
data
center
for
quite
some
time
now,
but
we're
now
seeing
tremendous
interest
from
users
that
want
to
deploy
kubernetes
clusters
at
the
edge
we're
actually
even
hearing
that
they
want
to
put
kubernetes
clusters
in
cars
in
airplanes,
with
the
proliferation
of
5g.
We're
hearing
about
kubernetes
clusters
that
want
to
land
at
many
edge
devices
or
many
theme
edge
devices,
and
a
lot
of
the
things
that
we
hear
from
these
users
is
that
they
want
to
focus
on
simplicity,
reliability
and
security.
A
So
they
want
to
make
sure
that
when
they
put
these
clusters
at
the
edge
they
can
manage
them
from
afar.
They
want
to
make
sure
that
these
clusters
run
autonomously
they're
secure,
but
their
applications
are
always
up
and
running,
whether
you're,
a
retail
customer,
a
manufacturing
plant
or
even
a
car.
A
But
you
can't
really
operate
kubernetes
without
the
registry.
One
of
the
fundamental
needs
of
actually
running
your
cluster
is
that
cluster
requires
images
that
need
to
be
provisioned
and
available
so
that
you
know
your
docker
or
your
container
d
runtime
can
actually
run
those
images.
So
there
is
a
need
here
for
something:
that's
a
registry.
A
A
A
The
second
area
that
we've
innovated
is
around
peer-to-peer
and
we've
integrated
with
dragonfly
and
kraken,
which
are
two
open
source.
Intelligent
peer-to-peer
based
systems
essentially
they're,
acting
like
a
content
delivery
network
for
making
sure
that
they
leverage
p2p
to
land
files,
in
this
case
your
artifacts,
where
they
need
to
go
saving
in
a
lot
of
ways:
enterprise
bandwidth,
because
they
do
that
very
efficiently.
A
A
A
We
have
identity
and
access
management
we
have
scanning,
we
have
cve
exceptions
and
the
last
one
extensibility
the
ability
to
integrate
with
the
tools,
services
and
processes
that
you
have
whether
you're
running
at
the
data
center
or
at
the
edge
we
have
web
hook,
integration,
replication,
integration
of
plugable
scanners,
a
rest,
api,
robot,
accounts,
cli
secrets.
All
of
those
make
it
possible
to
extend
hardware
and
connected
to
some
of
the
investments
that
you
made
within
your
data
center
and
for
kubernetes.
A
A
A
What
you're
seeing
here
is
the
hardware
installation
that's
on
demo.coharbot.io.
I
wanted
to
show
you
that
a
little
bit,
because
that's
a
free
instance
of
hardware,
that's
always
available,
so
you
can
go
and
try
out
some
of
our
latest
features
and
this
instance
is
actually
running
on
the
latest
release
of
hardware.
So
I
went
ahead
and
created
already
an
endpoint
for
a
registry
connected
to
docker
hub
and
I'm
going
to
show
that
to
you
really
quickly.
A
So
the
provider
here
is
dockerhub,
provided
you
know
a
name
for
this
connectivity
and
it's
an
extension
there's
a
connection
to
docker
hub
using
my
own
personal
account.
I've
went
ahead
and
verified
it,
so
we
can
test
that
connection
and
say
that
it
tested
successfully
and
click
and
exit
out
of
here.
So
now,
with
that
in
mind,
I'm
gonna
go
ahead
and
create
a
new
project
and
I'm
going
to
call
my
project
cubic
on
demo
and
hopefully
nobody
else
has
a
name,
I'm
going
to
mark
it
as
public.
A
So
I
don't
have
to
deal
with
using
username
and
password
to
connect
to
this
project
right
now
and
I'm
going
to
indicate
here.
This
is
a
new
feature
that
this
is
a
proxy
cache
and
by
enabling
this
as
a
proxy
cache,
I
get
to
link
it
to
one
of
the
existing
connections
that
I've
added
into
the
registries.
Remember.
A
The
connections
that
you
have
with
the
registries
are
being
reused,
also
with
some
of
the
replication
providers
that
we
have,
because
we
know
how
to
connect
and
replicate
content
in
and
out
pretty
much
every
popular
registry
out
there
and
including
docker
distributions.
So
in
this
case
I'm
going
to
connect
to
docker
hub
and
I'm
going
to
click.
Ok,
so
now
we've
created
our
project
here
and
it's
empty.
There's,
there's
nothing
in
it.
So
I'm
going
to
go
ahead
and
pull
up
my.
A
A
demo
mitch
mike
is
one
of
my
repositories
on
docker
hub
and
nvigo
is
one
of
the
images
I
have
there.
So
I'm
going
to
go
ahead
and
and
pull
this
and
what's
going
to
happen
behind
the
scenes
here
is
hardware
is
going
to
be
called
first
we're
going
to
realize
that
we
don't
have
this
image.
Hardware
will
pull
it
from
docker
hub
and
once
it
replenishes
the
cache
then
harold
will
have
it
will
have
it
and
provide
it
to
me.
A
So
if
I
do
docker
images
here,
I'm
going
to
see
that
you
know
I
was
able
to
download
this
image.
It's
about
one
point,
something
megabytes,
it's
a
fairly
small
image
and
I
have
an
image
id
here
and
I
get
some
of
this
info.
So,
let's
switch
back
here
to
hardware
and
if
I
refresh
this
page,
I'm
gonna
see
this
image
in
hardware,
so
there's
a
cubic
on
demo
mitch
mike
and
viggo
mis
image,
and
it
has
a
shot
here
and
I'm
gonna
go
ahead
and
copy
the
shot.
A
Just
to
show
you
that
this
is
the
same
shot
that
we
have
here
for
this
image.
If
we
were
to
look
at
this
in
docker
hub
so
connecting
to
the
same
image
in
docker
hub
and
there's
the
same
digest
that
you
see
here
is
a
linux,
amd64
image
and
now
in
hardware.
We
have
that
and
it's
available
and
it's
cached
so
next
time
we
request
it,
it
will
not
go
and
pull
it
down
from
docker
hub.
It
will
just
do
a
manifest
check.
A
Make
sure
that
this
is
the
latest
image
and
harbor
will
keep
a
local
cache
for
your
image.
So
the
more
images
you
bring
in
the
more
of
them
are
cached,
and
then
you
can
apply
all
the
different
policies
of
hubble.
You
can
scan
them.
You
can
look
at
the
policy
around
coda
and
the
ability
to
apply
tag
immutability
or
you
can
add
web
code
control
or
the
configuration
with
with
scanning
and
cv
exceptions.
A
A
So
I
can
go
into
this
option
now
and
I
can
create
a
policy
and
what
this
policy
will
do
is
it
will
take
images
from
this
project
are
defined
in
hardware
and
push
those
images
into
the
p2p
provider
dragonfly
or
kraken
and
preheat
those
images
so
that
we're
able
to
you
know,
distribute
them
based
on
the
p2p
policies
that
you
have
defined
in
that
tool,
whether
that's
dragonfly
or
kraken.
So
in
this
case
you
get
to
pick
the
provider
and
that's
dragonfly
we're
going
to
give
you
the
name,
we're
going
to
call
it.
A
A
Do
you
want
to
pick
up,
for
example,
I'm
going
to
put
star
star
here,
so
it
will
pick
up
all
the
all
the
images
and
then
the
tag
is
latest
so
now
we
will
pick
up
all
repositories,
we
tag
latest
or
you
can
add
one
or
more
tags
and
and
then
you
can
define
how
do
you
want
that
preheat
to
be
triggered?
Do
you
want
it
to
be
manual
as
in
usa?
I
want
you
to
preheat,
you
want
to
be
scheduled
based,
so
you
can
give
us
like
a
current
job.
A
For
example,
if
you
pick
customer
or
hourly
or
daily,
or
you
can
say,
I
want
it
to
be
event
based
and
the
events
here
is
when
an
artifact
is
pushed
when
an
artifact
is
labeled
or
scanned.
You
get
to
see
based
on.
Some
of
these
actions
are
happening.
For
example,
a
new
image
is
pushed
immediately,
will
get
preheated
and
sent
to
the
p2p
provider,
so
that's
it
for
today.