►
From YouTube: StackRox Community Meeting #10 - 2023-01-10
Description
The StackRox community meetings are held on the second Tuesday of every month. We use this time to get together and discuss gaps in the product and how best to move forward. Contributors are rewarded with StackRox gear as the RoxStar of the month.
- If you want to learn more about the project, head to StackRox.io
- The project's code repository can be found at https://github.com/stackrox/stackrox
A
Hello,
everyone
welcome
to
the
first
first
meeting
for
the
stack
Rocks
Community
in
2023
I'm,
a
community
lead,
Michael,
Foster
and
I'm
joined
by
my
other
community,
lead
Matthias,
medinger
I'll
just
introduce
you
because
it's
so
much
easier
to
do
it.
That
way.
We
have
a
couple
of
things
that
we
want
to
get
to
before.
We
kind
of
open
the
floor
to
some
questions.
A
First
thing:
I
want
to
apologize
for
some
delay
in
stack,
rocks
gear.
There's
been
some
issues
just
shipping
around
the
world,
so
you
should
see
an
email
if
you've
ever
gotten
a
rock
star
or
helped
us
out
during
hack,
Fest,
you've
seen
an
email
so
check
that,
if
not
please
post
in
the
channel
and
at
me
and
I,
will
get
you
some
gear
as
fast
as
possible.
Another
call
I
want
to
make
is
cloud
native
security
cons
coming
up,
February,
1st
and
2nd
Seattle
would
love
to
see
you
there
if
you're
in
the
area.
A
I
know
flying
and
traveling
is
kind
of
hectic
right
now.
So,
if
you
are
ping
me
I
think
I
have
some
extra
tickets.
So
just
add
me
in
the
chat
as
well.
In
the
slack
Channel
and
then
one
of
the
other
well
I
guess
I'll
hand
this
over
to
you
Matthias
for
the
big
sort
of
announcement
cautionary
tale
that
we
want
to
inform
everybody
about
this
3.74
update.
Yes,.
B
So,
actually,
tomorrow
will
be
our
code
freeze
if
I
remember
correctly.
Tomorrow
should
be
our
code
freeze
for
74.,
so
we
are
actually
beginning
the
process
of
preparing
the
next
release
and
with
that
release,
we're
actually
introducing
some
rather
big
changes.
We
in
the
last
update
we
already
had
that
as
a
kind
of
a
better
or
or
a
developer
preview,
if
you
want
to
which
is
post,
Chris
SQL
will
be
supersetting.
B
Our
current
database
setup
in
ACS
and
stack
rocks
as
well,
which
means,
with
the
next
upgrade
Please,
be
aware
that
your
installation
will
be
changed
to
using
a
postgrad
database,
which
is
which
also
means
please
people
be
mindful,
because
this
is
a
rather
big
change.
You
might
get
problems
rolling
back
from
if
you
or
you
might
get
problems
if
you
want
to
roll
back
from
74
to
73.
So
this
might
be
one
of
the
few
occasions
where
we
have
heavily
recommend
you
to
do
a
actually
execute
a
backup
before
you
upgrade
to
74..
B
The
release
is
expected
somewhere
early
to
mid-February,
so
as
just
as
a
rough
pointer
for
you
to
plan
and
in
general.
As
always,
we
are
very
interested
in
your
feedback
in
your
experience,
for
example,
how
performance
changes
if
you
experienced
any
problems
with
the
upgrade?
So
as
always,
please
let
us
know
either
in
this
community
meeting
or
in
the
slack
Channel.
A
And
typically
after
the
code
freeze,
the
documentation
gets
built.
The
preferred
method
of
upgrading
will
be
announced
too,
so
we'll
post
the
documentation
in
the
channel
when
we
know
more
about
sort
of
the
the
best
way
to
move
forward
and
yeah
kind
of
open
the
thread
to
to
feedback
as
well.
Any
questions
for
anybody
joining
I
see
Boaz
one
of
the
the
PMS
for
the
sack
rocks
projects
on
Dan.
Any
any
thoughts
you've
been
working
with
stack
rocks
for
how
many
years
now
so
I'm
kind
of
curious.
A
I
I
think
there's
definitely
some
performance
capabilities
that
we're
gonna
unlock
here
so
I
know
it's
a
little
somewhat
stressful
but
exciting
for
the
team,
especially
with
the
launch
of
the
cloud
service
as
well.
So
yeah
pretty
cool
time.
B
So
basically,
I
mean
postgraded
or
changing
to
post
gray
opens
up
a
lot
of
paths.
One
of
them
is
the
possibility
what
they
hinted
at
so
this
would
get
easier,
but
also
it
enables
users
and
customers
to
theoretically
also
bring
their
own
database,
which
is
something
that
is
currently
a
little
bit
hard,
and
that
would
also
enable
you
to
more
precisely
scale
it
to
your
requirements.
B
A
Very
cool:
that's
all
we
had
for
this
month.
It's
a
short
one.
A
lot
of
our
engineering
team
was
off
over
the
break,
so
I
hope
everybody
feels
rested
and
ready
to
go
for
2023..
Any
questions
to
the
floor.
Anybody
here,
I
just
I,
know
we
saw
we
had
some
questions
in
the
chat
I'm
trying
to
get
to
as
many
of
those
as
possible.
A
C
Yep,
here
again
to.
D
Yeah
just
like
what
I
would
like
like
introduce
myself
so
like
I'm,
a
recent
grad
and
currently
I'm
working
with
a
startup
named
Innovation,
so
we
use
stack,
rocks
at
our
organization,
so
I
kind
of
manage
the
stack
rocks
integration
with
CI
Etc.
So
that
is
why
I
just
hang
around
on
the
slack
Channel
and
I
thought
of
joining
the
community
meeting
today
as
well,
so
yeah.
So
it's
been
great
using
stack
rocks.
D
We
have
like
stream
aligned
quite
a
lot
of
image,
scan
pipelines,
Etc
with
it
and
like
a
basic
doubt,
I
could
use
this
opportunity
to
ask
is
like
we
are,
have
deployed
the
central
on
a
couple
of
clusters.
So
now
what
we
want
to
do
is
one
was
old
and
one
is
the
new
one.
So
we
want
to
move
all
the
Clusters
like
all
the
connected
clusters
to
the
old
one
to
the
new.
D
So
like
is
there
any
way
to
do
that
or
just
like
go
to
n
number
of
clusters
and
just
redeploy
the
help
there.
B
So
that
that
is
actually
a
use
case
that
I
have
not
tested
myself,
but
from
what
I
understand
what
I
remember
the
main
problem
is:
if
you
roll
out
a
secure
cluster
Services,
you
need
to
provide
it
an
init
bundle
and
this
init
bundle
is
basically
tailor
made
by
Central.
So
if
you
want
to
switch
to
switch
a
cluster
to
another
Central,
you
would
most
likely
need
to
generate
a
fresh
inert
bundle
and
then
basically
redeploy
the
secure
cluster
services
am
I
right,
mate,
Foster.
A
Yeah,
that
was
my
understanding.
Have
you
found
anything
to
the
contrary,
yeah
sure.
D
I
would
just
say
that
peanut
bundle
like
basically
in
the
init
bundle.
There
are
just
TLS
certificates
and
the
central
end
point.
So
if
we
could
keep
those
safe
on
both
the
Clusters,
then
it
should
be
quite
right.
A
Okay,
so
from
my
understanding
typically,
is
you
retire
the
old
clusters,
let's
say
from
the
central
UI
and
you
go
into
each
cluster,
you
remove
all
of
those
credentials
and
then
you
basically
join
the
old
clusters
to
the
new
Central
in
the
same
way
that
you
would
join
them
to
any
new
cluster.
B
A
C
So
curious,
why
are
you
replacing
your
central
rather
than
upgrading
it.
D
How
well,
but
to
be
honest,
I
actually
don't
know,
because
it
was
created
very
long
back
with
the
rock
CDL
command
line
tool
and
it
runs
a
quite
old
version
of
Stack
rocks
and
recently
the
in
the
3.72.1.
There
was
certain
issue
where
stack
rocks
was
down
around
the
world
right
for
a
like
a
couple
of
hours.
D
Yeah,
so
for
in
that
around
that
time
we
thought
of
creating
a
new
cluster
so
that
we
can
manage
the
policies
Etc
better
and
like
have
a
new
version
of
Stack
Rock.
So
just
to
sanitize
things,
we
created
a
new
cluster,
a.
A
Okay,
but
so
it's
just
kind
of
the
the
choice
instead
of
op
like.
D
A
When
do
you
have
this
planned
this
migration.
D
Well
it
it
would
be
just
ongoing.
I
was
just
like
doing
like
a
kind
of
POC
like
if
there
is,
if
there
is
any
way
that
we
don't
need
to
do,
changes
on
all
the
connected
clusters
like
because
we
have
a
significant
number
of
them.
So
I
was
just
doing
the
POC
so
like
nothing
planned
about
the
actual
migration
is.
A
That's
if
you
had,
if
you
had
the
operator.
D
A
A
lot
easier
for
sure,
but
yeah,
that
is
the
challenge.
I,
was
going
to
say
that
the
other
option,
if
you
use
something
like
a
terraform
template
to
bring
up
your
AWS
instances
that
in
the
future,
what
you're
going
to
want
to
do
is
add
some
of
those
ad
credentials
to
like
your
clusters
when
you
bring
them
up
so
that
they
automatically
have
that
init
bundle.
A
So
you
can't
do
that
as
an
option
so
that
every
new
cluster
or
that
gets
brought
up
in
AWS
like
an
eks
cluster,
will
have
that
in
a
bundle.
Then
they
automatically
connect
yeah,
absolutely.
A
Google
and
if
you
have
any
issues,
obviously
there's
a
bunch
of
essays
and
engineers
in
the
stack
rocks
Channel
you're
in
there
raviding
yeah
yeah
yeah,
all
right
perfect.
So
if
you
have
any
issues
just
ping
us
you
can
ping
me
and
Matthias
directly
too.
If
you
want
probably
a
little
faster
answer,
sure
cool
anything
else,
otherwise,
I'll
post
this
video
later
today
and
then
when
we
have
more
information
on
3.74
and
the
database
migration,
we
will
start
the
chat
up
as
well,
who
awesome
Matthias
I'll.
Let
you
sign
us
off.
B
All
right,
so
this
has
been
the
2023s
first
community
meeting.
So
thanks
everyone
for
participating
as
usual.
If
you
have
any
information,
questions
or
feedback
feel
free
to
Ping
Us
in
slack.
Otherwise,
as
always,
there
is
also
feedback
emails
and
with
that
folks,
stay
healthy
and
see
you
next
month
take
care.
Everyone
thanks.
Take.