Make continuing development of the opentofu configuration easier once we are actively using the zuul project's resources by ensuring that the automation can be configured to target a different project. This should mostly mean we need to expose more optional variables to the caller.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bd808 | T396247 Set up new project for Zuulv3+ pre-merge and non-image-build workloads | |||
| Resolved | bd808 | T396936 Provision Kubernetes cluster and bastion using OpenTofu and Magnum | |||
| Open | None | T399768 Make it possible to target other Cloud VPS projects with the zuul tofu automation |
Event Timeline
Comment Actions
bd808 opened https://gitlab.wikimedia.org/repos/releng/zuul/tofu-provisioning/-/merge_requests/32
kubernetes: use calico network driver
Comment Actions
bd808 merged https://gitlab.wikimedia.org/repos/releng/zuul/tofu-provisioning/-/merge_requests/32
kubernetes: use calico network driver