►
From YouTube: Enterprise and Harbor: A Good Partnership in Helping Each Other - Ye Liu & Ludwig Isaac Lim, HP
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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 and Harbor: A Good Partnership in Helping Each Other - Ye Liu & Ludwig Isaac Lim, HP
Ye Liu 和 Ludwig Lim（惠普公司）- Harbor 是一种安全、非常稳定和成熟的开源镜像注册表。惠普研发 IT 部门在部署 Harbor 时，将 Harbor 作为惠普公司的一个 docker 镜像注册表来运行；Ye 和 Ludwig 与 Harbor 团队和社区合作，使 Harbor 应用于惠普的工作。他们想谈一谈企业和 Harbor 如何进行合作，从而互惠互利。本次讨论分为两个小节，1) 企业如何帮助 Harbor 发展；2) 回馈：将 Harbor 调整为企业级的内部 Docker 注册表 -Ye 和 Ludwig 想分享他们在 Harbor 发展工作中的经验，并通过分享他们所学到的使 Harbor 适应企业生态系统的知识来回馈 Harbor 社区。
Ye Liu and Ludwig Lim (HP Inc.) – Harbor is a secure, very stable and mature open-source image registry. HP R&D IT runs Harbor as an docker image registry for HP Inc. In deploying Harbor; Ye and Ludwig work with the Harbor Team and community in making Harbor work for HP. They would like to talk about how an enterprise and Harbor can partner together and benefit each . This talk is divided into two sections 1) How an enterprise can help in Harbor development 2) Giving Back : Tuning Harbor into Enterprise Grade Internal Docker Registry – Ye and Ludwig would like to share their experience in their Harbor journey and give back to the Harbor community by sharing what they learned to make Harbor fit into an enterprise ecosystem.
A
A
A
B
A
Thank
you,
lurix
in
hp,
iit
delivers
engineering
and
software
development
solutions
for
rng
communities
to
create
great
products,
shorter,
the
product
life
cycle,
lower
the
cost
and
improve
the
quality.
We
are
also
catching
up
in
budget
chain
modernize
id
practice
with
latest
technology
cloud
native
tools
and
frameworks.
A
A
It's
a
very
interesting
journey
and
we
feel
some
essential
gaps
are
because
of
the
key
strategy.
Differences
between
enterprise
and
open
source,
for
example,
enterprise,
requires
a
service
to
be
stable
in
hp.
The
essay
of
our
hardware
service
is
99.5
availability
and
the
customers
are
very
sensitive
on
the
performance
operating
teams.
Care
about
the
maintenance
effort
such
as
patching
and
upgrading
every
enterprise
service
also
has
some
metrics
like
time
to
response
time
to
resolve
on
issues.
A
So
how
to
gather
right
support
on
right
time
is
also
critical
for
hp.
Have
a
service
time
to
response
is
one
working
hour
and
time
to
resolve
is
full
working
hours
on
critical
issues.
So
you
can
imagine
the
challenges,
each
enterprise,
environment,
some
securities
all
is
always
an
important
consideration.
A
Each
open
source
software
has
its
own
roadmap
for
new
features,
but
not
always
put
the
enterprise
requirements
with
high
priority.
We
definitely
need
some
good
approach
to
build
the
signage
between
enterprise
and
open
source,
and
we
are
going
to
share
you
our
learning
from
the
journey
deploying
the
hardware
service
into
hp
from
2020.
B
Okay,
thank
you
very
much,
okay.
So,
let's
start
with
how
enterprise
can
help
in
hardware
development.
For
this,
we
want
to
share
our
contributions
to
the
hardware
development.
Our
first
contribution
to
the
hardware
development
is
disabling.
Anonymous
access,
our
open
source
and
enterprise
have
produced
great
quality
softwares,
although
the
focus
of
both
is
very
different
for
open
source
projects,
the
focus
is
more
on
collaboration
and
openness.
B
B
Our
second
contribution
to
the
harbor
project
is
oidc.
Testing
hp
is
one
of
the
first
companies
that
use
oidc
integration,
feature
of
harbor
being
an
enterprise.
We
have
access
to
authentication
tools
that
have
complex
mechanisms
such
as
oidc
also
hp
has
thousands
of
employees
that
can
help
in
testing
this
feature.
B
B
Next,
our
next
topic
for
the
talk
is
turning
harbor
into
an
enterprise
grade
internal
docker
registry.
For
this
topic
we
have
three
sub-topics;
first,
the
technical
aspects;
second,
the
you
end
user
or
customer
aspects;
and
third,
the
security
or
compliance
aspect.
So
let's
go
to
the
technical
aspects.
B
First,
we
need
to
understand
the
harbor
components
during
our
initial
testing
with
harbor.
One
of
the
challenges
that
we
met
is
understanding
hardware
components,
because
it
seems
that
every
time
we
install
install
something
different
came
up.
For
example,
when
we
change
the
xposed
type
to
load,
balancer
hardboard
installer
will
create
an
nginx
controller,
but
if
we
set
the
exposed
type
to
ingress,
the
engine
x
controller
will
not
be
created
by
the
hardware
installer.
So
you
need
to
be
very
careful.
B
One
of
the
challenges
we
have
in
maintaining
harbor
is
our
customers
are
located
all
around
the
world
with
a
small
team.
We
cannot
have
24x7
support.
So
how
do
we
manage
heavy
workloads
when
they
come
suddenly,
for
example,
those
heavy
workloads
that
come
on
a
saturday
when
we're
both
out
of
office?
B
One
of
the
solutions
for
this
problem
is
to
leverage
kubernetes,
horizontal
pod,
auto
scaling
or
hpa.
So,
let's
start
by
by
showing
you
the
current
setup
we
have
for
this
demo
environment.
Okay,
I'm
going
to
show
you
the
the
current
pod
conf
replica
configuration
and
as
well
as
the
hpa
configuration.
So
let's
do
a
k,
get
deployment
for
the
hardware.
B
We
start
with
minimum
of
two
pods
for
the
engine
x
and
for
the
registry,
but
it
can
scale
to
maximum
of
five
pods
for
both
the
engine
x
and
for
the
registry.
It
can
scale
to
15
pods.
Now,
I'm
going
to
run
a
few
test
stress
test
scripts.
This
this
scripts
will
push
docker
images
and
do
multiple
docker,
logins,
okay,
so
we're
going
to
do
multiple
push
and
multiple
logins.
Let
me
run
the
scripts
okay.
There
you
go
this
one.
B
Okay,
tip
number
three:
don't
ignore
pod
restarts,
you
might
be
curious.
Kubernetes
has
a
self-healing
function,
so
why
worry
about
intermittent
pod
restarts
well,
because
pod
restarts
are
just
symptoms
of
a
bigger
problem.
So
if
you
don't
fix
this
problem
at
the
early
stage
of
your
deployment,
when
your
deployment
gets
bigger
more
complex
and
there
are
more
users
chances
are,
you
will
have
problems
every
day.
B
So
let
me
share
to
you
one
of
the
experience
that
we
have
like
for.
We
have
like
rare
occasion
where
in
our
harbor
pods
crash
and
it,
although
it
automatically
restarts,
we
still
want
to
fix
this
problem.
Okay,
after
a
long
investigation,
we
found
out
that
the
cause
of
this
was
because
it
ran
out
of
memory
and
after
the
pod
ran
out
of
memory
it
crashed.
Although
kubernetes
was
able
to
self-heal
users
still
notice
it.
B
B
B
B
B
B
Okay,
next,
our
next
tip
for
you
is
you
need
to
know
your
customers.
Okay,
what
kind
of
images
does
your
customer
produce?
Different
type
of
applications
will
produce
different
kind
of
docker
images
for
our.
In
our
experience,
we
have
a
customer
who
reported
to
us
like
he's
having
a
he's
having
issues
doing
docker
push
to
his
registry
and
when
we
investigate
we
found
out
that
his
docker
image
just
are
about
two
gigabytes.
B
It
turned
out
that
his
application
is
a
machine
learning
application
and
it
has
a
lot
of
like
machine
learning
data
in
his
image.
That's
why
it
took
a
long
time
for
the
image
to
push
okay
and
you
need
to
check
like
how
often
do
they
pull
their
image.
Okay,
the
number
of
pools
can
help
you
in
estimating
the
workload
that
your
customers
will
be
doing
in
production.
B
B
So
you
need
to
check
this
one,
because
sometimes
the
problem
might
be
because
of
hardware's
performance
other
times
it
might
be
because
of
networking.
Let's
say:
you're
you're
pulling
your
docker
image
from
an
on-premise
network.
So
if
you
know
where
your
customers
are
pulling
their
image,
your
images,
you
can
help
them
in
troubleshooting,
okay,
and
the
last
tip
is
involve
your
customers
in
testing.
B
B
First,
when
you
install
when
you
deploy
hardware,
you
need
to
work
with
your
cyber
security
team
for
hp.
Before
we
move
hardware
to
production,
we
had
lots
of
consultations.
We
have
lots
of
reviews,
architectural
reviews,
cyber
security
reviews
with
the
cyber
security
team.
They
check
our
architecture.
They
make
sure
that
the
hp's
intellectual
property
will
be
protected
so
for
enterprise
such
as
hp,
the
iit
team
has
responsibility
of
making
sure
that
the
hp's
intellectual
properties
are
properly
protected.
B
So
this
is
one
of
the
reasons
why
we
submitted
a
pull
request
to
the
hardware
team
to
disable
anonymous
access
number
two
integration
with
official
or
security
tools,
so
usually
big
companies
like
hp
have
a
partnership
with
cyber
security
companies
that
that
sells
product
that
protects
their
assets.
Let's
say:
image,
scans,
anti-virus
and
stuff
like
that.
So
in
the
beginning
of
the
hardware
project,
when
we
try
to
adapt
hardware,
we
work
with
the
hardware
team.
We
work
with
the
encore
team
in
in
the
anchor
plug-in
for
hardware.
B
We
not
only
test
the
anchor
plugin,
but
we
actually
submit
pull
requests
and
code
to
the
anchor
plugin
for
hardware.
You
can
you
can
see
our
contribution
at
their
github
repo,
okay
below
next,
in
intranet
or
internet,
facing
okay,
so
for
intranet,
facing
or
internet
facing
cyber
security.
Your
cyber
security
might
have
different
policies
for
this.
You,
you
need
to
check
with
them
before
launching
the
harbor
application.