chore: update master with rc1 - #3014
Conversation
Greptile SummaryThe PR advances Network Operator and component release references from 26.7.0-beta.5 to 26.7.0-rc.1, including the previously stale Helm chart metadata.
Confidence Score: 4/5The PR is not yet safe to merge because its rc.1 release sources still produce a tracked OLM bundle identified as beta.5. The Helm metadata is fixed, but the packaged ClusterServiceVersion retains the beta.5 name and spec.version, so publishing this commit's OLM bundle would misidentify the rc.1 release. Files Needing Attention: hack/release.yaml and bundle/manifests/nvidia-network-operator.clusterserviceversion.yaml Important Files Changed
Reviews (2): Last reviewed commit: "chore: update master with rc1" | Re-trigger Greptile |
| image: network-operator | ||
| repository: nvcr.io/nvstaging/mellanox | ||
| version: v26.7.0-beta.5 | ||
| version: v26.7.0-rc.1 |
There was a problem hiding this comment.
Stale chart version mixes releases
When a Helm installation does not override operator.tag, the unchanged Chart.appVersion selects the beta.5 operator image while this release manifest and component defaults select rc.1, causing a mixed-version deployment and leaving generated Helm and OLM artifacts labeled beta.5.
Knowledge Base Used: Deployment and Manifests
Signed-off-by: Fred Rolland <frolland@nvidia.com>
| @@ -8,21 +8,21 @@ | |||
| NetworkOperator: | |||
| image: network-operator | |||
| repository: nvcr.io/nvstaging/mellanox | |||
There was a problem hiding this comment.
When the OLM bundle is published for this rc.1 release, the unchanged ClusterServiceVersion still uses nvidia-network-operator.v26.7.0-beta.5 and version: 26.7.0-beta.5, causing OLM to identify the rc.1 artifact as the previous beta release.
Knowledge Base Used: Deployment and Manifests
|
/retest-all |
No description provided.