►
From YouTube: CNCF TOC Meeting 2021-12-07
Description
CNCF TOC Meeting 2021-12-07
A
B
F
F
It's
fine
yeah
by
the
way,
so
thank
you
for
thomas
who
helped
on
these
slides.
So
I'm
just
presenting
you
buddy
about
you
as
well.
Good
news
is
for
the
cooperative
delivery
working
group.
We
have
our
chairs
selected
with
josh
and
robert
who
already
started
working
on
this.
As
a
reminder,
this
is
a
working
group
that
deals
with
bringing
infrastructure
and
app
delivery
closer
together.
F
So
they
kicked
off
the
work
right
now
and
expect
more
results
to
see
when
they
well
they're
only
kicking
the
tires
on
the
work,
but
when
more
deliverables
are
there,
they
also
already
started
looking
into
scenarios,
definitely
motor
present.
The
next
time
we
meet,
which
will
be.
I
was
in
the
new
year.
F
They
also,
which
is
the
last
point
here,
especially
josh,
put
a
lot
of
work
into
potato
head
like
running
the
distributed,
app
examples,
bringing
them
up
to
speed
for
all
the
different
cncf
projects
that
are
out
there
for
different
delivery
delivery
methods.
So
this
is
being
updated,
so
they
also
took
this
project
as
their
reference
project
and
now
we're
reaching
out
to
some
of
the
other
cncf
projects
that
are
used
in
their
delivery.
F
F
We
still
owe
that
you
see
a
detailed
feedback
on
this
one.
We
are
kind
of
entirely
wrapping
it
up
and
we
understand
why
this
is
a
complex
project
to
look
at
so
for
those
who
are
not
familiar
with
conveyor,
it
is
a
collection
of
tools
that
help
you
to
migrate,
your
application
from
wherever
you're
running
it,
so,
whether
it's
in
a
very
traditional
environment,
environmental
cloud,
foundry
environment,
over
to
kubernetes,
with
a
set
of
tools
that
have
been
developed,
I
think
mostly
out
of
red
hat
and
ibm
consulting
over
two
kubernetes.
F
F
There
are
some
dependencies.
There,
though,
I
mean
there,
for
example,
rely
on
text
on
for
the
delivery
parts,
some
of
them,
where
we
have
to
talk
to
them,
some
of
the
base
images
when
they
convert
and
bare
metal
application
to
containerized
application
using
redhead
based
images
that
we
need
to
follow
up
on
with
them
and
and
other
smaller
things
that
we
need
to
follow
up
with
the
team
overall
or.
F
However,
the
question
is:
how
do
we
deal
with
a
project
like
this,
which
is
a
collection
of
tools,
so
it
can
never
actually
be
in
that
stage
of
like
being
used
in
production,
it
is
used
to
move
workloads
to
production.
So
I
think
it
depends
on
also
how
like
that
progression
of
a
project
like
like
this,
would
work,
because
it's
more
or
less
a
tool
collection
than
a
project
in
the
more
traditional
sense
of
the
other
cncf
projects.
D
When
I
had
a
comment
there,
there
wasn't
really
a
good
place
to
put
this
in
the
form.
This
is
josh
burkas
and
I
work
with
the
conveyor
folks.
Sometimes
they
submitted
it
initially
as
a
single
project
rather
than
a
separate
project
for
each
tool.
The
reason
being
that
there's
sort
of
a
currently
a
sixth
component
to
conveyor,
which
is
an
online
community
of.
D
F
Yeah,
I
think
it
takes.
We
will
also
circuit
back
with
the
team
and
provide
a
bit
more
of
a
condensed
review,
but
the
first
one.
It
is
a
bit
different
than
other
projects,
where
it's
mostly
doing.
One
thing
that,
like
this
collection
of
tools,
not
even
projects
that
you
run,
I
do
see
where
it
has
value
for
in
some
bits
and
pieces,
but
I
think
it's
a
general
question.
How
do
we
deal
with
this?
Looking
back
at
the
app
delivery
charter,
when
we
started
with
app
delivery,
helping
people
migrate,
workloads
to
kubernetes?
F
But
the
question
is
whether
this
should
actually
be
a
maybe
at
some
point,
even
a
working
group,
and
it's
like
sam-
that
did
the
tools,
maybe
doing
something
similar
to
what
the
git
tops
working
group
did,
but
we
still
need
some
time
some
more
time
to
wrap
our
head
around
it.
This
was
just
an
update
and
obviously
willing
for
input
on
this
one.
F
E
Yeah,
I
think
that
is
helpful.
I
mean
there's.
Certainly
a
few
question
marks
over
how
this
fit.
I
mean
it
clearly
is
targeted
at
people
using
cloud
native
software,
but
I
think
we
need
to
sort
of
yeah.
I
mean
if
you're
still
working
on
it,
then
I
think
that's
going
to
be
very
helpful
input
into
figuring
out
how
how
this
should
fit.
E
F
I
think
we're
getting
closer
with
them,
but
I
think
we
need
a
bit
more
time
because
it
also
like
it's
a
lot
of
different
tools
like
for
example,
it.
I
think
it's
called,
don't
remember
all
the
names.
I
think
it's
crane
that
helps
you
to
migrate
evm
to
cubeverd.
So
the
question
is
shouldn't
this
actually
be
part
of
qbert
per
se,
maybe
even
so
that
that's
why?
Like
there's
a
lot
of
things
in
flux,
but
we're
working
with
the
team
to
get
there?
F
There
is
that
some
of
these
projects
have
been
or
are
waiting
for,
cuc
support
for
for
quite
a
while,
and
we
totally
understand
that
you're
all
busy.
We
just
also
want
to
remind
you
of
the
rules
that,
if
approach
it
waits
for
longer
than
two
months,
it
would
actually
be
required
to
start
all
over
and
from
the
t
from
the
process.
I
think
if
your
sponsor
doesn't
appear
within
two
months.
E
G
E
F
Totally
answered
yeah
so,
and
I
think
that's
more
or
less
and
again,
if
that
uc
needs
us
to
help
more
here
on
some
of
those
projects
in
the
reverse
phase.
So
we
we,
I
mean
we
talked
internally
so
we're
happy
to
help
and
support
you
in
everything
we
can,
because
some
of
the
those
due
diligence
have
been
going
on
for
since
I
think
june
or
so
so,
wherever
we
can
help,
please
let
us
know
we
do
our
best,
where
we
can
help.
A
F
A
F
I
mean
the
general
question
came
up
be
like
how
are
our
projects
actually
supposed
to
get
a
toc
sponsor,
I
mean,
obviously
you
don't
want
people
to
reach
out
to
all
of
you
directly,
but
is
there
an
official
process
on
how
to
get
to
it?
So
do
you
see
sponsor
because
sometimes
they
reach
them
out
to
us
if
they
don't
have
a
sponsor,
yet
how
we
should
be
where
we
can
support
them,
which
I
think
is
a
bit
unclear
to
projects
how
they
should
do
it?
F
H
Part
of
what
is
happening
here
is,
I
think,
part
of
the
answer
which
is
so
actually
calvin
is
an
an
individual.
That's
on
the
call
that
represents
chaos
mesh
and
had
been
in
a
similar
situation
where
they're
looking
for
some
tst
sponsorship,
and
so
once
or
twice.
I
made
a
note
of
it
in
this
call,
and
so
what
you're
doing
is
the
same
thing
that
I
had
done,
and
I
think
that
that's
part
of
the
answer-
it's
just
you
know
elevating
raising
attention.
E
So
I
think
that's
the
the
answer
to
how
we
chase
it,
how
we,
you
know
how
we
make
sure
that
there
is
awareness
of
projects
waiting
for
or
looking
for,
toc
sponsorship,
and
I
find
the
thing
about
the
two
months.
So
it
says
if
a
tfc
incubation
sponsor
is
not
set
forward
within
two
months
after
the
pr
has
been
submitted.
E
F
E
A
I
F
J
E
F
E
E
F
Okay,
I
mean
that's
yeah.
We
already
covered
the
potato
head
project
from
the
updates
there.
We
have
the
updated
delivery
samples
switching
out
to
other
people,
but
it's
also
still
ongoing.
Not
on
this
list.
Here
is
the
working
group
on
that.
We
have
around
chaos
testing.
This
is
the
very
complex
one
where
we
need
to
bring
people
in
from
all
the
other
tags,
security,
observability
network
and
so
forth.
I'm
confident
that
we
will
soon
be
able
to
have
progress
there
as
well
it
just.
F
We
just
want
to
ensure
that
everybody
feels
on
board
with
what
we're
doing
there
as
well,
and
therefore,
obviously,
we
have
to
give
a
lot
of
people
the
time
to
have
a
say
and
the
word
in
this
one:
that's
that's
all
it
is
there.
Okay,
that's
it
from
tech,
app
delivery.
I
think
I
have
taken
a
bit
more
time
than
usual.
D
I'll
go
for
it:
okay,
yep
I'll,
try
to
make
up
some
of
the
time,
because
we
got
short
report
today
for
governance,
we're
gonna,
have
values
and
readme
templates,
headed
to
our
toc
liaisons,
for
approval
pretty
soon
follow
the
link
if
you're
interested
in
those
that's
just
basically,
you
know
projects
need
certain
information
in
their
core
readme
and
also.
We
feel
that
it's
important
to
have
a
statement
of
values
in
governance,
documents
the
and
wanted
to
provide
some
examples
of
that.
D
We
now
have
a
relatively
complete
set
of
templates
for
projects
to
use
for
a
lot
of
their
necessary
cncf
project
documentation,
and
I
haven't
really
come
up
with
a
good
way
to
make
sure
that
new
projects
that
join
the
cncf
are
aware
that
these
are
available
as
examples
for
them
to
use
and
copy
the
we
don't
actually
necessarily
want
to
dump
this
on
them
with
all
of
their
materials
that
they
get
when
they
first
join.
I
the
cncf,
because
those
materials
already
run
to
many
many
pages
and
that
wouldn't
help
with
visibility.
D
E
D
B
D
Okay,
well,
we
actually
have
in
an
hour
and
a
half
we
have
just
by
default.
The
governance
working
group
has
mostly
been
the
one
talking
about
this,
although
it's
really
all
across
tag
control
strategy,
so
we
have
in
an
hour
and
a
half.
We
have
the
governance
working
group
meeting
and
then
on
thursday
we
have
the
full
tag
meeting.
So
if
one
of
the
members
of
the
toc
wants
to
take
this
on,
but
we
need
that
member
of
the
toc
or
it'll
just
never
get
approved.
D
D
G
G
K
B
D
D
D
One
of
the
other
proposals
that
we
had
in
here
that
will
probably
be
coming
back
as
a
pr
is
remember.
The
cnc
cncf
staff
ihor
proposed
he
needs
a
place
in
within
our
hierarchy,
for
cncf
managed
mentorship
programs
to
live
things
like
the
cncf's
entry
into
google
summer
code,
and
he
was
suggesting
that
tag
contributor
strategy
be
that
place.
A
A
M
We
had
some
good
experience
in
the
past
with
let's
see
kubernetes
project,
for
example,
where
we
have
people
who
are
a
part
of
the
community
itself,
they're
also
running
the
mentoring
programs
there.
So
this
might
be
a
good
idea
also
to
to
basically
to
have
the
same
the
same
as
the
similar
process
for
the
cnc
flight,
mentoring
programs.
D
On
the
other
hand,
the
tag
has
actually
lost
some
of
our
regular
contributors
over
the
last
couple
of
months
to
a
variety
of
things,
including
health
issues.
So
this
would
be
a
matter
of
hey.
We
put
it
in
the
repository,
but
currently
it
doesn't
have
any
additional
people
to
staff.
It
doesn't
have
any
additional
contributors
to
staff
it.
D
M
Well
speaking
about
staffing,
it's
not
an
issue
for
now
at
all,
so
like
we
have
cncf
staff
with
stuff
in
this,
the
bigger
question
would
be
if
somebody
like
eventually,
somebody
from
community
may
want
to
to
do
this
and
we'll
have
ordered
this
open
to
public,
and
we
will
will
already
have
an
ability
for
folks
to
to
jump
in
and
basically
benefit
from
this,
rather
than
developing
the
brand
new
process
from
scratch.
When
somebody
will
want
to
do
it,
so
stuffing
is
not
an
issue,
it
will
be
like.
E
E
H
H
We'll
have
a
deep
dive
and
recorded
intro
at
cubecon
eu
about
well
about
a
lot
of
activities
that
go
on
inside
the
service
mesh
working
group.
It
takes
up
the
it's
consistently
the
majority
of
the
meeting's
agenda.
Recently
the
agenda
has
been
over.
The
last
couple
of
times
has
been
on
well
advancements
in
service
mesh
performance.
H
H
What's
the
most
representative
workload
for
or
what
are
the
yeah,
what
are
the
best
workloads
to
represent
what
organizations
and
what
users
commonly
have-
and
it's
almost
like
in
any
answer-
is
valid
because
there's
any
variety
of
workloads
having
some
that
there
are
some
that
maybe
represent
better
than
others,
though
so
having
a
variety
of
them
is
helpful.
There's
a
about
six
or
so
that
the
group
has
is
using
today.
H
F
So
the
original
design
goal
that
we
had
is
we
wanted
to
build
a
simple
to
run
app
that
everybody
can
run
on
their
local
machines,
which
was
kind
of
like
the
shortcoming
of
some
of
the
microservice
demo
apps,
because
if
you
want,
if
you
want
to
do
delivery,
you
need
to
run
multiple
stages
of
an
app.
So
you
needed
something
very
tiny.
F
Rather
than
the
complexity
of
the
code
itself.
The
code
is
pretty
simple
immediately.
It
delivers
a
body
part
pretty
much,
but
the
idea
is
okay.
What
if
this
is
on
a
persistent
volume
and
I'm
upgrading
and
upgrading
the
persistent
volume
or
how
to
handle
like
the
blue
green
deployment?
If
I'm
delivering
two
types
of
arms
at
the
same
time?
Or
how
do
I
know
that,
like
one
is
slower
deliberates
than
the
other
one?
So
these
are
more.
H
Thanks
for
that
that
good
yeah,
you
know,
there's
there's
some
part
of
the
view
of
this.
The
working
group
and
of
the
surface
mesh
performance
project
itself
is
that
performance
is
a
consideration
along
those
continuous
delivery
gates.
If
you
will
or
like
a
throughout
each
of
those
steps
that
at
one
or
more
of
those
points,
performance
might
be
considered,
and
so
so
that's
there's.
F
F
Active
community
also
on
the
cncfs
like,
if
you
find
look
for
potato
heads,
you'll
find
them
as
well,
but
you're
definitely
willing
to
collaborate.
So
it
was
the
idea
of
starting
this
project.
Well,
the
initial
idea
was
to
give
a
presentation
at
cubecon,
and
then
we
just
saw
more
people
participating
in
it
to
be
fair,
but
let's
catch
up
on
it,
offline
and
well.
In
the
cncf,
like
with
the
rest
of
the
team.
A
N
N
N
We
had
the
k-native
project
submit
their
pr
for
incubation,
so
I
think
dimms
is
the
sponsor
for
this,
but
they're
also
lay
in
dave,
I
think
they're
helping
out
with
the
with
the
incubation,
so
they're
working
on
the
on
the
the
due
diligence
document
right
now.
It's
still
pretty
early
also
not
actually
noted.
Here
we
are
working
on
the
due
diligence
for
cubert.
N
N
So
I
think
it's
a
very
similar
project
to
volcano
and
I
don't
think
they're
thinking
about
applying
for
the
cncf
yet,
but
maybe
they'll.
They
will
decide
that
in
the
future
in
open
cluster
management
is
a
project
that
helps
the
health,
the
management
of
kubernetes
clusters
and
the
life
cycle,
management
of
kubernetes
clusters
and
so
there's
a
series
of
utilities.
N
This
is
a
sandbox
project
already
and
we're
having
a
presentation
on
december
16th,
we're
very
close
to
christmas
that
they
decided
to
schedule
that
that
time
in
on
the
machine,
learning
operations
and
ai
edge
space,
we
have
another
project
called
k0s
which
is
similar
to
k3s
and
that's
presented
on
december
16..
It's
a
it's
a
kubernetes
distribution
for
the
edge
and
finally,
we're
working
on
the
batch
system
initiative
working
group
charter.
N
A
lot
of
folks
in
the
community
are
interested
in
studying
this,
some
of
the
folks
in
volcano
some
other
in
working
on
the
cube
batch,
and
I
think,
there's
some
als,
also
some
folks
on
on
the
armada
group
and
all
in
in
some
groups,
and
I
think
they're
at
apple
they're,
also
interested
in
starting
this
working
group
and
cubecut.
We
have
a
session
in
kubecon
china
schedule
for
next
week,
attack
runtime
session.
O
N
Yeah
include,
their
containers
is
already
sandbox.
Yuki
is
not
submitting
yet
to
the
cncf,
so
I
think
they
only
yeah
and
our
media
is
not
submitting
yet
either
and
k.
0
k,
0
s
is
not
submitted
yet
so
those
cycles
are
yeah,
so
the
only
one
is
k,
native
and
and
in
clover
containers
is
it's
a
part
of
the
sandbox
and
open
cluster
management
is
also
part
of
sandbox
right
now,.
E
B
N
P
All
right,
hello,
security,
yeah
good
morning,
good
afternoon
good
evening
to
all
of
you,
I'm
sorry
I'm
not
on
video.
So
this
has
been
a
little
bit
of
a
slow
month
for
tax
security
reason
was
there
were
a
number
of
conferences,
so
a
lot
of
people
were
attending
conferences,
but
still
we've
been
working
on
a
number
of
initiatives.
P
At
the
same
time,
cloud
native
security
white
paper
version
two
we've
been
working
on
table
of
contents
for
that
and
a
list
of
participants
who
can
contribute
to
that.
We've
kicked
off
the
discussions
for
cloud
native
security.
Con
2022.,
the
serverless
white
paper
has
made
a
huge
progress,
but
there
are
still
some
sections
which
are
being
worked
on
as
well.
P
They
were
not
able
to
incorporate
that
because
they
wanted
to
go
live
with
the
draft
because
of
their
timeline.
But
since
it's
a
draft,
we
have
almost
like
six
months
to
a
year
to
update
that
document
with
all
the
cloud
native
security
input
that
we
had
provided,
and
we
also
wanted
to
address
sas
right
when
software
as
a
service
provider
is
using
cloud
native
technologies.
What
does
that
mean
for
ssdf
and
so
on
and
so
forth?
So
that
is
a
good
piece
of
work
in
progress
that
we
will
take.
P
We
are
working
on
and
taking
up
with
nest
going
forward,
also
cloud
security
alliance
reached
out
to
us
and
they
want
to
collaborate
on
some
initiatives,
especially
like
cloud
native
security
controls,
serverless
initiatives
as
well.
The
reason
for
that
is
from
our
perspective,
why
we
are
interested
is
we
are
having
challenges
finding
volunteers
and
who
have
the
right
knowledge
and
cloud
security
alliance
already
has
a
large
list
of
participants.
B
P
Yeah
and
assessments
is
one
piece,
but
also
there
are
a
number
of
other
initiatives
like
app
delivery.
Has
a
project
on
chaos,
engineering,
there's
a
component
of
security
chaos,
engineering
that
we
want
to
work
on.
Similarly,
with
the
service
mesh
group,
we
want
to
make
sure
all
the
security
policies
are
being
addressed,
and-
and
so
there
are
overlaps-
that
we
want
to
contribute
to.
Where
again
we
have
limited
bandwidth.
Q
P
P
Q
E
E
Q
Q
E
E
J
Hi
shane
here
I
will
be
giving
an
update
for
text
storage.
So,
regarding
the
projects
we
have
longhorn,
that
is
an
incubating
project.
Now
for
chubby
fs
raphael
finished
the
dd
review
for
the
incubation
request.
So
from
text
dirty
side
we
are
recommending
incubation.
We
are
now
waiting
for
toc
on
the
next
steps.
Q
Yeah
yeah
so
yeah,
so
I
have
finished
almost
most
part
of
the
due
diligence
stock.
It
generally
looks
good,
so
next
step
is
the
the
the
maintainers
of
the
chuba
effects
have
already
arranged
the
three
and
user
interviews
which
have
already
enrolled
me.
So
this
will
happen
this
week,
so
I
would
say
after
this
week
the
end
user
interview
will
down
and
then
we
will
to
see
we
will
see
if
we
want
to
move
to
next
step
based
on
the
feedbacks
from
the
end-user
interviews
yeah.
This
is
the
current
status.
J
Okay,
thanks:
okay,
moving
on
to
open
eps,
we
had
meeting
with
the
team
availgo.
There
are
different
sub
projects
under
open
eds
that
have
different
statuses,
so
we
need
to
consult
with
the
tlc
liaison
on
how
to
handle
that.
So
I
think
I
will
talk
to
alex
about
this
and
reach
out
to
our
liaison
and
a
curve
storage
system.
J
They
presented
the
project
in
the
last
tag
study
meeting.
There
are
a
few
questions
that
came
up
in
the
meeting.
The
team
had
replied
through
email
on
some
of
those
questions.
They
provided
additional
documents,
so
we
will
go
through
those
and
follow
up
with
them
and
for
those
two
white
papers,
clown
native
disaster
recovery
and
performance
and
benchmarking
white
paper.
J
They
are
completed
and
we
presented
them
at
kukang,
north
america,
and
we
also
had
a
meeting
with
our
toc
liaison
aaron
a
few
weeks
back
discussing
what
other
next
steps
for
the
tag.
So
we
came
up
with
a
few
things
that
tag
could
work
on.
One
thing
is
to
have
an
end
user
survey
to
understand
their
pain
points.
J
Another
thing
is
to
invite
search
projects
to
present
and
invite
end
users
to
attend
to
get
their
feedback,
and
we
also
want
to
look
at
persistent
storage
and
the
databases
and
see
how
different
systems
use
persistent
storage.
So
those
are
the
things
that
we
are
going
to
work
on.
Next,
that's
all
from
tech,
storage,.
J
E
A
B
J
So
we
have
yes,
that's
the
thing
we
have
not
heard
from
them
for
a
while,
so
karen
right
karim
over
he
moved
and-
and
we
have
not
seen
him
in
the
textured
meeting
and
yeah.
So
there
is
another
person
who
usually
will
attend
the
meeting
and
we
have
a
email
thread
discussing
this
one.
We
just
have
not
heard
from
them
for
a
while.
So
I
will
reach
out
and
see
what's
the
status.
J
J
G
A
Moving
under,
like
you
know,
a
k-native
here,
only
thing
that
I
really
want
to
highlight
right
now
for,
like
all
the
toc,
that's
on
the
call
is,
if
you
have
not
yet
voted
for
litmus
chaos.
Please
do
so
yes,
okay,
good!
Is
that
also
true
for
openmetrics
as
well?
Openmetrics
is
like
the
that
one
is
currently
in
voting,
but
I
believe
that
one
is
passed.
We
are
working
with
that
team
to
be
able
to
make
sure
that
we
can
get
the
press
releases
out
for
all
of
them.
So,
okay,
yes,.
E
O
R
A
H
R
H
I'm
sorry
to
interrupt.
I
just
got
excited
there
from
so
there's
with
respect
with
respect
to
the
mesheriy
project.
There's
service
mesh
patterns
as
external
artifacts
that
are
like
basically,
a
collection
of
yaml
that
imbues
best
practices
for
how
you
would
run
a
particular
behavior
of
a
service
mesh,
and
so
these
patterns
are
there's
a
catalog
being
developed
by
the
project.
Now,
which
sounds
like
those
patterns
might
like
it
sounds
like
artifact
hub
might
be
a
good
repository
for
those
those
patterns.
R
R
Thank
you,
quick
quick
gut
check,
yeah
yeah,
and
we
even
do
things
such
as
related
packages.
So
say
you
go,
install
one
thing
and
there
might
be
something
else
in
a
different
category
that
relates
to
it.
Maybe
something
around
falco
that
relates
to
the
database.
You've
installed,
we'll
even
try
to
show
you
related
things
that
you
might
also
be
interested
in
to
help
discovery
of
some
of
these
different
projects
and
the
artifacts
they
have.
H
Let
me
take
it
one
step
further.
If
you
don't
mind,
and
that
is
that,
alongside
the
pattern
service
mesh
patterns,
there's
also
been
a
lot
of
focus
in
the
measuring
project
on
web
assembly
filters
and
curating
those
and
making
those
available
in
in
the
measuring
project
and
and
but
people
have
been
bringing
new
filters,
and
so
we've
been.
The
project
has
been
considering
how
to
distribute
those
so
yeah.
R
Yeah
and
I'd
be
happy
to
talk
about
that
and
further
somebody
wants
to
what
a
number
of
projects
are
doing
is
they're
letting
people
distribute
them
themselves,
because
the
big
problem
is
discoverability.
If
different
people
distribute
their
own
things,
how
does
somebody
discover
it?
You
go
to
a
typical
search
engine
and
you're
not
going
to
find
a
lot
of
those
things,
which
is
the
reason
for
artifact
hub,
because
you
can
go,
look
and
scope
it
down
to
the
projects
and
see
related
things.
E
R
R
Yeah
we
expect
there
to
be
one
main
instance
that
will
be
publicly
available
so
because
the
goal
is
discoverability
right
and
if
you
had
a
bunch
of
places
where
you've
got
to
go,
it
kind
of
hurts
discoverability,
and
so
we
expect
to
operate
the
one
artifact
hub.
So
people
can
do
that.
Yet
at
the
same
time
there
are
reasons
to
have
your
own
instance,
especially
in
corporate
networks
and
for
your
own
company.
R
There's
other
reasons
to
have
one,
maybe
where
you
don't
want
it
to
be
globally
discovered
right,
and
so
you
can
actually
go
ahead
and
install
artifact
hub
and
operate
it,
and
it
is
an
example
of
how
you
can
distribute
it
and
a
bunch
of
the
different
image
scanning
features
and
other
things
as
well,
and
so
there's
an
easy
install.
You
can
helm,
install
artifact
hub
yourself
if
you
want
to
just
go
run.
It.
E
R
So
it's
not
a
registry
in
that
it
hosts
your
artifacts.
It's
a
centralized
search
across
those
things,
and
so
you
don't
actually
push
any
of
those
artifacts
there.
You
may
have
a
registry
or
repository
holding
something
on
docker,
hub
or
quay
or
in
azure's
registry,
and
you
want
those
things
to
be
discovered
and
easily
found.
How
do
you
do
that?
You
get
them
listed
in
a
search
engine
and
that's
what
this
is.
E
R
E
K
S
S
Think
I
just
wanted
to
jump
in
for
a
second
liz
I'll
call
myself
sponsoring
artifact
hub,
but
I
think
to
your
point.
The
the
first
question
to
answer
is
the
one
you
just
brought
up
and
I
can
take
working
with
matt
and
them
to
figure
out
the
answer
to
it
and
assuming
we
continue
with
what
matt
said
it
goes
with
stages,
then
I'll
sponsor
it.