0.144.0
💡 Enhancements 💡
-
operator: change operator args in bundle to env variables (#4612)
The default configuration in the OLM bundle has been changed from command-line arguments to environment variables,
making it easily overwritable when deployed using OLM's Subscription config. Command-line flags continue to work.
All Config struct fields now support environment variable configuration.Configuration set via the Subscription's config section will persist and be reapplied after operator upgrades.
Example of overriding configuration via OLM Subscription:
apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: opentelemetry-operator spec: channel: stable name: opentelemetry-operator source: operatorhubio-catalog sourceNamespace: olm config: env: - name: FEATURE_GATES value: "operator.networkpolicy,operand.networkpolicy" - name: ENABLE_GO_AUTO_INSTRUMENTATION value: "true" - name: METRICS_SECURE value: "false"
🧰 Bug fixes 🧰
collector: Fix PodDisruptionBudget using all labels instead of selector labels, preventing PDB breakage during rollouts (#4623)
Use stable selector labels instead of all CR labels to prevent PDB breakage when mutable labels change during rollouts.auto-instrumentation: Fix NGINX and Apache instrumentation init container creation to avoid copying init-container-incompatible fields. (#3729)
The NGINX and Apache instrumentation init containers are now created from scratch instead of
cloning the main container, preventing probes, lifecycle hooks, and resize policies from being
applied to init containers.