Skip to content

Commit b0fc826

Browse files
author
Chanwit Kaewkasi
authored
Merge pull request #3198 from weaveworks/tf-docs
improve tf-c overview
2 parents 3091e1b + 4f42bf0 commit b0fc826

File tree

1 file changed

+15
-17
lines changed

1 file changed

+15
-17
lines changed

website/docs/terraform/overview.mdx

Lines changed: 15 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,22 +6,20 @@ hide_title: true
66

77
# Overview
88

9-
TF-controller is a controller for Weave GitOps that follows the patterns established
10-
by [Flux](https://fluxcd.io) to reconcile Terraform resources in the GitOps way.
11-
With the power of Weave GitOps together with Terraform, the tf-controller allows you to GitOps-ify infrastructure,
12-
and application resources, in the Kubernetes and Terraform universe, at your own pace.
9+
TF-controller is a controller for Weave GitOps that follows the patterns established
10+
by [Flux](https://fluxcd.io). It is a reliable tool for managing your infrastructure using the GitOps approach.
11+
With its support for Terraform and integration with Weave GitOps,
12+
you can trust that it will help you effectively GitOps-ify your infrastructure and application
13+
resources in the Kubernetes and Terraform universe at your own pace.
1314

14-
"At your own pace" means you don't need to GitOps-ify everything at once.
15+
The following GitOps models are available to suit your specific needs:
1516

16-
TF-controller offers many GitOps models:
17+
1. **GitOps Automation Model:** Fully automate the GitOps process for all of your Terraform resources, including the provisioning and enforcement steps.
18+
2. **Hybrid GitOps Automation Model:** Choose to GitOps-ify certain parts of your existing infrastructure resources, such as a nodegroup or security group in an existing EKS cluster.
19+
3. **State Enforcement Model:** Use GitOps to enforce an existing `tfstate` without making any other changes.
20+
4. **Drift Detection Model:** Use GitOps for drift detection, so you can decide what actions to take when a drift occurs.
1721

18-
1. **GitOps Automation Model:** GitOps your Terraform resources from the provision steps to the enforcement steps, like a whole EKS cluster.
19-
2. **Hybrid GitOps Automation Model:** GitOps parts of your existing infrastructure resources. For example, you have an existing EKS cluster.
20-
You can choose to GitOps only its nodegroup, or its security group.
21-
3. **State Enforcement Model:** You have a TFSTATE file, and you'd like to use GitOps enforce it, without changing anything else.
22-
4. **Drift Detection Model:** You have a TFSTATE file, and you'd like to use GitOps just for drift detection, so you can decide to do things later when a drift occurs.
23-
24-
To get started, follow the [getting started](../get-started) guide.
22+
To get started with TF-controller, simply follow the provided [getting started](../get-started) guide.
2523

2624
## Features
2725

@@ -48,11 +46,11 @@ To get started, follow the [getting started](../get-started) guide.
4846
You make change to the field `.spec.approvePlan`, commit and push to tell the TF-controller to apply the plan for you.
4947
With this GitOps workflow, you can optionally create and push this change to a new branch for your team member to
5048
review and approve too. _This feature is available since v0.6.0._
51-
* **First-class YAML-based Terraform**: The `Terraform` object in v0.13.0+ allows you to better configure your
49+
* **First-class YAML-based Terraform**: The `Terraform` object in v0.13.0+ allows you to better configure your
5250
Terraform resources via YAMLs, but without introducing any extra CRDs to your cluster. Together with a new generator
5351
called **Tofu-Jet**, we'll now be able to ship pre-generated primitive Terraform modules for all major cloud providers.
5452
A primitive Terraform module is a module that only contains a single primitive resource, like `aws_iam_role`, or `aws_iam_policy`.
55-
With this concept, we would be able to use Terraform without writing Terraform codes, and make it more GitOps-friendly at the same time.
53+
With this concept, we would be able to use Terraform without writing Terraform codes, and make it more GitOps-friendly at the same time.
5654
_This feature is available since v0.13.0._
5755
* **Enterprise Dashboard Support:** with Weave GitOps Enterprise v0.9.6 you are now able to manage `Terraform` objects the same way you can
5856
with `Kustomization` and `HelmReleases`.
@@ -61,5 +59,5 @@ To get started, follow the [getting started](../get-started) guide.
6159

6260
| Version | Terraform | Source Controller | Flux v2 |
6361
|:-----------:|:---------:|:-----------------:|:-------:|
64-
| v0.13.0-rc | v1.3.1 | v0.30.0 | v0.35.x |
65-
| **v0.12.0** | v1.1.9 | v0.26.1 | v0.32.x |
62+
| **v0.13.1** | v1.3.1 | v0.31.0 | v0.38.x |
63+
| v0.12.0 | v1.1.9 | v0.26.1 | v0.32.x |

0 commit comments

Comments
 (0)