►
From YouTube: Intro: Harbor - James Zabala & Henry Zhang, VMware
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Intro: Harbor - James Zabala & Henry Zhang, VMware
As container technology become widely adopted in the industry, how to manage containerized applications poses new challenges to platform engineers. One of the challenges is to securely and efficiently manage container images. Project Harbor is an open source trusted cloud native registry project that stores, signs, and scans content, thus resolving common image management challenges. In this presentation, we will focus on the management of container images through Harbor. We will review and provide solutions to challenges faced by organizations, including RBAC (Role Based Access Control), vulnerability scanning, large scale image distribution, image replication and image provenance (notary). Real world use cases will be discussed in the session.
To Learn More: https://sched.co/GrcE
A
Hi
welcome
to
this
session
harbour
101.
My
name
is
Henry
Z
the
chip
technologies
of
young
with
China
and
I'm,
the
creator
of
project
Harbor
and
today
joining
me
today
is
Stephen
Chow,
a
staff
engineer
of
VMware
and
he's
the
maintainer
of
Harbor
project
Harbor.
So
today
we'll
give
a
introduction
about
what
Harbor
is
and
what
one
can
help
us
in
the
cloud
native
space
and
then
hopefully
we
can
have
a.
A
Have
some
question
answer
some
questions
that
about
harbor?
This
is
the
first
time
that
we
join
the
cognitive
after
joining
the
cloud
native
foundation
since
F
and
the
first
time
we
in
the
North
America
cube
con.
So
hopefully
that
will
be
interested
to
other
people
here.
For
for
this
first
introduction
to
the
after
a
project.
A
Here
is
the
agenda
of
today.
We
first
introduced
what
harvest
briefly
about
the
the
project,
go
a
mission
and
then
we're
here
to
do
some
typical
use
cases
of
our
Harbor,
how
we
can
manage
container
images
and
other
contents
then
securely
and
efficiently,
and
then
we've
talked
about
the
road
map
and
have
some
demos
about
what
harbor
can
help
you.
A
So
harbors
mission
is
that
we
is
a
trusted
cloud
native
registry
that
store
signs
and
skin
some
content.
It's
especially
continued
images,
and
recently,
more
recently,
we
have
ahem
Charter,
and
the
mission
is
to
provide
a
cloudy
environment
to
the
ability
to
contain
confidently
to
manage
and
surf
container
images.
A
Harbor
was
originally
created
in
a
in
a
small
team
that
I
lead
a
led
in
China,
our
DBM,
where
at
the
time
is
about
2014,
that
we
created
a
small
project
and
open
source
in
2016
and
and
now
we
stopped
it
by
people
normally
in
China,
but
also
other
people
developer
in
the
world
were
community.
It's
basically
a
registry
for
containers
and
ham
charts.
A
The
current
focus
is
to
store
signs
and
skiing
content
provide
a
consistent
experience
either
on
Prem
of
the
cloud
the
open-source
license,
Apache
2,
which
is
presents
friendly
for
for
most
of
the
news
cases,
and
we
was
accepted
into
the
sandbox
stage
in
the
zoo
line
this
year
and
as
the
first
container
registry
and
more
recently,
last
year
last
month,
the
coop
con
Shanghai
we
are
was
announced
there.
We
move
into
the
incubation
incubation
project
in
the
ciencia.
A
Here's
the
timeline
for
project
harbour
initial
inception
inception
is
like
in
2014
the
second
half
in
our
VM
Burton
Rd,
and
then
we
open
source
about
after
two
years
of
internal
top-folding,
in
trying
in
our
own
projects
in
the
2016
March
and
later
on.
We
have
a
had
chief,
quite
some
community
attraction
and
momentum
from
the
community
and
more
recently,
this
year
we
join
the
CSF
from
sandbox
and
then
incubation
after
the
incubation.
A
A
A
The
key
features
of
harbor,
so
I've
listed
a
few
of
them
here
include
which
we
include
the
identity,
integration
row
based
access
control,
our
Beck
and
security,
and
vulnerability
scanning
and
analysis.
Also,
we
have
the
content,
trust
or
signing
or
a
validation
of
the
content,
and
we
have
a
image
verification
across
different
locations
and
between
our
instance.
A
Recently,
most
recently,
we
had
in
the
hem
chart
support
for
the
management
Hampshire
repo,
and
we
also
have
an
international
novelization
of
different
languages.
We
have
English
and
Chinese,
and
also
a
community
member
help
us
the
created
other
other
languages,
support
and
operationally
we
can.
The
harbor's
can
be
deployed
using
the
simple
talker
compose
command.
A
few
one
command
can
bring
up
the
harbour
system
and
we
or
recently
we
can
also
use
hem,
try
to
deploy
harbour
in
the
right.
Now
we
have
different
components
in
harbour.
A
Mostly
all
of
them
are
open-source
here's,
the
diagram
or
harbour
architecture.
Here,
the
blue
one,
the
our
code,
harbor
project
itself,
were
containing
the
score
services
about
API,
authentication
and
GUI,
and
we
have
so
happy
jobs,
services,
running
a
batch
allocation
and
a
scanning
job,
and
we
have
the
administer
base
for
manage
configuration
and
also
we
can
support
the
deployment
of
different
platform
like
darker
kubernetes,
so
other.
We
also
use
the
other
open
source
project
like
the
rocket
distribution,
one
rescanning
and
content
trust
and
so
on.
They
all
packaged
into
a
containers.
A
After
going
through
the
basic
introduction
of
harbor,
I
will
introduce
some
of
the
typical
use
cases
that
most
of
our
users
like
or
use
in
in
this
production
environment.
The
first
is
the
image
consistency
to
maintain
the
image
across
the
life
cycle
of
the
other
software
development,
and
the
second
is
the
image
replication
across
the
different
places,
so
that
you
create
a
very
interesting
deployment
architecture
that
I
wouldn't
reduce
a
little
bit
later
and
also
we
have
authentication
and
authorization
for
the
image,
control,
access,
control
and
vulnerability
scanning
on
the
image.
A
Content
also
have
the
image
signing
for
the
for
the
provenance
of
the
image
and
having
trust
management.
The
first
one
I
want
to
talk
about
is
the
shipping
the
binaries,
so
I
mean
in
a
real.
We
were
application
development
environment.
We
often
have
different
environment
for
like
test.
They
have
developed
development,
testing,
staging
or
production
environment.
So
in
all
these
environments
that
we
usually
need
a
different,
really
only
container
container
images.
A
So
we
some
most
of
our
user,
that
we
recommend
it
is
we
we
use
the
different
registry
in
different
environment
and
then
you
lose
the
replication
to
populate
the
image
across
the
boundary
so
like
here
from
the
from
the
key
open
source,
our
source
code
and
then
go
through
the
CI
system
and
then
build
up
the
container
image
to
store
in
a
development
registry.
And
then
we
replicate
a
image
to
a
testing
environment
for
for
the
testing
after
testing.
A
If
they
passed,
we
can
promote
the
image
to
the
next
level
to
the
staging
environment
staging
registry.
From
there
we
can
eventually,
if
everything
works
they
will.
It
will
eventually
goes
to
the
production
registry,
so
by
that
means
that
we
can
maintain
the
consistency
of
the
binary
of
the
on
the
of
the
image
so
that
if
they
you
have
trouble
in
the
production,
you
can
easily
trace
back
to
the
to
a
development
or
testing
environment
for
the
actual
image
that
that
you
are
using
in
the
production
in
one.
A
The
next
one
is
very
useful
feature
that,
like
by
our
users,
is
the
image
replication,
because
there
is
a
common
scenario
when
we
tried
you
need
to
move
the
image
from
one
place
to
the
other
or
from
one
from
the
cloud
to
your
local
data
center
or
between
your
data
centers.
So
the
idea
is
very
simple.
At
the
beginning,
when
you
set
up
a
replication,
you
can
just
replicate
the
across
the
network
to
the
other
end
of
the
harbor
instance,
so
that
you
have
exactly
the
same
copy
of
the
images
and
then
later
on.
A
When
you
have
new
image
pushed
to
the
source
harbor
registry,
you
have
incremental
replication
to
the
to
the
other
end,
so
that
you
always
maintain
the
same
images
or
the
two
instances
of
harbor
and
for
the
more
we.
We
added
other
other
conditional
criteria
for
this
for
this
replication,
so
that
we
can
select,
which
images
that
you
want
to
populate
it
to
the
other
end.
So
we
have
filtering
on
the
image.
So
some
quite
here
we
are
like
what
kind
of
what
kind
of
attacks?
A
What
kind
of
labels
of
the
images
that
you
want
to
replicate
it?
You
want
to
replicate
and
also
you
can
use
wildcard
in
the
you
know,
criteria
specification
and
we
also
have
the
be
time
I
mean
the
the
scheduled
scheduled
replication
so
that
you
can
schedule
your
medication
drop
at
the
midnight
or
or
at
a
lung,
busier
time
or
in
your
system,
so
that
you
won't
with
your
effect
your
normal
workload
during
the
business
time.
A
Another
scenario:
another
use
cases
for
the
revocation
is
the
scale
scaling
horizontally.
The
idea
is
that,
normal
times
that
people
do
have
a
large
cluster
of
nodes,
a
container
nodes
that
are
in
a
data
center,
they
want
to
quickly
populate
the
images
to
all
these
container
notes
so
that
they
can
run
the
application.
This
is
when
you're
routing,
when
you
are
dealing
with
all
very
large,
a
scale
container
nodes
you've,
often
time
you
will
have
an
trouble
to
have
to
populate
all
these
nodes
to
the
to
to
these
to
these
nodes.
A
A
You
can
replicate
the
image
to
the
next
layer
next
level
next
year
of
harbor
and
then
to
shoe
that
the
images
from
there
in
that
way
you
have
the
low
balancing
or
the
very
relatively
evenly
load
to
the
different
harbor
instances,
so
that
you
won't
be
a
bottleneck
either
in
the
networking
or
the
other
storage.
There's
just
one
many
Internet
company.
They
are
using
that
to
treat
their
through
their
a
large
workflow
in
the
image
image
discussion.
A
Another
use
case
sample
are
for
the
replication
is
the
globally
replication,
so
they
can
replicate
images
across
different
location
in
the
either
in
the
cloud
or
in
the
data
center.
We
have
very
large
Bank
in
the
in
the
spend
that
they
are
using
the
G
harbor
to
replicate
the
images
across
different
offices
in
different
continents,
so
that
in
this
way
they
can
have
image
backup
in
different
location,
as
well
as
the
local
access
for
the
images
for
different
location.
A
They
want
to
authorize
who
can
access
so
in
harbor
images
are
grouped
into
project,
so
all
the
image
belongs
to
a
particular
project,
and
then,
when
you
want
to
access
the
project,
you
need
to
have
to
have
to
be
a
common
member
of
the
project,
the
40-member
they
have
the
role.
We
call
it
a
row
based
access
control.
If
forecast
role,
you
can
only
read
the
image.
A
That
means
that
can
we
pull
put
the
image
from
folder
from
the
registry,
and
then
we
have
developer
role,
which
can
read
and
write
to
the
image,
virtually
it's
a
talker
pool
and
push,
and
you
also
have
the
demean
administrator
role,
which
can
do
all
the
things
from
the
developer
role.
In
addition
to
that,
you
can
have
a
management
role
like
managing
the
management
managing
the
member
or
the
role
of
the
each
of
the
member.
So
by
having
the
authorization
and
authentication
of
the
registry,
the
enterprise
can
easily
control
who
have
access
what?
A
What
with
image
registry
very
easy
and
in
terms
of
security,
in
addition
to
the
access
control
for
most
of
the
enterprises,
they
need
to
have
some
kind
of
some
way
to
scan
the
content
to
ensure
they
don't
have
any
vulnerability
inside
their
images.
So
we
integrate
with
another
open
source
project,
called
clear
to
to
perform
the
scanning
tasks.
So
once
you
have
this
task,
we
can
periodically
scan
the
image
and
to
ensure
there's
no
insurer
to
report
any
of
the
problem
or
one
ability
found
on
that
images.
We
frequently
check
with
the
CBE
database.
A
Currently
we
are
checking
with
this
five
database
for
the
for
the
known
vulnerabilities,
and
we
can
also
set
a
threshold
in
harbour
to
say
that
if
that
vulnerability
is
passed
some
threshold,
we
won't
let
it
to
be
pulled.
That
means
that
we
we
can
classify
the
one
already
into
several
level.
It's
just
low,
medium
and
high,
so,
for
example,
we
set
threshold
to
medium,
so
any
any
images
test
with
the
threat
with
the
vulnerability,
stability,
level
of
medium
or
high
or
high
will
be
blocked
by
the
harbour.
A
So
no
one
can
pull
from
harbour
so
that
in
that
way,
we
can
ensure
that
our
images
with
the
severe
one
or
really
cannot
pass
through
the
system
person
to
go
into
the
system
and
the
next
feature
of
the
security
is
the
image
signing
so
often
time.
We
need
to
know
how
which
this
image
particular
images
come
from,
which
is
also
which
which
which
what's
the
source
of
this
image.
A
Core
no
Latorre,
no
tree
array
Sallee
will
allow
us
to
store
the
signature
for
a
particular
image
and
then,
when
we
are
pulling,
the
image
from
the
registry
will
check
with
that
the
signature
store
in
the
notary
and
then
we'll
find
out
whether
it
is
no.
You
know,
source
or
not.
That's
trustful
Lynott,
and
the
next
feature
is
the
hem
trial
management.
So
hem
tries
the
way
that
more
recently
have
become
more
popular
for
deploying
application
on
top
of
kubernetes.
A
So,
basically,
hem
trice
is
helping
us
to
deploy
up
a
number
of
containers
to
be
to
be
running
on
kubernetes.
So
we
unify
the
image
management
and
Hampshire
repo
instrument
together
and
to
perform
the
access,
control
and
deployment
integration
so
that
you
have
a
consistent
way
to
manage
all
these
two
artifacts
and
in
our
Roma.
We
also
consider
to
to
be
updated,
replication
and
signing
and
skin
scanning
for
the
hem
track.
So
there'll
be
more
friendly
experience
when
using
the
hem
draw
with
your
container
images.
C
C
Okay
in
this
demo
were
covered
two
parts.
The
first
part
away.
I
will
show
how
to
use
the
harbor
portal
to
management
manager,
your
herb
chart
and
then,
in
the
second
part,
we'll
show
how
to
use
the
harmony
give
a
command
line
to
handle
the
related
operation
of
harm
chart
further,
let's
go
into
the
project
log
in
harbor
portal
and
the
click
as
a
particular
library.
This
is
a
product
at
aerial,
tab,
NEMA,
herb
charter
to
show
all
your
hearts
so
far.
C
We
do
not
have
anyone,
let's
upload
a
new
one,
yet
you
can
directly
use
the
upload
button
to
upload
your
harm,
cart
to
hover.
Okay,
now
we
have
uploaded
a
new
one
Harper.
This
is
a
ham
chart,
our
self
chart,
this
chart
version
they
are
routed
to,
and
then
you
can
check
the
details
of
the
each
of
the
harbor
charter
version
with
the
their
rhythm
II,
and
there
are
some
metadata
like
the
repository
and
the
meat
innards,
and
also
we
also
some
commander
reference
for
you
to
use
that
term.
Chart.
D
D
C
Move
on
and
for
the
Charter
had
the
director
dependencies,
which
shows
a
dependent
harm
chart
in
the
dependents
tab.
For
example,
in
Harper
hammer
cards
will
use
dependent
on
the
Reddy
sir
Matata,
so
you
can
see
already
chart
in
the
dependents
tab
here.
I
want
to
mention
only
that
erect
a
dependence
will
be
show
shown
here.
We
do
not
do
recursively
dependents
discovering
so
far.
Okay,
there
is
another
type
of
value
will
show
the
value
de
llamo
Cotentin.
In
this
view,
we
support
two
different
alleles
one.
C
Is
you
know
a
key
value
pairs
table
for
you
quickly
to
offender
the
the
required
key
and
the
another
is
a
pure
llamo
vo,
pure
llamo,
Ferriero?
Okay,
that's
you
didn't
need
to
be
llamo,
it's
just
a
veil.
We
do
not
support
any
edit
here
and
for
the
harm
cart
for
the
specific
charter
version.
You
can
use
the
download
apart
and
to
directly
download
the
hammer
charter
to
your
local
system.
First
system,
you
can
see
yeah,
it's
Donna
Lydia.
D
D
C
D
C
Yeah,
if
the
pervious
affair
it
uploaded
a
together
with
the
ham
chart
package,
then
we
are
sure
different
signatures
theaters
in
the
teacher
to
page
you
can
see
here.
If
we,
the
term
charter,
has
a
pro
res
affair.
The
sender's
theatres
will
be
shortened,
a
full
there's,
no,
a
progressive
related
with
the
harm
trader
package,
so
we
can
show
it
sunset.
Currently,
the
we
just
checked
the
status
the
existence
of
the
progress
progress
affair.
We
do
not
do
any
verification
over
the
you
know
the
progress
affair.
Let
me
be
do
next.
C
If
you
use
the
latest
her
command
a
harm
version,
you
can
ignore
that
affair
and
the
key
fare
option,
because
when
we
recorded
this
demo
there
is
some
bug
in
a
harm
command.
So
we
needed
to
provide
a
surveyor
and
a
keeper
option.
If
you
use
the
latest
the
one
and
only
thing
you
can
just
take,
ignore
those
the
two
options.
C
C
C
C
C
B
C
The
second
time
over
demonstrator
how
to
replicate
your
imagery
with
the
label
filter.
Okay,
first,
you
can
see
in
the
SSA
this
it
in
this
time
we
have
two
different
Harbor
instance:
when
is
the
source
Harbor
and
another?
Is
the
takács
Harbor
will
replicate
the
imager
from
a
sauce
Harbor
to
the
Tackett
Harper?
First,
let's
check
the
content
to
use
the
sauce
harbor
you
can
see
in
the
library
project.
C
C
Okay,
that's
the
current
status
of
the
source
project,
the
installs
Harper
per
registry.
Let's
create
a
replication
policy,
give
a
name
to
the
policy.
Okay,
lose
everyone
and
select,
select
the
image,
the
source
project
of
the
image
it
from
that's
right,
little
library
and
add
a
filter.
We
support
a
deeper
filtered
repository
name
tag,
name
and
also
a
label
fur
to
which
a
delivered
in
recent
hover
released.
C
C
One
labels
like
diddle
and
select
the
target
cover
and
you
select
the
trigger
model
keeper
the
trigger
mode
that
default
menu,
save
the
replication
rule.
This
is
the
rule.
Okay,
now,
let's
check
the
status
of
in
the
target
to
harbor.
In
the
talk
of
the
library,
there
is
nothing
okay,
no
any
imager
is
the
target
or
product
of
the
target
to
harbor.
That's
a
trigger
the
replication.
Okay,
it's
a
start
head
done.
Okay,
the
replication
is
done.
It's
a
manually
trigger
action.
C
Okay,
let's
check
the
target.
You
can
say
in
the
target.
Your
project
of
the
target,
harbor,
the
one
thousand
arrow
and
the
two
dotted
arrow
check
is
already
replicated
chose
a
target.
Harbor.
Okay,
as
a
serrated
error
check,
is
a
cannot
because
it's
had
no
label
named,
say
a
pass.
Okay,
that's
the
replication
with
label
with
label
field.
C
Okay,
after
the
demo,
I
want
to
I'd
like
to
share
some
insight
over
harbour.
Okay,
some
potential
deer
extra
harbour
in
future.
Okay,
I
want
to
mention
here,
I'm,
not
Connor,
to
explore
more
details
in
this
introduction
section.
We
have
a
tip
type
surgery
insert
stay
afternoon.
If
you
want
to
learn
more
details
of
the
potential
direction
you
filter
harbour,
you
can
join
us
in
the
deep
dive
possession.
Okay
I'll
quickly
go
through
these
items.
C
First
thing
in
addition
to
the
local
TB
and
our
data
of
the
technician,
tab,
a
way
we're
planning
to
support,
or
at
least
say
against
all
that
is
a
provider
to
support
tool.
Campus
tiles
education.
After
that
you
can
use
the
to
campus
a
to
accepted
token
to
access
harbour
area.
Okay,
that
may
be
is
therefore
2004
doing
integration
with
Harbor,
okay
and
for
the
devil's
popular
support.
We
are
planned
to
support
a
robot
or
account
for
the
ssed
people
and
to
easily
pull
and
a
push
image
in
the
pipeline.
C
Instead
of
use
a
username
Cordy
show,
that's
not
a
current.
Okay
also
will
enable
Bible
Hawk
that
meets,
publish
or
export
some
events.
As
a
notification
to
to
later
that,
the
sed
pepper
line,
aware
what
happened?
You
Harbor
Linda
Curtis,
the
follow
up
operations,
okay
and,
of
course,
in
currently
the
harbor
replication,
just
a
support,
a
replicate
image
be
true
and
harbor
instance.
So
in
future
we
or
improve
the
replication
to
support
a
replica
pools,
image
and
herm
chart
a
bit
too
and
tip
further
be
to
harbor
and
non
harbor
registry.
C
So
many
ok,
so
the
filter
will
support
such
a
sense
and
for
the
check
left
circle,
many
much
investment.
We
will
want
to
support
a
retention
policies.
That
means
you
can
set
a
summer
retention
policy
for
your
attack
left
circle.
You
can
only
keep
with
you
know
the
latest
array
or,
ladies
to
tell
checks
and
all
remove
the
older,
the
image
all
of
the
image
older
than
you
know
some
days.
So
you
can
say,
set
some
retention
policy.
Okay,
we
also
want
to
improve
some
containers
to
improve
the
contents.
Can
you
okay?
C
We
all
provider
more
flexible
or
scaling
like
a
core
like
a
schedule
that
you
can
to
site
the
scaling
per
your
requirement.
We
also
want
to
we
also
plan
to
support
a
policy
basis
schedule.
That
means
you
care
created
some
policy
to
trigger
the
content
of
scanning,
for
example
like
oh,
we
want
to
you,
know,
triggers
granularity
or
weekly.
That's
a
policy
basis
scanning
okay
for
the
herb
Chartered
repository.
We
also
to
improve
the
to
Tassimo
improvement,
because
I,
just
measured
currently
with
denotes
a
very
fair,
the
pro
res
affair,
with
the
Hermit
chart.
C
So
in
future,
we'll
do
some
verification
so
very
phrase.
The
purpose,
if
it
it's
a
vanity,
a
valid
each
signature,
okay
and
about
the
left
circle.
Support
of
harbor
on
communities
in
next
release
will
provide
a
harbor
harder
to
deploy
a
harbor
to
the
target
communities
and
we
wanted
to
do
to
cool
further
the
left
circle.
Management
of
harbor
should
the
support
you
know:
Carol
a
install,
monitor
data
backup
at
about
upgrade
as
at
the
soya
operation,
errors.
Okay
and
the
last
one
is
image
proxy
and
the
cache
that
means
harbor
can
be
harbor
cat.
C
Behavior
as
the
cache
of
our
stream
registry,
like
dock
harbor,
also,
we
can
provide
a
version
control
for
the
captcha
image.
That's
what
we
want
to
do
in
the
future.
Okay,
if
you
have
some
good
suggestion
comments,
you
can't
go
to
our
repo
to
read
the
issue
so
ever
measure
that
there,
the
harbour
dev
section
instantly
distemper
13,
so
worker
mood
to
join,
and
we
are
with
him
looking
for
forwarded
to
your
cooter,
cetera,
okay,
we
also
have
meet
in
Naples
here's
the
list.
If
you
want
to
talk
more,
please
come
to
the
meeting
applause.
B
If,
in
the
use
case,
you
described
picking
the
bank
that
have
multiple
sites
across
the
world,
if
I
have
a
CI
system
that
creates
an
image,
how
do
you
orchestrate
the
process?
Timing,
wise,
so
I
only
deployed
the
new
application
of
the
communities
cluster
after
the
image
was
propagated.
So
how
does
like,
if
I
push
the
image
and
tears
have
the
wait
time
the
deployment
to
the
image
being
propagated
to
the
to
the
sites
yeah
once.
A
Once
you
have
the
image
in
push
inside
the
the
the
registry,
then
you
can
set.
The
polish
replication
policy
are
shows
over
here.
Is
that
the
timing
you
can
set
what's
the
time
that
you
want
it
to
be
populated
to
the
next
level,
so
that
you'll
have
the
so
timing
here.
So
you
have
a
way
to
specify
the
time
at
a
particular
time.
My
24
is
normally
in
the
immediately
be
replicated.
B
A
A
Yeah
right
now
we
don't
have
a
way
to
tell
but
yeah.
So
that's
a
good
suggestion.
Yeah
I
hope
you
can
give
some
feedback
on
the
issue
of
PR
and
joy.
We
also
have
a
community
call
regularly,
so
welcome
everybody
to
join
that
call
to
discuss
with
us,
and
we
also
maintain
a
session
that
you
welcome
to
to
join.
Thank
you.
Thank
you.
Everyone
I,
don't
know.
We
are
out
of
time.
Thanks.