►
From YouTube: Harbor Community Meeting 20191023 - 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
Hello,
everybody
and
welcome
to
another
meeting
for
cncf
hardware
today
is
the
23rd
of
october
and
as
always,
this
is
a
recorded
meeting.
So
please
adhere
to
the
cmcf
code
of
conduct
and
and
guidelines.
A
So
I
have
a
few
things
that
I
want
to
basically
educate
everybody
today
on
some
of
them
are
logistical
and
other
things
are
like
some
exciting
announcements
from
our
community
and
then
we'll
do
a
couple
of
demos
as
well.
So
so,
let's
get
started.
So
let
me
share
my
screen.
Let
me
know
if
you
guys
can
see.
A
Takes
a
second
so
so
the
first
thing
I'm
gonna
talk
about
is
that
we
have
a
couple
of
changes
in
our
community.
The
first
one
is
mina
has
decided
to
step
down
from
the
maintainers
group,
and
that
was
a
result
of
you
know.
She
was
already
getting
pulled
into
a
lot
of
other
requirements
and
in
her
day,
job
which
is
at
vmware
and
she
has
been
replaced
with
danielle
pasak
who's
from
aqua
security.
So
daniel
has
done
a
lot
of
good
work
for
us.
A
Lately,
he's
been
spearheading
along
with
zach
and
others.
The
plugable
scanner
work-
and
you
know
this
is
a
testament
of
the
great
work
that
he's
been
doing
in
the
community
and
his
contributions,
and
he
is
now
the
latest
maintainer
in
the
hardware
ecosystem.
So
so
now
we
have
five
non-vmware
maintainers
and
we
have
four
vmware
maintainers
and,
of
course
the
core
maintenance
group
is
also
comprised
out
of
vm
more
folks.
A
So
congratulations.
If
you
see
danielle
on
slack
or
anywhere
else
on
twitter,
make
sure
you
congratulate
him
on
his
on
his
new
role
within
our
community.
The
second
thing
I
want
to
bring
your
attention
to
is
the
game
in
this
community
repo
for
the
go
harbor.
We
have
added
both
the
code
of
conduct,
which
essentially,
is
just
a
link
to
the
cmcf
code
of
conduct.
A
This
is
you
know
the
the
basic
guidelines
in
terms
of
you
know
how
communicate
with
each
other
with
respect
to
dignity,
and
you
know
how
we
carry
ourselves
within
the
community,
so
we're
following
the
upstream
or
our
governing
body,
cncf's
code
of
conduct
here
and
the
last
thing
is
we
added?
What
would
anyone
can
call
the
guiding
principles
for
the
project?
Think
of
this
as
a
set
of
values
and
emissions
statement
that
we
need
to
uphold
as
we
operate
within
the
hardware
community.
A
Most
important
thing
here
is
our
mission
statement,
which
is
to
be
the
most
secure
performance,
scalable
and
available
cloud
native
repository
for
kubernetes.
That's
a
kind
of
a
powerful
statement,
but
that's
really
what
we're
striving
to
be.
We
want
to
make
sure
the
hardware
is
ubiquitous
and
used
across
the
board
in
every
kubernetes
cluster.
A
These
are
important
aspects
in
terms
of
having
a
high
functioning
and
high
velocity
community,
so
we
have
seen
no
evidence
that
our
community
does
not
follow
these
values,
but
now
we
have
them
documented
and
we
have
a
a
way
to
reference
them
and
in
every
single
interaction
that
you
have
in
the
community
and
generally
other
cnc
projects
have
had
a
community
that
has
been
responsible
for
upholding
these
values
and
making
sure
everything
is
followed.
A
In
our
case,
we
didn't
want
to
dedicate
a
community
to
this,
but
essentially,
what
we're
doing
is
we're
saying
everybody
in
the
community
is
responsible
for
making
sure
we
uphold
our
values
and
guiding
principles
and
if
we're
not
make
sure
you
flag
it
up
and
we'll
have
a
discussion
about
it
and,
of
course
correct.
So
both
the
maintenance
group,
our
community,
open
source,
community
manager,
jonas,
that's
on
the
call
right
now
and
others
should
monitor
all
our
community
activities
and
make
sure
we
honor
our
values.
A
These
are
the,
and
the
last
thing
I
want
to
mention
here
from
a
logistical
standpoint
is
that
we
did
open
the
hardware
graduation
proposal
so
so
now
there
is
a
proposal
out
there
that
we
presented
at
the
cmcftoc
committee
on
november
5th.
We
once
the
voting
starts
for
harbor.
We
will
encourage
everybody
in
our
community
to
provide
a
non-binding
vote.
A
Of
course,
if
you
support
hardware
to
become
graduated,
you
can
offer
that
non-binding
vote.
So
you
can
read
more
about
it
in
the
cncf
qc
under
the
proposals.
That's
where
hardware
is
located
cool,
that's
it
from
the
couple
of
logistical
updates.
Let's
talk
a
little
bit
about
releases,
so
we
have
a
few
releases
in
the
pipeline.
A
We
have
1.8
that
is
slated
to
come
sometime
in
early
november.
A
A
Early
early
indications
are
are
probably
an
early
december
ship
date
with
potentially
released
candidates
that
you
can
showcase
at
cubicon
us
in
san,
diego
speaking
of
cubicon.
Is
anybody
going.
B
A
Yes,
you
are
yeah,
I
know
you're
going
to
join
us
in
kenny
zack.
Are
you
guys
going
yes
cool?
If
you
guys-
and
this
is
more
of
a
question
for
jonas-
is
a
contributor
summit
only
for
kubernetes
or
can
other
cnc
projects
also
attend.
B
So
contributor
summit
is
only
for
kubernetes
as
the
kubernetes
contributor
summit.
We're
gonna
be
roughly
450
people,
both
new
and
existing
contributors.
It's
not
for
other
other
cncf
projects,
but
we
do
have
the
the
harbor
event
on
monday,
which
is
the
same
time.
I
don't
know
if
you
talked
about
that
in
an
earlier
call.
A
So
if
you
guys
have
viewed
our
webinar
last
week
on
on
hardware,
one
of
the
things
that
we
talked
about
at
the
end,
by
the
way,
I
highly
encourage
everybody
to
view
that
and
one
of
the
things
we
talked
about,
was
this
lunch
and
learn
that
we
have
with
joe
beda,
where
we're
gonna
enable
a
lot
of
folks
to
to
come
in,
get
to
know
more
about
hardware
and
also
get
an
opportunity
to
interact
with
the
maintainers
other
users
contributors
and
and
give
you
opportunity
to
get
some
of
your
questions
answered,
but
also
get
real,
hands-on
experience
on
hardware
and
let
me
actually
open
up
some.
A
So
the
the
webinar
we
did
last
week
with
cncf
it
was
me
and
liz
rice
zach
was
there
as
well
and
so
other
folks
from
aqua
and
encore
is,
is
super
important
and
talks
about
some
of
the
new
capabilities
that
come
in
1.10
and
at
the
end
of
that
we
had
this
slide
about
this
working
lunch
at
cubicon,
it's
on
monday
november
18th,
12
30
to
4
p.m.
A
So,
if
you
guys
can
make
it
register
it's
a
50
registration
fee
which
will
donate
to
a
charity.
I
forgot
the
name
of
the
charity
now,
but
please
encourage
you
to
guys
come,
come
and
attend
that
event,
and
this
is
a
url
within
the
linux
foundations.
A
A
So
the
first
demo
I'm
going
to
do
is
I'm
going
to
show
cases
that
work
around
the
ability
to
create
what
you
call
a
limited
user.
We've
talked
about
this
in
the
past,
I
think
of
a
limited
user.
As
a
user
in
hardware,
that's
going
to
be
very
useful
in
multi-tenant
environments,
where
a
service
provider
is
basically
hosting
hardware
and
exposing
it
to
a
set
of
multiple
entities
where
those
entities
may
not
know
about
each
other
and
but
they
still
need
to
have
access
to
be
able
to
use
hardware.
A
So
rather
this
new
user
called
limited
guest
that
only
has
pulled
capabilities
for
containers,
but
at
the
same
time,
if
you
were
ever
to
login
into
hardware,
you
won't
be
able
to
see
each
other.
So
let's
go
ahead
and
create
a
couple
of
users
here
and
I'm
going
to
create
a
new
project
and
I'm
going
to
call
it
demo.
A
A
A
But
yes
blame
them.
Let
me
actually
delete
this
user
and
I
want
to
recreate
him.
A
So
obviously,
if
you're,
using
ldap
or
any
other
identity
federation,
you're
gonna
get
your
users
from
there.
A
A
All
right,
so
we
went
ahead
and
created
our
two
users
now,
so
let's
go
back
to
a
project
called
demo
and
let's
create
account
using
those
users.
So
let's
go
create
our
first
user.
In
this
case
we're
going
to
add
the
limited
guest.
A
A
Two
types
of
users
in
hardware
and
by
the
way,
if
you're,
not
aware
of
how
you
can
find
out
the
permissions
on
for
all
these
users,
we
actually
created
a
very
cool
documentation
here
under
the
user
guide.
A
A
Our
back
listing
of
what
each
user
is
able
to
do
so
if
you're
curious.
This
is
where
you
find
out
what
each
user
can
do
and
notice
here
that
the
limited
guest
is
able
to
do
very
few
things
right.
He
can
see
the
project
configuration,
see
a
list
of
repositories,
images
and
pull
an
image,
and
that's
about
it.
A
He
doesn't
have
access,
for
example,
to
see
project
logs
or
project
members
or
anything
else.
I
know
this
is
a
table.
It's
called
project,
we'll
fix
that.
Let's
go
back
to
our
demo
here
and
let
me
go
ahead
and
log
out
and
I
will
login
as
limited
guest.
A
A
A
A
What
version
did
this
come
out
in
this
will
come
out
in
version
1.10?
It's
that
the
release
of
hardware
that
I
mentioned
will
probably
ship
in
super
early
december,
and
we
might
have
a
release
candidate
at
cubicon
timeframe
cool.
Is
it
something
that
you're
interested
in?
Do
you
have
a
use
case
for
this
scenario
as
well.
C
A
Absolutely
the
the
presentation
I
mentioned
earlier
that
we
did
last
week
also
talks
about
1.9
features
and
we
have
a
detailed
deck
on
1.10
as
well.
So
if
you
get
a
chance,
you
can
view
that
as
well
and
kind
of
give
you
an
overview
of
where
we're
going
as
a
project
all
right.
Let's
move
on
to
a
second
second
feature,
which
is
called
immutable
tags.
A
So
you
can
delete
them.
You
can
overwrite
them
with
another
image.
You
have
to
go
and
remove
the
mutability.
If
you
want
to
do
any
of
that
in
those
cases.
So
let's
go
ahead
and
take
a
look
at
that.
So
so
we
have
here
our
project,
which
is
library
and
there's
a
new
section,
called
immutable
tag.
Now
before
I
click
on
that,
I'm
going
to
warn
you.
The
ui
is
not
finished
yet,
so
it
has
some
references
to
to
other
to
other
capabilities.
A
As
part
of
the
copy
and
paste-
but
you
know
basically
giving
you
guys
a
super
early
preview
of
this
feature.
So
when
I
click
on
immutable
tags
over
here,
I
don't
have
any
rules
and
it
says
retention
rules,
but
ignore
that
for
a
second,
but
let's
go
ahead
and
create
a
rule
so
notice.
Here
I
have
a
few
repositories
right.
So
I
have
this
hello
world,
which
has
a
demo
and
a
latest
tag.
A
Okay,
so
so
I
can
come
in
another
rule
that
basically
says
all
my
repos
should
be
immutable
or
I
can
set
a
rule
that
says
certain
repositories
should
not
be
immutable,
so
I
can
come
in
and
easily
create
a
set
of
of
of
rules
that
define
how
I
want
to
deal
with
these
images
so
think
about
a
specific
group
that
someone
could
do
right.
So
so
someone
could
come
in
and
say
if
my
demo,
sorry,
if
my
hello
world
application.
A
A
A
And
demo
tag
so
so,
if
I
were
to
create
that,
basically
I'm
instructing
hardware,
no
matter
what
happens,
nobody
can
update
hello
world
demo
tag
and
if
a
new
version
comes
out,
I
need
to
basically
call
it
the
m1
demo
2
or
version
1.2
version
1.3-
and
this
is
the
beauty
of
this.
So
this
works
very
well
in
scenarios
where
your
csd
system
is
going
to
produce
a
production
level
image.
A
You
can
tag
it
appropriately
and
then
you
can
also
use
the
same
cid
the
policy
to
create
an
immutability
rule,
so
that
hardware
can
maintain
the
original
desire
of
you
on
that
image.
So
you
cannot
have
someone
else
in
your
dev
team,
come
and
overwrite
it.
That's,
basically
the
beauty
of
immutability
and
as
I've
shown,
this
is
super
early
preview
and
some
of
these
things
didn't
work.
So
my
apologies
ahead
of
time.
A
So,
let's
let,
let's
keep
that
for
now
any
questions
on
on
some
of
these
new
capabilities.
A
B
A
And
by
the
way
I
was
able
to
add
the
tag
you
just
had
to
finagle
the
ui
a
little
bit,
but
by
pro,
by
bypass
some
of
its
capabilities,
but
essentially,
once
you
enable
the
immutable
tag.
A
If
you
try
to
put
to
a
push
on
the
image,
it
will
just
fail
using
the
same
tag
or
if
you
try
to
delete
it
same
thing,
and
one
of
the
things
I
forgot
to
mention
is
that
there's
going
to
be
situations
where
you
want
to
enable
some
tag,
retention
rules
for
compliance
and
those
type
redemption
rules
might
conflict
with
immutability
rules
that
protect
you
from
deleting
an
image
right
and
you
might
ask:
why
is
that?
A
Well,
one
of
the
things
we
want
to
prevent
is:
let's
say
you
set
up
and
I'm
going
to
pick
on
redis
here
you
set
up
reddish
version
1.2
to
be
immutable.
Well,
we
want
to
prevent,
delete
as
well.
For
one
reason
we
don't
want
someone.
We
certainly
don't
want
someone
to
override
radius
1.2,
but
we
also
don't
want
someone
to
go
and
delete
radius,
1.2
and
overwrite
it
with
an
image.
That's
exactly
the
same
thing,
essentially
so
with
immutability.
A
We
prevent
both
delete
and
overwrite,
so
delete
is
also
what
tag
retention
does
so
when
a
retention
rule
runs
and
you're,
essentially
based
on
policy.
You
want
to
delete
an
image
because
it's
out
of
compliance
or
basically
you're
running
out
of
space,
and
you
only
want
to
keep
any
number
of
images
or
the
image
should
not
be
more
than
90
days
old
or
whatever
your
policy
is
tackling,
might
decide
to
delete
an
immutable
image
on
purpose.
A
Harbor
will
also
fail
that
deletion
and
we
have
a
web
hook
that
we
have
configured
so
that
you'll
be
notified
as
an
operator
or
administrator
that
you
have
a
conflicting
policy
between
tag,
immutability
and
tag
retention,
and
you
can
take
action
on
that.
So
your
opportunity,
as
an
administrator
or
operator
of
hardware,
is
to
remove
the
mid-ability
on
that
image
and
clear
it
out,
or
you
can
actually
fix
your
attack
retention
rules.
A
All
right,
no
questions.
Well,
thank
you
all
for
attending.
I
really
appreciate
that.
Jonas,
since,
since
we
talked
about
it
today,
you
might
want
to
tweet
on
our
twitter
account
the
the
lunch
and
land
with
your
bed
again.
Let's
just
give
it
one
more
round
of
folks
to
be
aware
of
that,
and
hopefully
we're
gonna
see
quite
a
few
of
folks
from
our
community
attend.
That
sounds
great.
We'll
do!
Thank
you
all
have
a
good
day,
we'll
post
this
on
youtube
in
a
few
days,
bye
have
a
good
one,
bye.