-
Notifications
You must be signed in to change notification settings - Fork 26
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
OpenShift CI upstream #1125
Comments
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
I think we want to re-visit this as a part of adding more CI for cloud providers. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
There are now options to run custom GHA runners with big systems that might be able to run OpenShift. We've also hit lots of issues trying to reduce RBAC upstream and test those changes with OpenShift downstream, which showed this to be a priority. Re-doing the issue to be more generic about OpenShift in CI, will look into both methods. |
We need a way to do OpenShift testing upstream, without having to build upstream and send it to downstream QE for OpenShift testing.
We may be able to do this with GHA custom runners, or we may want to do this on a cloud provider like AWS.
Original:
Figure out how to give AWS credentials from CI so we can add AWS deploys GHA.
https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect should allow us to give a GHA access to AWS without storing credentials even in GH secrets.
Pre-populated templates work very well for non-interactive
openshift install
, that’s what I use all the time.Originally posted by @skitt in #1014 (comment)
The text was updated successfully, but these errors were encountered: