odiglet
is installed.
This works fine in static clusters — but in Karpenter-managed clusters, this causes a problem:
odiglet
is installed by a DaemonSet after the node is created.odigos.io/odiglet-installed=true
is only added to the node at runtime.odigos.io/needs-init=NoSchedule
).
odiglet
removes this taint after it prepares the node for instrumentation.spec.template.spec.startupTaints
:
startupTaints
, use the following command:
<NODEPOOL_NAME>
with the actual name of your Karpenter NodePool.
odiglet
DaemonSet: