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: docs/modules/ROOT/pages/tutorials/deploy_eks.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
= Deployment on Amazon EKS
2
2
3
3
An example of a local deployment on Amazon EKS is provided https://github.com/camptocamp/devops-stack/tree/main/examples/eks[here]. Clone this repository and modify the files at your convenience.
4
-
In the folder, as in a standard https://developer.hashicorp.com/terraform/tutorials/modules/module#what-is-a-terraform-module[Terraform module], you will find the following files:
4
+
In the repository, as in a standard https://developer.hashicorp.com/terraform/tutorials/modules/module#what-is-a-terraform-module[Terraform module], you will find the following files:
5
5
6
6
* *`terraform.tf`* - declaration of the Terraform providers used in this project;
7
7
* *`locals.tf`* - local variables used by the DevOps Stack modules;
@@ -59,7 +59,7 @@ The `user_map` variable of that module allows you to create OIDC users used to a
59
59
60
60
=== Let's Encrypt SSL certificates
61
61
62
-
By default, to avoid rate-limiting your domain by Let's Encrypt, the example uses the `letsencrypt-staging` configuration of the cert-manager module to generate certificates using the Let's Encrypt staging environment which has an invalid CA certificate.
62
+
By default, to avoid rate-limiting your domain by Let's Encrypt, the example uses the `letsencrypt-staging` configuration of the cert-manager module to generate certificates. This uses the Let's Encrypt staging environment which has an invalid CA certificate.
63
63
64
64
If you feel ready to test with production certificates, you can simply edit the `locals.tf` file and change the `cluster_issuer` variable to `letsencrypt-prod`.
65
65
@@ -90,7 +90,7 @@ TIP: The xref:eks:ROOT:README.adoc[cluster module documentation] can help you kn
90
90
+
91
91
[source,terraform]
92
92
----
93
-
include::example$deploy_examples/sks/locals.tf[]
93
+
include::example$deploy_examples/eks/locals.tf[]
94
94
----
95
95
96
96
7. Finally, run `terraform apply` and accept the proposed changes to create the Kubernetes nodes on Amazon EKS and populate them with our services;
@@ -110,7 +110,7 @@ TIP: Take note of the local called `app_autosync`. If you set the condition of t
110
110
111
111
== Access the cluster and the DevOps Stack applications
112
112
113
-
To access your cluster you need to use the AWS CLI to recover a Kubeconfig you can use:
113
+
To access your cluster, you need to use the AWS CLI to recover a Kubeconfig you can use:
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/tutorials/deploy_kind.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
= Deployment on KinD
2
2
3
3
An example of a local deployment on KinD is provided https://github.com/camptocamp/devops-stack/tree/main/examples/kind[here]. Clone this repository and modify the files at your convenience.
4
-
In the folder, as in a standard https://developer.hashicorp.com/terraform/tutorials/modules/module#what-is-a-terraform-module[Terraform module], you will find the following files:
4
+
In the repository, as in a standard https://developer.hashicorp.com/terraform/tutorials/modules/module#what-is-a-terraform-module[Terraform module], you will find the following files:
5
5
6
6
* *`terraform.tf`* - declaration of the Terraform providers used in this project as well as their configuration;
7
7
* *`locals.tf`* - local variables used by the DevOps Stack modules;
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/tutorials/deploy_sks.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
= Deployment on Exoscale SKS
2
2
3
3
An example of a local deployment on Exoscale SKS is provided https://github.com/camptocamp/devops-stack/tree/main/examples/sks[here]. Clone this repository and modify the files at your convenience.
4
-
In the folder, as in a standard https://developer.hashicorp.com/terraform/tutorials/modules/module#what-is-a-terraform-module[Terraform module], you will find the following files:
4
+
In the repository, as in a standard https://developer.hashicorp.com/terraform/tutorials/modules/module#what-is-a-terraform-module[Terraform module], you will find the following files:
5
5
6
6
* *`terraform.tf`* - declaration of the Terraform providers used in this project as well as their configuration;
7
7
* *`locals.tf`* - local variables used by the DevOps Stack modules;
@@ -101,7 +101,7 @@ TIP: If you do not provide a value for the `user_map` variable, the module will
101
101
102
102
=== Let's Encrypt SSL certificates
103
103
104
-
By default, to avoid rate-limiting your domain by Let's Encrypt, the example uses the `letsencrypt-staging` configuration of the cert-manager module to generate certificates using the Let's Encrypt staging environment which has an invalid CA certificate.
104
+
By default, to avoid rate-limiting your domain by Let's Encrypt, the example uses the `letsencrypt-staging` configuration of the cert-manager module to generate certificates. This uses the Let's Encrypt staging environment which has an invalid CA certificate.
105
105
106
106
If you feel ready to test with production certificates, you can simply edit the `locals.tf` file and change the `cluster_issuer` variable to `letsencrypt-prod`.
0 commit comments