►
From YouTube: Kubernetes SIG Security Tooling 20220607
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
The
main
goal
for
today's
meeting
is
reviewing
the
kep3203
which
we
have
planned
for
version
125,
and
I
know
for
me
personally:
it's
been
a
while,
since
I
looked
at
it
in
depth,
so
I
was
thinking
we
can
all
have
a
some
sort
of
a
reading
session
today,
where
we
spend
about
20
25
minutes
of
the
call
just
reading
through
the
cap
and
then
then
discuss
whatever
we
think,
based
on
what
we
read
and
figure
out.
What
next
steps
are
there?
A
Yes,
yes,
okay,
perfect
all
right!
So
let
me
let
me
share
my
link
to
the
pull
request
for
kept
threes,
two
zero,
three
and
I'll
just
show
by
sharing
my
screen,
how
I'm
going
to
read
it
because
sometimes
it's
hard
to
read
the
raw
markdown
in
a
full
request,
so
I'll
share
my
screen
for
a
bit
and
then
we'll
just
go
on
mute.
All
of
us
read
for
until
like
25
minutes
from
now
and
then
come
back
again.
A
A
Okay,
yes,
and
so
the
best
way
I
found
to
read
pull
request
in
rendered.
Markdown
is
kind
of
going
like
this
github.com
to
github.dev.
A
Then
it
opens
online
editor
and
then
basically,
you
get
this
rendered
blob
here.
You
can
close
this
if
you
like.
B
A
A
Okay,
cool,
oh,
but
by
two
hun.
Is
that
the
right
way
to
pronounce
I've
never
asked
you
this?
I
know
we've
chatted
before
oh
perfect,
all
right
so
github
1s.com
is
another
shortcut
seems
like
which
will
allow
us
to
have
that
rendered
markdown
in
the
online
editor.
So
that's
good
to
know.
I
didn't
know
about
that
before
so
folks
who
just
joined
and
are
new
I'll,
just
repeat
some
of
the
things.
So
this
is
our
attendee
list.
I
just
shared
on
the
zoom
chat.
A
Just
put
your
name
there
with
your
preferred
pronouns
and
today
in
the
working
session,
we'll
basically
go
ahead
and
read.
A
cap
cap
is
like
we
discussed
last
time
in
our
larger
call,
kubernetes
enhancement
proposal,
so
we'll
go
and
read
that
for
until
maybe
8
55
or
9
o'clock,
my
time,
which
is
about
20-25
minutes
and
then
after
that
we
can
discuss
it
and
you
can
all
ask
questions
and
then
we'll
wrap
up
at
15-20
minutes
from
then.
A
So
this
is
the
link
again
for
the
cap.
Take
a
look
I'll
go
on
mute,
I'll,
also
switch
off.
My
video,
you
can
all
do
the
same
and
then
we'll
stay
on
the
zoom
call,
and
once
I
am
once
it's
about
8,
55
20
minutes
from
now
I'll
come
back,
unmute
myself
and
say
like.
If
anyone
wants
more
time,
then
we
get
more
five
minutes
more
and
then
continue
from
there
all
right.
A
B
Hey
pj:
if
we've
got
some
grammatical
suggestions,
is
there
anything
should
I
commit
them
into
the
pull
request,
or
do
we
just
want
to
discuss
them.
A
Yeah,
if
you
have
something
I
know,
but
one
added
a
couple
comments
if
you
can
add
those
suggestions
as
like
the
on
as
a
github
comment
where
I
can
just
commit
your
suggestion,
I
think
that
would
be
great.
B
It
helps
if
I
reply
with
my
mute
off
so
yeah,
so
I've
never
used
the
inline
web-based
editor
for
a
pull
request
before
it's
kind
of
cool,
I'm
assuming
the
changes
I'm
making
locally
have
to
be
committed
to
it.
So
I
just
make
a
grammatical
change,
commit
and
push
it
in.
A
Yeah
that
that
could
work
as
well
or
if
you
want
to
go
back
to
the
the
usual
url.
You
can
add
a
comment
in
the
pr
itself
and
if
you
mark
it
as
a
suggestion,
then
I
can
commit
it.
I
can
show.
I
can
show
you
also
and
that
if
you
want.
B
C
A
A
A
B
B
A
Correct
yeah,
so
I
think
the
historical
context
behind
that
is
people
were
using
the
rss
feed
that
was
part
of
google
groups
in
the
past
to
get
the
cvs
whenever
src
announced
it.
So
people
assume
like
we
are
recreating
that,
but
when
the
person
who
was
asking
about
that
reddit,
he
had
they
added
a
comment.
Saying.
A
A
B
A
A
So
now
that
125
cycle
has
started,
I
think
once
we-
and
we
also
have
this
cap
that
needs
to
be
merged.
So
that's
the
first
goal
for
us
and
then
after
that,
we'll
start
kind
of
creating
issues
for
tasks
that
we
need
to
do
and
then,
if
we
need
to
create
a
pr,
we
create
a
pair
to
fix
those
issues
or
take
help
of
other
sigs,
like
kate
sinfora,
who
is
responsible
for
creating
gcs
bucket
to
do
do
the
things
that
we
need
for
us.
A
A
Hey
nia,
we
just
finished
most
of
us
at
least
rap
finished.
Reading,
the
oh
okay,
sorry,
I
thought
I
lost
you.
We
just
finished
reading
the
cap
in
the
current
state
got
some
feedback
from
couple
of
folks
and
just
discussing
what
to
do
next.
So
I
don't
know
how
much
you
caught
what
I
was
sharing
with
my
earlier.
C
A
Yeah
yeah
exactly
I
I'm
also
wondering
maybe
we
we
need
some
sort
of
like
a
project
tracker
almost
where
we
can
start
adding
issues
that
we
want
to
do
as
part
of
this
cap,
or
it
can
also
be
simple,
maybe
google
doc
that
we
keep
track
of
in
terms
of
what
we
need
to
do.
What
we
have
finished
another
option.
I'm
thinking
is
some
people
in
who
implemented
caps
in
the
past.
A
They
use
the
cap
issue
itself
as
a
tracker,
and
it
just
keep
editing
the
description
there
with
new
things
that
we
need
to
do
so
that
is,
that
is
another
option,
and
another
option
is
like
having
another
issue
that
is
tracking
all
of
this,
and
we
just
kind
of
link
it
to
the
cap
issue.
A
So
I
I
that
seems
like
the
plan
before
the
plan
for
us
to
do
at
this
time
then
merging
this
cap,
I
think,
is
the
next
thing,
so
we
we
know
that
it's
actually
going
to
be
in
125,
but
generally
looks
like
from
design
perspective,
which
we
had
a
lot
of
back
and
forth.
I
know
you
were
aware
of
that.
Looks
like
people
have
general
consensus
in
terms
of
what
we
need
to
do
so
that
part
I'm
very
happy
about.
So
it's
not
just
about
implementing
things.
A
Anything
you
remember
that
kind
of
stood
out
as
a
blocker
that
we
had
to
do
before.
We
could
make
progress.
I
know
it's
been
a
long
time,
so
I'm
also
was
there
the
details.
A
Yeah
no
worries
yeah
completely:
okay,
yeah
cool,
so
for
folks,
maybe
in
the
call
who
weren't
aware
of
the
cap
before
the
call
and
suddenly
saw
this
and
started
reading.
What
are
your
thoughts
because
you
have
that
superpower
of
not
knowing
anything
about
this?
Not
having
any
context
does
this
read
well,
does
it
make
sense
in
terms
of
what
is
being
written,
what
is
being
planned
to
be
implemented?
Any
other
feedback?
You
have.
C
One
one
thing
I
remember
now
is:
did
we
got
access
to
gcs
bucket?
I
think
we
were
waiting
on
that.
A
A
C
A
That's
one
thing
for
sure:
we
need
need
from
kate
sanfra.
Another
thing
I
think
we
need
help
from
sick
dogs
is
the
secret
to
trigger
the
build
of
k
website.
C
Yeah
that
team
tim
tim
said
that,
once
your
code
is
ready,
I'll
help
you
with
that.
So,
okay,
I
think
we,
I
have
been
done
a
bit
of
code
there
as
well,
and
so
the
thing
the
part
remaining
is
only
from
the
this
project
side.
We
need
to
complete
few
things
there,
then.
I
think
we
are
good
to
integrate
them,
because
I
also
created
the
script
to
generate
json
blob
and
we
have
to
push
that
to
gcs
bucket.
That
part
is
pending.
If
we
have
the
bucket.
B
C
Yeah,
maybe
we'll
sink
once
this
week
to
just
get
on
the
floor
once
again
and
create
the
issues.
A
Okay
sounds
good,
so
everyone
else
we
got
10
minutes
more
any
feedback
or,
if
nothing
on
the
cap,
we
can
discuss
any
other
things
that
are
are
on
your
mind
about
this
project.
Any
general
questions
you
have
like
what
the
hell
is
tooling.
What
do
we
do?
Is
this
something
that
you
might
be
interested
in
happy
to
answer
those
questions
as
well.
B
A
Okay,
if
nothing
else,
thanks
all
for
for
the
feedback
on
the
cap,
I
am
excited
to
have
our
first
cap
from
tooling
sub
project.
This
version
of
this
kubernetes
release.
Rather,
let's
see
how
this
goes,
and
hopefully
we
learn
something
and
keep
having
a
good
feedback
for
future
caps.
A
Like
this,
like
we
had
today,
we
might
bring
up
the
app
armor
kept
next
time
when
we
have
a
working
session
to
have
some
kind
of
similar
kind
of
feedback
and
then
we'll
see
in
the
meantime,
if
you
are
interested
to
give
a
learning
session
about
a
topic
related
to
kubernetes
and
security,
we
have
a
spot
open
for
next
week
next
to
next
week.
A
So,
two
weeks
from
now
where
we
will
use
the
same
meeting
and
you
can
talk
about
things
you're
working
on
which
is
related
to
kubernetes
or
security,
or
you
can
just
share
your
journey
about
how
you
started
on
this
kubernetes
security
world
and
where
you
think
you
want
to
go
happy
to
host
that
session
as
well.
If
you
have
a
tool
that
is
related
to
the
same
field,
want
to
showcase
it
get
feedback
from
community.