Skip to content

Commit faed77b

Browse files
committed
Update Blog “kubernetes-cluster-as-code-part-2”
1 parent 6da8606 commit faed77b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/blog/kubernetes-cluster-as-code-part-2.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In this blog post, I will focus on managing application deployments using IaC. H
4141

4242
### Helm provider
4343

44-
Below is the code block for adding **helm** community provider. Please refer to [my first blog post](https://developer.hpe.com/blog/kubernetes-clusters-as-code-part1/) for details regarding **hpegl_caas_cluster** data source.
44+
Below is the code block for adding **helm** community provider. Please refer to [my first blog post](https://developer.hpe.com/blog/kubernetes-clusters-as-code-part1/) for details regarding **hpegl\_caas\_cluster** data source.
4545

4646
```json
4747
provider "helm" {
@@ -57,8 +57,8 @@ provider "helm" {
5757

5858
In order to deploy Prometheus stack using the helm-release resource, the following values have to be filled in the **prometheus-deploy.tf** file:
5959

60-
1. Cluster Name: Fill in the **name** of the pre-created cluster in **hpegl_caas_cluster** block. In the below example, name= "tf-test-7"
61-
2. Namespace: Fill in the appropriate **namespace** in the **helm_release** block. In the below example, namespace= "test-namespace" 
60+
1. Cluster Name: Fill in the **name** of the pre-created cluster in **hpegl\_caas\_cluster** block. In the below example, name= "tf-test-7"
61+
2. Namespace: Fill in the appropriate **namespace** in the **helm\_release** block. In the below example, namespace= "test-namespace" 
6262

6363
**prometheus-deploy.tf** 
6464

0 commit comments

Comments
 (0)