-
Notifications
You must be signed in to change notification settings - Fork 595
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
[Octavia-ingress-controller] CI not exist? #2247
Comments
we have tests/e2e/cloudprovider/test-lb-service.sh file but I think it's for OCCM/LB only test |
Indeed it seems so. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale Yes, we're still missing a CI here. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
seems no CI for ingress controller? no e2e for #2246
checked original CI and still not find it , so not sure someone early than me know the history
https://github.com/theopenlab/openlab-zuul-jobs/tree/master/playbooks
@dulek @mdbooth FYI
What you expected to happen:
How to reproduce it:
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: