►
From YouTube: CNCF TOC Meeting 2022-06-21
Description
CNCF TOC Meeting 2022-06-21
A
B
B
B
D
D
B
B
B
B
They've
done
some
good
work,
they
have
integrated
with
cuboid
psyllium
submariner,
and
I
believe
this
is
metal
lb
to
provide
a
whole
network
solution,
improve
user
experience,
document
more
things
host
more
events
so
looks
like
they
are
trying
to
do
all
the
right
set
of
things
and
under
a
few
other
things
that
were
there
in
private
notes,
were
around
hey.
What
slack
are
you
using
and
is
it
it
would?
B
B
B
And
the
other
important
feedback
was:
why
do
you
need
cube
obn
when
there
are
other
things?
What
is
the
specific
use
cases?
I
think
the
documentation
needs
to
be
clearer
there.
So
some
of
these
notes,
we
will
end
up
typing
it
out
in
the
pull
request
as
well.
But
in
case
you
are,
you
all
are
watching
cube
obn,
that's
what
we
are
expecting
you
to
do
so,
just
to
be
clear.
There
is
nobody
from
qo
cube
oen
here
now.
Is
there.
E
E
E
B
F
If
not
that's
fine,
okay,
security
fence
is
an
api
first
devops
oriented
web
defense,
http,
filter
adapter
for
envoy
and
nginx.
It
provides
multiple
security
technologies
such
as
web
application,
firewalls
application
layers,
distributed
denial
of
service
protection,
bot
management
and
a
lot
of
other
things,
along
with
real-time
traffic
monitoring
and
transparency.
F
F
The
only
recommendations
that
I
can
really
find
with
the
project,
because,
overall
it's
it's
pretty
solid
and
their
documentation
is
great-
is
more
around
driving
that
contributor
growth
in
particular
looking
through
their
documentation.
The
readme
is
a
little
bit
light
on
content
and
it's
more.
It's
focused
more
on
the
use
of
the
project
rather
than
around
the
community
management.
F
If
it's
once
a
month,
once
every
two
months
publish
publishing
that
making
it
more
accessible
to
your
users,
leveraging
the
slack
channels
a
little
bit
more
so
right,
now,
they've
primarily
been
used
as
a
support
communication
mechanism,
so
certainly
driving
more
folks
to
attend
those
meetings,
develop
more
contributions
that
way
and
bringing
a
lot
of
that
content
back
forward.
Because
it's
it's
deep
in
the
in
the
github.
I
think
it's
a
couple
of
clicks
through
on
the
wiki
to
be
able
to
find
that
they
actually
had
them.
D
G
G
So
the
interest
is
very
high,
obviously
behind
all
these
projects,
but
they
realized
that
container
engagement
has
been
a
problem,
so
there
was
one
at
it,
but
having
a
look
at
the
list
of
maintainers,
which
is
quite
extensive,
it
seems
that
most
are
inactive.
So
this
is
something
to
look
at
then,
aside
from
adoption,
the
the
question
about
the
move
to
incubation
the
project
stated
that
they're
waiting
for
the
v3
release
before
applying
for
incubation.
G
So
here
I
had
a
couple
of
comments
which
was
this.
This
seems
to
be
the
main
core
of
the
work
ongoing,
but
it
is
not
reflected
in
the
roadmap.
Actually,
the
roadmap,
if
you
dig
into
the
project
page,
is
not
very
clear,
so
I
think
I
think
that
that's
something
that
could
help
a
bit
is
to
to
review
the
roadmap
which
hasn't
been
updated
for
a
while
and
especially
describe
the
path
to
incubation.
G
G
B
Sorry
so
the
usual
answer
we
have
is,
you
know,
look
at
the
cncf
service
desk
and
see
if
things
are
available
there
and
if
it's
not
there,
then
we
can
figure
out
how
to
get
them
added.
There
is
a
bunch
of
things
that
are
available
here
and
yeah
so
that
that's
basically
what
we
would
tell
them
so
come
ask
us
on
the
toc
channel.
If
you
can't
figure
out
how
to
get
help
with
the
things
that
you
need
to
do
essentially
any
other
observations
from
the
toc
members.
H
I'm
here
I'm
just
walking
down
the
street
with
my
kids
from
school,
so
let
me
know
if
it's
too
noisy
or
anything
like
that
I'll
make
you
talk
for
me.
So
I
don't
know
if
anybody
from
smi
is
on
the
call.
I
wanted
to
give
them
a
little
bit
of
time
to
talk
and
then
my
kind
of
big
takeaways
are
on
this
slide,
but
I'll
pause
for
a
second.
H
I
don't
think
anybody
is
here,
so
please
go
ahead,
okay
and
I'll
I'll
just
say
some
stuff,
and
then
they
can
correct
me
on
slack
or
somewhere
else.
Overall,
the
review
looked
good.
There
are
a
lot
of
like
interesting
and
like
big
and
small
names
in
in
the
review
and
like
around
their
pages
of
companies
and
projects
that
are
using
this
that
are
using
smi.
The
hard
thing
with
smi
is
that
it's
a
spec
and
most
of
our
like
rules
and
guidelines
are
written
around
projects
that
are
like.
H
I
don't
know
what
to
call
like
actually
built
executables
as
opposed
to
specs.
So
it
looks
pretty
good,
but
they
had
a
few
questions
that
I
kind
of
had
the
same
questions
of
like
what
does
it
mean
to
apply
for
incubation
when
you
are
a
spec,
so
I
think
we
as
a
toc,
and
obviously
anybody
from
the
kind
of
community
around
should
have
that
conversation
of
what
it
means
to
move
through
stages
of
spec.
B
H
Or
just
put
it
in
the
pr
because
they
wrote
in
their
annual
review.
I
forgot
what
it
said.
I
don't
have
it
in
front
of
me
now,
but
I
think
they
wrote
something
on
the
lines
of
like
we
think
we're
pretty
much
ready
for
incubation,
but
we're
not
quite
sure
what
that
means,
because
we're
a
spec.
So
it
would
probably
be
good
for
us
to
kind
of
get
that
conversation
moving,
even
if
it's
extremely
slow
moving.
B
I
Yes,
so
disclaimer,
I
I'm
on
the
fifth
floor,
but
I
have
builders
outside
so
it
can
get
very
noisy
and
sometimes
swearing.
So
if
that
happens,
I
apologize
in
advance.
It's
no.
It's
not
me
back
to
I'm
not
sure
if
there
is
anyone
from
kgb
here,
but
this
is
a
project
that
pretty
much
provides
a
jslv,
a
global
global
service
load.
Balancing
multiple
solutions
are
available,
however,
they're
vendor
bound.
There
is
nothing
open
source.
Well,
ksgb
is
actually
serving
the
problem,
so
I
think
it's
still
a
very
relevant
project.
I
Now,
looking
throughout
their
contributors,
actual
maintainers,
they
have
six
maintainers,
five
of
which
are
from
the
same
organization,
so
an
advice
is
definitely
kind
of
to
improve
that
to
get
a
bit
more
diversity
and
a
bit
more
contributions
from
different
organizations
and
yeah
kind
of
different
industries
as
well.
Another
thing
is:
this:
is
an
apsa
donated
project,
so
they
have
a
production
use
case
for
this
for
kgb.
I
So
it's
great
for
that
organization.
They
have
other
doctors,
but
there's
no
use
cases.
It's
gonna
help
to
actually
showcase
a
bit.
More
of
that.
So
definitely
celebrate
your
successes
and
actually
get
those
stories
out
looking
into
their
latest
achievements.
It's
looking
quite
good.
They
try
to
integrate
with
different
hubs
such
as
operator
hub
and
artifactory
hub,
which
is
great
for
their
visibility
and
kind
of
increase
their
transparency,
so
I
think
they're
doing
very
good
there.
However,
I
haven't
found
the
roadmap.
I
looked
through
the
project,
github
organization.
I
I
couldn't
find
a
roadmap,
so
please
correct
me
if
or
like
link
it
to
the
pr.
If
there
is
one
it's
going
to
be
great
to
see
one
of
those
and
in
terms
of
the
commits
this
project
was
developed
on
a
spike
basis,
so
it
had
a
lot
of
commits
at
in
one
go.
They
still
have
some
commits
npr's
available
now,
however,
it's
definitely
declined
since
that
general
spike
they
had
in
in
at
the
beginning,
so
again
kind
of
enforces
the
same
thing.
I
They
need
more
contributions
and
more
people
to
in
terms
of
where
they're
moving
they're
looking
into
integrating
with
other
clusters.
Other
providers-
sorry
so
they
currently
they
have
integrations
with
aws
but
they're.
Looking
for
other
cloud
providers,
which
I
think
is
going
to
help
again
to
increase
the
transparency,
I
still
think
it's
a
very
good
project
considering
that
it's
an
open
source
gslv,
but
they
just
need
that
more
kind
of
visibility,
then
maybe
collaborating
and
finding
the
right
peers
to
integrate
with
our
providers
is
going
to
help
that.
I
So
I
think
that's
everything
I
wanted
to
say
around
this
one
yeah
overall,
I
haven't
seen
anything
towards
incubation
movement,
but
if
they
would
like
to
move
to,
the
next
stage
definitely
recommend
increase
your
like
diversify
your
contributor
base
actually
celebrate
your
success.
Do
you
have
people
that
adopted
your
tool,
kind
of
write,
something
about
it
and
put
it
down
on
the
page
as
well,
and
I
think
yeah
definitely
needs
more
confidence.
E
Yeah,
so
this
project
in
general
is
in
good
shape
and
we
we
observed,
there
are
a
lot
of
contributors
and
end
users
engaged
in
the
ecosystem
and,
overall,
this
project
positioned
itself
as
a
application
delivery
control
plan.
It
can
actually
work
with
existing
ci
cd
and
give
up
github
system
as
long
as
you
need
to
deploy
applications
across
multiple
environments
like
staging
production
or
multiple
cloud.
So
basically,
it's
more
like
a
application
delivery
system
that
focus
on
multiple
clusters
and
multiple
environments.
E
This
is
a
unique
value,
and
the
highlight
is
this:
project
indeed
has
serious
design
on
minimizing
user
privilege.
You
know
when
you
try
to
manage
multiple
clusters.
It
has
a
five
grand
user,
impersonation
and
ipac
system
to
make
sure
that
that
those
clusters
cannot
be
abused
and
the
community
growth
is
also
solid
and
it
it's
basically
have
doubled
its
contributors
to,
I
think
150,
also
after
the
standard
box
and
the
contribution
company
is
also
growing
very
fast.
E
Well,
I
think
this
project
still
needs
some
improvements
in
its
documentation.
For
example,
although
his
blog
says
it
can
work
with
argo.
Cd
is
jenkins
with
a
lot
of
virus
systems,
but
they
barely
provide
documentation
for
that,
and
those
blogs
are
needed
to
become
outstanding,
so
I
will
say
that
they
added
these
all
of
these
integrations
and
formal
documentation
and
samples
and
part
of
their
website,
instead
of
just
putting
them
inside
the
blog.
So
overall,
I
think
this
project
in
good
shape.
They
are
asking
for
incubation
planning
for
that.
B
E
Yeah,
let's
just
mention
they
do-
have
a
serious
design
in
the
security
part,
because
they
this
project
actually
will
manage
multiple
clusters
and
deliver
applications.
It's
easy
for
them
to
ignore.
You
know
the
user
privileges.
I
think
the
highlight
is
that
they
do.
They
have
a
very
vibrant
user
impersonation
system
in
case
the
the
privilege
becomes
abused.
So
I
I
do
think
they're
securely
designed
in
sonic
and
speaking
of
governance.
D
One
note:
if
you
go
and
wander
through
the
toc
kind
of
like
overall
space,
you
will
notice
that
cube.
Vela
is
still
in
onboarding.
This
is
because
the
trademark
agreement
is
still
running
out
there.
However,
legal
counselors
advise
me
that
could
take
years,
so
don't
don't
have
that
be
a
hold
up
for
incubation
for
them.
That
was
all.
B
A
Yeah,
let's
talk
about
brigade,
so
brigade
is
basically
event-based
scripting
built
on
top
of
kubernetes
and
the
project
isn't
in
great
shape.
They
note
that
themselves.
Their
adoption
for
their
v2
version
has
their
api
servers
only
had
you
know,
2700
polls
from
docker
hub
and
outside
of
that
they
really
haven't
seen
adoption
from
people
picking
it
up.
In
fact,
if
you
go
and
expand
in
the
adoption
side
right
now,
there's
only
four
maintainers,
and
only
one
of
them
actively
contributes
to
it.
A
Two
of
them
are
doing
reviews
and
two
of
them
are
no
longer
actively
involved
at
all
and
so
they're.
Just
there
aren't
people
contributing
to
it
very
much.
They
don't
really
have
users
and
they're
aware
of
this
problem.
In
fact,
the
one
maintainer
who's
been
actively
involved
is
you
know,
going
to
be
even
stepping
back
from
that
and
so
they've
been
considering.
In
fact,
the
maintainers
themselves
got
together
and
said:
hey,
given
that
it's
not
getting
uptake.
B
J
A
Yeah-
and
I
will
say,
the
person
who's
interested
in
taking
it
over
needs
to
to
rally
people
around
it,
and
they
haven't
been
involved
enough.
That,
by
any
governance,
means
that
they
were
ready
to
just
hand
off
the
keys.
They
wanted
our
input
before
they
handed
it
off
so
to
speak,
because
they
don't
know
the
people
well
enough
to
make
that
judgment
call
to
hand
off
on
their
own.
So
it's
that
kind
of
disconnected
relationship
with
somebody
taking
it
over.
A
B
B
Our
you
know
thought
here
is:
if
somebody
wants
to
step
up
if
they
could
be
brought
on
board
and
given
some
guidance
so
for
a
period
of
time,
and
if
that
doesn't
still
work
out,
then
we
archive
it.
So
should
we
say
okay
say
give
them
time
till
until
the
next
annual
release
and
at
that
time,
if
things
haven't
moved
in
a
good
direction,
then
we
archive
it.
I'm.
D
Simply
because,
like
if
oh
just
like,
if
it's
not
going
to
work
out
like
that,
let
us
make
that
call
early
rather
than
giving
another
annual
review
cycle
yeah
and
then
life
support
and
torture,
and
that's
not
no.
No,
it's
fine
to
be
able
to
say
this
was
a
great
idea.
It
is
now
archived
that
is
great.
D
B
B
B
Okay,
milestones
are
out
of
date;
it
would
be
good
to
bring
it
back.
How
cncf
can
help
okay
paid
docker
hub
account?
Yes,
we
can
do
that
and
there
is
already
something
where
dockerhub
you
know.
You
can
talk
to
dockerhub
and
say
that
this
is
a
cncr
project
and
they'll
they'll
remove
the
rate
limits
on
on
the
project.
So,
yes,
if
you
need
more
people,
then
you
need
to
move.
D
B
Okay,
so
yes,
we
agree
that
it
is
not
ready
for
incubation.
Yet,
yes,
perfect,
please
do
all
the
things
that
you
can
do
to
increase
the
footprint
of
the
number
of
maintainers
and
you
know,
increase
the
momentum.
I
think
there
is,
you
know
a
bunch
of
things
happening.
People
want
to
use
it,
so
go
for
it
and
ask
us
on
toc
if
you
need
anything
more
richie,
any
other
thoughts
while
going
through
this.
L
J
Not
really,
okay,
I
meant
oss
so
schooner
I
looked
through
it.
It
used
to
be
called
k8
dash,
and
I
think
we
also
need
to
update
that
on
our
side,
so
the
dev
metrics
show
up
correctly
but
they're,
going
through
a
transformation
of
rebranding,
even
the
repos
and
everything
else
right
now.
They
have
seven
maintainers
that
I
counted
but
they're
all
from.
J
Within
there
they
may
have
it.
It
might
be
called
something
else,
but
when
I
went
through
the
project
and
get
I
couldn't
find
that
one
of
their
requests
to
the
toc
was
recruiting
more
contributors
and
I
don't
really
see
a
process
by
which
they
can
get
engaged
either
through
slack
or
have
meetups.
I
just
didn't
see
kind
of
any
sort
of
community
opportunities
there,
so
you
know
be
happy
to
help
advise
in
ways
they
could
grow
it
through
that.
But
that
was
one
thing
that
I
saw
that
they
needed
help
on.
J
They
also
needed
help
for
external
demos.
I
don't
know
that
we
do
that
amy
I
haven't
had
that
request
before
good.
We
can
see
okay,
all
right
and
then
again
they
asked
for
marketing.
Again
we
don't
do
that
for
sandbox.
So
I
will,
you
know,
add
that
into
my
comments
to
the
pr
just
to
indicate
that's
at
sandbox
level,
that's
not
really
appropriate
and
then
they
also
wanted
help
visibility
of
who
might
be
using
the
project.
J
B
C
B
I
J
J
They
have
a
roadmap
and
they
have,
I
think,
10
features
planned
for
their
next
release.
Right
now,
they're
not
looking
to
move
to
incubation
they're
they're
fine
staying
with
sandbox,
so
I
think
we
just
revisit
them
later
on.
In
the
years
we
look
to
incubation.
It
looks
like
a
project
that
I
don't
today
have
a
lot
of
concerns
around.
J
J
B
J
B
D
They're
they're,
I'm
kind
of
working
on
being
able
to
like
make
sure
that,
like
the
press
releases
and
all
of
that,
so
nothing
nothing
really
currently
outstanding.
As
far
as
the
voting
groups,
if
we've
still
got
ricardo
on
the
line,
I
know
that
there
was
a
availability
for
cloud
custodian
to
move
into
public
comment.
Where
are
we
on
that?.
G
H
A
A
We
haven't
done
it
yet
and
then
on
the
artifact
hub
side,
they
have
started
out
picking
up
trying
to
document
in
the
traditional
sense
who
the
adopters
are
to
see
what
that
is
because
there's
the
criteria
for
three
adopters,
and
so
we
we
need
to
tackle
that
from
both
directions.
So
I
think
that's
still
sitting
there
waiting
for
us
to
take
some
action.
H
Okay,
that
makes
sense.
I
think
it
might
be
good
if
we,
I
don't
know,
didn't
delay
artifact
hub
on
the
tocs
like
an
inability
to
define
this
and
then
just
figure
out
with
artifact
hub
like
who
the
who
the
doctors
are
and
then
maybe
within
the
tlc
just
decide.
If
that
I
don't
know,
qualifies
or
not
or
feed
that
into
our
making
the
definition.
B
H
H
Ahead,
okay,
cool
so
istio's
moving
along.
I
think
the
dd
dock
is
pretty
good
and
craig,
and
I
have
gone
back
and
forth
a
bit
on
some
little
things,
but
I
think
they
did
a
good
job
with
it.
The
next
step
with
this
deal
is
just
figuring
out
end
users
to
interview,
and
they
sent
me
a
few
when
I'm
kind
of
looking
around
at
their
general
list
of
end
users
to
decide
if
I'm
going
to
stick
with
one
of
the
ones.
H
Some
of
them
are
a
few
of
the
ones
they
suggested
or
pick
other
ones,
and
then
I
have
to
figure
out
like
between
my
summer
plans
and
when
they
have
time
to
figure
out
when
to
actually
do
that.
But
I
think
right
now
the
biggest
blocker
is
really
just
me.
Finding
more
time
to
interview
people
and
figuring
out
when
to
do
it.
D
J
Yep,
I'm
here
I
reached
out
to
the
kiko
team.
There
was
some,
I
think,
confusion
whether
or
not
I
was
the
sponsor.
Now
that
we've
cleared
that
up,
I
think
we're
going
to
be
full
steep
ahead.
I
need
to
just
see
where
we
are
with
the
project
and
look
back.
I
know
they're
still
interested
in
incubation
they've
been
at
this
a
while.
So
you
know
I
definitely
want
to
put
my
focus
on
and
make
sure
they
get
the
attention
they
deserve.
B
J
D
B
Sounds
good
okay
project
ratings
for
sponsors
I
did.
Oh,
we've
got
some
time
go
ahead,
yeah
yeah!
We
have
17
minutes,
so
we
have
open
ebs,
open
yard,
shrimzy
and
open
cruise
four
of
them
that
are
available
for
some
some
folks
to
pick
up.
I
might
go
ahead
and
pick
up
open
year.
I
think
let
me
do
a
little
bit
of
a
research
there.
The
edge
use
cases
seems
important,
so
I
I'll
pick
that
up
anybody
interested
in
any
of
the
other
things.