►
From YouTube: Argo Contributors Office Hours Dec 9th 2021
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
I
believe
we
can
start
so
quiet.
Everyone
is
still
getting
from
argo
county,
so
exhausted,
but
it
was
a
good
event.
D
By
the
way,
because
I
wasn't
able
to
attend,
but
I'm
very
interested
in
the
recordings,
will
they
be
publicly
available.
C
A
A
Okay,
we
had
several
topics
actually
from
from
previous
meeting
and
before
we
go
into
topics.
I
know
that
we
usually
share
support,
expect
not
not
support
moderator
experience,
and
I
was
that
I
was
trying
to
be
that
moderator
this
week
and
with
kate
and
basically
I
can.
I
wanted
to
share
one
item
that
I
I
noticed.
Basically,
there
was
a
interesting
quest.
There
was
not
so
many
questions
in
the
discussions,
but
there
was
one
related
to
dog's
translation.
A
So
I
realized,
I
guess,
having
a
second
like
you
know,
translated
version
of
documentation
is
a
commitment,
and
I
just
wanted
to
hear
the
thoughts
and
I
already
replied
to
the
discussion.
I
said
that
we
obviously
welcome.
You
know
help
with
translation,
but
maybe
it
makes
sense
to
wait
for
for
this
documentation
refactoring,
because
we
kind
of
we
are
hoping
to
do
it
for
a
long
time
already.
D
Good
question
yeah:
I
think
we
have
so
much
documentation
depth
right
now.
Right
I
mean
I
I
guess.
Having
I
mean,
having
translated
documentation
is,
is
is
a
great
thing,
especially
for
for
languages
like
chinese
right,
because
I
I
figured
there
are
quite
a
few
chinese
uses
already
and
there
is
a
huge
difference
in
the
language
family,
between
english
and
and
chinese
or
mandarin
or
whatever,
and
but
I'm
not
sure
if
we
should
pull
that
in
into
the
official
documentation
and
maybe
rather
say.
D
You're
welcome
to
to
translate
the
the
documentation
and
we
will
link
to
the
docs
that
you
bring
up
but
refer
to
it
as,
like
an
unofficial
version,
an
official
translation,
I'm
not
sure,
because
we,
we
can't
even
know
what,
if,
if
it's
properly
translated
or
if
you
know
what
I
mean
so
like
yeah,
I'm
not
sure.
That's
just
my
two
cents.
C
C
C
G
You
could
imagine
a
release
maintenance,
cadence,
that's
just
very
aggressive
about
deleting
old
translations.
So
basically,
you
have
a
snapshot.
We're
sure
that
the
translation
is
good
for
v2.whatever
when
the
release
for
2.,
whatever
plus
one
comes
around.
If
someone
hasn't
contributed
the
updated
translations
by
the
time
we're
ready
to
release
just
delete
them,
wait
for
the
work
to
be
done
for
a
different
release.
H
Yeah,
I
think
in
general
we
need
commitment
almost
to
the
same
level
as
we
maintaining
but
for
dogs
with
respect
to
this-
and
I
think
if
whoever
is
volunteering
for
this
is
happy
to
put
in
that
level
of
commitment,
we
should
try
it
out
and
see
how
the
dogs
shape
up
and
then
a
couple
of
releases
from
now
to
take
a
call
again
if
they
have
to
be
part
of
our
documentation
or
even
linked
from
our
documentation.
H
But
then
I
think
the
first
step
is
not
really
should
there
be
lingerie
should
be
part
of
our
documentation.
We
need
to
see
how
things
run
for
at
least
a
couple
of
releases
before
we
move
them
into
our
documentation.
I
think
that's.
That's.
That's
probably
that's
probably
something
that
would
be
a
consequence
of
good
practices
with
dogs
upkeeping.
A
All
right,
so
it
it
sounds
like
okay,
I'm
trying
to
summarize
what
I
heard
just
now,
basically
idea
that
yeah
everyone
agrees,
it's
it's
a
big
commitment
and
we
definitely
should
not
even
try
before
we
refactor
the
dogs,
because
we
we
know
they're,
basically
going
to
be
changed
a
lot,
and
even
after
that,
we
need
to
be
super.
Careful.
C
I
I
A
Really
like
a
suggestion
from
michael
that,
basically,
if
you
we
cannot
translate
documentation,
but
we
know
that
if
we're
changing
corresponding
document
in
english
and
if
chinese
version
don't
get
refreshed
within
you
know,
by
the
end
of
the
next
release
cycle,
then
we
can
just
have
an
agreement
to
remove
it.
And
you
know
so.
Some
kind
of
compromise
might
work.
It.
J
Yeah,
but
I
think
that
doesn't
seem
maintainable,
because
documentation
is
incremental
in
nature
right
like
so
it
basically,
if
someone
add
a
feature
and
add,
like
maybe
a
paragraph
or
two
about
that
feature,
does
that
mean
basically
where
every
release
they
have
submit?
We
have
to
have
this
part
where
we.
A
Yeah,
so
it
it
basically,
I
guess
how
it
might
work
out
if,
if
we
get
initial
version
of
translations
and
then
in
the
next
release,
we
update
couple
pages
and
we
don't
get
volunteers
to
re-translate
them.
We
kill
these
two
pages
and
eventually
we
might
kill
all
of
the
translated
documents
and
the
project
died.
But
if
we
have
maintainers
who
stick
around
and
keep
re-translating
them,
then
it
stays
alive.
Basically,.
C
So
I
I
I'm
just
trying
to
estimate
the
averages
I
feel
like
if
I
have
some
professionals
like
to
do
in
the
translation-
maybe
that's
easy
for
them,
because
they
do
that
in
day-to-day
basis,
but
I
don't
think
we
will
get
one
like
that.
But
if
I
ask
me
to
translate
the
english
document
in
chinese
actually
extremely
painful,
I
mean
I
might
be
using
twice
of
the
time
to
writing
that
in
english
in
chinese,
then
eventually
I
I
personally
might
give
up.
So
I
really
need
to
see
there.
G
C
Big
group,
I
know
they're
like
like
thai
each
high,
like
we
have
maybe
two
alternative,
like
three
of
us
in
the
community
relative
active,
can
read
and
write
in
chinese,
but
I
don't
think
that's
enough.
That
means
every
single,
like
docs
pr
has
to
go
through
us.
If
we
open
that
panel
box.
A
Okay,
like
basically
what
if
we
just
don't
push
it
hard,
but
if
people
really
want
it,
they
will
come
back
again.
It's
the
same
question
and
if
we
hear
again-
and
if
if
we
hear
it
from
like
a
dozen
of
people,
then
we
can
reconsider.
I
I
H
H
F
I
think
the
only
concern
I
have
there
was,
I
said
earlier:
it
kind
of
becomes
almost
official
if
we
do
that
and
I'm
just
worried
about
the
quality
and
I'm
not
sure
if
people
will
be
able
to
distinguish
between
the
documentation
being
in
argo
or
argo
labs,
and
I
think
a
lot
of
people
will
just
consider
it
to
be
official.
And
if
it's
out
of
date
or
not
good,
then
it'll
reflect
early
on
yeah.
J
So
we
have
like
kind
of
like
unofficial,
helm,
charts
like
the
community
maintain
charts.
I
don't
know
if
you
tried
to
use
them,
but
they're,
not
great
and
but
a
lot
of
people
use
them
because
they
kind
of
feel
that
it's
you.
J
The
helm
choice
for
argo,
but
it's
they're
always
out
to
out
of
date
and
like
I
don't
know
that
anyone
in
this
room
ever
maintains,
like
the
any
of
the
official
maintainers
work
on
them,
but
they're.
I
I've
tried
to
use
them
and
they
actually
are
not
like
up
to
date
with
the
stream
right.
H
We
tell
them
that
you
can
go
ahead
and
start
something
that's
outside
of
any
argo
and
then
eventually,
if
we
see
in
a
couple
of
releases
that
you
know
it's
really
up
to
the
standards
that
it
can
be
maintained
potentially,
then
then
we
move
it
to
argo
approach
labs
so,
which
means
that
we
would
have
a
fair
level
of
understanding
to
see
if
it's
actually
sustainable
and
it
could
be
two
or
three
or
four
releases,
depending
on
what
our
comfort
level
is.
But
then
the
idea
is
that
you
know
go.
H
Try
it
out
we're
not
going
to
stop
you
from
doing
so,
because
you're
helping
out
the
community
and
then
eventually,
if
it's
very
popular,
very,
very
well
maintained
it
has
a
path
to
broad's
labs,
not
our
products.
A
Basically,
I
I
really,
I
I
think,
I'm
going
to
just
post
what
you
just
said
so
big
into
the
you
know
in
in
reply
to
the
discussion
again
and
basically
propose
to
if
they
want
to,
I
would
propose
them
to
start
a
lobster
positive
and,
and
we
can
offer
kind
of
advertising
help.
You
know
we
can
not
advertising,
we
can
yeah,
and
now
we
can
discuss
next
steps.
We
can
figure
out
how
we
carefully
can
promote
that
repository.
Once
we
ensure
the
good
quality,
I
guess
so.
Does
it.
H
Sound
good,
it's
like
very
good,
so
so
I
actually
kind
of
specified
something
a
little
bit
like
a
little
different,
rather
not
project
labs
repository
right
now
at
all,
but
rather
we
tell
them
that
you
go
ahead,
starting
your
own,
get
a
get
in
your
own
github
and
then
down
the
line.
If
in
two
or
three
releases
we
see
that
it's
good,
you
can
apply
to
be
a
part
of
argo
broad's
labs,
even.
G
C
C
B
F
F
That's
just
going
to
say
we
can
at
least
do
an
initial
review
from
the
people
that
that
speak
the
language.
Then
I
think
that
at
least
the
rest
of
us
can
at
least
keep
an
eye
and
see
how
how
they
do
in
terms
of
number
of
updates
and
things.
When
things
change,
I
mean
that's
a
little
easier
to
keep
track
of.
C
J
A
J
A
D
A
D
I
can
give
you
the
time
back
so
because
so
the
topic
I
have
put
up
is
just
like.
I
I
just
wanted
to
bring
that
back
to
attention
to
to
my
fellow
maintainer
colleagues
that
they
take
a
look
at
the
proposal.
I've
sent
and
specific
discussion.
D
So
we
don't
need
to
discuss
now,
because
we
we
do
have
to
two
demos
or
two
two
things
that
people
want
to
show
and
time
is
sparse,
so
yeah.
This
is
just
a
quick
reminder
that
I've
put
a
lot
of
work
in
this
proposal
and
unfortunately,
no
one
really
took
a
look
right
until
now
so
yeah,
just
just
as
a
as
a
friendly
reminder
that.
G
D
Could
have
a
look
and
yeah.
A
D
A
J
I'm
not
sure
if
you
saw
the
maintainer
update
yesterday
on,
but
I
did
mention
like
self-service
workspace
level
application
cr
was
you
know
something
that
we
want
to
move
towards
in
in
the
future.
So
it's
it's
just
a
bit
more
about
the
approach
rather
than
we
agree
on
the
destination,
but
we
have
to
figure
out
the
approach.
E
Hey
alex,
I
can
quickly
speak
about
being
on
being
the
secondary
moderator
for
the
first
time.
Last
week,
okay
yeah,
I
try
to
treat
as
much
as
I
can.
I
added
labels
on
at
least
seven
issues,
and
also
I
submitted
a
pr
for
one
of
the
issues
yesterday
and
josh
has
already
made
a
comment
on
that
one
and
two
of
them
I
investigated
and
provided
a
resolution
or
explanation
for
the
problem
that
the
originator
had
and
both
issues
have
been
marked
as
closed
by
by
them
as
of
early
this
morning.
A
All
right,
so
I
guess
maybe,
is
and
chetan
are
you
going
to
do
the
km
demo?
Do
we
have
enough
time.
A
L
C
L
Yeah,
I've
selected
that
option.
Oh
yeah,
I've
shared
my
screen,
hope
it's
visible
to
everyone,
so
yeah,
so
hey
everyone.
L
So
today
I
wanted
to
demo
and
quickly
introduce
a
tool
known
as
cam,
so
we
at
red
hat
have
been
working
on
it
for
more
than
a
year
now,
and
the
reason
why
I
want
to
demo
it
here
is
because
it
has
a
few
similarities
with
the
the
project
ago,
cd
autopilot,
and
so
we
believe
that
there
is
room
for
collaboration,
because
both
the
tools
generate
an
opinionated
kit,
ops,
repository
layout,
so
so
I'll
start
with
the
presentation.
L
So
I
have
a
small
ppt
just
to
provide
some
context
around
cam.
So
if
you
have
any
doubts
or
questions,
so
please
feel
free
to
stop
me
in
between
and
we
can
discuss
more
so
so.
L
Cam
is
a
cli
tool
that
generates
an
opinionated
detox
repository,
and
so
it
follows
a
certain
predefined
directory
layout
and
so,
along
with
that,
it
generates
agua
city
applications
to
deploy
different
services
and
applications
to
multiple
environments,
and
also
it
generates
tecton-based
resources
that
generates
a
simple
pipeline
or
a
ci
for
your
detox
repository.
L
So
one
of
the
main
motivation
behind
the
project
is
to
help
users
who
are
new
to
our
cd
and
who
wants
guidance
on
and
one's
guidance
on,
the
and
on
an
opinionated,
github's
workflow.
So
that's
one
reason
why
we
started
this
project,
so
the
workflow
is
pretty
it's
pretty
straightforward.
So
let's
assume
that
I
have
a
python
app
that
I
want
to
deploy
to
multiple
environments
like
dev
stage
and
fraud.
So
as
a
user,
I
use
cam
and
it
will
generate
a
great
ops
repository
for
me.
L
So,
along
with
github's
repository,
it
generates
cargo
cd
applications
that
will
take
care
of
deploying
everything,
all
the
services
and
everything
to
these
environments
and
and
it
generates
the
tecton
pipe,
which
acts
like
a
ci
and
does
a
basic
check
of
the
of
the
patches
that
will
be
introduced
to
this
githubs
repository.
L
So
this
is
the
simple
basic
overall
workflow
that
can
be
done
using
cam
and
so
so
I'll
be
explaining
more
about
repository
layout
while
showing
the
demo
but
the
so
so
it
follows
this
hierarchical
structure
where
we
have
a
service
at
the
lowest
level.
So
this
would
be
your
micro
services
and
which
you
want
to
deploy
to
these
environments,
and
so
these
services
could
be
grouped
together
into
applications,
and
so
you
can
deploy
each
application
to
the
various
environments.
L
So
so
the
hierarchy
model
is
that
the
environments
will
encapsulate
your
applications
and
your
applications
will
in
turn
encapsulate
your
services,
different
services
so,
and
also
it
realized.
As
I
mentioned,
for
continuous
integration,
it
use
openshift
pipelines
and
it's
openshift
pipelines
is
again.
It
uses
it.
It's
based
on
tecton,
and
so
it
configures
a
simple
pipeline
for
your
github's
repository.
L
L
Open
my
openshift
console
so
openshift.
Those
of
you
don't
know
it's
it's
a
it's
an
enterprise
version
of
kubernetes
and
I've
opened
its
console
over
here
and
also
I've
installed,
the
the
red
hat
openshift
detox
operator
from
operator
hub.
So
the
installation
is
pretty
easy.
I've
installed
it
already
just
to
save
some
time,
so
it's
a
single
click
install
and
on
installation
operator
will
create
a
default
argo
cd
instance
in
the
openshift
github's
namespace.
So
this
is
just
a
default
instance.
L
L
So
so
we
have
the
setup
ready.
We
have
installed
ago
cd
using
the
operator.
So
now
so
I'll
use,
cam
and
quickly
bootstrap
repository,
so
I've
construct
cam.
L
So
it
supports
both
the
flag
mode
as
well
as
the
interactive
mode
for
now
I'll
go
with
the
interactive
board,
and
so
also
it
provides
you
an
option
to
to
select
the
defaults.
So
if
you
don't
want
to.
L
L
So,
while
bootstrapping,
we
could
also
deploy
a
service
to
different
environments,
so
we
don't
have
to
generate
an
empty
repository,
so
I'll
provide
a
service.
It's
just
a
simple
go
application.
L
And
yeah
it
has
created
all
the
resources,
so
the
outcome
of
this
bootstrap
command
is
a
git
ops
repository
that
will
be
pushed
to
your
your
github
or
gitlab,
and
also
it
creates
the
folder
on
your
local
machine
so
that
if
users
want
wants
to
configure
something
manually
and
wants
to
push
it
later,
so
so
these
are
the
two
directory.
So
this
is
this
is
the
folder,
so
important
thing
to
note
here
is
that
it
doesn't
the
bootstrap
or
any
command
in
cam
it?
L
Doesn't
they
don't
directly
apply
anything
to
the
cluster,
so
they
can
talk
to
your
git
repository.
They
can
generate
resources
locally,
but
it's
the
argo
cd
which
which
which
which
finally
applies
everything
to
different
environments,
so
I'll
quickly
explain
different
folders
of
this
repository,
so
we
the
environments
directory.
L
As
I
mentioned
it,
this
is
the
hierarchy
that
I
was
talking
about,
so
environments,
you
will
have
different
environments
and
each
environment
will
have
apps
and
each
application
can
have
different
services
and
everything
is
linked
together
using
customize
and
yeah.
So
this
is
the
environments
folder.
L
So
we
have
the
config
directory
where
we
store
all
the
so
configuration
resources
for
managing
your
detox
repository.
So
we
have
the
arco
cd
applications
for
deploying
our
services
to
our
environments
and
also
so
we
have
the.
L
The
tecton
pipelines,
and
so
the
bootstrap
it
generates
a
minimalistic
pipeline
that
does
a
simple
cube.
Ctl
dry,
run
of
all
the
resources
in
your
githubs
repository
whenever
there
is
a
pull
request
or
push
event,
but
this
is
customizable
depending
on
the
requirements
of
the
user.
They
could
add
any
number
of
steps
in
their
pipeline,
so
yeah.
Finally,
there's
this
manifest
file
known
as
pipelines.tml,
so
this
is
sort
of
like
a
configuration
file
for
your
detox
repository.
It
will
have
all
the
configuration
details
required
to
manage
your
github's
workflow.
L
It's
not
a
custom
resource
yet,
but
it
has
all
the
config
details
so
yeah.
So
this
is
the
repository,
so
we
don't
have
anything
deployed
yet
so
I'll
apply.
L
And
so
the
bootstrap
also
creates
a
one,
more
folder
known
as
secrets
where
it
keeps
track
of
all
the
all
the
the
secrets
that
is
that
are
required,
for
it
could
be
a
web
book
secret
for
triggering
your
technon
pipelines
or
it
could
be
your
image
registry
secrets.
Something
like
that.
So
I'll
apply
those
secrets
as
well.
K
L
Yeah
created
and
if
I
go
to
my
harbour
city
web
ui,
so
here
I
can
see
all
the
different
apps
that
are
being
synced
and
going
to
my
openshift
console.
So
I
have
my
different
environments
over
here.
So
dev,
broad
and
stage.
L
So
so
let's
say
I
want
to
make
a
change
in
my
githubs
repository
say.
I
want
to
increase
the
number
of
replicas
for
this,
this
github's
repository,
so
so
I
can
I'll
have
to
raise
a
full
request
in
my
detox
repository
so
before
doing
that
I'll
have
to
create
a
a
web
hook
so
I'll
do
that
using
cam
web
create
command
so
so
cam
web
command.
It
creates
a
web
hook
in
our
guitars
repository,
and
so
this
is
the
the
route
of
your
techton
event
listener.
L
So
whenever
there
is
a
push
event
or
a
full
request
raised,
it
triggers
this
web
book
and
sends
this
sensor
request
to
this
event,
listener
which
is
running
in
our
cluster.
L
L
So
here
I
can
see
that
my
pipeline
has
been
triggered
so
so
in
tecton,
so
we
have
different
steps
in
our
pipeline
and
each
of
these
steps
will
run
as
a
container
in
in
the
same
cluster
so
the
pipeline.
L
So
so,
if
I'm
an
admin
who
is
reviewing
this
full
request,
I
would
wait
for
the
ci
to
complete
to
succeed,
and
so
here
review
it.
So
it
has
passed
all
the
checks
have
passed
I'll
I'll,
just
watch.
This
request.
L
L
And
so
here's,
my
second
replica
of
the
board
of
the
application
that
I
just
created
so
yeah.
This
is
the
the
bootstrap
command
and
we
generated
a
bootstrap.
We
generated
a
talks
repository,
we
applied
our,
we
deployed
our
apps
to
different
environments
and
we
also
made
a
build
request
and
observe
the
ci
succeed,
but
so
we
also
have
other
commands
in
cam.
L
So
if
you
want
to
add
more
environments
to
our
detox
repository,
so
we
have
this
cam
environment,
add
command
so
I'll,
add
an
environment
known
as
test,
so
it
should
have
added
a
new
environment
test
with
everything,
and
so
I
can
also
add
a
new
service
to
this
in
this
environment.
Test.
L
And
so
this
is
my
newly
added
service,
so
yeah.
So
this
is
these
are
the
different
commands
that
are
currently
implemented
in
cam.
So
there's
also
a
view
for
this
for
these
environments
that
are
created.
So
if
I
go
to
the
environments
page,
my
open
shift
console
so
here
I
see
my
app
that
we
just
deployed
to
three
different
environments,
and
so
all
of
them
are
in
sync,
so
the
last
deployment
was
made
to
broad
that's
the
change
which
is
triggered
and
if
I
go
here.
L
So
here
so
this
page
would
show
all
the
different
environments.
My
app
is
deployed
too
so
so
for
some
reason:
it's
not
showing
the
other
two
environments.
So
maybe
I
missed
something
or
there's
a
bug
so
yeah,
but
normally
you'd
see
all
the
different
environments
that
my
app
is
deployed
to
so
yeah.
L
So
this
is
the
the
environments
page
where
you
can
visualize
all
the
apps
and
environments
so
yeah.
L
A
There
any
questions
yeah,
I
had
a
quick
question.
I
I
just
I
was
curious.
The
pipelines
that
come
generates
are
these
pipelines
for
kind
of
deployment
only
or
the
pipelines
also
build
codes
and
push
images.
L
Yeah,
so
there
are
two
pipelines
that
are
generated,
so
one
of
the
pipeline
that
I
triggered
so
this
is
this
is
for
your
detox
repository
where
it
does
it
dry
turn
off
everything,
and
the
second
pipeline
is
your
ab
ci
pipeline
and
it'll
build
and
push
an
image
to
a
image
register.
It
could
be
an
external
image
registry
or
in
my
case
I
didn't
provide
anything.
So
it
will
push
to
my
internal
openshift
internal
registry.
L
So
so
I
didn't
showcase
this,
because
so
it
will
take
some
time
to
build
and
push
an
image
so
just
to
save
time
as
I've
just
showcased
on
the
the
pipeline
for
github's
repository,
so
basically
end
user
kind
of
gets
ci
as
well.
A
C
M
M
B
M
Okay,
could
you
please
share
my
screen,
see
my
screen
right,
oh
yeah.
Now
we
can
see.
Okay!
Thank
you,
okay,
so
so
this
is
the
first
time
for
us
here,
I'm
gaijin,
I'm
I'm
with
here
juji.
We
are
from
ibm
research.
M
So
the
purpose
of
this
talk
is
to
to
introduce
this
argos
in
english
project
to
the
community
and
to
see
there's
an
interest
so
that
we
can
possibly
contribute
this
project
to
the
the
community
so
I'll,
just
quickly
run
through
this
chart
in
one
few
slides,
though,
the
problem
that
we
consider
in
this
setup
in
this
product
context
is
that
when
you,
let's
say
when
you
have
when
you
have
to
deploy
application
in
the
auto
cd
using
the
key
docs
approach,
so
let's
have
imagine
that
you
are
that,
in
the
applications
are
deployed
in
the
certain
target
clusters,
where
those
administrators
will
be
interested
in
seeing
whether
those
materials
the
resources
were
generated
based
by
argo
cd
after
checking
their
source
material
signature,
for
example.
M
Currently,
argo
cd
have
this
commit
me,
commit
signature
based
verification
before
the
singing
process,
but
from
the
administrator
side.
If
they
want
to
make
sure
that
okay,
this
this
is
already
done
when
these
resources
were
created
where
before
they
deployed
to
the
cluster.
In
addition
to
that
also
administrator
would
be
interested
in
seeing
okay.
These
these
particular
resources
coming
from
trusted
resources
of
med,
github
repository
and
so
on.
So
if
the
particular
commit
who
committed
and
what
commit
was
this
deployment
update
and
so
on?
M
But,
however,
so
if,
however,
without
such
direct
access
to
those,
you
know
repository
or
the
cd,
if
you
can
enable
this,
like
a
very
verifiability
of
these
resources
from
the
signature
perspective,
as
well
as
as
well
as
by
providing
there's
some
kind
of
a
transparency
about
where
these
resources
came
from
for
this
target
cluster
administrator
that
it
would
be,
I
would
it
would
be
additional
benefit
for
them
from
the
administrative
perspective.
So
here's
just
an
example
that
shows
that
okay.
M
These
are
the
two
interesting
points
so
to
address
this,
we
we
came
up
with
a
tool
called
interlaced
so
which
is
basically
where
I
talked
about
the
supply
chain,
integrity
for
our
city.
But
I
will
explain
that
what
it
means
exactly
so
interlace
is
basically
an
application
controller
which
produces
the
signature
on
the
manifest
generated
by
our
city.
So
basically
it
lays
checks,
the
source
material.
M
If
this
source
material
has
signature,
if
their
signatures
are
valid
and
then
based
on
that
assumption,
intellects
will
get
the
manifest
that
is
built
by
argo
city
during
the
same
process
and
it's
detect
that
sync
process
automatically
and
it
retrieves
the
latest
manifest
and
create
the
signature
patch
for
that
manifest.
So
when
this
manifest
patch
manifest
is
deployed
to
the
cluster,
the
signature
is
available
for
any
kind
of
verification.
M
For
example,
you
can
imagine
that
if
their
signature
is
available,
we
could
imagine
like
using
some
technological
like
admission
controller,
so
we
can
enforce
okay,
only
the
resources
which
nature
could
be
deployed
in
this
cluster
and
also
with
a
what
are
the
resources
that
should
be
deployed
by
this
particular
process
in
this
from
this
application,
whether
these
are
with
where
they
came
from,
and
also
continuously
have
this
all
auditing
mechanism
to
observe
whether,
if
there's
any
violation
to
this
cluster
for
this
application
resources.
M
So
so,
in
addition
to
that,
so
there
is
also
this
antilles
could
generate
some
kind
of
evidence
which
shows
the
mapping
between
the
when
we
are
the
source
materials
and
what
source
materials
were
used,
how
those
source
materials
were
transformed,
for
example,
with
a
customized
build
or
a
custom,
plug-in
or
helm
based
transformation
happen.
So
then
it's
kind
of
an
actual
log
that
is
available
for
administrator
to
see
whether
this
is
how
it
is
done.
So
so
having
said
that,
so
this
is
the
kind
of
architecture
of
the
eclipse
process.
M
M
We
can
also
capture
the
source
materials
from
that
we
could
obviously
less
can
check
the
source
material
signature
where
the
signature
has
been
very
if
they
need
to
verify
the
signature
of
the
source,
material
and
based
on
the
it
is
successful
and
it
will
generate
the
patch
for
the
manifest.
So,
in
addition
to
that,
we
this
manifest
build
or
process.
It
will
capture
the
medical
build
process,
whether
it
is
customized
tool
used
and
what
are
the
values
parameters
used?
M
All
this
information
can
be
captured
and
free
does
a
very
verifiable
evidence
store.
So
we
just,
I
think
you
some
of
you
may
know
that
there's
a
prominent
important
tool,
six
stories
prominent
in
this
area
to
store
this
kind
of
provenance
information
where
you
can
verify
this
information
at
any
time
regarding
the
the
logs
that
is
generated
here.
So
that's
how
this
tool
works.
So
the
current
status
is
that
we
have
the
open
source
as
a
open
source.
M
It
has
in
the
under
the
ibm
repository,
but
we
would
like
to
see
there's
interest
if
there's
any
interest
that
we
can
contribute
this
project
to
the
arbor
city
community.
So
I
think
it's
given
the
time
interval,
so
I
could
do
the
long
demo
for
the
next
semi
next
talk.
But
if
you
I
would
appreciate
any
any
comment
or
feedback
on
this.
H
M
Okay,
so
yeah
so
sure
I
can
show
you
the
quick
demo
long
camera
as
well.
Yeah.
A
I
think
I
have
the
same
feedback
and
I
think
one
thing
is.
I
I
feel
like
what
you're
trying
to
solve
is
a
real
gap,
at
least
when
I
was
using
cargo
cd.
It's
kind
of
this
a
way
to
see
what
was
deployed
using
cargo
cd
right
now,
it's
kind
of
missing
right
now,
it's
not
so
easy,
and
but
I'm
I
also
feel
like
the
long
demo,
would
help
me
personally
to
understand
you
know
yes,
better.
M
Yes,
yes,
definitely
we
want
to.
We
will
show
you
how
what
information,
for
example,
what
log
evidence
store
information
carries
and
how
the
signature
is,
can
be
enforced
in
the
cluster
side,
so
those
those
are
in
our
already.
We
have
already
demonstrated
you
know
in
this
case,
so
we
would
like
to
show
you
the
benefit
of
using
such
tool.
In
this
context,.
A
And
I
have
a
feeling
that
that
project
definitely
will
be
very
welcome
in
our
google
apps,
because
the
most
likely
there
are
a
lot
of
users
who
would
benefit
from
it
too
yeah.
So
I
guess
yeah.
If
you,
if
you
don't
mind,
I
will
just
keep
that.
You
know
your
demo
on
that
and
we
can
talk
about
it
in
the
next
meeting.
Again,
basically
continue
the
conversation.
A
A
Thank
you,
and
we
already
really.
You
know
we're
already
seven
minutes
past
the
end
of
the
meeting,
and
I
guess
I
don't
want
to
call
people
forever.
Thanks
for
for
the
demo-
and
I
guess
we'll
see
you
again,
the
next
meeting.