George Gaál

I did something (like upgrading cert-manager configuration according to https://cert-manager.io/docs/releases/release-notes/release-notes-1.18/#acme-http01-challenge-paths-now-use-pathtype-exact-in-ingress-routes and removing orders/challenges) and now I see: ```bash $ kubectl get certificates -n thinkopp thinkopp -oyaml | yq .status conditions:...

Faced the same issue. ```bash $ kubectl get certificates -n emissary wildcard -oyaml ``` ```yaml status: conditions: - lastTransitionTime: "2025-06-17T06:54:02Z" message: Certificate is up to date and has not expired...

@hawksight it happens in any environment. I checked multiple times. The only thing that works perfectly is self-signed `Issuer` and associated `Certificates`. Regarding the last observation of this nasty thing...

> In the context of ArgoCD, because of the unpredictable order of the elements from a list, an application that creates/reconciles such objects is constantly out of sync ArgoCD bugs....

> ArgoCD Application that is deploying a networkacl object should be in a synced state it's another thing. It is related to kstatus support I believe #1899 The very same...

Also proof that ArgoCD still has an issue with the ordering of the lists: https://github.com/argoproj/argo-cd/issues/12033

@adriananeci thanks, your remark makes sense.

@swapnachagam Hi! I am kindly asking you to add a proper formatting to your issue otherwise it is very difficult to read it. Particularly - indentation of logs and yamls.

@swapnachagam again please fix formatting.

```yaml apiVersion: services.k8s.aws/v1alpha1 kind: AdoptedResource metadata: creationTimestamp: '2024-09-04T16:18:30Z' finalizers: - finalizers.services.k8s.aws/AdoptedResource generation: 1 name: dexp-c-uw2-kinesis-firehose-logs-transformer-test namespace: dexp-c-aws-781371715081 resourceVersion: '1770078' uid: 335f7aff-74ed-4679-960e-78e52f1f732b status: conditions: - status: 'True' type: ACK.Adopted spec: aws:...