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
fix: honor insecureSkipTLS in OCI storage secret (rancher#4890)
Fleet currently reads the legacy `insecure` field from the OCI storage
secret. If the secret is created with `insecureSkipTLS: true`, that
value is not recognized, so Fleet agents still perform TLS verification
and may fail against registries using a self-signed/private CA.
This change:
- prefers `insecureSkipTLS`
- keeps `insecure` as a backward-compatible fallback
- updates test coverage to use `insecureSkipTLS`
This is intended to be a minimal fix for OCI storage secret parsing and
avoids breaking existing setups that may still use the legacy `insecure`
field.
Co-authored-by: Corentin Néau <tan.neau@suse.com>
(cherry picked from commit 3951853)
// getBoolValueFromSecretWithFallback extracts a boolean value from data, using keys in the provided order of priority, and returns the first found value, if any.
119
+
// If no value is found, the function returns false, with an error if the value was required.
0 commit comments