►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
We
added
the
systig
systic
secure
as
an
image
scanner
through
our
plugable
interrogation
services
framework
and
we're
also
able
to
host
ai
machine
learning
data
models
on
harper.
A
A
All
right
so
yeah
we
can
talk
about
the
cluster
operator
or
the
heart.
What
is
the
harbor
operator.
A
So
the
background
is,
you
know
we
have
been
working
on
a
hardware
operator.
In
addition
to
you,
know
the
docker
composed
deployment
that
we
have
and
the
helm
chart
and
deployment.
So
now
there's
an
operator-
and
you
know
this
project
started
when
ovh
a
cloud
company
in
europe
reached
out
to
us
and
wanted
to
work
on
an
operator,
and
so
there
are
actually
two
operators
right
now,
there's
a
harbor
core
operator
which
you
can
find
here.
It's
under
go
harbor.
There's
a
repository
called
harvard
operator.
A
Job
service
and
some
of
the
optional
components
like
notary,
clear
charm,
museum
trivia-
we
actually
don't
have
trivia
yet
but
we're
adding
in
the
next
release-
and
you
know
this
is
great-
if
you're,
just
managing
your
own
infrastructure
and
you're,
adding
harvard
to
a
pass.
You
know
where
you
have
redis
and
database
already
deployed
somewhere
as
a
service.
You
know
maybe
in
the
cloud
and
then
the
cluster
operator,
which
is
located
here.
A
Harbor
cluster
operator
also
undergo
harbor.
You
know
parallel
to
I'm
sorry,
it's
this
one
right
here
also
under
under
go
harbor,
so
that's
kind
of
like
our
all-in-one
inclusive
on
operator,
and
you
know
this
has.
Let
me
go
back
to
the
ppt.
A
And
this
has
all
the
different
components
you
know
it
becomes
with
everything
and
the
crd
will
handle
installing
all
the
services
prior
to
installing
hardware,
so
pg
sql,
redis,
cache
storage.
A
And
so,
if
we
look
at
the
overall
architecture,
there's
a
harbor
cluster
controller,
that's
essentially
managing
all
the
services
needed
for
the
registry
and
so
the
harbor,
the
cluster
operator,
custom
resource.
You
know
that
encapsulates
the
core
operator
customer
resource,
as
well
as
the
custom
resources
for
database
for
redis
tenant,
is
the
storage
component
leveraging
main
io
s3,
and
so
for
each
of
these
you
know
we're
using
existing
open
source
operators.
A
The
hardware
cluster
controller
will
call
the
related
dependent
services,
it'll
instantiate,
these
first
and
then
inject
the
related
info
into
the
harper
cluster
cr
through
secrets
and
config
maps,
and
so
basically
it
it'll
it'll
start
postgres
and
it'll
start
redis,
start
storage
and
then
finally,
it'll
start.
The
hardware
registry.
A
A
A
So
yeah
most
of
this
comes
from
the
the
harbor
core
operators
here,
so
you
have
the
version,
which
is
the
version
of
harper
the
image.
The
image
version
you
use
public
url
is
the
public
access
point
of
harbor,
define
the
admin
password
for
admin
to
compound
define
certificates,
we're
using
cert
manager
to
do
this.
A
You
can
define
the
replicas
here,
so
there's
a
replica
and
there's
also
a
job
service
replica
and
there's
a
global
replica
that
you
can
define,
and
then
you
can
also
increase
the
number
of
job
service
instances
you
have,
depending
on
your
workload,
declare
claire
trivi
charm
museum
and
then
declare
your
regis
instance.
So
you
can
use
an
external
external
cache
like
a
red
is
deployed
somewhere
else
in
your
public
cloud
or
you
can
use.
A
You
can
declare
it
as
an
in-class.
So
you
need
to
define
the
storage
class,
the
storage
size.
Essentially,
that
will
just
invoke
the
the
embedded
redis
operator
to
create
that
service.
Based
on
this
config
same
thing.
For
for
database
for
pdq
sql,
you
can
use
an
external
db
or
you
can
do
it
in
class
and
the
one
that
the
in-class
version
you
know
will
create
a
highly
available
storage
service
using
the
pg
sql
operator
that
we're
consuming.
A
So
you
know
the
core
operator
0.5
right
now
is
based
on
hybrid
1.10
and
as
we
move
to
you,
know,
hardware
2.0.
We
want
to
sync
with
the
2.0
version,
so
the
ovh
team
is
already
working
on
doing
some
refactoring
of
the
crs
to
leverage
2.0
and
then
the
cluster
operator.
Will
you
know
it'll
rebase
on
the
core
operator,
so
it'll
support
hardware
2.0
as
well.
A
So
I
want
to
thank
everyone
who
worked
on
this.
So
we
have.
You
know
maintainers
from
different
companies
who
worked
on
this
from
that
ease
from
through
guys
from
vmware
from
gene
cloud
and
obviously
ovh
who
reached
out
to
us
to
kick
start.
This
whole
project.
B
Yeah,
this
is
like
a
super
critical
milestone
for
us
right.
It
will
significantly
simplify
how
hardware
is
deployed.
It
will
kind
of
drive
towards
a
consistent
way
of
deploying
hardware,
the
same
way
or
whether
you're
on
premise
in
the
public
cloud
through
some
other
products.
I
think
this
you
know
is
a
tremendous
value
from
this
project,
so
I'm
super
excited
for
us
to
get
to
the
stable
support
for
this.
A
Yep,
you
know
it's
pretty
much.
What
I
want
to
cover
both
the
roadmap
and
the
implementation
is
still
in
flux,
we're
still
making
some
changes.
You
know,
and
obviously,
because
we
already
have
the
docker
compose
deployment
and
the
helm
deployment
of
harper.
A
This
is
just
something
else
that
we
need
to
maintain,
but
we
have
seen
some
traction
in
the
community,
so
I
think
it's
a
it's
a
good
investment.
A
And
you
know
I
the
ovh,
you
guys
the
ovh
guys
aren't
on
the
call,
but
I
really
want
to
thank
them
for
for
reaching
out
to
us
and
kickstarting
soul
project
we've
been
at
it
for
a
while.
Now
it's
something
we've
always
wanted
to
do,
but
it's
good
that
we
finally
got
around
to
it.
So
I
anticipate
we'll
probably
have
a
stable
release
for
the
cluster
operator
sometime
by
the
end
of
next
month.
C
Cool
what
version
are
you
using
right
now
we're
on
2.0
right
now,
but
we're
looking
to
transition
to
2.1
as
soon
as
we
can,
because
it's
got
a
lot
of
cool
features.
We
want
to
use
okay
cool.
Have
you
run
into
any
problems.
C
2.0,
I
don't,
I
don't
think
so
I
mean
we,
we
did
the
migration
from
1.10
to
2.0
and
it
was,
it
was
pretty
seamless.
It
just
worked.
A
Great,
and
are
you
guys
only
hosting
docker
images
and
home
charts?
Are
you
hosting
anything
else
that
you
know
the
oci
capability.