:_mod-docs-content-type: PROCEDURE
[id="modifying-kubelet-one-time_{context}"]
= Modifying the kubelet as a one-time scenario

To modify the kubelet in a one-time scenario without rebooting the node due to the change of `machine-config(spec":{"paused":false}})`, allowing you to modify the kubelet without affecting the service, follow this procedure.

.Procedure

. Connect to the node in debug mode:
+
[source,terminal]
----
$ oc debug node/<node>
----
+
[source,terminal]
----
$ chroot /host
----
+
Alternatively, it is possible to SSH to the node and become root.

. After access is established, check the default log level:
+
[source,terminal]
----
$ systemctl cat kubelet
----
+
.Example output
[source,terminal]
----
# /etc/systemd/system/kubelet.service.d/20-logging.conf
[Service]
Environment="KUBELET_LOG_LEVEL=2"
----

. Define the new verbosity required in a new `/etc/systemd/system/kubelet.service.d/30-logging.conf` file, which overrides `/etc/systemd/system/kubelet.service.d/20-logging.conf`. In this example, the verbosity is changed from `2` to `8`:
+
[source,terminal]
----
$ echo -e "[Service]\nEnvironment=\"KUBELET_LOG_LEVEL=8\"" > /etc/systemd/system/kubelet.service.d/30-logging.conf
----

. Reload systemd and restart the service:
+
[source,terminal]
----
$ systemctl daemon-reload
----
+
[source,terminal]
----
$ systemctl restart kubelet
----

. Gather the logs, and then revert the log level increase:
+
[source,terminal]
----
$ rm -f /etc/systemd/system/kubelet.service.d/30-logging.conf
----
+
[source,terminal]
----
$ systemctl daemon-reload
----
+
[source,terminal]
----
$ systemctl restart kubelet
----

