Bug Description
When updating profile information, old keys to not get removed. I had a profile with
resources:
hard:
limits.cpu: "128"
limits.memory: "1.5Ti"
limits.requests.storage: "1Ti"
nvidia.com/gpu: "4"
This was synced as expected. Then I prepended limits. to the profile:
resources:
hard:
limits.cpu: "128"
limits.memory: "1.5Ti"
limits.requests.storage: "1Ti"
limits.nvidia.com/gpu: "4"
Now the profile has both keys and looks like this:
resourceQuotaSpec:
hard:
limits.cpu: "128"
limits.memory: 1.5Ti
limits.nvidia.com/gpu: "4"
limits.requests.storage: 1Ti
nvidia.com/gpu: "4"
I believe the nvidia.com/gpu should be removed.
To Reproduce
- put the first profile from above into git and run sync
- verify
kubectl get profiles -o yaml
- change the profile to the second one from above
- check
kubectl get profiles -o yaml again
Environment
App Version Status Scale Charm Channel Rev Address Exposed Message
github-profiles-automator active 1 github-profiles-automator latest/edge 230 10.152.43.67 no
Relevant Log Output
Additional Context
No response
Bug Description
When updating profile information, old keys to not get removed. I had a profile with
This was synced as expected. Then I prepended
limits.to the profile:Now the profile has both keys and looks like this:
I believe the
nvidia.com/gpushould be removed.To Reproduce
kubectl get profiles -o yamlkubectl get profiles -o yamlagainEnvironment
App Version Status Scale Charm Channel Rev Address Exposed Message
github-profiles-automator active 1 github-profiles-automator latest/edge 230 10.152.43.67 no
Relevant Log Output
.Additional Context
No response