►
From YouTube: Harbor Community Meeting 20190410 - 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
All
right,
hello,
everybody
and
welcome
to
another
cncf
harbor
meeting.
This
is
the
us-based
time
zone
and
it's
the
10th
of
april
of
2019..
I
guess
it
looks
like
this
time
works
a
little
bit
better
for
folks,
since
we
got
tyler
and
nathan
to
join
us
and
join
us
as
well.
A
So
we'll
keep
this
time
and
see
if
we
can
kind
of
get
a
few
more
folks
to
start
joining
us
and
kind
of
grow,
the
community
outside
asia,
pacific
as
well,
since
it's
only
a
few
of
us,
let's
go
and
do
a
quick
round
of
introductions
since
it's
my
first
time
meeting,
tyler
and
nathan.
So
let's
spend
a
couple
of
minutes
on
that.
So
jonas,
why
don't
you
start.
B
Sure
hi
everyone,
my
name,
is
jonas
rosslyn.
I'm
an
open
source
community
manager
here
at
vmware.
Harbor
is
one
of
the
projects
that
I
help
with
community
management.
A
Excellent
cool.
Thank
you
I'll
go
next,
michael
michael!
I'm
the
product
lead
for
harbor,
one
of
the
I'm
one
of
the
directors
of
product
management
at
vmware,
and
I
have
responsibilities
across
a
few
different
tools
like
hardware
vcr,
integrated
containers,
enterprise
pks.
In
addition
to
that,
I'm
one
of
the
chairs
in
the
kubernetes
community.
So
I
lead
the
sick
windows
community.
There
brad,
you
know
next.
C
A
D
Sure,
hello,
I'm
nathan,
lowe,
I'm
a
devops
engineer
with
highland
software
out
in
west
lake,
ohio
we've
been
using
harbor,
since
I
don't
know
one
two
or
one:
three:
it's
been
working
out
pretty
well
so
far
for
our
internal
registry-
and
I
just
recently
became
a
maintainer
on
the
harper
project
earlier
this
year.
E
I
guess
that
was
me,
so
my
name
is
tyler
britton.
I
work
for
pivotal
on
on
kubernetes
and
mpks
and
I
just
started
poking
around
with
the
harbor
helm
tools
most
recently
in
the
last
couple
weeks.
A
It
so
I'll,
since
it's
mostly
folks
that
are
super
engaged
into
the
project,
I'll
I'll
go
through
a
couple
of
slides
really
quickly
and
then
after
that
I'll
give
us
an
opportunity
to
have
a
discussion
as
well.
A
So
let
me
go
through
the
slides
really
quickly.
Can
you
guys
see
my
screen
all
right,
cool
excellent?
So
you
know
our
agenda
today
is
a
little
bit
of
one-to-date
development
updates.
We'll
talk
a
little
bit
about
the
community
survey
that
that
we
have
published
not
long
ago
and
there's
a
couple
of
new
features
that
we
have
demos
that
are
recorded
and
they,
if
they're
not
published.
Yet
they
should
be
published
by
end
of
day
on
our
community
websites.
A
A
You
know
all
that
upheaval
that
happens
in
the
conference-
and
you
have
a
lot
of
folks-
are
really
interested
in
the
cloud
native
there's
a
lot
of
announcements,
there's
press,
so
we
can
kind
of
write
that
momentum
and
that
can
also
carry
our
1.8
release.
We
are
going
to
have
a
community
vendor
and
I'll
talk
about
that
in
a
second.
A
So
so,
from
a
from
a
development
standpoint,
the
robot
accounts,
health
check,
api,
new
master
role,
the
new
swagger
apis,
the
chrome
scheduled
tasks
and
the
refactoring
as
well
as
some
of
the
reworker
on
prepare
scripts
is
all
done.
A
The
oidc
support
is
nearing
its
end
and
we've
actually
reached
out
to
a
couple
of
different
entities
that
have
asked
to
integrate
with
hardware
or
take
advantage
of
idc
to
get
feedback
in
that
area,
and
then
the
replication
work
that
we're
doing
it
did
have
some
hiccups
at
a
couple
of
points
in
time,
mainly
because
of
researching
and
availability
of
certain
folks
to
come
in
and
contribute,
but
they've
been
able
to
add
additional
engineers
from
a
vmware
standpoint
and
that's
on
on
track
now
and
it's
close
to
being
completed.
A
So,
overall,
the
the
release
is
looking
to
be
in
good
shape
and
and
progressing
well,
one
of
the
other
things
that
I've
asked
the
team
to
make
sure
that
it
produces
that.
Every
time
we
have
a
release
of
hardware,
I
want
us
to
also
have
an
equivalent
release
in
home
chart.
Maybe
the
release
numbers
don't
need
too
much,
but
for
every
release
of
hardboard
we
need
to
make
sure
that
the
home
chart
is
updated
and
tested
validated
and
it
works
well
with
one
to
date.
A
So
I
guess
coming
back
to
the
to
the
point
that
tyler
mentioned
that
he's
looking
into
the
home
chart.
One
of
our
goals
is
to
have
consistency
across
the
releases
of
hardware
platform.
A
A
We'll
merge
that
in
my
goal,
is
to
kind
of,
as
we
move
on
to
the
1.9
and
future
harbor
releases,
we
might
kind
of
adopt
a
similar
ways
to
how
kubernetes
manages
releases,
where
you
have
like
a
a
one
month,
period
or
so
of
feature,
requests
being
happening,
and
we
do
prioritization
as
a
community
with
all
the
maintainers
who
identify
all
the
items
that
are
important
to
us
as
a
community
to
work
on
and
then
assign
owners
or
leads
from
the
community
that
will
kind
of
drive
those
features
forward
and
and
check
them
in.
A
And
ideally
we
want
to
keep
you
know
whatever.
We
are
proving
that
mouse
in
that
time
line
is
the
only
things
we're
going
to
basically
allow
into
the
release.
So
that
picture
that
you
kind
of
asked
for
will
probably
slot
that
in
for
1.9
and
then
allow
you
to
incrementally
make
changes
and
and
slowly
merge,
that
into
the
tree.
A
A
A
There
was
a
community
survey
that
we've
run
for
almost
a
month
or
so
across
a
wide
variety
like
a
lot
of
folks
had
access
to
it.
We
published
it
on
twitter
on
wechat
on
on
the
cncf
flag
channels,
so
we've
had
a
wide
variety
of
users
from
harvard
that
gave
us
answers
in
terms
of
what's
important
to
them
from
the
community.
So
I
wanted
to
kind
of
share
a
little
bit
the
results
here.
So
if
you
look
at
the
survey
here,
I'm
assuming
you
guys
can
see
my
new
screen
here.
A
Most
of
the
folks
that
have
answered
the
survey
are,
they
have
already
deployed
hardware.
They
understand
hardware
within
for
in
terms
of
the
features
and
functionality,
so
they
were
not
like
more
on
the
beginner
side
or
folks
that
you
know
had
very
little
knowledge
of
hardware.
Obviously,
we
did
have
a
good
healthy
percentage
of
contributors
and
maintainers
that
answered
the
survey
and
those
are
the
guys
that
are
have
mostly
vmware
and
as
well
as
you
know,
for
folks,
like
you
guys
that
are
deeply
knowledgeable
about
our
investment
in
harbor.
A
So
continuing
down
the
survey,
you
know
the
location,
it
seems
that
we
have
a
good
distribution
here
between
asia,
pacific
and
north
america
with
a
little
bit
of
european
respondents
as
well.
A
A
So
at
that
point
in
time
it
is
the
latest
release
of
hardware,
so
when
the
date
is
not
out
yet
so
we're
happy
to
see
that
we
don't
have
a
lot
of
old
versions
of
hardware
out
there
and
that
also
helps
along
our.
You
know
the
fact
that
we
don't
really
support
hardware
for
an
indefinite
amount
of
time.
A
So
this
makes
it
easy
for
us,
as
we
transition
folks
from
all
the
releases
to
the
latest
and
greatest
and
we're
hoping
that
everybody
will
kind
of
start
using
one
to
date
when
it
comes
out
both
from
the
perspective
that
you
want
to
make
that
the
best
release
of
hardware,
but
also
that's
the
release
that
we're
going
to
continue.
Iterating
on.
A
The
the
approaches
for
installation
of
hardware
kind
of
very
widely
we
have
folks
using
the
home,
chart
the
online
installer
offline,
installer,
ova's
or
kind
of
building
their
own
homegrown
tools
from
an
investment
standpoint,
we'll
I
think,
we'll
continue
making
more
and
more
investments
into
the
home
chart.
A
A
As
you
can
see,
there's
also
quite
a
few
folks
that
are
deploying
hubble
with
tks
and
ops
manager.
That's
the
enterprise
pks
solution
that
vmware
is
selling
all
right
so
one
when
we
kind
of
ask
folks
what
are
the
main
functions
of
hardware
that
they're
using
the
you
know.
The
results
here
are
a
little
bit
additive.
It's
just
more
around.
You
know
allowing
folks
to
say:
hey.
Are
you
using
x,
y
or
z?
A
So
the
sum
is
bigger
than
100,
but
it
looks
like
vulnerability
scanning
seems
to
be
one
of
the
features
that
most
of
our
users
are
using.
So
that
indicates
to
us
that
we
need
to
continue
investing
in
that
lwd
integration,
that's
also
highly
valued,
and
the
oidc
support
that
we're
having
in
one
today
will
only
continue
further
the
the
usage
of
this
feature
and
then
the
one
thing
that
was,
I
guess
a
surprise
to
me-
was
the
content
test.
A
So
that
means
to
me
that
we
need
to
find
better
ways
of
improving
usability
of
content,
trust,
specifically
maybe
around
replication.
Today,
if
you
replicate
your
image
across
multiple
hardware
instances,
content
trust
is
not
replicated.
So
that's
a
problem
there,
so
for
me
as
a
pm,
I
can
identify
some
of
these
issues
and
see
how
we
can
solve
them
and
that
could
drive
content
trust
to
be
more
more
widely
used.
C
Hey
michael,
I
I
agree
with
you
in
general.
The
the
idea
of
replication
being
a
problem
is
something
that
users
wouldn't
actually
figure
out
until
they'd
actually
tried
it,
and
I
think,
actually,
that
the
biggest
problem
with
adoption
there
is
just
the
complexity
of
onboarding.
C
C
A
Yeah,
no,
absolutely
so
well,
I
was
just
giving
that
as
an
example
of
something
that's
not
easy
to
use
and
people
don't
like
it.
So
our
goal
here
is
to
make
it
very
simple
and
with
as
little
friction
as
possible
to
utilize
content
trust
like
the
same
way,
we
do
it
from
what
was
coming.
You
don't
have
to
do
much
today,
you
just
upload
your
images,
select
what
kind
of
scanning
blocks
you
want
to
put.
If
you
want
to
block
images
from
the
imported,
they
have
a
high
cd
and
you're
done.
C
Right
well,
it's
got
it's
got
value
and
you
enable
the
feature
with
the
checkbox
right
yep,
and
so
I
think,
content
trust
has
very
similar
value,
but
it's
not
just
a
checkbox
and
that
I
think
that's
the
the
problem.
I
think
if
it
was
a
check
box,
everybody
that
would
everybody
would
use
it
like.
Why
would
you
not
use
it?
You
know.
A
Next,
one
is
kind
of
trying
to
get
folks
to
see
what
kind
of
new
features
you
might
want
from
from
a
hardware
perspective
we
had,
it
looks
like
it's
all
over
the
place,
you
know
improved
replication,
webhook
for
integrating
with
csd
systems
or
or
other
allergic
notification.
Mechanisms
who
have
cicd
pipeline
integrations
also
rank
highly
high
availability.
Obviously,
so
you
can
see
here
that
we
have
improved
health
charge.
A
A
I
think
that
we
need
to
make
sure
that
we'll
probably
prioritize
this
and
look
at
both
the
investments
that
that
some
of
our
users
are
making
into
hardware
and
make
sure
we
kind
of
double
down
on
the
areas
that
are
going
to
have
the
biggest
impact,
starting
maybe
from
low-hanging
fruits,
but
also
things
that
are
going
to
protect
our
investments
into
hardware
and
how
hubble
grow
more
on
that
when
we
start
doing
the
1.9
prioritization.
So
we'll
definitely
talk
about
this
more
at
that
point.
A
So
so
a
question
asking
folks:
if
they're
willing
to
do
contributions
to
the
harvard
community,
it
looks
like
there's
a
good
percentage
of
folks
that
are
interested
in
contributing
more.
I
think
you
know
the
first,
the
first
item
there
is
to
get
them
to
start
being
engaged
in
the
community
and
and
having
a
good
time
zone
that
folks
can
come
in
and
talk
to
us
and-
and
this
bi-weekly
meeting
now
hopefully
will
help
beyond
that.
You
know
getting
them
engaged
into
slack
and
asking
questions.
A
A
And
this
is
more
around.
You
know,
domain
expertise
of
folks
who
seem
to
have
a
significant
uptick
in
devops
folks
that
are
interested
in
contributing,
and
one
of
the
last
questions
is:
if
folks
have
attended
the
harbour
community
activities,
we
have
a
good
percentage
that
has
but
a
lot
of
folks
that
are
interested
in
hubble.
They
want
to
be
part
of
the
harbour
community,
but
have
not
attended
any
of
our
meetings.
A
So
I'm
hoping
we're
going
to
change
that
and
we
are
going
to
have
a
big
community
meeting
at
cubicon
that,
hopefully,
will
spearhead
some
of
that
effort
of
bringing
more
members
into
our
community.
A
So
one
of
the
things
that
stephen
zhao
that
presented
this
at
the
asia
pacific
time
zone
is
that
at
least
some
issues
around
the
job
service,
whether
that's
job
status,
it's
freezing
or
users
are
not
able
to
stop
or
cancel
jobs,
and
some
of
the
time
into
a
precision
is
not
there.
We
are
aware
of
all
those
issues,
so
you
guys
have
hit
them.
A
So
rest
assured
that
you
know
when
we
encounter
an
area
like
this,
that
it's
not
performing
up
to
our
quality
standards
will
address
it
quickly
and
and
deliver
the
fixes.
A
All
right,
so
a
few
couple
of
upcoming
community
events
there's
a
hackathon,
that's
happening
in
china,
not
expecting
of
you
guys
to
attend.
But
if
you,
if
you
are
really
interested,
please
let
us
know
we'll
hook
you
up
to
the
right
folks
and
you
can
attend.
I
think
a
prerequisite
might
be
speaking
chinese.
So
there
might
be
a
few
barriers
to
entry
here,
but
then
at
the
two
next
kubicon
events,
both
in
eu
and
in
shanghai.
A
We
have
secured
both
hardware
meetings
as
in
breakout
sessions
that
are
related
to
hardware,
so
people
can,
from
an
end
user
perspective,
we'll
be
able
to
attend
and
learn
about
hardware
and
basically
see
demos
of
hardware.
But
we've
also
have
secured
meeting
space
for
the
hardware
maintainers
and
the
community
to
come
together.
Talk
a
little
bit
about
hardware,
look
at
our
roadmap
and
our
next
investment
give
an
opportunity
for
everybody
to
get
to
know
each
other,
share
some
food
and
drinks
and
and
have
a
discussion
around
open
source
registry.
A
A
I
know
that
nathan,
you
will
not
be
make
it
to
either
barcelona
or
shanghai,
but
our
goal
is
to
have
something
similar
for
the
san
diego
kubicon
later
on
this
year.
So
maybe
it
won't
be
as
big
of
a
over
media,
but
we
will
have
something
for
the
maintainers
so
that
it
gives
us
an
opportunity
to
to
get
together
as
a
community.
A
All
right,
the
demos
I
mentioned
it
earlier,
you
should
be
able
to
find
the
recordings
on
the
community
website
where
recorded
them
from
earlier.
So
if
you,
if
you
need
to
check
them
out
do
so,
if
you
have
any
questions,
you
know
we
can
handle
it
in
slack
or
or
even
in
github,
all
right.
Anything!
A
That's
on
your
mind
to
to
talk
about
today,
anything
that
we
can
help
you
with
anything
that
hubble
related
that
we
can
address.
E
Yeah
yeah,
the
only
thing
I'd
say,
is
I'd
like
to
see
a
little
more
activity
in
the
issues
and
pull
requests
and
stuff
in
the
at
least
in
the
helm.
I
don't
know
how
it
is
in
the
mainstream,
harbor
repo,
but
the
helm.
One.
A
Yeah
and
then
tyler
since
you're
a
pivotal
employee.
If
you
have
any
questions
on
the
home,
I
know
alexander
brandt
from
the
vmware
side
has
been
writing
out
some
documentation
around
how
to
deploy
hardware
using
a
home
chart.
So
if
you
shoot
me
an
email,
either
me
or
jonas
will
put
you
in
contact
with
alex
and
you
you
guys
can
share,
but
yes
loud
and
clear,
we
need
to
get
hardware
to
be
up
to
date.
We
need
to
stay
on
top
of
prs
and
and
we
will
do
that
cool.
D
A
So
I
want
us
to
use
issues
as
the
main
tracking
for
features
and
then
we'll
use
a
product
prioritization
board
to
slot
those
issues
into
releases,
so
that
will
bring
a
little
bit
more
clarity
to
everybody.
And
if
you
want
to
know
about
something
and
why
certain
decisions
were
made,
you
can
go
to
that
issue
and
not
do
any
pr's
and
read
about
it
and
see
the
discussion
that
happened.
A
Excellent
well
seems
that
we're
give
you
guys
back
a
few
minutes
of
your
day.
Thank
you.
So
much
for
attending
hopefully
see
you
guys
every
two
weeks
we'll
have
a
regular
cadence
now
so
we
are,
it
will
be
predictable
and
everybody
can
start
joining
us.