search

argoproj-labs / argocd-operator

A Kubernetes operator for managing Argo CD clusters.
https://argocd-operator.readthedocs.io
Apache License 2.0
630 stars 712 forks source link

Support installation on OpenShift/OKD >= 4.14 without DeploymentConfig #1359

Open psy-q opened 4 months ago

psy-q commented 4 months ago

DeploymentConfig is deprecated starting with OpenShift/OKD 4.14 and should no longer be used.

Is your feature request related to a problem? Please describe.

Trying to install the Argo CD operator on such a cluster without DeploymentConfig enabled results in argocd-operator-controller-manager crashlooping with:

ERROR setup problem running manager {"error": "failed to wait for argocd caches to sync: timed out waiting for cache to be synced for Kind *v1.DeploymentConfig"}

Describe the solution you'd like Ensure the operator works on OCP/OKD clusters that don't have the DeploymentConfig capability enabled. Normal Kubernetes Deployment manifests can be used instead.

Describe alternatives you've considered None, since the resource is already deprecated and will be removed from OpenShift/OKD soon.

svghadi commented 4 months ago

Thank you @psy-q for creating the issue. We have some on-going efforts to address this in https://github.com/argoproj-labs/argocd-operator/pull/1329.

ti8m-dah commented 2 months ago

Hi all

Sorry to bump this, but we ran into this on a new cluster as well. From what I can tell the "fixing" Pull Request was merged and "released" as part of 0.11.0, however, that versions seems to be not available, from neither the OperatorHub nor the community operators. Since there is no documentation regarding the release process, I was wondering if the release is still being staged or if something else is missing?

Thank you for any insights you could provide!

svghadi commented 2 months ago

Hi @ti8m-dah, Sorry for the confusion. We have cut a GitHub release for 0.11.0, however, the operator is not yet available on OperatorHub or the community operators. The current release process for the operator is manual, which sometimes leads to delays. We are in the process of streamlining our release pipeline to automate it for quicker releases and better visibility for users.

As for 0.11.0 release, it should be available on OperatorHub in next few weeks. I will communicate here once it's released.

ti8m-dah commented 2 months ago

Hi @svghadi

Thank you for your response and resolving the confusion! I know the pain too well for not automated release workflows, sadly I have no experience with releasing OperatorSDK projects, otherwise I would been happy to support with GitHub Action know-how.

svghadi commented 1 month ago

Hi @ti8m-dah, The 0.11.0 version of the operator is now available on OpenShift Community Operators. However, due to a backend issue on the OperatorHub side, the latest version is not yet available for Kubernetes users. We are following up with the OperatorHub team on this.

ti8m-dah commented 1 month ago

Hi @svghadi

Thank you very much for the update and best of luck with the fix for the OperatorHub!