►
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
I
linked
here
and
if
you
are
interested,
you
can
dig
into
this
blog
and
find
more
and
also
please
try
the
build
that
delivered
in
our
environment
and
then.
The
second
item
is
that
we
have
found
our
first
cve
issues
and
we
have
fixed
this
issue
in
harbor
1.7.6,
however
1.8.3
and
hubble
109,
and
so
we
would
suggest
you
to
upgrade
to
the
latest
patch.
A
And
if
you
don't
have
a
plan
or
resources
to
upgrade,
and
we
also
have
a
workaround
and
the
workload
is
you
need
to
disable
the
self
registration
and
there's
a
workaround
steps
mentioned
in
this
link
and
please
take
a
look
at
this
adversary
and
make
an
actions
on
your
environment.
A
So
next
item
is
for
alex
g
before
I
go
to
next.
Is
there
any
questions.
B
B
Oh
yeah,
can
you
see
my
screen?
Yes,
hey
everyone.
So,
like
the
students
said,
we
experienced
our
first
cv
last
week.
It's
actually
on
the
same
day
as
release.
So
out
of
that
experience,
we
formulated
security
release
process
which
we
have
detailed
in
the
security
diagnd.
B
So
if
you
just
go
on
the
harper,
go
harbor
repo
on
the
very
the
front
page,
there's
a
security.md,
so
I'm
not
going
to
go
through
all
of
it
on
this
meeting,
because
I
want
to
make
sure
we
have
ample
time
to
go
through
the
demo
and
the
global
scanner
and
the
the
sharing
on
helm
chart.
So
please
read
through
this
and
basically
it
details
what
you're
supposed
to
do.
B
B
You
know
we'll
patch
the
fixes
back
port,
the
patch
to
all
the
releases
and
then
notify
people
on
the
distributors
list
and
then
eventually
to
the
general
public.
So
it's
a
very
detailed
guide
on
the
entire
process.
If
you
have
any
questions
or
any
comments,
you
can
make
a
pr
on
this
document
as
well,
but
yeah.
Please
take
a
look.
I
also
put
the
link
here
in
chat.
B
And
yeah,
that's
it
for
me,
so
I
think
we
can
go
on
with
the
the
demo
for
pogba
scanner.
A
Yeah,
thanks
alex,
I
think,
to
add
for
alex
that
so
please
to
register
this
thing:
cf
harbor
distributor,
email
list,
so
that
so
once
we
have
any
security
resolve
solution
and
issues
and
we
will
advertise
to
this
email
list.
I
also
please
encourage
your
customer.
If
you
have
a
customer
with
also
use
your
product
can
include
harvard.
Please
also
include
them
for
this
list,
so
they
can
know
whether
there
will
be
a
security
issue
impact
zone.
C
D
D
Okay,
thank
you,
yeah.
I'm
glad
to
represent
the
scanning
work
group
to
do
updates
about
the
plug
global
scanner,
which
is
a
anchor
feature
in
1.10.
D
Before
I
do
the
demo
I'd
like
to
quickly
give
you
some
introduction
about
the
plug
pluggable
scanner
framework
yeah
the
motivation.
The
motivation
is,
we
heard
some
voice
from
the
community.
Yes,
some
end
user.
I
want
to
use
their
own
or
their
some
other
scanner
default
from
other
security
providers
to
do
the
image
scanning
instead
of
using
claire-
and
I
think,
a
couple
years
ago,
some
secure
security
provider
like
anchor
kimo
reads
a
proposal
to.
D
Raise
the
proposal
to
harvard
community
to
they
want
to
hover
to
they
want
the
harbor
to
provide
a
you
know
for
likable
framework
to
enable
other
scanners
in
harbor
to
do
the
artifact
scanning.
So
so
we
did
the
communication
with
a
security
provider
like
anchor
like
equal
security,
and
we
set
up
a
working
group
to
continue
this
work.
So
so
far
we
have
a
proposal.
D
We
have
draft
drafted
a
design
proposal
and
if
you
want
to
check
the
details
you
can
go
to
the
community
repository
under
go
have
a
name
space.
I
think
the
pr
number
is
92
here.
I
will
not,
you
know:
go
through
every
detail
to
just
quickly
update
the
high
level
architecture
so
compared
to
the
previous
harbor,
we'll
provide
a
framework
to
introduce
other
scanners
into
harbor.
D
I
think
the
primary
change
is,
there
will
be
a
rest
eps
back
to
define
what
capability
or
what
behaviors
the
scanner
should
be
provided,
and
with
this
open
a
rest
aps
back
harbor
will
easily
to
talk
to
those
different
scanners
and
in
harbor
side
we
will
support.
You
know
a
different
scanner
measurement.
That
means
that
we
can
add.
D
You
know
different
and
the
points
of
the
scanner
into
hardware
then,
and
maybe
they
can
choose
one
of
them
set
as
default
when
the
user
starts
the
one-based
scanning
or
some
other
types
of
scanning
will
use
the
the
user,
the
but
the
mis
administrator
configured
scanner
to
complete
the
work,
and
I
think
another
big
change
is.
We
will
cache
the
latest
copy
of
the
report
into
hardware
set.
Then
we
can
quickly.
You
know,
render
the
report
for
user
with
a
high
performance.
D
I
think
that's
the
core
idea
of
the
plugable
scanner
framework.
So,
for
this
part,
do
you
guys
have
any
questions.
D
So
before
before
starting
the
demo,
I
needed
to
clarify
the
work
is
still
you
know
undergoing
not
fully
ready
to
not
fully
ready.
So
today's
the
demo
we're
not
to
a
full
demo,
we
will.
We
will
only
demo
the
most
demonstrate
to
the
scanner
management
and
we
will
not
demo
the
trigger
the
scanning
flow.
D
D
You
can
navigate
to
the
configuration
part
here.
We
will
add
a
scanner
section
with
this
section.
You
can
now
add
the
different
scanners
here,
if
you
want
to
add
a
new
scanner,
click
the
new
button
and
give
the
scanner
name.
For
example,
it's
a
simple
100
just
demo.
Maybe
you
can
give
some
description
to
click
for
what
this
scanner
can
be
do
and
you
will
need
to
provide
the
endpoint
of
the
scanner.
D
D
Yeah
I
have
already
set
up
one.
This
one
is:
is
a
micro
scanner
provided
by
a
core
security
company.
It's
also
an
open
source
scanner
to
do
while
basic
scanning
targeting
the
image
you
can
check.
Here
I
have
sent
the
micro
scanner,
you
have
a
mega
scanner
and
a
micro
scanner
adapter
here.
D
So
this
is
this
is
the
point
of
this.
This
scanner.
D
And
also
you
can
figure
out
which
authentication
will
be
provided
so
far
so
far,
this
microscan
adapter
does
not
involve
authentication,
so
we
just
keep
now
here
and
before
doing
it,
you
can
you
need
to
do
the
connect
testing.
D
D
Okay,
try
again:
okay,
the
testing
is
passed
so
now
I
can
add
it
to
my
list.
Okay-
and
I
only
add
one
scanner
here,
so
it
will
be
auto
automatically
marked
as
a
default
scanner,
and
here
is
a
narrow
echo.
If
you
click
this
narrow
echo,
there
will
be
more
metadata
of
this
scanner,
be
retrieved
and
render
here
you
can
see.
D
What's
the
name
of
this
scan
scanner
attempt
and
what's
the
vendor
of
this
scanner
adapter
and
what's
the
version
and
also
there
are
some
like
companions,
that
means
what
artifact
memory
types
this
scanner
will
support
and
what
types
of
report
it
will
provide.
Also
there
are
some
other,
you
know
different
properties.
For
example,
what's
the
one
big
database
update
the
timestamp
of
the
vulnerability
database
updated?
D
D
Okay,
so
of
course
you
can
do
some
management
work.
Okay,
for
example.
I
think
this
is
not
the
meter
thing.
You
can
change
some
other
information
here,
so
that's
a
scanner
management,
part,
okay
and
before
the
administrator
you
know
manages
the
different
scanner
at
the
system
level.
In
the
project
level.
D
The
project
at
mikka
also
select
can
also
configure
different,
different
scanner
to
their
project.
That's,
but
all
the
candidates,
scanner
of
from
the
system,
level.
That
means
the
user
can
choose
some
other
scanners.
Maybe
it's
not!
The
system
default,
okay,
but
all
the
candidates
should
be
configured
or
added
by
the
administrator
so
here,
because
we
only
have
one
and
the
user
did
not
set
its
own
scanner
and
forehead
for
their
project.
So
so
the
default
will
be
inherited
to
this
project.
D
Okay,
because
I
only
have
one
scanner,
I
only
have
I
only
set
up
one
scanner,
so
I
cannot
under
another
one
to
demo
the
different
cells.
Okay,.
D
So
after
the
after
you
configure
the
different
scanner,
then
you
can
go
to
the
repository
and
select
the
tag
you
wanted
to
to
to
to
do
to
skype.
Okay,.
D
D
Scan
you
can
see,
the
scan
request
is
passed
to
macro
scanner.
Microscanner
will
do
their
work
to
complete
to
finish
the
scan
work
here.
The
job
is
done,
but
so
far
we
have
some
bugs
to
retrieve
the
report
back
to
harbor.
So
that's
the
current
status
of
this
this
feature,
I
think,
that's
all
the
things
I
can
demo
today.
B
A
D
C
Cool,
so
this
is
a
presentation
that
I
gave
two
weeks
ago.
It's
a
longer
presentation
but
I'll
jump
through,
and
it's
all
about
how
the
helm
project
is
starting
to
use
registries
as
a
new
way
of
storing
helm
charts,
and
it's
really
something
else.
That's
going
on
in
the
community,
that's
outside
of
helm.
C
So
I'm
you
may
know
me
from
the
chart
museum
project
I
created
chart
museum
and
from
there
got
involved
with
the
helm
project
as
a
maintainer,
and
so
the
what
I
think
is
going
to
happen
is
by
the
end
of
next
year
that
things
in
the
cloud
native
world
are
going
to
be
starting
to
be
shipped
over
oci
distribution
and
oci
distribution
I'll
go
into
in
a
second.
C
So
the
char
museum
project
I
released
it
in
2017
and
then
was
donated
to
helm
and
it's
a
very
basic
way
to
run
a
chart
repository
and
unless
you
it
allows
you
to
plug
in
different
storage.
Such
as
amazon
and
different
other
clouds
and
it
powers
a
lot
of
internal
chart
services
so
including
the
harbor
project
actually
uses
chart
museum
as
a
back
end
service
for
pushing
and
retrieving
home
charts.
C
So
the
reason
why
all
this
started
has
has
actually
a
long
history.
C
Back
before
I
was
even
involved
with
helm
people
from
quay
such
as
antoine
and
jimmy,
came
out
with
or
released
the
app
registry,
which
was
a
way
to
store
helm,
charts
on
on
quay,
which
never
really
reached
a
lot
of
usage
where
it
changed
the
way
home
was
doing
things,
but
that
was
over
two
years
ago,
then
we
had
a
summit,
a
helm
summit
where
somebody
from
jfrog
gave
ankush
gave
a
presentation
about
how
the
entire
system
of
helm
was
subject
to
memory
concerns.
C
If
you
put
a
ton
of
charts
in
a
index.aml
file,
it
started
to
your
laptop
started
to
get
very
hot
from
all
the
memory
consumption
and
then
so.
Finally,
after
after
all
of
these
different
problems
came
up
over
time,
and
since
I
was
involved
in
the
chart
museum
project,
we
started
to
have
meetings
about
how
we
can
make
improvements
for
home
three.
That
would
tackle
the
problems
that
we're
trying
to
be
solved.
C
For
example,
how
do
we
log
into
a
repository
if
you're
familiar
with
the
helm,
cli
you'll
know
that
there's
you're
basically
passing
basic
off
username
password
on
the
command
line,
and
if
you
have
access
to
the
repo
you
have
access
to
every
chart
in
that
repo
and
not
just
the
ones
that
scope
to
your
user
and
then
also?
How
do
we
upload
charts
to
a
repository?
C
There
is
a
plugin
that
works
with
chart
museum,
but
how
do
we
in
a
more
generalized
way,
upload,
charts
to
repository
and
then
out
of
nowhere?
Somebody
comes
in
steve
lasker
from
microsoft
and
makes
this
large
proposal
against
helm
that
should
work
exactly
or
in
very
similar
way
as
docker
registries
and
this
sort
of
this
concept
sort
of
started
to
take
off.
C
So
it
turned
into
a
conversation,
though,
about
and
not
just
about
helm
or
docker,
but
about
oci
as
the
standard
for
for
doing
these
things,
and
so,
if
you're
not
familiar
with
oci,
it
is
it's
the
open
container
initiative
and
here's
sort
of
a
timeline
of
what,
when,
if
what
happened
is
docker
came
out
in
2013
and
then
rocket
came
out
with
an
alternative
spec
in
2014
and
then
finally,
the
year
after
they
kind
of
agreed
on.
C
This
is
an
open
way
to
do
these
things
with
containers
and
then
in
2018
it
added
another
spec
called
the
distribution
spec.
The
distribution
spec
is
basically
a
copy
of
the
docker
registry
api,
so
they
took
what
the
docker
distribution
project
did
and
turned
it
into
spec.
C
So
this
is
this.
Red
line
is
kind
of
representing
exactly
what
the
distribution
spec
is
right.
Every
time
you
do
a
docker
push
or
a
docker
pool,
taking
http
requests
to
one
of
these
different
registries
harbor
being
over
here
and
this
api
is
now
a
spec,
that's
under
the
oci
organization.
C
So,
through
those
conversations,
a
project
came
out
called
aurus
which
stands
for
oci.
Registry
is
storage
and
what
auras
is,
and
it
was
originally
created
by
sheeway
from
microsoft's
ad
container
registry
team
and
auras
lets.
You
push
anything
up
to
a
registry
over
the
oci
over
the
oci
spec,
so
helm
now
has
imported.
Helm3
has
now
imported
the
auras
library,
so
you
can
start
to
do
things
like
you
would
with
docker
against
registries.
C
So
imagine
if
you've
deployed
a
harbor
to
mysite.io,
you
can
start
doing
downloading
and
uploading
charts.
Just
like
you
could
a
docker
image
so
now
we're
able
to
do
this
with
helm,
but
now
the
question
becomes.
Where
do
we
actually
push
these
two
and
it's
a
little
bit
of
a
tricky
question,
because
the
cloud
registries
have
sort
of
white
listed.
C
We
only
accept
docker
images
in
the
registry,
so
we
really
only
have
two
open
source
options
to
do
so,
one
being
docker
distribution,
also
known
as
docker
registry-
and
this
is
the
the
most
basic
way
to
do
so
and
then
we're
on
the
harbor
call.
The
the
second
way
is
with
project
cargo.
So
if
you
want
to
deploy
project
harbor
with
helm,
charts
support,
I
have
a
fork
here.
You
can
look
at
the
diff,
it's
a
little
work
around.
C
I
need
to
work
with
some
of
the
people
from
this
community
and
figure
out
the
correct
way
to
do
this
change,
but
you
basically
swap
out
the
core.
This
is
based
on
top
of
the
1.9.
I
just
updated
it
and
it
allows
you
to
push
things
into
the
registry
and
here's
some
other
settings
for
allowing
like
one
megabyte
upload
over
nginx.
C
That's
about
it.
I
think
I
have
one
minute
just
to
show
how
you
can
push
a
chart.
So
imagine
if
you
have
a
helm,
a
helm2
chart.
C
So
this
is
just
a
normal
wordpress
chart.
I
can
actually
do
a
save
here
and
I
can
start
to
you.
D
A
A
C
Okay,
I'll
I'll
go
for
just
one
more
minute.
I
have
a
link
to
share
too
you
see
still
erican.
B
E
C
Okay,
great
yeah,
so
helm
now
has
a
way
to
start
working
with
things
that
looks
more
similar
to
docker,
so
you
can
do
helm,
chart
list
and
you
can
see
kind
of
a
similar
output
to
docker,
which
shows
the
digest
the
size
and
then
from
here
you
can
start
to
push
things
up
to
the
registry
and
then
so
there
was
a
upload
event
and
hold
on.
I
lost
my.
C
Browser
so
now
you
can
come
into
harbor
and
you
can
see
that
these
things
are
uploaded.
You'll
see
it
has
like
a
bunch
of
ui
things
that
are
an
issue
like
it
doesn't
really
work
with
the
ui.
That
being
said,
somebody
could
like
somebody
right
now
could
probably
pull
this
chart
right
now
from
their
local
using
helm3.
C
That's
that's
pretty
much
it
all
of
this.
All
of
this
information
is
available
in
the
helm3
documentation,
so
I'll
throw
these
into
the
slack,
and
I've
also
put
together
this
github
repo
that
has
example
of
how
to
install
helm3
deploy
harbor
with
this
experimental
support
and
then
commands
for
how
you
can
start
uploading
charts
to
harvard,
but
I'm
interested
to
kind
of
work
together
and
figure
out
how
we
can
do
this
in
a
more
long-term
way.
E
You
this
is
a
great
demo.
Thank
you.
I
think
that
if
you
can
go
ahead
and
file
a
github
issue
around
the
support
for
home
three
in
harbor
and
add
a
lot
of
these
details,
including
the
link
to
the
to
the
repo
you
have
that
way,
we
can
work
together
and
maybe
some
of
the
initial
issues
you
found
like
the
size
issue
outline
them
there
and
let's
have
start
having
a
discussion
on
how
to
do
a
better
together
support
and
what
it
would
look
like.
Definitely
it
thank
you.
E
B
C
B
Don't
know
if
you
know
and
theme,
how
does
that
fare
against
auras
that
you
just
talked
about.
C
Yeah,
so
I
I
should
have
probably
s
slim
down
the
slides,
even
more
yeah,
so
the
oci
artifacts
is
a
new
project
under
oci,
and
this
is
going
to
define
how
we
do
these
things.
So
there's
still
discussion
on.
C
What's
the
correct
way
to
do
things
or
us
is
an
opinionated
way
that
came
out
from
steve's
side,
so
the
if
you
use
helm3
today,
it's
actually
marked
as
an
experimental
feature,
because
we're
waiting
to
have
oci
sort
of
put
a
line
in
the
sand
that
this
is
the
way
to
do
artifacts.