Repository navigation
ci: update nic-configuration-operator version to b2975b4 (of branch main) - #3586
nvidia-ci-cd wants to merge 1 commit into
Conversation
Signed-off-by: nvidia-ci-cd <svc-cloud-orch-gh@nvidia.com>
[Medium impact] The update reaches NIC configuration operator deployments using these defaults or examples. Refresh the bundled CRDs before merging so users can request eight Spectrum-X planes. Findings
SummaryUpdates the NIC configuration operator and daemon to
Reviews (1) · Last reviewed commit: "ci: update nic-configuration-operator ve..." · Reviewed by Greptile |
| crdSourceLocation: config/crd/bases | ||
| crdTargetLocation: manifests/state-nic-configuration-operator | ||
| version: network-operator-v26.10.0-beta.5 | ||
| version: b2975b4 |
There was a problem hiding this comment.
Eight-plane templates are rejected
b2975b4 includes the fix to allow eight Spectrum-X planes, but this update leaves the bundled NicConfigurationTemplate schema unchanged. Its numberOfPlanes enum still permits only 1, 2, and 4. The Network Operator installs that schema alongside the new images, so Kubernetes rejects templates with numberOfPlanes: 8 before the updated component can use them. Refresh the bundled CRDs with this version bump.
Knowledge Base Used: Deployment and release packaging
Automated CI update for component 'nic-configuration-operator', created by GitHub actions reusable workflow run 40477232435 for release branch main.
Component updates
nicConfigurationOperator
hack/release.yaml:network-operator-v26.10.0-beta.5b2975b4Commits from
network-operator-v26.10.0-beta.5tob2975b4:nicConfigurationConfigDaemon
hack/release.yaml:network-operator-v26.10.0-beta.5b2975b4Commits from
network-operator-v26.10.0-beta.5tob2975b4: