You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are having trouble connecting our gitlab certificate to our argocd repository to configure our application. We tried manually installing our gitlab certificate into our config map in the install.yaml file and deploying our application. We are currently using Azure Gateway Ingress Controller to setup our backend pool and listeners. We know it's not our network configuration because we are able to connect our repository with the no verify option when connecting the gitlab repository. Past that point we are unable to deploy applications because argo does not allow for the no verification option when it comes to deploying the application itself. Below we are sending our configuration files for install.yaml.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are having trouble connecting our gitlab certificate to our argocd repository to configure our application. We tried manually installing our gitlab certificate into our config map in the install.yaml file and deploying our application. We are currently using Azure Gateway Ingress Controller to setup our backend pool and listeners. We know it's not our network configuration because we are able to connect our repository with the no verify option when connecting the gitlab repository. Past that point we are unable to deploy applications because argo does not allow for the no verification option when it comes to deploying the application itself. Below we are sending our configuration files for install.yaml.
santizeargocd.txt
Beta Was this translation helpful? Give feedback.
All reactions