mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
21 lines
1.2 KiB
Plaintext
21 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/optimization/optimizing-cpu-usage.adoc
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="running-services-with-encapsulation_{context}"]
|
|
= Running additional services in the encapsulated namespace
|
|
|
|
Any monitoring tool that relies on the ability to run in the host operating system and have visibility of mount points created by kubelet, CRI-O, or containers themselves, must enter the container mount namespace to see these mount points. The `kubensenter` script that is provided with {product-title} executes another command inside the Kubernetes mount point and can be used to adapt any existing tools.
|
|
|
|
The `kubensenter` script is aware of the state of the mount encapsulation feature status, and is safe to run even if encapsulation is not enabled. In that case the script executes the provided command in the default mount namespace.
|
|
|
|
For example, if a systemd service needs to run inside the new Kubernetes mount namespace, edit the service file and use the `ExecStart=` command line with `kubensenter`.
|
|
|
|
[source,terminal]
|
|
----
|
|
[Unit]
|
|
Description=Example service
|
|
[Service]
|
|
ExecStart=/usr/bin/kubensenter /path/to/original/command arg1 arg2
|
|
----
|