►
Description
In episode 8, we will discuss the previous week's engineering meetings and how to navigate the StackRox project and walk through a basic Kubernetes deployment.
Join us live on the 19th at 1 pm Pacific and 4 pm eastern will all of your questions and feedback.
A
A
A
B
Hello,
hello
and
welcome
once
again
to
stackrock's
office
hours,
I'm
your
host
michael
foster
and
today,
as
always,
we're
going
to
be
discussing
everything
you
need
to
know
about
the
stackrocks
project.
Stackrock's
open
source
joining
me
is
the
co-host
technically
co-host
for
the
day
and
fellow
stackrock's
community
manager
mathias
matias.
Thanks
for
coming
on
the
show
it's
it
was
snowing
yesterday,
where
I
am
so.
This
is
kind
of
my
break
for
the
week.
B
A
Thanks
for
having
me,
so
I
am
a
software
engineer
currently
working
in
team
maple
so
doing
most
most
or
exclusively
core
engineering
for
our
product.
I
joined
the
project
in
january
last
year,
so
I've
been
I've
been
with
the
project
for
a
little
bit.
Currently
I'm
working
out
of
germany
and
what
I
did
so
far
is,
amongst
other
things
and
with
other
people.
B
That's
awesome:
yeah,
thanks
for
taking
the
time
to
come
on
for
everybody
watching
we
have
engineering
meetings,
the
second
tuesday
of
every
month,
12
p.m.
Eastern!
That's
posted
on
youtube!
If
you
missed
it
and
then
again,
the
third
tuesday,
which
is
today,
is
when
we
talk
office
hours
and
we
welcome
any
questions.
We'll
do
demos
walkthroughs.
So
today
the
big
focus
is
on
getting
started
with
rocks,
specifically
because
now
that
we
are
open
sourced
as
of
march
31st,
it
is
freely
available
for
everybody
to
use.
So
anybody
that's
watching,
throw
questions
in
the
chat.
B
If
you
are
unaware
of
links
stackrocks.io,
we
are
more
than
happy
to
take
you
through
it
all.
So
you
actually
mentioned
the
community
charter.
I
think
a
good
place
to
kick
it
off
would
be
stackrocks.io
just
to
walk
through
a
little
bit
of
the
community
site.
Is
there
any
chance
that
you
want
to
take
us
through
that
showcase?
You
know
maybe
some
of
the
links
and
blogs
articles,
everything
like
that
sure
we.
A
A
So
this
is
stack,
rocks
io
our
main
website,
where
you
can
definitely
where
you
can
see
upcoming
events,
where
you
can
see
our
calendars
as
well
as
most
of
the
community
links
that
are
that
are,
or
at
least
most
of
the
community
links
to
be
able
to
getting
started.
For
example,
you
can
join,
you
can
join
our
slack,
which
is
we
are
on
the
cncf
slack
and
we
have
the
channel
stackrocks.
So
this
is
one
of
the
quickest
way
to
read
ways
to
reach
us.
A
B
Yeah
yeah,
the
other
thing
about
that
slack
channel
too,
which
is
awesome,
is
there
are
some
people
who
have
let's
say
departed
since.
Obviously,
stockholm
has
been
acquired
by
red
hat
and
they're,
still
very
active
in
the
channel
and
and
using
the
products.
So
it's
awesome
to
see
people
who
are
are
staying
a
part
of
the
community.
B
So
you
know
finding
the
project
on
github
there's
the
open
source
cube
linter
project
that
was
also
released
at
the
end
of
2020.
again
office
hours.
Third,
tuesday
of
every
month,
like
you,
you
guys
are
watching
right
now
and
of
course,
slack
channel
and
twitter,
and
you
did
mention
the
community
charter.
So
there's
the
code
of
conduct
at
the
bottom
of
the
page
there
matthias
and
for
anybody
who's
joining
the
community
recommend
you
check
it
out.
There
are
three
individuals
who
are
part
of
the
codaconic
team.
B
A
Of
course,
especially
as
github
also
recently
introduced,
the
feature
of
following
following
organizations
feel
free
to
follow
the
stack
rocks
organization
on
github
and,
of
course,
leave
a
star
on
the
on
the
repos
that
we're
mainly
using
especially
stackrock's
cube
linter
and
maybe
the
hem
charts.
If
you're
interested.
B
Yeah
for
sure,
there's
there's
a
ton
of
public
repositories
on
that
github
account
and
stackrock's.
The
main
stackrocks
stackrocks
is
the
github
that
you
can
get
the
deploy
script
that
we'll
be
showcasing
a
little
bit
later
in
the
episode
for
documentation.
There
is
the
docs
link
at
the
top
there.
If
you
can
click
that
that'd
be
awesome
there
you
go
so
new
stack
rocks,
there's
insulation
with
helm,
insulation
with
rocks
cuddle
and
the
openshift
operator.
B
Now,
if
you
click
some
of
the
documents
it
takes
you
to
the
rhacs
paid
product,
which
is
funny
because
they're
just
for
everyone
watching
at
home,
they're
the
same
product.
So
the
only
thing
that
really
changes
is
the
container
image
that
you're
pulling
from
the
open
source
images
are
in
quay,
but
when
it
comes
to
setting
up
and
using
the
application
and
all
of
the
how
to's
they
are,
the
exact
same
and
we're
looking
to
we're.
B
A
No,
absolutely
not
maybe
to
to
add
to
that
is
we're
currently
we're
linking
to
the
to
the
commercial
documentation,
but
also
one
of
the
problems
that
we
have
right
now
is,
or
one
of
the
challenges
that
we're
still
ironing
out
a
little
bit
is
the
fact
that
we
don't
provide
release
images.
Yet
that
is
something
that
we
need
to
sort
out
in
our
build
process,
and
we
are
currently
working
on
that.
A
That
also
has
has
its
own
release
tags
that
are
basically
following
suit
with
the
commercial
product,
but
still
we
have,
we
will
have
open
source
release
tags.
This
is
something
again:
that's
a
work
in
progress,
that's
something
that
we
need
to
do
right
now
and
that
will
that
will
change
in
the
near
future,
just
as
a
preface
to
all
the
to
the
deployment
options
that
we're
talking
through
today.
A
B
B
You
will
come
across
all
of
these
public
repositories
and
I
believe,
there's
something
like
40
40
plus
public
repositories
in
this
github
account.
So,
like
matia
said
you
can
follow
the
stack
rocks
organization
on
github
and
you'll
see
a
plethora
of
of
resources,
so
the
stack
rocks.
Then
it's
the
main
one
that
you
can
get
started
with
the
application.
There's
also
cube
linter
and,
of
course,
helm,
charts.
The
stack
rocks
collector
and
a
ton
of
more
goodies
for
you
to
check
out
and
let's
see,
look
at
look.
B
B
A
Yeah
sure
so
I
would
we
should
maybe
differentiate
between
doing
development
deployments
and
production
deployments.
The
code
base
is
the
same,
although
obviously
it
has
some
slight
changes.
The
development
process
is
already
done,
so
this
is.
This
is
something
that
we're
happy
with,
as
is
and
again
the
the
production
deployment
of
the
oss
flavor.
That's
something
we're
currently
working
on.
We
encountered
some
smaller
things
that
we
would
like
to
fix.
So
this
is
something
that
will
be
coming
soon
for
illustration
purposes.
We
maybe
it's.
A
A
A
Basically,
anything
that
is
happy
with
cubecuttle
and
helm.
Charts
is
something
you
can
install
in.
So
I
am,
I
know
that
we
are.
I
definitely
know
that
we
are
that
everything
will
work
with
docker
for
desktop
mini
cube
is
also
working.
I
I
believe
k3s
has
some
smaller
tweaks.
That
think
that
people
need
to
do,
but
I
think
andy
clemenco
is
one
of
the
people
that
that
figured
that
out,
and
I
think
he
documented
that
and
just
that
we
could
link
in
if
anyone
is
interested
in,
but
for
now
to
get
started.
A
So
the
idea
is:
if
we
follow
the
quick
start,
you
will
end
up
at
a
point
where
you
basically
do
a
make
image
which,
which
builds
our
you
build
your
local
images
for
the
sake
of
time.
I
will
skip
this
now
because
it
takes
roughly
10
to
15
minutes
depending
on
your
hardware,
that
you
are
locally
running
and
I
think
we
don't
need
to
borrow
we
don't
we
don't
need
to
show
the
docker
build
process.
B
A
With
with
some
time
magic,
we
are
now
skipping
the
next
10
minutes
and
what
you
do
is
you
start
with
a
deploy?
So
this
is
the
folder
that
contains
all
the
different
deploy
scripts
and,
as
you
can
see,
we
have,
for
example,
kubernetes,
and
then
you
have
two
options
you
have
for
kubernetes.
You
have
the
deploy
dot,
shell,
which
is
for
remote
deployments,
so
something
that
is
not
running
on
your
own
machine
and
we
have
deploy
local,
which
is
especially
tailored
towards
locally
running
docker,
for
desktop,
for
example.
A
A
So
what
you
do
for
development
is
the
workflow
of
you.
You
make
a
change
or
you
you
build
a
feature
or
something
like
that.
You
do
you
execute,
make
image,
and
then
you
can
deploy
that
to
your
local,
darker
or
darker
and
kubernetes
setup,
and
the
neat
thing
about
this
is
this:
does
everything
for
you
so
once
it
is
done
so
our
documentation
distinguishes
between
installing
central
and
and
secure
cluster
services.
A
B
B
I
am
right
there
right
so
just
underneath
that
to
deploy
part
it.
So
when
you're,
when
you're
deploying
oh
yeah,
there
there's
a
password
output
to
a
specific
text
file
in
your
repository
that
you're
gonna
have
to
click
to
log
in.
If
you
read
the,
if
you
go
through
the
readme,
it
is
there
it's
just
not
necessarily
standing
out,
hey
here's
the
password
so
just
worth
pointing
out.
A
B
Yeah
sorry
rock
count
points
out
real
quick.
Is
it
possible
or
intended
to
be
used
in
air
gap
environment?
Yes,
that's
the
architecture
so
along
with
being
able
to
deploy
in
a
kubernetes
cloud
environment
if
you
are
on
prem
and
you
want
to
be
in
an
air
gap.
Environment
that
is
stack
is
also
designed
to
run
there
as
well.
A
This
repository
contains
multiple
quality
of
life-
things,
for
example,
a
teardown
script
that
will
just
tear
down
all
all
traces
of
stack
rocks
being
installed
in
your
cluster,
which
is
especially
handy
if
you're
doing
development
and
testing
work,
as
well
as
log
me
in
which
is
a
command
that
just
launches
the
browser
and
already
logs
you
in.
So
you
don't
have
to
do
the
copy
paste
password
dance.
So
this
is
also
kind
of
nice
and
heavily
recommended,
especially
if
you're
interested
in
development,
where
you
do
a
lot
of
teardown
and
redeploy
of
these
clusters.
A
B
It's
alright,
it's
it's
getting
late
for
you
right.
I
think
it's
way
past
dinner
time
out
where
you
are
so
yeah.
It's
all
good.
This
is
yeah.
This
looks
great,
so
we
have
one
option:
we're
running
several
openshift
clusters,
each
in
disconnected
environment,
with
a
complete
git
ops
approach.
I'd
like
to
see
more
yaml,
slash
deployment,
examples
in
the
documentation
does
the
deployment
work
with
open.
So
I
guess
the
question
is
we're
talking
about
rh
acs
documentation?
B
That's
something
we'd
be
happy
to
help.
If
right,
please
feel
free
to
reach
out
in
the
chat,
and
we
can
get
something
that's
a
little
bit
better
for
something
that's
disconnected,
especially
for
your
use
case,
but
openshift
and
obviously
rhcs
has
an
operator.
In
fact,
it's
my
favorite
way
to
deploy
the
application.
The
operator
is
awesome
on
openshift,
definitely
worth
checking
out.
A
If
we
have
some
restarts
so
one
or
two
restarts,
depending
on
especially
your
docker
desktop
version
for
so
collector,
is,
is
sometimes
prone
to
restart,
especially
depending
on
your
docker
desktop
version.
There
were
some
versions
where
the
collector
was
missing.
I
think
kernel
drivers
for
specific
kernels
in
docker
desktop.
A
So
that's
something
to
know,
but
usually
that
is
not
a
big
problem,
so
the
important
parts
are
central
scanner,
scanner
db
and
sensor.
So,
of
course,
collector
is
also
a
vital
part
of
of
the
stack
rocks
platform
itself,
but
collector
is
yeah,
as
the
name
might
imply.
Collector
is
collecting
metrics
and
runtime
information
from
inside
containers.
So
this
is
one
of
the
parts
of
the
platform,
but
the
platform
would
also
be
able
to
work
and
run
without
that
part.
B
Sort
of
similar
to
a
fluentd
architecture,
it's
collecting
and
shipping
to
the
central
in
the
database,
but
it
can
restart
and
then
recollect
after
it
when
it
comes
back
up
right,
awesome
and
that
came
up
extremely
quickly.
Obviously
it
had
been
previously
built
on
your
local
host,
but
you
know
we
were
up
and
running
in
what
two
three
minutes.
A
B
A
A
Lets
our
build
process
skip
the
ui
build
because
in
day-to-day
operations,
if
you
don't
make
changes
to
the
front-end
and
only
make
changes
to
the
back-end
or
services
in
the
back-end,
you
usually
don't
need
to
rebuild
the
ui
and
the
ui
build
takes
quite
a
lot
of
time.
So
that's
that's
one
of
the
recommendations.
A
Is
you
don't
need
to
rebuild
the
whole
central
image
every
time
there
is
a
way
to
to
hot
mount
your
local
central
binary
in
the
remote
cluster
that
you're
working
on?
So
that's
basic.
That's
almost
like
a
live
reload
with
the
added
step
of
you
need
to
compile
into
a
go
binary,
but
that's
something
that
is
quite
nice
and
that
shortens
your
average
build
time
from
15
minutes
to
under
5
minutes.
A
B
A
B
A
B
But
I
will
comment
on
on
a
couple
things
that
that
I've,
you
know
the
first
time
I
went
through
the
open
source
deployment.
You
get
a
little
hiccup
done
and,
although
honestly,
it's
extremely
smooth
now,
it's
very
the
only
thing
I
have
trouble
with
is
just
finding
the
password
sometimes
but
by
design
yeah.
So
you,
obviously
you
had
two
clusters.
You
had
your
local
setup
and
then
now
you're
switching
context
to
your
gke
right.
A
Let
me
think
so.
What
I
would
say
is
maybe
we
just
do
yeah,
so
we
actually
have
multiple
options
or
multiple
routes
to
go.
So
there
is
the
interactive
installer
or
that,
ideally,
I
would
recommend
to
do,
as
you
already
mentioned,
the
openshift
operator,
which
is
the
most
comfortable
and
stable
way
to
deploy
the
platform.
Unfortunately,
we
don't
have
that
for
the
open
source
flavor.
A
Yet
so
I'm
I'm
not.
I'm
actually
not
entirely
sure
if
we
are
planning
on
doing
that,
but
generally,
if
the
community
would
be
interested
in
an
openshift
operator
for
the
open
source
product,
please
let
us
know
so
we
can.
So
we
can
argue
that
the
next
best
thing
you
can
do
is
helm
charts,
which
is
something
that
is
very
great,
so
helm
charts,
basically
give
you
the
the
option
of
doing
rollbacks
and
and
and
targeted
installs
and
uninstalls
of
of
bigger
deployments.
A
I
guess
everyone
so
for
for
the
people
that
are
not
aware
of
it
have
a
look
at
hem
shots,
they're,
great
and
also
the
final
thing
or
the
next
best
thing
that
we
have
is
roxcuttle,
which
is
our
local
command
option
to
yeah.
This
can
also
generate
deployments,
and
this
can
also
generate
helm
charts,
so
I
have
actually
just
implemented
something
to
generate
helm,
charts
that
are
pointing
to
the
default
way.
I
o
open
source
repository.
So,
let's
see
if
that
works.
So
if
that
works,
that
might
even
be
a
nice
thing
to
have.
A
B
A
B
Well,
you
go
typing
away,
I'm
just
gonna
answer:
rockhound
yeah,
it
is
funny.
I
mean
a
lot
of
people
at
red
hat.
Obviously,
openshift
is
just
a
you
know,
a
let's
say:
enterprise
version
of
vanilla,
k8s
right
with
some
guardrails
and
some
extra
security
features
and
things
like
that,
and
you
know
we
want
people
who
are
coming
in
and
can
just
go
fire
up
a
kubernetes
cluster
to
be
able
to
use
the
application.
B
A
B
Shucks,
sorry,
don't
worry
all
right,
helm
chart
version
two
coming
up
next
month
after
these
releases,
so
I
mean
I
could
showcase
just
I
already
did
it.
I
already
kind
of
deployed
it,
but
I
can
showcase
the
deploy
script
that
would
be
on
github
that
most
people
would
see
yeah.
If
we
are
interested.
Let
me
just
go
over
to
stackrocks.
B
And
I
actually
I've
been
meaning
to
push
this
readme
change,
because
there's
a
couple
of
options
of
things
that
I've
been
meaning
to
update
but
yeah
the
helm
chart,
like
you,
said,
rox
cuddle,
uses,
helm,
charts
underlying
to
create
and
generate
the
manifest.
Even
the
deploy
script,
I
believe,
uses
helm,
charts,
correct.
A
B
But
for
people
who
are
following
along
at
home,
who
want
to
deploy
to
their
vanilla,
k-8
cluster,
whether
it
be
gke,
azure,
aws,
whatever
it
is,
if
you're
in
the
main
stack
rocks
repository
towards
the
bottom
of
the
readme
which
I'll
be
moving
to
the
top,
but
towards
the
bottom
of
the
readme.
You'll,
see
these
steps
for
orchestrator
specific
deployments,
whether
it
be
kubernetes
or
openshift.
B
Something
easy.
If
you're
download
the
github
repository
and
you
want
to
try
it
out,
run
the
deploy
script
and
you
will
be
do
where
is
it
you'll
be
basically
running
the
playscript
and
setting
a
image
tag?
So
you
set
the
environment
variable
to
main
image
tag
which
will
be
latest
again,
I'm
going
to
update
the
readme
so
that
this
copied
line
works
every
time
and
what
you'll
get.
B
Is,
oh,
that's
not
it!
Let's
go
back
over
stop
over
to
my
other
screen.
You'll
see
this
so
main
image
tag
latest
and
we're
running
the
deploy
script
and
you
can
see
all
of
the
variables
that
are
by
default,
set
so
in
cluster
central
endpoint
scanner,
support
collection,
method,
ebpf,
stackrock's
namespace.
By
default.
We
want
to
deploy
to
that
statcrux
namespace.
Just
everything
will
work
so
much
smoother
because
we
obviously
use
kubernetes
native
networking
underneath
the
hood
and
when
you
go
down
you'll
see
this
part
right.
B
B
I
believe
it
would
be
stackrock's,
deploy,
k8
central
bundle
and
then
password
now
in
the
on
the
readme.
It
says
the
exact
location
of
it,
but
just
an
fy
that
you
have
to
go
and
find
the
password
do
not
try
to
reset
this
in
the
kubernetes
secrets
either
because
it
is
a
decrypt
hash
password.
So
it
will
not
be
accepted.
Am
I
correct
here
mathias,
because
that
is
something
that
I've
seen
as
well.
A
I'm
I'm
not
entirely
sure
if
we
even
have
no,
I
I
don't
think
you
should
do
that
from
from
from
the
outside.
I
think
there
is
a
way
to
reset
the
admin
personally,
but
I'm
also
not
entirely
sure,
because,
honestly,
that's
something
that
I
as
a
developer
never
ran
into,
because
usually,
if
I
lose
my
admin
password,
I
honestly
just
do
a
teardown
and
redeploy
because
it's
just
so
fast.
B
And
realistically,
if
you're
setting
this
up
for
multiple
uses,
you're
going
to
want
to
set
up
an
oauth
or
some
sort
of
authentication,
oh
yeah,
on
top
of
that,
it's
kind
of
an
anti-pattern
just
to
sit
there
with
an
admin
password
so
but
it
is
good
for
first
use,
so
you
can
get
access
to
it.
Rockhound
asks
if
I
start
looking
for
a
security
solution.
Why
should
I
go
for
stack,
rocks,
not
aquas
new
vector
systig?
Is
there
a
main
differentiator?
I
didn't
get
yet
main
differentiator
kubernetes
specific.
B
So
a
lot
of
the
other
platforms
you'll
see
a
lot
of
container
specific
information
focused
across
cloud
workloads
and
trying
to
push
the
cspm
methodology.
Stack
rocks
is
very
specific
for
kubernetes
native
so
as
we'll
get
into
the
dashboard,
you'll
see
a
lot
of
kubernetes
vernacular
and
ways
of
managing
risk
that
you
won't
see
in
other
platforms,
but
stay
tuned
and
you'll
you'll
see
a
little
bit
more
yeah.
B
B
So
I
think,
like
matthias
said,
let's
go
to
platform
configuration
and
go
to
system
health
everything's,
looking
good
and
really
that
was
just
a
run,
a
script
and
it
worked
perfect
with
gke.
So
now,
let's
just
go
and
make
sure
that
we
check
to
click
the
scan
environment,
and
this
makes
sense
right.
We
don't
want
to
install
it
and
then
just
have
our
application
going
and
scanning
automatically.
B
I
think
one
of
the
best
things
that
I
like
about
this
is
risk,
because
this
is
something
that
everybody
has
their
own
definition
of
risk
and
in
kubernetes
it
is
slightly
different
right.
You
know
it's
not
the
vms
of
the
past.
We
need
to
look
at
things
like
how
deployments
are
set
up
the
deployment
details,
the
name
space,
the
port
configurations,
what
ports
are
exposed,
things
like
that
that
are
missed,
I
believe-
and
then
I
mean
even
things
like
security
contacts,
secrets
volumes,
specific
image
names
everything's
in
there.
B
And,
of
course,
we
have
your
typical
compliance,
vulnerability
management
violations,
and
one
of
my
favorite
is
the
network
graph.
Let's
check,
I
really
want
to
check
out
the
the
sock
shop
that
I
set
up,
so
you
can
see
the
shop
application
and
the
how
it
is
exposed.
So
obviously
we
have
something
that's
exposed
to
external
entities
and
we
create
network
policies
and
generate
them
as
well,
but
I
don't
want
to
get
too
far
into
this.
I'm
kind
of
saving
like
a
whole
deep
dive
for
next
month.
That
was
supposed
to
be
the
plan.
B
This
was
kind
of
getting
started
getting
into
the
application
looking
for
feedback
from
y'all
that
are
watching,
hopefully
at
next
month's
engineering
meetings
and
yeah.
Any
questions
in
the
chat
would
love
to
hear
from
you.
We
have
a
couple
more
minutes
left,
but
rockhound
thanks
for
joining
and
and
chatting
with
us
on
ocp
would
I
have
different
r
back
roles.
View
admin,
self-defined
roles,
like
argo
ocp,
there
are
different
default
roles
right
so,
instead
of
having
default
service
accounts,
ocp
likes
to
go
and
change
those,
especially
per
namespace.
B
That
is
actually
a
security
feature,
because
you
don't
want
default
service
account
mounted
into
every
single
pod.
Stackrocks
will
actually
alert
on
something
like
that
if
you're
using
the
default
service
account.
So
it
is
definitely
it's
different
in
terms
of
just
being
able
to
go
and
deploy,
but
in
general,
most
applications
can
deploy
freely
and
that
not
to
get
too
preachy,
but
that
is
kind
of
the
big
difference
between
vanilla,
k8s
and
something
that's
an
enterprise
version
of
kubernetes
right.
It's
a
little
bit
more
security
guard
rails
yeah.
B
Yeah
overall,
that's
that's
one
of
my
favorite
ways
to
deploy
it
if
you're,
just
looking
to
check
it
out
on
a
vanilla,
k8
cluster
use
that
deploy
script,
pull
the
password,
you
can
run
a
port
forward
as
well.
You
don't
have
to
expose
it
publicly
using
a
load
balancer
or
anything
like
that,
although
it
is
fairly
easy
with
the
simple
command
anything
else
I
missed
mathias.
B
A
Yeah,
so
let
me
think,
but
honestly
I
like
the
deploy
script,
especially
for
the
for
the
death
builds.
I
would
still,
I
would
always
say,
deploy.
Script
for
development
is
a
great
idea
because
you
have
so
much
quality
of
life.
It
just
is
a
one-stop
shop.
You
run
it
and
you
basically
don't
need
to
worry
about
anything
else.
Besides
that
we
are
currently
ironing
out
some
some
smaller
wrinkles
around
the
whole
open
source,
open
source,
yeah
we're
calling
it
flavor,
so
the
all
whole
open
source
edition
yeah
the.
A
Is
is
still
a
work
in
progress
where
we're
actively
chipping
away
in
our
current
development
sprints
on
that,
so
there
is
more
to
come.
We're
we're
not
stopping
here,
we're
we're
actually
planning
a
lot
of
things
that
might
that
will
improve
the
whole
usability
and
onboarding
experience
or
deployment
experience
for
the
open
source
and
community
editions.
B
Would
say
yeah,
I
think
one
of
the
other
biggest
things
is
like
we
showed
on
the
on
the
github
repository.
There
is
an
issues
list.
So
if
you
see
something,
we
would
love
for
you
to
say
something.
It's
one
thing
to
post
it
in
slack
and
say:
hey.
I
don't
know
how
to
do
this,
but
if,
if
you
really
want
a
lot
of
eyes
on
it
and
some
actionable
intel,
I
would
recommend
you
go
and
open
an
issue
and
say
hey,
michael
matthias.
This
thing
is
not
as
simple
as
you
make
it
out
to
be.
A
If
that
issue
is
if
we
need
some
more
information
or
what
what
will
happen
with
the
issue
and
as
soon
as
we're?
Okay
with
the
issue,
we
have
all
the
information
that
we
need.
We
will
take
this
issue
and
basically
relay
it
to
the
internal
engineering
and
discuss
with
them,
and
then
I
guess,
yeah
and
then
we'll
come
back
in
the
next
community
meeting
and
basically
be
open
for
discussion.
We
are
we
come
prepare.
A
B
And
to
get
up
to
date
on
the
calendar,
if
you're
in
google
outlook,
whatever
calendar
you're
using
you,
can
subscribe
community
stackrocks.com,
I
need
to
like
a
little
blurb
that
pops
up
in
this,
so
everybody
can
yeah
if
you're,
red
hat,
there's
of
course
another
way
to
log
issues.
That's
true!
If
you're
using
rhcs,
there
is
the
internal
site.
B
That's
that's
all
I'm
thinking
about
oh
yeah,
and
if
you
join
the
engineering
meetings,
we
do
have
monthly
rock
stars,
so
there
will
be
swag
that
gets
handed
out
the
more
issues
and
the
more
you
contribute,
the
more
likely
you
are
to
become
a
rock
star.
So
we
appreciate
everybody
that
helps
out.
We
understand
that
you
are
also
volunteering.
Your
time
when
you
open
up
issues
and
complaining
complaining
to
us
is
actually
extremely
valuable.
B
A
B
That's
for
sure,
until
then
check
us
on
the
slack
channel
or
we'll
see
you
the
second
tuesday
next
month
at
12
p.m,
eastern
in
zoom
and
I'll,
be
posting
the
slack
channel
and
on
linkedin
as
well
to
make
sure
you
guys
get
the
link
thanks,
everyone
for
all
the
questions
and
comments,
and
we
hope
to
see
you
next
month
as
we
walk
through
next
month.
The
plan
is
to
walk
through
the
dashboard
and
really
show
you
all
the
tips
and
tricks
on
how
to
use
stackrock.