►
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
container
security
weekly
group
discussion,
so
I
just
wanted
to
start
off
since
we're
all
in
the
middle
of
the
alert
dashboard
work
just
to
take
a
moment
to
get
a
little
bit
of
an
update
on
that
and
see
how
how's
that
work
coming.
I
know
our
confidence
level
getting
it
into
this.
Milestone
was
pretty
low
last
week
and
just
wanted
to
see
how
we've
come
over
the
last
week.
B
I
can
start
from
the
front-end
perspective.
First
of
all,
the
the
cut-off
date
for
things
to
get
merged
is
the
15th,
which
is,
I
believe,
tuesday
and
since,
as
I
mentioned
in
the
document,
it
takes
about
a
week
to
get
things
merged.
So
anything
that
probably
wasn't
up
yesterday
end
of
day,
like
might,
will
probably
not
get
in.
That
being
said,
my
confidence
level
is
is
a
lot
lower
than
last
week
now,
because
I've
had
some
bad
luck
with
the
review
process,
like
the
mr
to
just
show.
B
The
alerts
took
like
four
days
to
get
some
eyes
on
it,
and
that
was
a
shame,
and
hopefully
it
goes
in
tonight,
but
that's
held
up
the
reviews
for
everything
else,
because
they
all
depend
on
that.
But
I've
been
moving
ahead
and
I
have
about
three,
mrs
that
rely
on
that
one.
They
just
haven't
been
moved
into
review
because
of
how
long
that
one's
taken.
A
Got
it
yeah
thanks
for
that
update
one
thing
that
I've
been
trying
to
understand
too
on
the
front
end:
is
you
know
where
did
we
land?
I
know
we've
kind
of
gone
all
over
the
place
as
far
as
what
our
experience
is
going
to
be
like
for
this
first
release,
but
I'm
not
100
sure
on
everything
that
made
it
versus
did
not
make
it
into
that.
B
Yeah
great
question:
the
spike
that
I
did
basically
showed
that
the
kanban
style
was
possible,
but
not
in
the
time
frame
we
were
hoping
for
which
was
this
milestone.
It
was
a
lot
of
code,
a
lot
of
moving
pieces.
There
was
some
I
got
80
up
in
two
days,
but
it
would
have
taken
a
long
time
to
review
everything,
and
so-
and
that
was
just
like
a
prototype,
so
we
I
decided
to
go
with
the
table
style
because
it
was
what
I
thought
our
best
chance
of
getting
into
this
milestone.
B
If
and
basically
with
the
mrs
they're
up
like
we,
we
would
have
shown
the
alerts,
we
would
have
been
able
to
dismiss
them,
and
then
I
am
getting
up
today,
an
mr
that
would
have
hid
the
dismissal
which
is
most
of
the
requirements.
B
Two
things
that
wouldn't
have
gone
in
is
the
filtering
by
environment
or
by
policy
name.
I
think
those
are
that's
the
only
requirements
I
didn't.
I
saw
that
I
wasn't
able
to
get
up
in
a
reasonable
time
in
an
mr,
but
I
think
also
there's
some
back
end
issues
with
that.
Currently.
B
A
B
A
A
The
whole
year
is
getting
things
through
maintainer
review,
it's
just
an
unfortunate
reality
of
where
we're
at
we
don't
have
a
maintainer
on
our
team,
and
so
we
rely
on
the
other
teams
to
give
us
some
of
their
time
to
get
our
mrs
merged
in
and
it's
kind
of
it's
just
a
reoccurring
thing
that
we
face
pretty
much.
Every
single
iteration
as
part
of
this
team
is
getting
those
mrs
merged
in.
So
you
know
pros
and
cons
to
working
with
this
group.
A
Unfortunately,
right
now,
that's
probably
one
of
the
cons,
but
it
is
what
it
is.
It's
not
it's
nothing
new
for
me,
I've
I've,
I
feel
like
I've
been
hearing.
You
know,
mrs,
are
stuck
in
maintainer
reviews
since
I
started
here,
so
we
just
make
the
best
of
it,
and
you
know
we
get
it
in
in
the
next
milestone.
If,
if
it
misses
this,
one.
C
Yeah,
I
just
would
like
to
reiterate
that
on
that
a
little
bit
don't
feel
bad
alexander,
that's
how
we
have
been
going
through
in
this
team
so
far,
so
it's
not
it's
not
it's
just
breaking
through
each
day
and
and
each
will
get
merged
this
time
this
milestone
or
the
next
don't
worry
about
that.
A
All
right,
alexander,
did
you
have
more
to
add.
I
know
there's
a
lot
of
comments
here
in
the
notes.
B
A
A
D
Yes,
so
I
have
two,
mrs
that
are
like
almost
going
through
their
second
week,
so
one
mr
has
now
eight
participants
and
I'm
gonna
plan
to
hit
100
comments
on
that.
So
there
are
hundred
different
comments
on
the
march
I'm
trying
to
push
through.
I
also
invite
you
some
there
is
one
other
team's
pm
is
asking
some
questions
now
clarifications
further
clarifications,
but
is
in
a
maintainer
review
for
some
time.
I'm
doing
my
best
every
day.
I'm
waking
up.
D
I'm
answering
all
these
questions
and
I
am
you
know
pushing
through,
but
it's
quite
crowded
for
a
simple,
mr,
I
must
say
so.
It
reduces
my
confidence
to
to
merge
this
thing
in
milestone.
D
Another,
mr,
is
to
filter
things
and
separate
them
between
two
different
views.
That
is
also
in
maintenance
review,
and
so
I
updated
yesterday
today
is
a
maintenance
review.
So
two
of
my
mrs
isn't
maintaining
a
review
and
I
try
to
keep
them
on
maintenance
as
much
as
possible.
E
A
I'm
wondering
at
least
for
that
first
one
that
has
a
lot
of
comments.
Do
we
need
to
just
schedule
a
synchronous
meeting
for
that
one.
I
wonder
if
that
might
be
more
efficient
to
just
get
everyone
together
on
a
zoom
call.
We
can
talk
through
the
concerns
that
they
have
and
I
don't
know
I'm
just
I'm
asking
what
what
can
I
do.
D
To
help
yeah,
if
you
could
just
talk
with
other
teams
pm
now
she
involved
in
mr
that's
like
so
it
will
confuse
maintenance
now,
my
internet,
you
know
he
will
wake
up
and
you
don't
want
to
merge
and
he
sees
this
kind
of
stuff.
You
know,
and
I
thought
we
clarified
what
we
are
doing,
but
you
know
out.
D
So
sorry,
I
just
did
a
little
bit
of
segue
to
my
problems,
but
if
you
could
just
sync
with
other
teams,
alerts
team
pm
and
say
what
we
are
doing
we'll
be
correct.
Absolutely
I
will
I'll
talk
with
sarah
today
and
then
we
we
just
dismissed
this
actually
like
solve
this,
resolve
the
threat
so
that
you
know
main
maintenance
won't
be
confused.
D
So
the
maintenance
for
this
bird-
I
I
don't
know
how
to
pronounce
his
name
tong,
I
know
yeah,
so
he
is
in
you
know
he
is
the
best
candidate
to
actually
actually
the
merch,
because
those
are
the
configure
team
and
you
know
he
will
he
will
he's
in
new
zealand.
So
he
will
wake
up
in
our
evening
time
few
hours.
A
D
A
E
B
All
right,
john,
I
sort
of
asked
us
in
the
in
the
doc,
but
your
mr
to
separate
the
the
board's
view
does
that
by
was
it
by
domain
right.
D
D
A
new
field
to
others
table
called
domain
and
by
default,
the
domain
value
is
operations.
So
it's
like
for
operations.
You
know
so
excellent,
so
that
mr,
the
second,
mr,
is
making
the
operations
table
view.
Like
you
know,
you
don't
need
to
send
anything
from
front-end.
It
will,
by
default,
for
ce
by
default,
will
fill
use
alerts
for
domain
operations.
B
Excellent
yeah
that
don't
that
default
value
is
what
I
want
to
know
about.
Thank
you.
C
From
my
side,
I
can't
verbalize
that
so
one
of
the
the
members
of
the
configure
team-
it's,
I
thought
I
said
last
week
that
he
started
refactoring
cass
and
agent
k
to
have
like
a
plug-in
architecture.
C
And
now
one
thing
that
was
missing
was
the
to
have
a
a
possibility
for
us
to
call
the
our
end
points.
So
then
he
pinged
me
in
one
of
the
mars.
I
need
to
check
that
I
had
the
day
off
yesterday
so
then
I
need
to
catch
up
on
that.
So
hopefully
we're
going
to
have
everything
that
we
need
for
our
things
in
that
plugin,
and
then
we
just
need
to
extend
that
from
the
kubernetes
api
perspective.
C
I
was
able
to
get
more
information
from
the
kubernetes
endpoints.
There
is
one
flag,
that's
kind
of
hidden
on
the
ceiling
configuration
that
you
need
to
enable
in
order
to
be
able
to
see
policy
status
information
when
you
query
for
the
end
point,
and
then
the
next
step
now
for
me
is
to
I'm
linking
already
the
log
with
the
endpoint
status.
But
I
I
still
need
to
link
with
the
policy
and
then
that
would
be
the
first
version.
C
Second
version
would
be
to
have
a
smart
way
to
buffer
those
informations
based
on
the
watchers
for
kubernetes,
api
and
yeah,
but
I
I
don't
have
any
mario
yet,
hopefully
I
have
some,
mrs
by
the
end
of
this
week,.
A
Great,
if
there
is
a
flag
like
that,
that's
kind
of
hidden,
it
would
be
nice
if
we
could
just
set
that
flag
by
default
as
part
of
our
home
chart
rather
than
having
the
user
add
yet
another
thing
to
their
yaml
file.
It
just
makes
it.
You
know
one
step
easier
for
them.
If
it's
pre-configured
the
way
it
needs
to
be.
C
Yeah,
to
make
things
easier,
the
the
best
way
to
move
forward,
I
think,
is
to
bump
the
version
from
1.8
to
1.9,
and
then
I'm
gonna
do
that
there's
a
issue
for
that
already
and
then
I'm
gonna
do
exactly.
As
you
said,
I'm
gonna
enable
the
flag
by
default
and
I'm
going.
We
need
to
add
in
the
documents.
If
people
don't
want
this
feature,
they
can
disable
it
to
to
improve
the
performance
on
their
site.
A
Yeah,
that
sounds
like
a
great
great
approach,
so
awesome.
Well,
thanks
for
all
the
updates
there
and
kyle,
it
looks
like
you've
got
some
updates
as
well.
F
Yeah
mine
are
just
about
some
of
the
kind
of
follow-up
iterations
we
can
make
to
the
alerts
dashboard.
F
So
a
prototype
is
quite
a
few
steps
ahead
of
of
the
initial
nbc,
but
like
one
is
on
the
table
view
is
showing
the
details
of
the
related
alert,
so
whether
you're
on
the
kanban
view
or
on
the
table
view
just
showing
the
actual
details
of
what
the
alert
policy
was
in
the
past.
F
We
looked
at
this
a
little
bit,
but
one
one
thing
that
was
kind
of
unsure
of
and
like
the
the
details
that
we
saw,
there
were
really
for
a
placeholder
for
usability
testing
and
they
kind
of
have
the
basics,
but
I
opened
up
this
little
this
like
discovery
issue,
just
to
answer
a
few
questions
of
for
an
mvc.
What
information
will
we
have
available
to
show
for
those
alerts,
and
then
we
can
kind
of
figure
out
what
the
mvc
is
for,
how
to
show
it.
F
Some
other
basic
kind
of
questions,
too,
is
like
one
of
the
here
I'll
just
quickly
show
like
one
of
the
ux.
Things
is
like
if
someone
is
looking
at
this
and
they
want
to
share
this,
the
drawers
don't
create
like
a
unique
identifier
that
you
could
link
to
another
user,
so
maybe
we
could
figure
out
a
way
of
doing
that,
but
also
on
the
the
ux
side.
I
still
need
to
show
an
expanded
view
of
that.
So,
but
that's
a
few
steps
down
the
road
yeah
I
one
suggestion
would
maybe
be
like.
F
Could
we
do
this
discovery
like
with
alexander
and
john
like?
If
we
do
like?
I
don't
know
in
the
past,
I've
just
done
like
a
discovery
where
we
have
front
end
and
back
in,
and
we
just
kind
of
answer
some
of
those
questions
and
in
a
milestone.
I
know
we're
kind
of
at
the
end
of
this
milestone,
but
maybe
for
next
milestone.
F
A
Where
would
be
working
on
it?
Next
milestone
yeah
in
13,
8.
F
B
Okay,
yeah
kyle,
have
you
looked
at
the
operations
alert
page?
Obviously
you
have
that's
a
dumb
question,
but
no,
there
are
no
dumb
questions
because
they
have
a
details
page
that
they
can
navigate
to
separately.
That
does
create
a
unique
url.
Is
that
something
you
would
be
interested
in.
F
Yeah,
I
think
that'll.
If
there
wasn't
a
a
unique
url
for
the
drawer,
that's
available,
then
there'll
need
to
be
one
for
like
even
in
the
drawer.
If
we
put
like
a
copy
and
paste
icon
or
something
so
you
could
just
quickly
like
share
it
with
someone
it'll
take
them
to
the
to
the
expanded
page.
F
You
know,
but
I
think
the
key
question
right
now
is
just
exactly
what
details.
Can
we
show?
What's
the
information
that
we
can
show,
that's
the
one
that
I'm
I'm
not.
C
Sure
I
can
have
a
right
now,
I'm
at
a
point
that
I
can
have
the
information
from
the
logs.
So
then
maybe
I
could
just
grab
like
a
couple
of
the
logs
plug
entry
and
other
information
that
we
would
map
and
just
add
in
the
issue.
So
then
you
have
some
idea
on
on
what
we
can
get
from
the
back
end.
But
with
that
said,
john
is
working
on
the
private
api
and
I'm
not
sure
exactly
the
mapping.
That's
going
to
happen
there
so
yeah
we
might,
we
might.
C
F
Yeah,
I
know
way
back
when
we
first
started
this
and
then
we
it
dropped
off
for
a
little
bit
with
alerts.
But
the
there's
a
small
discussion
that
maybe
that
there's
just
like
we
just
take
any
information,
that's
there
and
put
it
into
the
details,
page
container
and
then
eventually
we
kind
of
comb
through
that
and
format
it
a
little
bit
better
after
follow-up
iterations.
F
But
I
think
what
would
be
helpful
is
just
to
see
like
the
examples
you're
talking
about,
so
we
can
kind
of
see
how
that
might
be
put
into
the
drawer,
for
example,
or
the
unique
page.
So
should
I
I'll
just
ping
you
on
that
issue
and
yeah
yeah?
That
would
be
great.
B
F
B
I
had
a
similar
idea
I
like,
if,
if
the
drawer
would
or
when
the
drawer
happens,
I
was
just
going
to
like
dump
everything
in
there
and
be
like
here's
more
information
and
then
get
feedback
on
it
later.
C
B
Yeah
thread
insights
is
doing
something
similar
with
their
scanners,
so
maybe
we
can
take
a
page
from
their
book
and
create
use
some
generic
components.
Maybe
we
could
share
with
them.
A
A
All
right,
so,
in
the
same,
for
the
sake
of
time,
we
probably
want
to
keep
moving
along
alexander
anything
new
to
demo.
I
took
a
look
there.
It
looks
pretty
blank
other
than
I
do
see
you
added
the
alerts,
tab,
so
good
job.
B
Yeah,
it's
work,
I'm
working
on
it
but,
like
I
said
at
least
hopefully
the
alerts
will
show
by
tomorrow,
so
that'll
be
exciting.
I'll,
probably
ping
everybody
with
emojis
and
stuff
like
that.
To
celebrate.
A
And
then,
with
the
time
we've
got
left,
I
just
wanted
to
sync
up
on
our
rough
notional
plans
for
the
next
couple
milestones,
so
it's
becoming
pretty
apparent
we're
not
going
to
actually
ship
the
alert
dashboard.
This
milestone,
I'm
hoping
that
it
doesn't
take
all
of
13
8
to
ship
it.
You
know,
I'm
hoping
that
we
can
wrap
it
up.
13-7-
and
you
know,
we've
got
some,
mrs
that
are
still
going
through
maintainer
review,
but
I'm
hoping
we
can
ship
that
fairly
early
in
the
next
iteration
and
still
have
some
time
to
go.
A
You
know
that
initial
iteration,
but
now
to
add
in
things
like
alert
details,
some
of
the
stuff
the
monitor
team
already
has
in
their
ui,
but
like
the
ability
to
create
an
incident
from
an
alert
the
ability
to
assign
a
user
to
an
alert
filtering
by
status,
environment
policy,
the
kanban
view.
So
that's
kind
of
my
short
list
of
things
that
I
would
like
to
still
see
happen
on
the
front
end.
A
B
B
B
I
just
need
to
verify
that
there's
a
couple
there's
a
couple
things
that
I
don't
know
about
and
from
the
back
end,
which
is
filtering
alerts
by
environment
and
by
policy
names
amir,
you
mentioned
that
you're
mapping
to
policy
or
that
mr
is
going
to
go
up.
Maybe
this
week
is
that
correct.
Is
that
what
you're
saying.
C
Yeah
yeah,
but
my
mr,
is
going
to
be
just
a
call
to
the
internal
api.
So
then,
after
the
after
he
gets
to
the
internal
api,
that's
going
to
be
john's
code.
That's
going
to
drop
this
into
the
alert!
B
C
Yes,
yes,
I
would
have
to
check
the
demar
that
this
demars
are
in
progress.
Maybe
jen,
would
you
be
able
to
see
which
fields
are
we
going
to
have
split
out
of
the
block?
Yes,.
D
Yes,
so
I
use
the
same
piece
of
code
to
from
alerts
team
to
j,
create
a
generic
alert.
You
know
so
you
know
this,
you
you
enable
the
others
integration
and
you
hit
the
end
point
with
the
payload
and
you
create
alerts.
So
you
know
all
those
things
you
can
see.
As
an
example
was
this.
D
B
C
Would
you
mind,
checking
the
I'm
not
sure
I'm
not
familiar
with
the
front
end?
Do
they
do
the
I'm?
Assuming
do
they
get
like
a
json
blob
and
they
parse
things
in
the
view
code
before
displaying
it,
or
do
they
already
get
like
the
the
information
as
like
just
different
attributes
in
this
object?
Maybe
that's
the
the
tricky
got
it.
Okay,.
F
C
Have
the
natural
work
information
as
attributes
of
this
json
blob,
it
would
require
a
parsing.
B
Okay,
got
it
all
right,
so
it
sounds
like
the
verdict
is
also
out
on
environment
and
policy.
Name
right
now.
There
neat
we
need.
There
needs
to
be
some
verification,
but
that
would
be
potential
back
end
work,
but
basically
a
lot
of
stuff
could
go
forward
with
the
front
end.
A
Awesome
so
I
will
create
a
follow-on
epic
to
capture,
basically
the
delta
of
what
we
where
we
want
to
be
versus,
where
we
actually
got
with
our
initial
mvc
and
kyle's
got
some
design
issues
that
I'll
associate
up
with
that
and
and
I'll
write
up
the
requirements
there,
just
so
that
we
can
finally
start
to
actually
separate
out
like
here's
the
mvc
in
our
first
release,
and
then
you
know,
here's
some
of
that
follow-on
work
and
then,
lastly,
on
the
back
end
team,
so
I'm
hoping
that
any
ongoing
support
there
for
the
alert
dashboard
after
this
is
minimal.
A
A
I
know
alexander,
you
did
a
really
good
job
breaking
that
out
and
refining
it
on
the
front
end,
but
I
think
there's
more
complexity
on
the
back
end,
so
it'll
be
good
to
give
the
back
end
team
a
head
start
on
that
one.
So
they
can
hammer
out
some
of
those
unknowns
before
we
have
everyone
working
together.
C
Me
my
concern
is
that
we
are
going
to
have
a
big
change
on
agent,
k
and
cass,
and
now
we
need
to
synchronize
with
them
when
they're,
when
do
they
are
going
to
release
these
new
versions?
So
then
it's
not.
We
just
don't
rely
on
the
pipeline
for
having
the
rails
code
delivered.
C
So
then
that's
what
concerns
me
on,
assuming
that
we're
going
to
have
everything
tested
by
the
first
part
of
the
next
milestone,
and
I
think
we
still
have
different
pieces
everywhere-
that's
very
hard
for
me
to
see
that
for
sure
we
are
going
to
have
something
on
the
bikini
of
the
milestone
and
we
are
going
to
have
maybe
like
half
or
more
of
the
my
son
to
work
on
something
completely
different.
That's
my
only
concern
there.
A
Got
it
okay?
Well,
I
mean,
I
guess,
regardless
of
of
the
timing,
I
would
just
say,
as
you
start
to
finish
up
with
the
alert
dashboard,
if
you
have
extra
time,
that
would
be
the
next
priority.
Is
those
tasks
scheduled
scans,
so
even
if
you're
working
both
in
parallel
for
a
little
while
you
know
that
would
be
the
next
thing
to
pick
up.