►
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
A
A
A
Oh
okay,
he
dropped
so
any
other
topic.
A
So
then,
I
think
we
can
wrap
up
yeah
if
you
are
interested,
please
steve
is
asking
what
is
the
current
progress
on
internal
metrics
in
the
previous
community
meeting
the
developer
qian
has
been
demoing
it,
so
you
can
probably
find
it
on
the
youtube
to
see
the
previous
community
meeting.
Now
he
demoed
how
how
you
can
use
promise
use
to
to
to
check
all
the
requests
are
sent
to
harbor
all
the
requests
to
the
api
endpoint
and
to
harbor,
and
now
we
are.
A
A
A
So
if
no
more
questions
or
topics
alex,
I
think
we
can
wrap
up.
C
C
B
C
So,
do
you
have
some
documentation
for
that
or
I
I
don't
have
some
material
by
hand.
B
I
don't
have
documentation
for
yet
I
just
I
made
a
note
of
it
after
our
discussion,
but
essentially
you
know
we're
opening
up
api
access
for
robot
accounts
in
a
very
controlled
manner.
So
right
now
we
have
you
know
when
you
create
a
robot
account,
you
can
give
the
robot
account
push
access
or
pull
access
on
images
or
are
on
helm,
charts
and
then
in
the
upcoming
2.2.
B
We're
thinking
about
granting
api
access,
so
robot
accounts
cannot
just
push
and
pull
images
as
well
as
delete
images
and
then
sign
images
and
push
signed
images
as
well
as
maybe
or
we're.
Thinking
of
adding
the
ability
to
add
text,
remove
tags,
add
labels
and
scan
images.
So
those
are
the
core
api
actions
that
robot
accounts
will
have
access
to
as
part
of
their
their.
You
know,
cicd
a
lot
of
users
have
asked
for
other
api
access,
such
as
you
know.
B
Robot
account
or
using
a
robot
account
to
configure
retention
policies
or
security
policies,
or
do
anything
any
of
the
other
configuration
that
a
project
admin
only
the
project
admin
would
have
access
to,
and
so
I
think
that
sort
of
falls
outside
of
their
scope,
and
you
know
the
purpose
of
of
doing
this
feature
of
you
know
working
on
this
feature.
So
for
now
it's
just
going
to
be
the
those
core
essential
actions
that
that
were.
A
A
This
permission
does
not
belong
to
any
project
right,
it's
doable
in
the
background,
but
the
the
gap
is
on
the
ui.
We
don't
know
how
to
expose
that
on
the
ui.
I
think,
if
you
have
a
you
know
intuitive
way
to
show
user
how
to
set
the
permission.
It's
also
a
good
enhancement
because
there
are
requests
from
other
users.
They
want
to
use
robot
account
to
do
replication.
If,
if
the
robot
account
cannot
create
project,
some
of
the
replication
will
not.
You
know,
be
successful.
B
Replication
is
a
bit
it
might
be.
B
It
might
not
be
appropriate
for
robot
account,
because
even
the
project
admin.
A
B
Yeah,
did
you
also
discuss
how
we're
getting
rid
of
the
or
solving
the
the
special
character
that
causes
an
issue
in
bash.
B
B
Sure
so
we
have
quite
a
few
sessions
related
to
harvard
kukan.
We
have
meet
the
maintainers
today
at
one,
I'm
sorry
what
I
found
what
the
time
is,
I
believe
it's
1
50,
I'm
sorry.
It's
3,
50
3,
3
50
p.m.
Eastern
time,
there's
also
an
office
hours
every
day
for
today
and
for
tomorrow
at
1
pm
eastern
and
then
I
played
henry
jong
and
painting
from
netease
also
have
a
session
on
managing
artifacts
at
distributed
scale.
B
That
has
you
know
not
just
harvard,
but
some
other
projects
as
well
tied
into
harbor,
and
we
had
a.
We
had
a
great
office
hours
yesterday.
We
maxed
it
out
at
28
participants,
lots
of
really
good
questions,
lots
of
questions
on
proxy
cash.
You
know
how
proxy
cash
can
help
with
the
recent
doc
health
rate,
limiting
announcement
and
then
michael
michael
had
a
lightning
talk
on
using
harvard
to
manage
your
artifacts
at
the
edge
through
proxy
cache
and
ptp
distribution.
So
we
have
a
lot
of
engagements
in
kubicon.
B
B
Office
hours
are,
you
know,
we
don't
have
anything
explicitly
planned
like
no
demos
or
or
deck
or
anything
like
that.
Just
comment
with
your
questions
and
share
whatever
experiences
you
have
around
harper.