cigna-asoria

These are the API's that will be deprecated: `customresourcedefinitions.v1beta1.apiextensions.k8s.io` `ingresses.v1beta1.extensions` and its being called by `system:serviceaccount:argocd:argocd-application-controller argocd-application-controller/v0.0.0` according to https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22 `apiextensions.k8s.io/v1beta1` manifest should be update to `apiextensions.k8s.io/v1` `extensions/v1beta1` and `networking.k8s.io/v1beta1`...

Thanks @KrustyHack - that would be great information. I was working with RedHat on another similar issue with an operator though not the same as ArgoCD. But what was interesting...

Only 12 issues listed and yet no updates? Can someone please assist

Hi @davgordo - I did not install the cert-utils operator through Helm. I actually installed it through OperatorHub UI via the OpenShift Console. Can I provide you with any additional...

@davgordo - We do have cert-manager installed and I just checked, there is no certificate for cert-utils like the one provided in https://github.com/redhat-cop/cert-utils-operator/blob/v1.3.10/config/helmchart/templates/certificate.yaml Let me get the data your requested

Here is the service yaml, for DNS, how do I pull that information? I can't provide the secret since it contains certificates. I did remove the UID and IP's below....

Here is the DNS output. Downloads % openssl x509 -in cert.crt -text -noout |grep DNS DNS:cert-utils-operator-controller-manager-metrics-service.openshift-operators.svc, DNS:cert-utils-operator-controller-manager-metrics-service.openshift-operators.svc.cluster.local Downloads %

@davgordo - I provided the information above. All seems right so why did Prometheus use the wrong server_name?

@davgordo - cert-utils is installed under `openshift-operators ` **not** `cert-utils-operator` - that is why i think we are running into this issue.

@davgordo No, we don't have a namespace called `cert-utils-operator` -- Let me check where I can pull the `ServiceMonitor`