►
From YouTube: Protect:Container Security group discussion 2021-11-09
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
Welcome
to
the
group
meeting
for
container
security
got
a
really
short
agenda
here
and
one
item
that
I
added
last
minute
so
apologize
for
not
having
that
in
sooner.
A
But
first
of
all,
we've
got
a
couple
new
things
to
demo
I'll
just
read
alexander's
here
he
says
the
environment
drop
down
now
only
loads
20
environments
at
a
time,
so
it
loads
an
appropriate
amount
of
time,
which
is
awesome
because
that
used
to
take
forever
for
large
projects
with
lots
of
environments
and
then
alexander
also
says
he's
added
a
new
empty
state
for
the
scan
execution
policy
editor
when
a
user
does
not
have
the
ability
to
create
one,
which
is
also
super
helpful,
because
the
workflow
there
before
was
a
little
bit
misleading
and
third
brian
says.
A
Cluster
image
scanning
now
works
with
the
get
lab
agent
and
he
created
a
great
demo.
Video
of
that
that
you
can
go
ahead
and
watch
it's
out
on
youtube
in
the
protect
stage
playlist
if
you
want
to
find
it
there.
A
So
I
just
had
one
item
I
wanted
to
talk
about
and
get
some
feedback
on.
I
assume
most
of
you
probably
have
seen
by
now
that
the
certificate
connection
method
or
gma
v2
is
deprecated
now,
so
I
was
thinking
about
it
over
the
weekend
and
last
night
and
I
realized
that
we're
actually
doing
quite
a
bit
of
work
to
support
the
certificate
connection
method
for
cluster
image
scanning
and
I'm
wondering
if
we
should
just
cut
that
work.
A
If
you
know
I
don't
know
how
far
along
we
are
with
all
of
it,
but
I'm
wondering
if
maybe
we
should
just
not
do
the
work
for
certificate
connection
method.
There
are
a
few
areas
there.
One
is
the
ui.
I
know
we
are
planning
to
add
a
security
tab
when
you're
viewing
a
cluster
with
the
certificate
connection
method.
A
So
I'm
wondering
if
maybe
we
don't
do
that
and
only
add
that
security
tab
for
the
agent
connection
method
same
thing
with
I
know
there
was
some
complexity
with
some
of
the
filtering
too,
because
we
had
one
drop
down
for
filters,
but
we
wanted
to
have
both
clusters
and
agents
in
the
list
and
anyway,
there's
some
complexity
there,
I'm
starting
to
think
that
maybe
we
just
support
the
gitlab
agent.
Only
especially
where
it's
deprecated
now
and
don't
add,
support
for
that
certificate
method
at
all,
but
I
wanted
to
get
the
team's
thoughts.
B
So
the
good
thing
about
the
certificate
connection
was
that
it
was
very
simple
to
set
up
like
the
the
demo
effect
and
being
able
to
quickly
present
that
oh,
it's
working
and
you
can
specify
the
policies,
and
so
on
was
great
with
configuring
agent
and
so
on.
There's
like
more
steps
that
we
need
to
do,
but
at
the
end
we
are
building
that
so
users
will
use
it
not
just
to
demo
it
and
and
brag
that
that
we
have
it.
So
I
believe
we
haven't
started
lots
of
things
in
this
area.
B
Definitely
frontend
was
not
started
and
I
believe
we
we
have
added
some
items
to
actually
we're
supporting
the
certificate
connection.
Currently,
so
it's
working,
I
don't
believe
we
have
demoed,
but
I
believe
it's
working.
I
just
need
to
double
check,
but
we
have
it
so
we
we
can
either
disable
it
depress,
duplicate
it,
but
there's
not
so
much
in
the
back
end
that
we
can
do
to
stop
it
so
because
it's
already
done
so.
I
believe
we
need
to
focus
on
adding
the
support
for
for
agent.
B
A
I
know
probably
brian
and
alexander
are
the
two
people
that
this
is
most
relevant
for
so
I'll
have
the
same
discussion
async
so
that
they
can
participate
in,
but
just
wanted
to
see.
If
anyone
else
had
any
thoughts,
I
think
you're
right.
What's
already
done,
is
done
and
there's
nothing
wrong
with
that.
A
I'm
just
wondering
if
going
forward,
we
probably
should
cut
from
scope
any
of
the
development
work
that
was
going
to
be
for
the
certificate
method,
because
I
know
we
had
some
work
planned
there
to
make
that
easier
to
use,
and
it's
probably
not
worth
doing
that
at
this
point.
Since
that's
going
away.
B
Yeah
yeah
definitely
separate
tab,
definitely
like
adding
some
things
to
graphql
to
be
able
to
filter
those.
It
was
not
started,
so
I
believe,
all
the
back
and
back
end
work
and
analyzers
was
finished
and
and
the
engine
that
supports
the
security
policies
and
then
everything
that's
related
to
ui
and
presenting
the
list
different
police.
I
don't
believe
we
have
anything
right
now,
apart
from
like
separate
category
for
the
vulnerability
that
is
cluster
image
scanning
and
that
you
can
filter
on
that.
But
there's
like
nothing,
we
can
do
about
it.
B
No
additional
work
from
the
development
point
of
view
is
needed.
Okay,.