https://github.com/suse/cap-terraform
Terraform templates for deploying SUSE Cloud Application Platform
https://github.com/suse/cap-terraform
Last synced: 27 days ago
JSON representation
Terraform templates for deploying SUSE Cloud Application Platform
- Host: GitHub
- URL: https://github.com/suse/cap-terraform
- Owner: SUSE
- Created: 2019-07-04T09:20:37.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2021-03-10T19:24:00.000Z (about 4 years ago)
- Last Synced: 2025-03-26T18:54:34.795Z (about 1 month ago)
- Language: HCL
- Homepage:
- Size: 391 KB
- Stars: 7
- Watchers: 13
- Forks: 13
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# End-to-end CAP deployment for public cloud platforms with Terraform
The goal is to setup a cluster, configure dependencies(storage classes, helm 3) and perform helm installs for CAP, Stratos and Metrics.
In cap-1.5.x, UAA and SCF are deployed with an nginx Ingress Controller but Stratos and Metrics are deployed with LoadBalancer services. Let's Encrypt issued certificates are used for UAA/SCF but self-signed certificates are used for Stratos and Metrics deployments.
**For cap-2.x you must use Terraform 0.13**. The CAP, Stratos and Metrics services are exposed through a single Ingress Controller with different ingress rules. The top-level domain is the same for all deployments, Stratos is deployed with a stratos subdomain and Metrics with a metrics subdomain so they can be accessed at stratos.yourdomain.com and metrics.yourdomain.com FQDNs. Let's Encrypt certificates are issued for CAP, Stratos and Metrics.
The inputs are provided through terraform variables (for use with [blue-horizon](https://github.com/SUSE-Enceladus/blue-horizon)). For details on how to use the templates for specific providers see the respective READMEs in the provider directories.