We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug When deploy a route object with ArgoCD the kind:route is showing without a quick link to the route address like ingress.
And from time to time the object itself disappear from the UI at all and then returns with no understandable pattern.
To Reproduce Steps to reproduce the behavior: Deploy a route object with ArgoCD.
See that no quick link to the route address. Try to stop and start the argo server and see if the route item disappears.
Expected behavior Any route object should have a quick link to the route address so it can be easily accessible via the ArgoCD UI
Objects shouldn't disappear from the UI.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
When deploy a route object with ArgoCD the kind:route is showing without a quick link to the route address like ingress.
And from time to time the object itself disappear from the UI at all and then returns with no understandable pattern.
To Reproduce
Steps to reproduce the behavior:
Deploy a route object with ArgoCD.
See that no quick link to the route address.
Try to stop and start the argo server and see if the route item disappears.
Expected behavior
Any route object should have a quick link to the route address so it can be easily accessible via the ArgoCD UI
Objects shouldn't disappear from the UI.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: