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
Terraform**example** module for the Datadog Kubernetes Operator on Google Kubernetes Engine (GKE).
15
+
OpenTofu**example** module for the Datadog Kubernetes Operator on Google Kubernetes Engine (GKE).
16
16
17
17
> [!NOTE]
18
-
> We do not recommend consuming this module like you might a [public module](https://registry.terraform.io/browse/modules). It is a baseline, something you can fork, potentially maintain, and modify to fit your organization's needs. Using public modules vs. writing your own has various [drivers and trade-offs](https://docs.osinfra.io/fundamentals/architecture-decision-records/adr-0003) that your organization should evaluate.
18
+
> We do not recommend consuming this module like you might a [public module](https://search.opentofu.org). It is a baseline, something you can fork, potentially maintain, and modify to fit your organization's needs. Using public modules vs. writing your own has various [drivers and trade-offs](https://docs.osinfra.io/fundamentals/architecture-decision-records/adr-0003) that your organization should evaluate.
19
19
20
20
## 🔩 Usage
21
21
@@ -28,18 +28,16 @@ Our focus is on the core fundamental practice of platform engineering, Infrastru
28
28
29
29
>Open Source Infrastructure (as Code) is a development model for infrastructure that focuses on open collaboration and applying relative lessons learned from software development practices that organizations can use internally at scale. - [Open Source Infrastructure (as Code)](https://www.osinfra.io)
30
30
31
-
To avoid slowing down stream-aligned teams, we want to open up the possibility for contributions. The Open Source Infrastructure (as Code) model allows team members external to the platform team to contribute with only a slight increase in cognitive load. This section is for developers who want to contribute to this repository, describing the tools used, the skills, and the knowledge required, along with Terraform documentation.
31
+
To avoid slowing down stream-aligned teams, we want to open up the possibility for contributions. The Open Source Infrastructure (as Code) model allows team members external to the platform team to contribute with only a slight increase in cognitive load. This section is for developers who want to contribute to this repository, describing the tools used, the skills, and the knowledge required, along with OpenTofu documentation.
32
32
33
33
See the [documentation](https://docs.osinfra.io/fundamentals/development-setup) for setting up a local development environment.
@@ -49,21 +47,16 @@ Links to documentation and other resources required to develop and iterate in th
49
47
50
48
### 🔍 Tests
51
49
52
-
All tests are [mocked](https://developer.hashicorp.com/terraform/language/tests/mocking) allowing us to test the module without creating infrastructure or requiring credentials. The trade-offs are acceptable in favor of speed and simplicity. In a Terraform test, a mocked provider or resource will generate fake data for all computed attributes that would normally be provided by the underlying provider APIs.
50
+
All tests are [mocked](https://opentofu.org/docs/cli/commands/test/#the-mock_provider-blocks) allowing us to test the module without creating infrastructure or requiring credentials. The trade-offs are acceptable in favor of speed and simplicity. In an OpenTofu test, a mocked provider or resource will generate fake data for all computed attributes that would normally be provided by the underlying provider APIs.
53
51
54
52
```none
55
-
terraform init
53
+
tofu init
56
54
```
57
55
58
56
```none
59
-
terraform test
57
+
tofu test
60
58
```
61
59
62
-
## 📓 Terraform Documentation
60
+
## 📓 OpenTofu Documentation
63
61
64
62
> A child module automatically inherits default (un-aliased) provider configurations from its parent. The provider versions below are informational only and do **not** need to align with the provider configurations from its parent.
A child module automatically inherits its parent's default (un-aliased) provider configurations. The provider versions below are informational only and do **not** need to align with the provider configurations from its parent.
| <aname="input_cluster_prefix"></a> [cluster\_prefix](#input\_cluster\_prefix)| Prefix for your cluster name, region, and zone (if applicable) will be added to the end of the cluster name |`string`| n/a | yes |
38
-
| <aname="input_limits_cpu"></a> [limits\_cpu](#input\_limits\_cpu)| CPU limits for the Datadog Operator |`string`|`"200m"`| no |
39
-
| <aname="input_limits_memory"></a> [limits\_memory](#input\_limits\_memory)| Memory limits for the Datadog Operator |`string`|`"64Mi"`| no |
40
-
| <aname="input_operator_version"></a> [operator\_version](#input\_operator\_version)| The version of the Datadog Operator to install |`string`|`"2.11.1"`| no |
41
-
| <aname="input_requests_cpu"></a> [requests\_cpu](#input\_requests\_cpu)| CPU requests for the Datadog Operator |`string`|`"100m"`| no |
42
-
| <aname="input_requests_memory"></a> [requests\_memory](#input\_requests\_memory)| Memory requests for the Datadog Operator |`string`|`"32Mi"`| no |
43
-
| <aname="input_watch_namespaces"></a> [watch\_namespaces](#input\_watch\_namespaces)| Restricts the Operator to watch its managed resources on specific namespaces - set to [""] to watch all namespaces |`list(string)`| <pre>[<br/> "datadog"<br/>]</pre> | no |
44
-
45
-
## Outputs
46
-
47
-
No outputs.
48
-
<!-- END_TF_DOCS -->
3
+
> A child module automatically inherits default (un-aliased) provider configurations from its parent. The provider versions below are informational only and do **not** need to align with the provider configurations from its parent.
0 commit comments