►
From YouTube: Harbor Community Meeting 20190731 - Americas Time zone
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
Okay,
all
right
so
we'll
just
quickly
kind
of
run
through
this,
and
so
everybody
kind
of
has
an
idea
of
what
was
talked
about
this
morning
on
on
the
main
call,
and
hopefully
we
can
get
some
more
traction
coming
through
here
and
then
we
can
make
this
another
big
main
call
as
well.
So
my
name
is
kenny
coleman.
I
am
a
technical
product
manager
for
harbor
over
at
vmware,
as
most
people
know
that
most
of
the
development
team
is
based
out
of
beijing
china.
A
So
there
was
a
call
earlier
this
morning
where
the
main
team
went
over
and
most
of
the
the
the
maintainers
themselves
went
over
a
lot
of
the
features
and
a
lot
of
this
already,
but
we'll
kind
of
rehash
this
and
kind
of
talk
about
exactly.
What's
going
on
just
some
updates
on
really
where
we
are
with
1.9
features
as
well
as
some
of
the
progress
is
there
a
quick
community
update
not
too
much
there
and
then,
if
we're
ever
so
inclined,
we
can
do
the
feature
demos.
If
not
we
can.
A
We
cannot
and
then
we'll
just
take
some
questions
so
on
1.9.
The
quotas
per
project
is
mostly
complete
at
this
point
that
was
demoed
this
morning
and
being
able
to
see
exactly.
A
How
can
you
put
not
only
just
a
quota
on
the
amount
of
images
that
you
want
to
have
pushed
into
harbor
and
when
I
say
amount,
this
can
be
both
a
container
registry
image,
as
well
as
a
helm
chart,
so
each
one
counts
as
a
plus
one.
In
that
regard,
you
also
have
the
ability
to
do
a
quota
by
size,
so
you
can
say
a
particular
repository
or
a
particular
project
only
has
500
megabytes
or
100
gigabytes
whatever
it
is.
A
It's
up
to
the
administrator
to
decide
when
that,
when
that
particular
project
is
actually
being
created,
so
most
of
that
work
is
in
progress
right
now
by
default,
when
a
new
project
is
created,
it
is
set
to
unlimited
and
unlimited.
A
A
A
The
help
hub
adapter
is
also
done,
and
then
the
network
proxy
support
is
also
in
progress.
The
web
hook
support
being
able
to
call
different
web
hooks
based
on
push
pull
and
delete,
is
currently
in
code
review.
The
white
list
in
cves
is
currently
done.
A
This
was
shown
on
last,
or
should
I
say
two
weeks
ago
on
that
on
the
last
community
update
being
able
to
show
exactly
what
it
is,
what
it
looks
like
to
actually
whitelist
a
cbe.
A
You
have
the
ability
to
after
claire
does
its
initial
scanning
for
an
image
after
it's
been
pushed
into
the
container
registry
you're
able
to
look
inside
of
that
particular
tag,
see
what
the
vulnerabilities
are
for
that
image
and
then,
if
you
want
to
set
a
certain
threshold
to
say,
we
just
don't
want
anything
above
high,
but
there
are
certain
cves
that
are,
I
guess,
listed
as
high.
A
A
There's.
Also,
the
syslog
endpoint
for
log
shipping
is
complete,
and
then
there
are
current
performance
tests
that
are
being
done
with
distribution
and
comparing
it
to
what
can
be
done
to
docker
hub
today
on
the
community
update
right
now
there
is
just
collection
still
happening
for
1.10.
A
So
if
there
are
individual
stories
or
individual
issues
that
you
would
like
to
see
tackled
in
1.10,
we
encourage
you
to
please
go
ahead.
Put
a
thumbs
up.
Make
yourself
known
comment
on
it,
whatever
it
is,
to
make
sure
that
it's
being
calculated
and
being
prioritized
for
inclusion
inside
of
1.10
there's
also
a
plugable
scanner,
or
should
I
say,
what's
inside
the
scanning
working
group,
what
this
is
is,
as
I
mentioned
already
claire,
is
an
integrated
part
of
what
harbor
is
today.
A
So
now
I
can
dive
into
the
demos,
or
somebody
can
tell
me
if
any
topics
that
you'd
like
to
discuss
here,
I'll
kind
of
take
it
over
to
gary
and
amy.
If
there's
anything
you'd
like
to
know
or
if
you
really
want
to
see
a
demo,
you
tell
me-
and
I
can
I
can
do
it
for
you,
because
it
to
jump
into
a
demo.
A
A
It,
okay,
all
right
so
with
inside
here
we're
going
to
kind
of
run
through
exactly
what
this
looks
like.
So
the
first
thing
we
want
to
do
is
look
at
the
the
the
feature
for
being
able
to
do
quotas
so
with
inside
here
we
have
our
projects,
let's
create
a
new
project.
We're
gonna
call
this.
Actually,
let
me
go
ahead
and
refresh
this,
because
I'm
sure
it's
already
had
to
sign
out
by
now.
Of
course,
it
did.
A
So,
within
here
coming
to
a
new
project
within
here,
I'm
just
going
to
call
it
we'll
just
call
it
quota.
So
the
one
thing
that
we
we
know
that
we
want
to
be
able
to
see
right
here
is
that
by
default,
if
set
us
to
minus
one,
that
means
it
is
unlimited.
So
if
we
want
to
say
let's
limit
to
three
and
we'll
say
we
want
to
limit
to
200
megabytes,
we
can
do
that
so
we'll
go
ahead
and
click
ok,
coming
into
the
quota
library.
A
Now
we
can
see
up
here
on
the
right
hand,
side
underneath
our
our
project
quotas
exactly
what
this
really
does
look
like.
A
A
A
A
So
go
ahead
refresh,
so
we
have
that
come
into
our
summary.
Now
we
can
see
that
we
have
an
artifact
count
of
one
of
three
as
well
as
storage
consumption
there
as
well.
One
of
the
things.
That's
that's
interesting
about
what
you
can
do
within
here
is
looking
at
the
I'm,
not
too
sure
if
it
has
it
in
here
for
the
individual
tags
that
was
shown
in
the
in
the
one
this
morning.
Let
me
see
if
I
oh
yeah,
okay,
so
we
can't
do
this.
A
So
if
we
come
back
over
here-
and
we
come
to
this
individual
winner
here,
we
can
see
that
it's
tagged
is
here.
If
we
go
to
the
come
inside
here,
and
so
we
can
see
that
this
is
tagged
as
the
latest,
we
can
actually
retag
it
we're
going
to
go
ahead
and
put
it
in
the
same
one
and
then.
A
A
The
only
thing
that
didn't
change
was
the
actual
storage
consumption,
so
the
blob
in
itself,
since
it's
actually
stays
the
same,
it
doesn't
actually
change
the
storage.
Consumption
actually
stays
the
same.
However,
you
can
see
that
the
artifact
count
increases
incrementally
by
one
now.
A
If
we
try
to
upload
a
an
image,
that's
going
to
be
bigger
than
our
allocated
amount,
we'll
kind
of
look
and
see
what
that
looks
like
right
here
so
docker
tag,
and
since
we
know
that
we
only
have
a
few
a
little
bit
left
in
here,
so
we'll
do
golang
oops.
A
A
A
So
it's
not
going
to
actually
fail
or
anything
like
that
right
away.
That's
something
that
the
the
team
is
going
to
look
into
the
problem
that
actually
exists
with.
That
is
that
this
is
utilizing
the
docker
client,
so
it
would
require
to
see
exactly
if
the
docker
client
can
do
anything
within
that
regard.
A
If
it
works,
we
have
a
problem.
Okay,
so
there
you
go
so
now
it
sees
that
it's
it's
actually
retrying.
We
can
come
into
our
repository.
We
can
see
that
it
didn't
actually
get
pushed
or
anything
like
that,
and
we
can
see
that
the
storage
consumption
is
actually
over.
However,
it's
going
to
continue
to
keep
trying
and
re-pushing,
but
it
will
never
actually
get
in
there,
so
it's
actually
going
over
our
our
maximum
quota
there.
A
Okay,
so
that's
the
quota
demo,
so
you
exactly
see
what
that
is
if
people
need
to
use
that
next
is
looking
at
our
tag.
Retention
policy-
that's
available
here.
So
the
first
thing
I'm
gonna
do
is
I'm
gonna
come
over
here.
I'm
gonna
go
ahead
and
upload
this
one
into
here.
Just
so.
We
have
some
more
to
talk
about
here,
so
tag
test
oops.
A
A
Okay,
so
the
way
that
this
this
one's
actually
set
up,
we
don't
have
any
anything
limiting
it,
so
unlimited
pieces
coming
through
here,
I'm
also
gonna
upload,
a
few
more
helm
charts
in
here
just
so,
we
can
kind
of
see
exactly
what
this
all
looks
like.
A
A
A
Alpine,
this
should
go
relatively
quickly
because
it's
already
uploaded
okay,
so
there
we
go
now.
We've
got
three
different
container
images
in
our
repository.
We've
got
four
different
helm
charts
so
coming
over
to
the
tag
retention
policy
right
now,
there's
nothing!
That's
created
any
rules,
so
let's
go
ahead
and
create
our
first
rule.
A
It
also
means
our
images
as
well
as
our
charts,
and
we
can
say
wordpress,
and
so
we
can
sit
there
and
say
here's
if
we
want
an
individual
tag.
We
can
do
that,
but
now
we're
just
going
to
say
every
single
one
of
them,
any
labels
that
you
have
associated
with
that.
You
can
do
that
too.
So
we
can
see
exactly
that.
What
we're
trying
to
do
here
is
we're
setting
up
a
retention
policy
that
all
we
want
to
keep
are
images
or
helm,
charts
that
have
wordpress.
A
This
is
going
to
be
more
important
if
you
have
a
particular
image
that
you
utilize
as
your
conditional
standard
say
it's
golang
version
x,
dot
whatever
you
can
you
set
that
as
your
as
your
retention
rule,
so
if
anybody
goes
and
tries
to
upload
or
keep
updating
individual
their
or
their
own
tags
and
keeps
re-tagging
things,
this
will
automatically
be
sort
of
a
clean
up
process
for
you
and
also
do
online
garbage
collection
for
you
as
well
so
with
inside
here.
What
we
can
do
is
we
want
to
do
a
dry
run.
A
Our
dry
run
is
exactly
what
you
think.
What's
going
to
happen.
If
we
do
run
this,
so
you
can
see
it's
currently
in
progress,
we'll
refresh
it
still
in
progress
still
in
progress.
A
I
think
it's
done,
but
we'll
go
ahead
and
we'll
try
to
take
a
look
okay,
so
it
says:
oh,
it's
still
running
on
the
wordpress
one.
That's
why
so
we'll
give
it
just
a
second,
but
one
thing
that
we
can
see
is
that
we
start
coming
through
here
is
that
we
can
look
to
the
log
and
we
go
to
say
the
cockroachdb
we
can
see
what's
going
to
happen
here
with
inside.
The
retention
is
that
it
would
run
a
delete
scan
onto
it.
A
A
I'm
assuming
it's
finished,
but
it
still
says
in
progress.
So
let's
go
ahead:
let's
run
it
and
see
what
happens.
We're
going
to
have
this
dialog
box
that
comes
up.
This
is
going
to
make
sure
that
you
actually
do
want
to
run
this,
and
you
kind
of
understand,
what's
going
to
happen
as
well,
so
go
ahead,
click
it.
We
can
see
that
the
dry
run
is
set
to
no,
and
we
can
see
that
it's
already
finished
it
succeeded.
We
can
come
over
here.
We
can
look
at
the
individual
logs.
A
We
can
see
that
right
now
the
wordpress
retained,
and
if
we
go
back
to
our
individual
repository
here,
we
can
see
that
all
of
the
other
images
now
are
gone
same
with
inside
of
the
helm
chart
and
all
we
have
is
our
wordpress
repository
and
our
wordpress
help
chart
that
is
remaining.
A
Cool
well,
I'm
gonna
go
ahead
and
stop
sharing.
If
there's
anything
else
that
you
have
to
bring
up
in
regards
of
features.
Regards
of
the
community
updates.
Anything
like
that
speak
now,
or
we
can
go
ahead
and
kind
of
in
the.
A
Meeting,
I
think
we're
good
to
go.
Thank
you
all
right.
I
think
so
too,
all
right,
well,
amy
and
gary.
Thank
you
so
much
again
for
for
hopping
on
and
have
a
great
rest
of
the
day
thanks
you
too
thanks
so
much
bye.
Thank
you.