-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
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
Allow deployment of vm-console-proxy on Kubernetes #534
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stal |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
First, we need to make |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind enhancement
What happened:
vm-console-proxy can only be deployed on OKD / OpenShift because it relies on certificates injected by OpenShift and the
Route
CRD.What you expected to happen:
SSP should be able to deploy vm-console-proxy on upstream Kubernetes too.
How to reproduce it:
Deploy SSP on a Kubernetes cluster.
Environment:
virtctl version
):kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: