►
From YouTube: StackRox Community Meeting #3 - 2022-06-14
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
So
hello
and
welcome
this
is
the
third
edition
of
the
stack
rocks
community
meeting
since
we
open
sourced
the
docs
I
linked
in
the
chat
david.
If
you
need
me
to
copy
and
paste
again,
I
can
do
it
matthias
and
I
I
guess
I
should
probably
introduce
myself
for
people
who
don't
know
community
chair
mike
foster-
and
this
is
my
co-community
chair,
matthias
as
well
in
the
dock.
A
You
will
see
all
of
the
information
that
you
need,
including
our
community
charter
and
just
all
the
links
that
you
need
to
get
started
with
the
project
post,
that
again
so
for
the
meeting
today
we
have
an
agenda
for
kind
of
topics
that
we
wanted
to
go
through.
Then
we
wanted
to
open
the
floor
and
give
a
shout
out
to
our
rock
star
rock
stars
of
the
month,
possibly
so
wanted
to
kick
it
off
matthias
we
had
a
new
release.
3.70
was
released.
B
Yes,
so
370
brought
some,
I
mean,
I
would
say
smaller
or
yeah.
Medium
changes
that
are,
there
are
also
very
much
quality
of
life.
So
what
we
have,
what
we
introduced
are
two
things
for
anyone
on
the
call.
The
links
show
a
point
to
youtube:
videos
of
kalikawas
introducing
and
showing
off
the
features.
So,
if
you're
interested
follow
the
links
have
a
look,
there
is
a
visual
demo
of
the
things.
So
what
did
we
actually
add?
B
We
have
two
things
which
is
a
policy
creation
for
for
network
policies,
so
you
are
now
able
to
actually
create
system
policies
to
require
network
policies.
So,
for
example,
you
can
define
a
system
policy
that
requires
every
deployment
to
have
at
least
one
ingress
network
policy
which
in
turn
ends
up
enabling
you.
So
we
ship
a
new
default
policy,
but
this
default
policy
is
currently
deactivated.
B
B
The
other
thing
that
we
introduced,
which
is
kind
of
nice,
is
the
support
for
cosine
in
image
signing.
So
we
are
now
able
or
you,
as
a
user,
are
now
able
to
make
use
of
image,
signing
and
verify
this,
so
you
can
actually
have
policies
to
only
allow
specific,
signed
images
or
images
signed
by
a
specific
key.
So
you
could
even
even
restrict
your
scope
to
images
that
were
signed
with
a
specific
key
which
is
kind
of
nice
and
accompanying
the
new
release.
B
We
now
also
published
our
our
open
source,
so
stackrock's
images
to
to
quay
io's,
stackrox
io
so
to
our
public
koi
io.
You
are
now
able
to
actually
download
and
use
let's,
let's
call
them
release
tech
images.
A
Yes,
which
is
awesome,
and
if,
for
those
following
along
in
that
document,
there
are
two
youtube
videos,
actually
that
two
of
our
essays
created.
So
if
you
want
to
take
a
look
at
what
those
features,
look
like
and
a
little
more
hands-on
with
them,
there's
links
to
those
videos
in
the
document
and
along
with
that,
we
have
a
helm
chart
update
that
matias.
You
and
a
couple
colleagues
have
been
working
on
right.
B
So
this
this
actually
our
team,
together
with
a
colleague
I
set
up,
which
is
we
now
have
actual
helm
charts
for
our
for
our
open
source
release
flavor.
So
that
means
not
only
have
we
published
a
release,
tagged
images
on
kw.
B
You
now
have
hand
charts
that
you
can
actually
use
to
basically
install
and
then
modify
all
your
stack
rocks
installations
out
there.
So
this
this
comes
with
all
the
benefits
that
helm
has.
As
in
you,
you
have
defined
states,
you
can
roll
back,
you
can
upgrade,
and
it's
it's
just
nice
to
have
that
and
we
publish
these
hand
charts
on
github
as
well
as
added
them
to
artifact
tab,
which
is
basically
a
search
engine
for
helm.
Charts
the
publishing
to
hell
to
artifact
tab
is
a
little
bit
rough
around
the
edges.
Right
now.
B
We
need
to
clean
up
some
some
old
readmes
and
some
old
information
in
there,
but
that's
a
task
that
will
follow
up
within
the
next
weeks.
A
Awesome
and
speaking
of
documentation,
so
we
need
to
update
the
readme
on
the
github
site
with
that
new
helm.
Chart
edition,
along
with
that,
once
that
gets
pushed
later
in
the
week,
I'm
going
to
sort
of
push
a
breakdown
of
everything.
Stack
rocks
has
been
vetted
to
run
on
the
open
source
version.
Obviously
the
open
source
isn't
supported
anyway,
but
it
is
really
nice
to
know
exactly
what
we
vetted
and
what
we
haven't
vetted
and
along
I'll,
probably
put
a
call
to
action.
In
case
somebody
runs
across
a
new
distribution.
A
They
want
to
test
it
out.
We
would
love
to
get
feedback
if
you're
going
to
go
run
on
like
ibm
z
or
something
like
that
or
different
or
k3s.
You
know
what
did
you
have
to
change
to
make
it
work
et
cetera?
That
would
be
awesome,
so
yeah
and
then
eventually
we
have
all
that
information
collected.
We
want
to
create
sort
of
a
you
know,
mk
docs
documentation,
site
for
getting
started,
because
I
know
people
don't
really
like
read
me
that
much
and
I
don't
blame
you,
they
are
not
fun
yeah.
A
B
Yeah,
so
the
the
current
situation
is
that
or
in
general
operators
are
just
a
pleasure
to
use
so
it's
it
would
be
nice
to
have
them
for
the
open
source
flavor.
Currently,
we
only
have
them
for
acs
and
we
support
them
for
acs,
and
what
we
could
do
now
is
our
acs
operator
is,
as
far
as
I
know,
also
based
on
the
helm
charts,
which
means
now
that
we
have
open
source
helm
charts.
B
We
could
also
port
the
operator
to
use
open
source,
basically
the
open
source
images
and
have
an
open
source
stack
rocks
operator
as
the
problem
with
that
is
we,
as
acs
team,
don't
have
the
customer
demand
for
that.
So
it's
a
little
bit
hard
for
us
to
sell
that
to
pm
and
management
to
actually
invest
the
engineering
time
into
that.
So
what
we
would
do
is
we
would
like
to
open
that
for
contributions.
So
we
will
create
an
issue
and
then
open
that
for
community
contributions.
B
So
if
anyone
in
the
audience
or
generally
may
be
watching
that
later
on
youtube,
if
anyone
is
interested
in
actually
taking
up
the
work
and
porting
the
operator
to
use
the
open
source,
hem
charts
feel
free
to
do
so.
We'll
have
an
issue
ready
that
you
can
take
over
and
start
working
on
it
and
obviously
we
will
be
there
to
support
for
for
support
and
questions
either
in
these
community
meetings
or
on
the
cncf
slack
in
the
stack
rocks
channel.
A
Agreed
yeah,
so
I
think
in
for
the
operator,
the
update
is
we're
going
to
open
up
an
issue
sort
of
describe.
I
think
what
we're
looking
to
achieve
in
terms
of
putting
it
over
from
the
helm
chart
and
leave
it
up
to
a
contribution
from
open
source
or
any
engineer.
Who's
got
extra
time
cough
cough
kneel.
If
you
want
to
do
it
just
kidding,
but
yeah
we'd
love
it.
If
we
could
get
a
k-8
operator
up
and
running
any
questions
on
that
before
we
open
the
floor.
A
C
A
A
Cool
cool,
well
that
keeps
it
really
short
and
sweet.
If
anything
does
pop
up
again,
the
slack
channel
you
can
also
you
know,
put
something
in
this
dock
and
tag
us
as
well.
We
we
monitor
stock,
pretty
religiously
and
then
for
the
fun
thing,
because
it's
a
short
little
session,
everybody
well,
so
we
actually
have
two
rock
stars,
edvin
and
michael,
who
have
been
extremely
useful
in
terms
of
on
slack
in
github
opening
poll
requests
and
issues.
A
So
we
wanted
to
send
some
merch
their
way,
and
the
other
thing
too
is
we
want
to
send
everybody.
This
call
some
stackrock
swag,
so
thanks
for
coming
out
I'll
I'll,
be
pinging
all
of
you
individually,
and
so
a
nice,
sweatshirt
and
tumbler
are
gonna,
be
coming
your
way.
Neil!
You
picked
the
perfect
session
to
join.
C
No,
I
I
actually
had
my
mouth
full.
I
was
just.
I
was
just
amusing
that
I
do
in
fact
have
acs
swag
already
and
pre-acquisition
stack
rocks.
A
A
Yeah
thanks
everyone
again.
The
recording
is
going
to
be
up
on
youtube
either
later
today
or
tomorrow
and
I'll
ping.
All
of
you
on
slack
individually,
hopefully
everybody's
in
the
stack
rocks
channel
that'll
be
easiest.
If
you're,
not
you
can
email
me,
mfoster,
redhat.com
or
join
the
slack
channel.
That'll
be
easiest,
but
yeah
thanks
for
joining
and
look
forward
to
seeing
you
next
month.