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
Client Version: v1.31.3
Kustomize Version: v5.4.2
Server Version: v1.29.10-eks-7f9249a
Cloud provider or hardware configuration: AWS EKS
OS (e.g. from /etc/os-release): Ubuntu
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
👍 for "I would like to see this bug fixed as soon as possible"
👎 for "There are more important bugs to focus on right now"
The text was updated successfully, but these errors were encountered:
Can you try this patch with kubectl once and see if it works as you expect it to?
The design and approach is inspired from [kubectl patch command](https://github.com/kubernetes/kubectl/blob/0a61782351a027411b8b45b1443ec3dceddef421/pkg/cmd/patch/patch.go#L102C2-L104C1)
Update a container’s image using a json patch with positional arrays kubectl patch pod valid-pod -type='json’ -p=’[{“op”: “replace”, “path”: “/spec/containers/0/image”, “value”:“new image”}]’
Before creating the resource modifier yaml, you can try it out using kubectl patch command. The same commands should work as it is.
What steps did you take and what happened:
I tried to use a resource modifier to add a label to a custom resource, in the following way:
However, this is removing all the previous labels present in the resource, and letting the velero added labels only.
What did you expect to happen:
The modifier should have added the label
alfredo: "true"
to the resourceEnvironment:
<NOT SET>
kubectl version
):AWS EKS
/etc/os-release
):Ubuntu
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: