►
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
our
group
discussion
for
container
security
alexander
you've
got
something
new
to
demo
for
us.
B
Yes
yeah,
so
I
put
the
link
to
the
the
project
on
staging.
That
is
where
you're
going
to
be
able
to
see
and
test
out
all
the
cool
new
features.
I've
turned
the
feature
flag
on
for
this
project.
I
posted
this
last
time
because
I
had
several
mrs
in
review
and
was
hoping
to
get
them
in
in
time
for
the
meeting.
But,
as
sam
pointed
out
last
time,
there
was
only
a
tab.
B
This
time
we
get
the
alerts
showing
we
have
sorting
capabilities,
we
have
and
the
ability
to
change
statuses
on
those
alerts,
which
is
all
great.
C
C
Yeah
I
didn't
sign
in
okay,
forget
about
it.
Can
we
remove
that
from
the
recording?
It's
a
bit
embarrassing,
no
problem.
A
So
it
looks
like
we're
still
not
quite
done.
Zamir
is
still
working
on
getting
stuff
through
from
agent
k,
but
all
in
looks
like
we've
had
some
great
progress.
I
just
realized,
as
I
was
reviewing
your
demo
alexander,
have
we
accounted
for
adding
the
alerts
in
the
policy
editor,
I'm
wondering
if
somehow
that
fell
through
the
cracks
and
got
missed
somewhere
along
the
way.
B
Yes,
but
definitely
did
fall
through
the
cracks.
Oh,
I
do
think
there
is
a
ticket
for
it,
though
I
just
didn't
think
I
don't
know
what
I
thought.
Let
me
try
to
find
that
and
I'll
link
it
in.
A
Okay,
yeah,
I'm
wondering
if
I
I
don't
know
if
there
are
back
end
changes
needed
as
part
of
that
as
well
or
not.
I
think
you
would
all
be
front
end,
but
I
could
be
wrong.
A
A
A
B
A
A
Then
there
are
priority.
Two
would
be
a
couple
bugs
that
I've
got
identified
there
and
actually
looking
at
this
one.
I
think
this
actually
may
be
a
front
end
bug.
I
thought
it
was
back
in,
but
I
took
a
look
and
it's
got
a
front-end
label
on
it,
so
that
yeah
that
bug
is
in
the
policy
areas
you
you
might
look
at
it
at
that
same
time
that
you're,
adding
the
alert
to
the
policy
ui
might
go
hand
in
hand
with
that.
C
End
work,
it's
in
it's
in
refinement,
alexander
and
zamir
seems
to
know
what's
going
on
there,
so
we
can
always
ping
him.
A
Got
it
sounds
good
yeah.
I
can
also
point
you
at
a
probably
should
have
taken
the
discussion
out
of
slack,
but
there's
an
old
slack
thread
talking
about
some
of
the
nuances
there.
A
It's
a
little
bit
subtle
the
way
you
can
configure
your
network
policies,
you
can
figure
it
one
way
and
it
blocks
all
the
traffic.
You
can
figure
it
another
way
and
it
allows
all
the
traffic
and
we're
actually
telling
the
user
the
wrong
thing
in
the
ui.
So
we're
misrepresenting
what
it's
doing
so
it's.
Actually
I
don't.
I
hope,
no
one's
come
across
this.
Yet
I
really
hope
because
it's
actually
a
really
bad
bug,
because
we're
misleading
users
about
what
the
policy
is
doing.
A
Cool
and
then
next
priority
for
back
end,
it
looks
like
that
would
cross
all
the
back
end
bugs
off
the
list
for
the
most
part.
So
the
next
priority
would
be
the
das
scan
schedule,
policies,
open
question
there
and
thiago.
You
may
have
answered
this
already
inadvertently
in
our
one-on-one
sync
up,
but
are
we
ready
to
move
this
to
refinement
or
do
we
need
to
do
more?
Research
like
where
are
we
at
with
this
one?
Is
there
any
more
clarification
that
I
can
provide
from
my
end,
or
are
we
good
to
go.
C
No
okay,
you
can
move
to
refinement,
I'm
sure
there'll
be
questions
and,
and
we
we
already
have
all
the
spikes
in
there
that
we
think
we're
gonna
need.
C
I
I
consider
spike
part
of
refinement
to
be
honest,
because
it's
just
part
of
trying
to
answer
the
questions
about
you
know
technical
blockers
or
architecture.
Things
like
that.
Okay,
so,
yes,.
A
A
All
right
and
then
especially
since
we've
got
alexander
and
lindsay
here
on
the
call
synchronously
with
us.
Do
you
have
any
questions
about
13.8
for
the
front
end
other
than
that
one
bug
it'll
just
be
continuing
work
on
the
alert,
dashboard,
doing
follow-up
design
improvements
there.
B
No,
I
think,
I
think,
I'm
good,
I'm
sure.
D
D
Alexander,
I
was
going
to
update
the
das
scheduled
scan
issues
out
of
13
8
and
into
given
how
much
work
is
left
for
the
alerts
and
the
follow-up
for
alerts.
Do
you
feel
like
I
should
move
those
into
13,
9
or
13
10.
B
I
think
we
should
just
I
think
it's
fine
to
leave
them
here
and
then
move
them
later.
Realistically,
I'm
probably
not
getting
gang
to
them
to
13
nine.
I
guess
so
yeah.
I
guess
it
makes
sense
to
move
them
right.
D
I
was
just
wondering
if
139
is
even
realistic,
given
the
amount
of
work
you
still
to
do
on
the
initial
alerts
issue
and
then
the
follow-up
issue
that
sam
created
so
there's
a
good
amount
of
work
in
that
as
well.
Those
are
the
priorities
before
the
das
project
bubble
scan.
So
I
was,
I
was
feeling
like
13
9
was
maybe
even
optimistic
for
that.
B
I
see
I
see,
got
it
yeah.
Okay
sounds
good
when's.
Where
are
we
in
we're
in
13
8
right
now,
right?
Thirteen.
D
B
Yeah,
let
me
let
me
think
about.
C
It
the
thing
that
I
was
going
to
mention
was
about
the
the
design
updates.
The
I
saw
that
alexander
you
and
sam
have
already
been
talking
about
the
statuses
and
the
lack
of
the
confirmed
from
from
a
background
point
of
view.
C
A
Yeah,
so
my
proposal
is
to
continue
to
punt
on
that
I
I
do
want
to
add
a
fifth
status,
but
not
right.
Now,
not
I
don't
think
it's
a
higher
priority
than
the
other
things
we've
got
going
and,
as
you
pointed
out
like
you
know,
that's
gonna
take
a
lot
of
cross-team
collaboration
and
it's
going
to
be
probably
a
fairly
hefty
endeavor
to
make
that
happen.
Just
you
know
amongst
ourselves.
I
don't
know
that
the
coding
is
so
difficult,
but
yeah.
A
C
I
can
see
it
it's
great
if
you've
put
it
in
as
further
details
and
and
it's
designed
without
a
scope
for
this
epic,
so
that
that's
that's
excellent,
like
we
will
keep
going
as
it
is
and
keep
it
in
our
mind
and
if
there's
anything
that
we
can
start
discussing
with
them,
that's
great,
but
otherwise
it's
not
stopping
us
from
getting
this
done.
D
Before
we
break
with
this,
do
you
think
that
the
design
issues
you
said
they're
to
be
ready
by
the
end
of
this
week?
I
mean:
when,
should
we
be
starting
the
planning
breakdown?
Those
do
you
think
it'll
happen
before
the
holiday.
Do
you
think
we
should
be
targeting
doing
that
in
this
discussion
next
week,.
A
So
I
will
be
working
next
week,
so,
if
whoever's
on
then
and
still
around,
I'm
happy
to
do
it,
then
if
we
don't
have
a
quorum
next
week,
given
the
holidays,
then
we
can
do
it
after
that,
I
think
hopefully,
alexander
kyle's
been
in
touch
with
you.
I
think
he
has
to
some
extent,
so
it's
a
fairly
large,
like
follow-on
epic,
there's
a
lot
in
there.
A
B
I
yeah,
I
definitely
have
a
sort
of
a
clear
path
forward,
as
sam
mentioned,
there
are
some
open
questions
there,
but
you
know
creating
the
kanban
board
digging
into
the
side
panel.