Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Align deployment yaml #645

Merged
merged 1 commit into from
Oct 18, 2023
Merged

Conversation

rollandf
Copy link
Member

Align the operator deployment yamls between
the Helm template and the kubebuilder generated
yaml in config/manager/manager.yaml.

Align the operator deployment yamls between
the Helm template and the kubebuilder generated
yaml in `config/manager/manager.yaml`.

Signed-off-by: Fred Rolland <frolland@nvidia.com>
@adrianchiris adrianchiris merged commit 33a2937 into Mellanox:master Oct 18, 2023
14 of 15 checks passed
adrianchiris added a commit that referenced this pull request Oct 31, 2023
Remove `control-plane: {{ .Release.Name }}-controller` selector from the
network-operator object in the helm chart
to fix helm upgrade behaviour.

With the current selector we will have the following error when trying
to upgrade from the latest GA version (23.7)

```
helm upgrade -n nvidia-network-operator network-operator ./network-operator -f myvalues.yaml 
Error: UPGRADE FAILED: cannot patch "network-operator" with kind Deployment: Deployment.apps "network-operator" is i
nvalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"n
etwork-operator", "app.kubernetes.io/name":"network-operator", "control-plane":"network-operator-controller"}, Match
Expressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable       

```

The extra selector was added as a part of
#645
@rollandf rollandf deleted the align-manager branch February 28, 2024 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants