-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
-
GitOps Crimson - Sprint 3262, GitOps Crimson - Sprint 3263
Description of problem:
Changing host in the Argo CD CR for Argo CD Server does not update the ingress configuration.
Complete details here - https://github.com/argoproj-labs/argocd-operator/issues/558
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
Do a kubectl apply on something like:
```yaml
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
name: argocd
spec:
server:
ingress:
enabled: true
```
followed by a kubectl apply on something like:
```yaml
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
name: argocd
spec:
server:
host: foo.bar
ingress:
enabled: true
```
then the host will still be set to the default value when describing the ingress.
Actual results:
Expected results:
- Fix the issue in the Argo CD Operator.
- Add tests to validate the change (Unit and E2E)
- Bring the changes to the downstream - GitOps Operator along with the tests.
- Document the fix in the release notes.
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- links to
-
RHEA-2024:139495 Errata Advisory for OpenShift GitOps v1.15.0