Skip to content

Commit 8407ce7

Browse files
authored
Merge pull request #29372 from hashicorp/link_multicloud_tutorial_from_use_cases
Link multi-cloud K8s tutorial from use cases page
2 parents 1206298 + fae0567 commit 8407ce7

File tree

1 file changed

+17
-9
lines changed

1 file changed

+17
-9
lines changed

website/intro/use-cases.html.markdown

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,23 @@ description: |-
1010

1111
This page lists a subset of use cases for [Terraform](/intro/index.html).
1212

13+
## Multi-Cloud Deployment
14+
15+
It's often attractive to spread infrastructure across multiple clouds to
16+
increase fault-tolerance. By using only a single region or cloud provider,
17+
fault tolerance is limited by the availability of that provider. Multi-cloud
18+
deployment allows for more graceful recovery of the loss of a region or entire
19+
provider.
20+
21+
Realizing multi-cloud deployments can be very challenging as many existing
22+
tools for infrastructure management are cloud-specific. Terraform is
23+
cloud-agnostic and allows a single configuration to be used to manage multiple
24+
providers, and to even handle cross-cloud dependencies. This simplifies
25+
management and orchestration, helping operators build large-scale multi-cloud
26+
infrastructures.
27+
28+
> **Hands-on:** Try the [Deploy Federated Multi-Cloud Kubernetes Clusters](https://learn.hashicorp.com/tutorials/terraform/multicloud-kubernetes) tutorial on HashiCorp Learn.
29+
1330
## Heroku App Setup
1431

1532
Heroku is a popular PaaS for hosting web apps. Developers create an app, and then attach add-ons, such as a database, or email provider. One of the best features is the ability to elastically scale the number of dynos or workers. However, most non-trivial applications quickly need many add-ons and external services.
@@ -82,12 +99,3 @@ Terraform is not limited to physical providers like AWS. Resource schedulers
8299
can be treated as a provider, enabling Terraform to request resources from them.
83100
This allows Terraform to be used in layers: to setup the physical infrastructure
84101
running the schedulers as well as provisioning onto the scheduled grid.
85-
86-
## Multi-Cloud Deployment
87-
88-
It's often attractive to spread infrastructure across multiple clouds to increase fault-tolerance. By using only a single region or cloud provider, fault tolerance is limited by the availability of that provider. Multi-cloud deployment allows for more graceful recovery of the loss of a region or entire provider.
89-
90-
Realizing multi-cloud deployments can be very challenging as many existing tools
91-
for infrastructure management are cloud-specific. Terraform is cloud-agnostic
92-
and allows a single configuration to be used to manage multiple providers, and
93-
to even handle cross-cloud dependencies. This simplifies management and orchestration, helping operators build large-scale multi-cloud infrastructures.

0 commit comments

Comments
 (0)