Hướng dẫn triển khai hạ tầng với Terraform và Kubernetes

tel4vn@devops:~/terraform_example$ touch main.tf

tel4vn@devops: minikube start

tel4vn@devops:~/terraform_example$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready master 20h v1.19.2

provider "kubernetes" {
  config_context_cluster   = "minikube"
}

resource "kubernetes_namespace" "minikube-namespace" {
  metadata {
    name = "tel4vn-namespace"
  }
}

tel4vn@devops:~/terraform_example$ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding latest version of hashicorp/kubernetes...
- Installing hashicorp/kubernetes v1.13.2...
- Installed hashicorp/kubernetes v1.13.2 (signed by HashiCorp)

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, we recommend adding version constraints in a required_providers block
in your configuration, with the constraint strings suggested below.

* hashicorp/kubernetes: version = "~> 1.13.2"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

tel4vn@devops:~/terraform_example$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.


------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

# kubernetes_namespace.minikube-namespace will be created
+ resource "kubernetes_namespace" "minikube-namespace" {
+ id = (known after apply)

+ metadata {
+ generation = (known after apply)
+ name = "tel4vn-namespace"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

tel4vn@devops:~/terraform_example$ terraform apply

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

# kubernetes_namespace.minikube-namespace will be created
+ resource "kubernetes_namespace" "minikube-namespace" {
+ id = (known after apply)

+ metadata {
+ generation = (known after apply)
+ name = "tel4vn-namespace"
+ resource_version = (known after apply)
+ self_link = (known after apply)
+ uid = (known after apply)
}
}

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.

Enter a value: yes

kubernetes_namespace.minikube-namespace: Creating...
kubernetes_namespace.minikube-namespace: Creation complete after 0s [id=tel4vn-namespace]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

tel4vn@devops:~/terraform_example$ kubectl get ns
NAME STATUS AGE
default Active 20h
kube-node-lease Active 20h
kube-public Active 20h
kube-system Active 20h
tel4vn-namespace Active 93s

tel4vn@devops:~/terraform_example$ helm create tel4vnchart
Creating tel4vnchart

provider "helm" {
  kubernetes {
        config_context_cluster   = "minikube"
       
  }
}

resource "helm_release" "local" {
  name          = "tel4vnchart"
  chart         = "./tel4vnchart"
}

tel4vn@devops:~/terraform_example$ terraform init

Initializing the backend...

Initializing provider plugins...
- Using previously-installed hashicorp/kubernetes v1.13.2
- Finding latest version of hashicorp/helm...
- Installing hashicorp/helm v1.3.2...
- Installed hashicorp/helm v1.3.2 (signed by HashiCorp)

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, we recommend adding version constraints in a required_providers block
in your configuration, with the constraint strings suggested below.

* hashicorp/helm: version = "~> 1.3.2"
* hashicorp/kubernetes: version = "~> 1.13.2"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

tel4vn@devops:~/terraform_example$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

kubernetes_namespace.minikube-namespace: Refreshing state... [id=tel4vn-namespace]

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

# helm_release.local will be created
+ resource "helm_release" "local" {
+ atomic = false
+ chart = "./tel4vnchart"
+ cleanup_on_fail = false
+ create_namespace = false
+ dependency_update = false
+ disable_crd_hooks = false
+ disable_openapi_validation = false
+ disable_webhooks = false
+ force_update = false
+ id = (known after apply)
+ lint = false
+ max_history = 0
+ metadata = (known after apply)
+ name = "buildachart"
+ namespace = "default"
+ recreate_pods = false
+ render_subchart_notes = true
+ replace = false
+ reset_values = false
+ reuse_values = false
+ skip_crds = false
+ status = "deployed"
+ timeout = 300
+ verify = false
+ version = (known after apply)
+ wait = true
}

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

tel4vn@devops:~/terraform_example$ terraform apply --auto-approve
kubernetes_namespace.minikube-namespace: Refreshing state... [id=tel4vn-namespace]
helm_release.local: Creating...
helm_release.local: Still creating... [10s elapsed]
helm_release.local: Still creating... [20s elapsed]
helm_release.local: Creation complete after 28s [id=tel4vnchart]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

tel4vn@devops:~/terraform_example$ kubectl get pods
NAME READY STATUS RESTARTS AGE
tel4vnchart-59bdc8554d-8l4w7 1/1 Running 0 2m8s

tel4vn@devops:~/terraform_example$ ls
tel4vnchart main.tf terraform.tfstate terraform.tfstate.backup

tel4vn@devops:~/terraform_example$ terraform refresh
helm_release.local: Refreshing state... [id=tel4vnchart]
kubernetes_namespace.minikube-namespace: Refreshing state... [id=tel4vn-namespace]

tel4vn@devops:~/terraform_example$ cat main.tf
provider "kubernetes" {
config_context_cluster = "minikube"
}
resource "kubernetes_namespace" "minikube-namespace" {
metadata {
name = "tel4vn-namespace"
}
}
//provider "helm" {
// kubernetes {
// config_context_cluster = "minikube"

// }
//}
//resource "helm_release" "local" {
// name = "tel4vnchart"
// chart = "./tel4vnchart"

tel4vn@devops:~/terraform_example$ terraform apply
kubernetes_namespace.minikube-namespace: Refreshing state... [id=tel4vn-namespace]
helm_release.local: Refreshing state... [id=tel4vnchart]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
- destroy

Terraform will perform the following actions:

# helm_release.local will be destroyed
- resource "helm_release" "local" {
- atomic = false -> null
- chart = "./tel4vnchart" -> null
- cleanup_on_fail = false -> null
- create_namespace = false -> null
- dependency_update = false -> null
- disable_crd_hooks = false -> null
- disable_openapi_validation = false -> null
- disable_webhooks = false -> null
- force_update = false -> null
- id = "tel4vnchart" -> null
- lint = false -> null
- max_history = 0 -> null
- metadata = [
- {
- app_version = "1.16.0"
- chart = "tel4vnchart"
- name = "tel4vnchart"
- namespace = "default"
- revision = 1
- values = "null"
- version = "0.1.0"
},
] -> null
- name = "tel4vnchart" -> null
- namespace = "default" -> null
- recreate_pods = false -> null
- render_subchart_notes = true -> null
- replace = false -> null
- reset_values = false -> null
- reuse_values = false -> null
- skip_crds = false -> null
- status = "deployed" -> null
- timeout = 300 -> null
- verify = false -> null
- version = "0.1.0" -> null
- wait = true -> null
}

Plan: 0 to add, 0 to change, 1 to destroy.

Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.

Enter a value: yes

helm_release.local: Destroying... [id=tel4vnchart]
helm_release.local: Destruction complete after 0s

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.

tel4vn@devops:~/terraform_example$ terraform destroy
kubernetes_namespace.minikube-namespace: Refreshing state... [id=tel4vn-namespace]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
- destroy

Terraform will perform the following actions:

# kubernetes_namespace.minikube-namespace will be destroyed
- resource "kubernetes_namespace" "minikube-namespace" {
- id = "tel4vn-namespace" -> null

- metadata {
- annotations = {} -> null
- generation = 0 -> null
- labels = {} -> null
- name = "tel4vn-namespace" -> null
- resource_version = "51354" -> null
- self_link = "/api/v1/namespaces/tel4vn-namespace" -> null
- uid = "6121e451-528c-4ca7-926f-46f87cc4d219" -> null
}
}

Plan: 0 to add, 0 to change, 1 to destroy.

Do you really want to destroy all resources?
Terraform will destroy all your managed infrastructure, as shown above.
There is no undo. Only 'yes' will be accepted to confirm.

Enter a value: yes

kubernetes_namespace.minikube-namespace: Destroying... [id=tel4vn-namespace]
kubernetes_namespace.minikube-namespace: Destruction complete after 7s

Destroy complete! Resources: 1 destroyed.

tel4vn@devops:~/terraform_example$ kubectl get ns
NAME STATUS AGE
default Active 22h
kube-node-lease Active 22h
kube-public Active 22h
kube-system Active 22h
tel4vn@devops:~/terraform_example$ kubectl get pods
No resources found in default namespace.