You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document a way to run the plugin and the sidecar with logLevel=debug #514
I think specifying the envs could be enough? In that case we should only document the usage
// InstanceSidecarConfiguration defines the configuration for the sidecar that runs in the instance pods.
type InstanceSidecarConfiguration struct {
// The environment to be explicitly passed to the sidecar
// +optional
Env []corev1.EnvVar `json:"env,omitempty"`
// The retentionCheckInterval defines the frequency at which the
// system checks and enforces retention policies.
// +kubebuilder:default:=1800
// +optional
RetentionPolicyIntervalSeconds int `json:"retentionPolicyIntervalSeconds,omitempty"`
// Resources define cpu/memory requests and limits for the sidecar that runs in the instance pods.
// +optional
Resources corev1.ResourceRequirements `json:"resources,omitempty"`
}
Activity
armru commentedon Sep 9, 2025
I think specifying the envs could be enough? In that case we should only document the usage
alexklibisz commentedon Sep 9, 2025
This is pretty much a dupe of #497, which was left unanswered.
To my knowledge the env vars do not dictate logging. Logging is dictated via the CLI arg
--log-levelon themanager. Hence my request in #501.I've documented a workaround here: #501 (comment)
feat: introduce `logLevel` setting to control verbosity (#536)
feat: introduce `logLevel` setting to control verbosity (cloudnative-…
feat: introduce `logLevel` setting to control verbosity (cloudnative-…
feat: introduce `logLevel` setting to control verbosity (cloudnative-…