Open llavaud opened 7 months ago
After some tests, I noticed that if I take the ownership on the spec.template.spec.containers.image
field using the following command, Argo CD succeed to do the diff.
apiVersion: apps/v1
kind: Deployment
metadata:
name: foo
spec:
template:
spec:
containers:
- name: foo
image: <my_image>
kubectl -f deployment.yaml --server-side --field-manager='myself'
I guess, if the image field is managed by another controller, it is added when doing the server-side diff otherwise if no one manage this field and as the respectIgnoreDifferences is active, the image field is not added and cause the invalid manifest error, so not sure it is a bug, seems more like the normal behavior of the server-side feature, don't know if Argo can manage this situation in some way...
Describe the bug
An application that set an
ignoreDifferences
on a required field of a manifest spec will fail to diff if bothRespectIgnoreDifferences
andServerSideDiff
are enabledTo Reproduce
Create an application with the following spec:
Expected behavior
Diff app without errors
Version
Logs