You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/terraform/overview.mdx
+15-17Lines changed: 15 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,22 +6,20 @@ hide_title: true
6
6
7
7
# Overview
8
8
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.
13
14
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:
15
16
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.
17
21
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.
25
23
26
24
## Features
27
25
@@ -48,11 +46,11 @@ To get started, follow the [getting started](../get-started) guide.
48
46
You make change to the field `.spec.approvePlan`, commit and push to tell the TF-controller to apply the plan for you.
49
47
With this GitOps workflow, you can optionally create and push this change to a new branch for your team member to
50
48
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
52
50
Terraform resources via YAMLs, but without introducing any extra CRDs to your cluster. Together with a new generator
53
51
called **Tofu-Jet**, we'll now be able to ship pre-generated primitive Terraform modules for all major cloud providers.
54
52
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.
56
54
_This feature is available since v0.13.0._
57
55
***Enterprise Dashboard Support:** with Weave GitOps Enterprise v0.9.6 you are now able to manage `Terraform` objects the same way you can
58
56
with `Kustomization` and `HelmReleases`.
@@ -61,5 +59,5 @@ To get started, follow the [getting started](../get-started) guide.
0 commit comments