Unable to install fresh on OKD 4.15 about argo-cd HOT 3 CLOSED

I believe the "Red Hat way" to install Argo CD is to use the Argo CD Operator

But I'll let @ishitasequeira @jannfis or @sabre1041 take a look in case they have a workaround.

from argo-cd.

@christianh814 @EdwardCooke A couple areas to unpack here

1. @EdwardCooke The issue that you are facing is that OpenShift's default security posture does not allow the use of fixed UID's which aligns to the failures that you are seeing
2. The Argo CD Operator, as @christianh814 has the best supportability for an OpenShift/OKD perspective. However, most of the available Argo CD installation methods can be used to install on OpenShift (with some considerations in mind). For example, Kustomize can be used in combination with the raw manifests or the Helm chart to customize the resources for deployment on OpenShift
3. It is challenging for any project with the adoption that Argo CD has attained to have a fully compatible deployment on every platform and operating environment. OpenShift is just one example. But other environments might make use of policies that inhibit the use of Argo CD (such as Validating/Mutating Webhooks). @EdwardCooke If there is a hard requirement of the Redis image to use a fixed UID, you could look to leverage an alternative source with better support for randomized UID's as OpenShift's default security expects

from argo-cd.

Closing as this is a provider platform specific issue. If you need to change the default manifest of ArgoCD to conform with your cluster/provider restrictions, you can use Kustomize or Helm to configure the default manifest, then deploy them.

You can see a basic example of an ArgoCD deployment with Kustomize here argoproj/argoproj-deployments@HEAD/argocd or you can take a look at the helm chart here argoproj/argo-helm@main/charts/argo-cd

from argo-cd.