►
Description
In this video we'll present how to increase logs level of the different Red Hat OpenShift Sandboxed Containers to "debug", then, the enhanced logging can be viewed in the node's journal or to be collected by the must-gather tool.
Learn more: https://www.redhat.com/en/openshift-sandboxed-containers
A
Hello
in
this
video,
I
will
demonstrate
how
to
enable
debug
level
login
for
openshift
sandbox
containers
at
runtime.
Multiple
cata
and
virtualization
components
are
running
under
the
hood,
such
as
scatter
runtime,
catagen,
qmu
and
wheelchair
fsd.
By
default.
Most
of
these
are
printing
limited
amount
of
log
types,
mostly
aero
and
warning
locks,
and
here
we'll
learn
how
to
enhance
logging
and
print
also
debug
level
logs.
A
Currently,
in
order
to
set
openshift
sandbox
container
components
to
print
their
logs
at
debug
level,
we
should
set
also
cryo's
log
level
to
debug.
In
order
to
do
that,
we
will
use
the
following
container
runtime
config
custom
resource
which
allows
you
to
customize
container,
run
time
configuration,
and
in
this
case
we
will
change
the
configuration
of
the
runtime
log
level
to
debug
on
each
of
the
worker.
Now
using
machine,
config
pull
selector.
A
A
Now
all
local
nodes,
cryo
instances
as
the
backlog
level
set
from
now
on
each
deployed
sandboxed
workload,
allows
the
cutter
components
running
it
to
print
the
logs
a
debug
level
note
that
a
new
configuration
will
be
applied
only
on
newly
created
sandbox
workloads.
Let's
apply
some
sandbox
to
workload.