►
From YouTube: CNCF SIG Runtime 2020-01-16
Description
CNCF SIG Runtime 2020-01-16
A
A
B
B
So
what
happens
is
that
the
cig
hasn't
been
officially
created
so
would
they're.
Starting
to
you
know,
this
is
like
our
first
meeting
really
so
we
had
another
meeting
like
a
lot
of
months
ago,
but
not
many
people
were
there
so
and
then
the
vote
went
out
to
the
TOC
I
think
last
week
to
create
this
a
clam
and
it's
looking
like
it's
gonna,
be
you
know
created,
but
but
it
hasn't
been
officially
created
right,
so
yeah.
So
one
of
the
agenda
items
that
I
have
there
is
to
have
data
readme
file.
D
Not
to
make
things
more
complicated,
but
you
guys
were
tasked
to
do
the
hardboard
graduation
review.
A
cig,
runtime
Quinton
was
the
one
that
basically
kind
of
spearheaded
that.
So
that's
why
I'm
here,
if
we
can
spend
a
few
minutes
to
discuss
that
today,
that'd
be
great,
we
don't
know.
Review
needs
to
be
done
today,
but
I
just
want
to
talk
about
it.
All.
D
B
So
hopefully
it's
whenever
he
pops
up
in
him,
we
should
be
able
to.
You
know
sync
up
with
him
so
yeah,
so
so
the
first
half
on
the
agenda.
It's
basically
calls
for
participation,
so
we're
looking
for
another
code
error
and
we're
also
looking
for
techniques.
So
so
anybody
who
wants
to
do
this
is
interested
in
run.
I'm,
there's
an
example
of
projects
in
their
charter.
B
E
I'm
interested
in
possibly
being
a
co-chair
I
want
to
make
sure
that
I
really
understand
the
duties
involved
and
everything,
but
I
think
what
I
would
bring
to.
This
is
knowledge
of
the
AI
runtimes.
That's
what
I
work
at
Red,
Hat,
so
I
think
I
just
need
to
know
how
much
of
a
time
commitment
you
expect
it
to
be.
B
Yeah
I
think
that's
not
really
described
in
the
document,
but
I
feel
like.
The
reason
we
have
co-chairs
is
because
not
everyone
can,
you
know,
say,
run
meetings
or
you
know,
do
different
things
that
need
to
be
done
so
I
think
it's
not
something
that
that
you
have
to
spend
tons
of
time
on
it.
So
maybe
when
Quentin
comes
back,
maybe
he
can
give
it
a
little
bit
more
details
about
that.
B
E
B
B
Yeah
something
like
that
in
in
and
it
in
you
yeah
it's
all
kind
of
up
to
you
too
I
mean
if
you
want
to
participate
more
certain
week
or
you
know
you
have
less
time
another
week,
so
it
will
be
up
to
I.
Think
for
us
and
coordinate
so
and
then
yeah.
We
would
love
to
have
you
write
so
I
mean
I,
think
I've.
Also
the
AI
expertise
will
be
great.
So
some
of
the
those
things
maybe
there's
gonna
be
more
projects
coming
in
in
yeah
all.
B
C
B
B
B
Cool
yeah
yeah,
so
so
another
so
I've
seen
some
of
the
other
six.
For
example,
the
six
security
they've
been
around
for
maybe
six
or
eight
months,
so
they've
actually
have
a
pretty
well-established
process.
So
one
of
the
things
that
that
we
may
be
going
forward
would
like
to
have
is
somebody
who
you
know
writes
down
what
goes
on
in
these
meetings
and
sickly
do
describes,
and
so
that
would,
and
it
will
hopefully
set
up
the
process
as
we
go
for
it.
B
So
the
other
item-
buteo
seasick
process,
so
lists
rice-
is
the
chair
of
the
TOC
tree
and
some
of
the
other
TOC
members
came
up
with
process
of
interaction
between
the
TOC
and
the
sick.
So,
like
a
flow
diagram
or
it's
it's
still
in
the
works,
it's
not
fully
defined
yet
so,
if
you
have
any
input
feel
free
to
chime
in
so
the
idea
is
just
you
know.
B
The
six
are
meant
to
be
there
to
support
this,
the
TOC
and
and
provide
some
guidance
to
them
and
in
a
lot
of
the
members,
then
the
TOC
don't
have
all
the
expertise,
but
nobody
has
expertise
on
every
area.
So
the
idea
is
just
kind
of
spread
the
load
more
and
and
have
the
six
do.
Maybe
some
of
some
of
the
work
that
that's
what
you'll
see
doesn't
have
time
to
do
or
or
doesn't
have
expertise,
and
so
it
can
help
out
in
that
area.
C
E
B
Yeah,
my
cell
phone,
not
a
completely,
you
know
knowledgeable
about
every
step
of
the
way.
But
generally
is
you
know,
you're
going
to
Samba
oxid
and
then
PR
gets
open
and
it
gets
approved
and
it
goes
in
the
sandbox.
And
then
then,
when
the
project
has
to
gather
or
as
the
other
I
think
the
TOC
sponsors,
then
then
PR
gets
opened
and
then
into
like,
so
that
the
project
goes
into
incubation
and
then
there's
some
due
diligence
and
I
think
this
is
kind
of
like
what
the
six
come
in.
B
Wouldn't
when
it's
incubation
in
incubation
for
some
time,
then
a
PR
also
it's
opened
and
for
the
project
to
graduate
in
and
I
think
there
are
some
criteria
defining
on
some
of
the
CN
CF
pages
or
readme
files
and
github
repository
I
mean
I,
think
the
criteria
there
is
like
you
something
like
use
by
say.
You
know
over
a
hundred
customers
or
something
like
that,
or
you
know
a
large
number
of
people
who
is
running
in
production
for
more
than
say
two
years.
B
E
B
D
As
part
of
that,
there
is
some
very
light
to
diligence
that
happens
by
the
TOC
for
some
box
later
on
as
a
project
advances
stages,
whether
its
incubation
or
graduation,
that's
where
the
six
come
in
and
they
are
responsible
for
shepherding
the
much
larger
due
diligence
and
needs
to
happen
to
make
this
work.
If
you
actually
look
at
the
harbor
graduation
review,
that's
one
of
the
items
in
legend
that
I
have
you
consider
diligence
talk
is
about
26,
30
pages.
This
is
what
we
created
this
horrible
team
to
basically
go
through
the
review.
B
So
the
other
item
that
I
have
no
agenda
is
this
new
CFC,
a
project
that
or
this
project,
that
the
open
PR
for
donation
from
Microsoft
are
from
Red
Hat.
It's
called
Kega,
it's
kubernetes,
autoscaler,
so
I
I
think
Amy
is
not
around
so
I,
don't
if
some
of
the
other
six
I've
actually
so
I'll
think
back
with
us
executing
and
see
if
they
have
any
format.
B
I
think
Liz
said
on
the
chat
Deb.
If
we
don't
have
a
specific
format,
then
we
we
can
actually
interact
with
with
our
six
liaison
or
our
TOC
liaison
I'm.
Sorry,
it's
so
to
find
out
whether
we
can
recommend
it
or
not,
but
I'm
gonna
I'm
no
kind
of
wait
until
Quentin's
back,
and
so
we
can
go
forward
on
this
project.
D
D
So
essentially
there
so
we
have
a
PR
for
the
harbor
graduation
proposal
and
as
part
of
the
PR,
the
responsibility
for
some
of
the
shepherding
of
other
six
that
may
have
to
review.
It
lies
on
securing
time.
That's
something
that
Quinton
kind
of
spearheaded
here.
If
you
see
in
the
comments
later
on,
so
there
storage
and
security
seek.
D
That
also
need
to
take
a
look,
but
since
Eve
had
asked
us
to
go
through
sick
run
time
first,
which
is
why
we're
here
now
we
are
willing
to
work
with
you
guys
to
to
spend
as
much
time
as
necessary
to
answer
your
questions,
but
in
the
first
starting
point,
is
these
two
documents?
The
first
one?
Is
this
technical
due
diligence
document
for
graduating
harbor?
This
is
something
that
I
created
as
a
maintainer
of
harbor.
D
It
walks
you
through
a
gamut
of
logistical
governance,
security
architecture,
items
on
harbor,
it's
30
pages
would
try
to
not
miss
anything
so
that
when
you
guys
go
through
this,
there's
not
much
that
you
have
to
ask
more
of
us
to
produce
as
a
team.
Obviously,
a
lot
of
these
have
links
back
to
the
github
page.
The
harbor
has
it
has
customer
testimonials,
so
I
feel,
like
you
know,
you
have
a
complete
view
of
harbour
in
addition
to
that.
D
Quintin
created
these
due
diligence
by
the
CNC
f6,
which
is
where
you
guys
as
a
cig,
get
to
add
some
feedback
in
terms
of
uncertain
some
questions
for
hard
work.
You
like
I,
don't
feel
like
you
need
to
answer
each
question
one
by
one,
because
we
I
tried
to
follow
the
same
format
in
my
due
diligence.
You
can
probably
just
say
meat
or
requirements
or
something
like
that,
but
if
you
want
to
be
more
explicit
and
spend
more
time
on,
this,
obviously
feel
free.
So
so
that's
that's
kind
of
it.
D
B
D
I
have
and
I
don't
think
you
need
to
go
through
each
one
of
them.
Super
like
I
mean
like
I,
don't
know
if
you
want
to
sit
down
and
answer
these
questions.
If
you
look
at
the
like,
for
example,
you
successful
in
production,
you
can
come
back
to
my
document
and
basically
there's
a
horrible
users
adoption.
You
can
go
here
and
look
at
people
that
have
used
it,
so
each
of
them
I
tried
to
make
it
easy
for
you
guys
to
find
things.
B
D
The
the
biggest
thing
that
we
are
looking
for
from
from
a
harbor
team
is
to
have
some
form
of
understanding
when
you
guys
might
start
looking
into
this,
because
we've
been
waiting
for
a
couple
of
months
right
now
in
this
graduation
stage.
So
just
let
me
know
we'll
work
with
you
guys
and
identify
the
right.
The
right
thing,
yeah.
B
D
Yeah
and
and
by
the
way
I
don't
want
to
be
I
would
also
like
to
participate
in
Sea,
Grant
I'm.
You
know
I'm
already
one
of
the
leads
in
kubernetes
community,
so
I
would
love
to
participate
more,
but
it
I
will
feel
there
would
be
a
conflict
of
interest
participate
before
her
board
review
gets
done
so
yeah
yeah.
B
D
B
D
That
isn't
really
it's
more
around.
You
know,
as
a
project
reached
maturity
to
facilitate
the
need
to
actually
give
it
that
elevated
status
within
since
EF
we
have,
we
have
so
many
users,
I,
wouldn't
know
if,
like
every
every
few
days
or
every
week,
we
find
out
about
a
new
user,
that's
using
harb
or
a
skill
that
you
never
even
fathomed.
Like
you
know,
we
had
the
other
day
like
right
before
the
Christmas
holiday.
D
That's
a
company,
that's
using
harbor
and
they
have
terabytes
of
storage
and
harbor
with
thousands
of
images
and
tags
we
didn't
even
know
about
these.
Guys
is
less
so
many
of
them.
So
people
are
coming
out
of
the
Woodworks
and
telling
us
that
you
know
hey
be
using
harbor.
We
love
it
through
putting
in
production
so
kind
of
killing
that
to
the
next
stage
in
CN
CF.
Is
there
a
natural
progression.
B
D
B
So,
and
so
we
don't
have
a
there's,
a
meeting
on
Tuesday
I
won't
be
able
to
make
that
meeting.
There's
a
TOC
meaning
so
so
some
of
the
people
interested
in
the
signal
also
can
attend
that
meeting.
So
I
asked
I
started
attending
those
meetings
as
well
uh-oh
and
yeah
Michael.
You
can
also
bring
it
up
on
the
on
that
meeting
as
well.
Well,.
D
D
C
C
C
G
Yes,
I'm
just
listening
in
I'm
a
container
team,
maintainer,
okay,
yeah
I
mean
well
we'll
see,
I
mean
I
I'm
a
talker,
then
on
container
D
for
a
while.
But
my
thing
is
usually
limited
time,
but
I
can
try
to
participate
when
I
can
but
I,
don't
I,
don't
know
about
time
commitments
right
now,
we'll
see
Oh.