Repository navigation
Conversation
Preserve existing defaults and support optional startup probes. Assisted-By: GPT-6
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mtomaska The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 23m 34s Warning: |
fernandoroyosanchez
left a comment
There was a problem hiding this comment.
Just a non blocking comment, the rest lgtm
| errors = append(errors, errs...) | ||
| continue | ||
| } | ||
| config.Merge(*probe.override) |
There was a problem hiding this comment.
config.Merge assigns Command by reference (lib-common ProbeConf.Merge: p.Command = overrides.Command), and it flows straight into the final corev1.Probe.Exec.Command. Since probe.override here is spec.Override.Probes.*.Command from the CR spec, a custom command ends up aliasing the cached CR's backing array instead of being copied. The existing test only covers the default-command path, not this one.
Suggest copying the slice before merging (supplied.Command = append([]string(nil), supplied.Command...)), or add a test proving the built probe's Command isn't the same slice as the CR spec's.
This change allows user to configure ovn-controller pod probe intervals (Readiness, liveliness and startup) via CR.
Before this change, these timeout values were hardcoded. There are cases where user need to bump these values when deployment systems are large and ovn-controller take a long time to do initial computations. For example, if pods are restarted
Resolves-Jira: https://redhat.atlassian.net/browse/OSPRH-33460
Assisted-By: GPT-6