Skip to content
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

Add task for OCP (or OSD) cluster provisioning in GCP #33

Closed
Tracked by #57
trepel opened this issue Jul 24, 2024 · 1 comment · Fixed by #55
Closed
Tracked by #57

Add task for OCP (or OSD) cluster provisioning in GCP #33

trepel opened this issue Jul 24, 2024 · 1 comment · Fixed by #55
Assignees

Comments

@trepel
Copy link
Collaborator

trepel commented Jul 24, 2024

Summary

This task should provision a new OCP/OSD cluster backed by GCP.

One way of doing this I am aware of is to use openshift-install cli tool. Other way is to use ocm tool to create OSD cluster in GCP. I would probably go with latter approach (OSD) because we also need to test on OSD. On the other hand the former approach is similar to AWS #7 so that is should be relatively simple to implement GCP once AWS is complete.

The end goal is to have a pipeline capable of creating cluster, installing Kuadrant, running tests, cleaning up. So do also an OCP cleanup task as part of this.

Documentation
https://docs.openshift.com/container-platform/4.16/installing/installing_gcp/preparing-to-install-on-gcp.html (OCP)

Parent Epic
#57

https://docs.openshift.com/dedicated/osd_install_access_delete_cluster/creating-a-gcp-cluster.html (OSD)

@github-project-automation github-project-automation bot moved this to 🆕 New in Kuadrant QE Jul 24, 2024
@trepel trepel self-assigned this Jan 28, 2025
@trepel trepel moved this from 🆕 New to 🏗 In progress in Kuadrant QE Jan 28, 2025
@trepel
Copy link
Collaborator Author

trepel commented Jan 28, 2025

Decision was made to go with OSD. Reason: OCP is more trickier to automate since for OCP you need to store files generated by the installer that are used later for cluster removal.

@trepel trepel moved this from 🏗 In progress to In Review in Kuadrant QE Jan 28, 2025
@trepel trepel linked a pull request Feb 5, 2025 that will close this issue
@github-project-automation github-project-automation bot moved this from In Review to ✅ Done in Kuadrant QE Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant