Description
Syncing the following resource
apiVersion: apps.openshift.io/v1
kind: DeploymentConfig
metadata:
name: example
spec:
selector:
app: httpd
replicas: 2
template:
metadata:
labels:
app: httpd
spec:
containers:
- name: httpd
image: >-
image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest
ports:
- containerPort: 8080
resources:
limits:
cpu: '1'
memory: '1.2G'
will be constantly in an OutOfSync condition.
Expected behavior
Resource is in Synced status, without any drift
To reproduce:
1) Put the above resource in a Git repository (or use resource in repository https://github.com/jannfis/test-multi-app/blob/main/openshift/deploymentconfig/dc.yaml)
2) Create an Argo CD app
3) Sync the app
4) Oberve OutOfSync due to several factors
Workaround
Set known types for DeploymentConfig resource in argocd-cm:
resource.customizations.knownTypeFields.apps.openshift.io_DeploymentConfig: | - field: spec.template.spec type: core/v1/PodSpec
- relates to
-
GITOPS-1303 [ArgoCD] feat: Argo UI Identifies OpenShift objects, such as Route and DeploymentConfig
-
- Closed
-
-
GITOPS-2673 Argo CD Application controller is stuck Syncing applications
-
- Closed
-
-
-
- Closed
-