►
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
C
This
is
today's
agenda
and
first,
where
I
will
introduce
the
hubble
version,
1.8.1
data
we
released
last
week
and
the
second
we
will
introduce
the
hubble
v
1.9
plan
and
next
we'll
introduce
some
upcoming
community
events
and
then
well
well,
do
a
feature
diamond
of
the
new
feature
in
the
developing
I
developed
and
not
so
in
today's
staging
is
discuss
anything
about
hubble.
C
C
In
the
last
week
we
released
the
hubble
v
1
1.8.1.
In
this
release.
We
fix
the
some
no
issues
which
is
now
in
the
1.8
point,
and
what
can
and
this
you
you
welcome
to
download
and
try
it
on
the
hubble's
github
repo
and
if
you
encounter
some
problems,
feel
free
to
open
issue
to
ask
well
well
fix
it
as
soon
as
possible.
C
Okay,
after
a
long
discussing
of
on
the
features
in
1.9,
the
the
planning
is,
the
plan
is
finished.
The
next
week
network
mike
michael
to
introduce
the
final
features
in
the
v
1.9
hello,
michael.
D
Hi
everybody:
how
are
you
so
so
yeah?
It's!
We
had
a
lot
of
time
after
cubicon
to
kind
of
prioritize
some
of
the
features
that
we
want
to
address
for
1.9,
including
the
timeline
for
1.9
and
the
list
that
we
came
up
with
that
addresses
a
lot
of
the
issues
that
our
customers
are
seeing
and
things
that
we
want
to
implement
to
advance.
D
We
will
implement
a
retention
policy
so
that
you
will
be
able
to
define
how
much
how
long
you
want
to
keep
certain
images
in
in
your
repositories
and
in
your
projects
and,
more
importantly,
we're
going
to
give
you
some
flexibility
in
terms
of
the
policy
and
the
engine
that
you're
going
to
get
to
define
for
retention.
Actually,
in
fact,
last
night
the
maintainers
of
hardware
had
a
big
discussion
on
retention
policy
and
and
we're
gonna
continue
on
that
discussion,
as
we
finalize
both
the
user
experience
and
the
capabilities
in
this
area.
D
If
you
guys,
remember,
zach
zack
nathan
lowe
had
some
good
implementation
and
ideas
on
our
retention
so
he's
on
vacation
now.
D
So
when
he's
back
we'll
sing
with
him
and
kind
of
finalize,
that
webquest
was
something
that
we
wanted
to
implement
before
we're
going
to
end
up
doing
that
now
and
for
web
hooks,
we're
going
to
go
down
the
path
of
a
minimal
viable
product,
initially
we're
going
to
support
only
one
web
per
project
and,
more
importantly,
we
will
only
have
web
box
around
containers,
images,
push
pull
delete
and
then
home
charge
push
pull
delete
as
well
as
cv
scanning.
D
The
white
listing
cve,
that's
a
feature
that
will
allow
us
to
exclude
certain
cvs
from
policy
so
that
if
a
new
cd
came
out-
and
it
has
not
had
a
chance
to
be
patched-
we
don't
want
to
prevent
images
from
getting
pulled.
D
The
syslog
endpoint
is
going
to
allow
us
to
push
the
logs
from
hardware
into
syslog,
capable
providers.
I
think
of
this
as
being
able
to
push
your
logs
to
splunk
or
elk
or
fluency
or
other
tools
that
can
support
syslog,
we're
obviously
going
to
improve
replication
to
add
more
providers
and
their
application
working
group
is
working
hard
at
that
and
the
last,
but
not
least,
that
is
the
repository
beyond
images
and
home
charts.
D
We're
only
going
to
do
the
ground
work
there
to
start
thinking
about
what
do
we
need
to
do
to
support
things
like
kubernetes
operators
and
cena,
bundles
and
other
things
in
harbor,
so
that
work
is
more
investigation
and
proof
of
concept
now
and
in
the
future.
We're
gonna
target
into
into
production,
and
one
other
thing
I
wanted
to
mention
is
our
goal
for
hardware:
1.8
is
to
release
sometime
at
the
end
of
august,
so
that
is
the
proposal
for
our
release.
The
28th
of
august.
D
C
You
thank
you
michael,
oh,
okay,
next
is
the
upcoming
community
events.
You
now
in
the
june
20s
and
june
26
cuba,
car
china
were
housed
in
shanghai
and
also
hubble
have
four
stations
in
the
cubicle.
C
The
first
is
since
they
have
china
or
originated
project
community
reception,
and
this
is
in
june
24th
and
this
is
hosted
by
hubble
and
the
dragonfly
and
the
thai
are
working
to
join
the
reception
and
there
is
a
nighting
talk
about
the
new
home
chat,
installation
experience
with
visual
and
the
repeatable
approach,
which
is
a
president
president
by
stephen
zaw,
which
is
a
committee
in
hubble
all
about
havoc
by
stephen.
C
This
station
is
by
stephen
zor
and
wun
kai
in
the
june
24
phase,
and
the
nasdaq
is
upgrade
images
by
digging
out
and
automatically
fixing
the
violent
vulnerability
vulnerabilities
and
which
is
the
speaker,
is
yam
and
stephen
zaw,
which
is
in
june
26th
welcome
to
attend
the
session
of
the.
C
Sessions,
oh
oh,
oh
there's
one
thing
to
mention
is
that
in
the
july
and
august
the
travel
community
meetings-
well,
you
might
oh
in
each
community
meeting,
will
well
invite
one
or
two
hubble
users
to
sharing
their
experience
and
their
user
case
of
hubble
in
their
company
and
in
production
environment.
C
So
in
the,
if
you
wanna,
learn
something
or
to
know
something
other
people
how
to
using
hubble
in
their
environments.
You
can
join
me
community
meeting
in
july
and
august.
C
D
If
you
don't
mind,
I
want
to
say
one
one
more
thing
as
well,
so
now
that
we
have
cubic
on
shanghai
happening
next
week,
it's
also
the
right
amount
of
time
to
submit
sessions
for
the
next
cubicon
in
the
united
states
in
san
diego
in
november.
So
it's
very
important.
If
any
of
you
have
ideas
around
sessions
that
one
you
want
to
submit,
or
you
your
specific
use
cases
on
terms
of
how
you're
using
hardware
in
your
organization
would
love
to
hear
from
you.
D
You
can
pick
me
sing
me
private
on
slack
or
you
can,
or
basically
you
can
send
me
a
message
on
on
twitter.
I
love
to
work
with
you
to
identify
a
session
that
you
want
to
submit
and
even
we
can
co-present
with
you,
but
the
important
thing
is
we
want
to.
E
One
more
thing
I
want
to
add
is
that
if
you
have
any,
you
want
to
share
your
use
cases
with
other
people
with
the
community
members.
You
are
also
welcome
to
contact
us
so
that
you
can
be
sharing
your
kcc
in
one
of
our
subsequent
community
meetings
in
july
or
august
or
maybe
in
september
and
october,
depending
on
the
on
the
on
the
schedule,
but
anyone
is
welcome
to
share
their
use
cases
of
harbor.
So
everyone
is
welcome.
So
please
contact
us
if
you
you're
interested
in
sharing
thanks.
F
C
And
this
is
the
feature
diamond
session
and
then
let's
work
on
yeah
the
engineer
from
women.
Well,
they
he
will
diamond
as
the
robot
account
pull
and
push
hello,
yeah.
G
G
G
Hi,
okay,
so
much
going
okay!
So
actually
today,
I
will
tell
you
how
to
use
a
rubber
account
to
do
hand
push
and
put
so.
The
original
request
was
from
the
community.
So
one
guy
found
the
issue
to
ask
team
to
add
a
option
to
allow
a
rubber
user
to
do
the
helm,
pull
and
push.
G
G
I
have
already
set
up
a
harbor,
so
let's
try
to
a
new
rubber
cup
and
we
ground
it
even
named
daimler,
so
we're
growing
it
with
ham,
char
push
and
have
sharp
okay,
let's
copy
the
token.
G
G
G
Okay,
in
the
help
I
have
gone,
I
have
already
add
my
harbor
into
the
hem
river
list,
so
we
can
see
here
my
rainbow
is
here.
So
let's
try
to
use
the
rubber
cone
to
push
my
local
hem
into
harbor.
G
G
G
G
G
D
I
think
the
the
important
thing
I
want
to
stress
here
is
that
how
responsive
we
were
to
some
of
the
customer
feedback.
So
so
we
had
a
user
that
asked
for
home
chart
abilities
in
the
robot
accounts
and
we
were
able
to
very
easily
go
back
and
address
it
very
quickly
for
our
users.
So
thank
you
and
that's
a
great
job.
I
C
Welcome
to
me,
what's
me,
is
a
hubble
is
an
engineer.
I
Yes,
okay,
I'm
very
glad
to
show
this
demo
here.
As
you
know,
I
will,
I
will
show
I
will
introduce
to
a
newer
new
replication,
adapter
aws,
ecr
and
google
gcr.
I
I
You
can
see
the
difference
is
first,
we
we
suppose
the
new
provider
here
and
we
introduce
the
new
url
endpoint
selector
here,
and
we
need
to
use
aws
ak
as
the
credential
and
the
this
driver
also
supports
bypass
certification,
very
verified
here.
I
also
have
a.
I
also
set
up
a
hyper
first.
I
First,
you
can
create
a
new
registry
endpoint
here
you
can
select
the
aws
ecr,
okay,
here,
ecr,
okay
and
the
endpoint
url
I
have
I
have
in.
I
have
put
all
regions
here,
so
you
can
just
select
or
if
you
use
all
the
ui,
you
can
just
input.
The
correct
url,
for
example,
I
enter
ap
note
is,
which
is
japanese
chapter
10,
and
here
I
input
the
id
the
the
ak
id
is
from
ecr.
I
I
I
I
I
I
I
I
J
Switch
back
to
the
yeah,
I
think
you're
you're,
using
a
wrong
name.
I
Oh
here
you
can
see
when
image
is
being
replication
and
the
log
is
here,
it
is
showing
and
the
image
is
replicated
here
and
it
is
replica.
It
is
that,
but
I
still
can't
kind
of
show
you
the
aws
website.
Okay
and.
I
I
I
I
I
I
I
Here
the
the
json
field
is
just
like
something
like
this,
and
you
can
just
copy
this
copy
this
into
into
here.
Okay,
so,
let's
test
the
connection.
Okay,
it's
connect
successful.
If
we
change
from
some
key,
for
example,
it
should
fail.
I
I
It
is,
it
is
because
it
is
replicated
to
the
gcr,
because
I
already
pushed
it
before
so
so
the
so
the
blob
is,
the
thing
already
exists.
I
I
B
I
I
I
A
I
I
I
I
Okay,
that's
all.
C
Okay,
let's
go
to
the
next
session.
If
you
have
any
questions
you
can
discuss
here,
any
question.
C
A
So
pre
1.8,
it
was
quite
simple:
we
could
use
environment
variables
or
config
file
to
set,
you
know,
generate
user
authentication
to
uaa
or
whatever
post
1.8,
it's
quite
painful
to
work
with
the
configuration
api
and
it
makes
it
very
difficult.
A
So
you
know
we
use
the
helm
chart
to
stand
up
harbor
and
then
we
need
to
throw
a
bunch
of
curl
commands
to
actually
configure
the
rest
of
it
quite
painful
and
error-prone,
and
it
would
be
good
to
go
back
to
having
an
option
to
do
it
via
config
file
or
environment
variable
as
well
as
that,
I
don't
know
of
any
tools
currently
that
will
like
easily
integrate
with
that
the
config
api,
especially
without
a
cli.
A
A
Everything
understands
how
to
write
a
write,
a
config
file
and
restart
a
service
natively,
because
that's
how
everything's
been
done,
whereas
nothing
really
understands
how
to
do
that
by
the
config
api
but
yeah,
but
by
the
api.
A
J
Yeah,
let
me
explain
why
we
do
this
because
we
currently,
when
neutral
properties
you
have-
I
mean
before
1.8.
There
are
two
ways
to
configure.
Hardware:
first,
is
you?
Can
you
know
configure
it
as
you
did
via
environment
variable
or
configuration
file?
The
other
is
there'll,
be
a
the
ui
console
or
api.
J
We
found
that
problematic,
because
when
users
do
some
update
of
the
configuration
via
ui
and
if
they
up
you
know
restart
the
vm
or
somehow
restart
hardware
and
the
latest
change
they
make
will
be
overwritten
by
the
configuration
file
or
whatever
bootstrap
script.
They
use,
because
the
change
user
makes
on
the
ui
or
api
will
not
be
reflected
in
the
configuration
file.
So
that's
why
we
we
had
to
you
know
make
the
decision
that
we
categorize
the
configurations
into
two
areas.
J
One
user
can
only
set
via
configuration
file
or
environment
variable
and
the
other
part
they
have
to
configure
the
api
or
ui.
So
that's
why
you're
seeing
the
issue,
but
for
this
particular
problem
I
think
somehow
you
can,
or
maybe
we
can
for
help
chart.
We
can
add
something
in
the
pod
template
in
the.
I
think.
There's
a
life
cycle
life
cycle
attribute
to
support
that
or
the
other
way
around.
J
A
J
A
I've
seen
people
solve
it
by
if
a
config
has
been
set
by
a
config
or
environment
variable,
then
it
gets
grayed
out
in
the
ui
and
doesn't
let
you
change
it,
and
that
way
you
kind
of
get
that
protection,
but
you
also
get
the
flexibility.
If
someone
wants
to
configure
it
by
the
api
or
by
the
ui,
if
they
don't
set
it
by
the
config
file,
then
they
can
always
yeah.
J
A
Yeah,
the
other
alternative
would
be,
I
think,
if
we
had
a
decent
config
api
cli,
that
we
just
make
sure
it's
item
potent
and
then
we
could
then
use,
as
you
kind
of
said,
like
a
life
cycle
like
a
post
install
hook
and
helm
to
run
that
cli.
A
I
just
feel
that
the
just
running
curl
commands
is
pretty
fragile
and
it's
hard
to
detect
errors
and
deal
with
those
errors.
J
Yeah,
I
I
think
yeah
yeah-
I
I
think
I
I
haven't
made
that
issue,
and
could
you
write
up
an
issue
on
our
repo
and
collect
like
thumb
up
icon
with
other
community
users,
and
if
you
see,
if
you
know
it's
a
quite
common
issue
and
you
have
got
a
lot
of
support,
probably
we
should.
You
know,
spend
some
time
to
work
that
out
in
one
of
my
time
frame.
J
D
L
L
L
K
K
K
D
Well,
we're
way
past
time,
so
I
think
we
need
to
kind
of
start
closing
down
the
meeting
and
maybe
in
the
future
we
can
put
time
boundaries
on
demos,
so
we
can
stay
on
our
30-minute
bi-weekly
meeting
times
time
some
as
well.
I
just
you
know
so
that
all
community
members
can
probably
allocate
for
the
time,
but
today
was
excellent.
Thank
you,
ziming
for
doing
a
great
job
driving
the
meeting.