When you have the configuration files all set, you can begin by initializing the directory.<\/p>\r\n\r\n\r\n\r\n

terraform init<\/pre>\r\n\r\n\r\n\r\n
Terraform will then download the required plugins. You should see an output similar to below.<\/p>\r\n\r\n\r\n\r\n
Initializing the backend...<\/strong>\r\n\r\nInitializing provider plugins...<\/strong>\r\n- Finding latest version of hashicorp\/local...\r\n- Finding latest version of hashicorp\/kubernetes...\r\n- Finding upcloudltd\/upcloud versions matching \">= 2.11.0\"...\r\n- Installing hashicorp\/local v2.4.0...\r\n- Installed hashicorp\/local v2.4.0 (signed by HashiCorp)\r\n- Installing hashicorp\/kubernetes v2.22.0...\r\n- Installed hashicorp\/kubernetes v2.22.0 (signed by HashiCorp)\r\n- Installing upcloudltd\/upcloud v2.12.0...\r\n- Installed upcloudltd\/upcloud v2.12.0 (self-signed, key ID 60B4E1988F222907<\/strong>)\r\n\r\nPartner and community providers are signed by their developers.\r\nIf you'd like to know more about provider signing, you can read about it here:\r\nhttps:\/\/www.terraform.io\/docs\/cli\/plugins\/signing.html\r\n\r\nTerraform has created a lock file .terraform.lock.hcl<\/strong> to record the provider\r\nselections it made above. Include this file in your version control repository\r\nso that Terraform can guarantee to make the same selections by default when\r\nyou run \"terraform init\" in the future.\r\n\r\nTerraform has been successfully initialized!<\/strong>\r\n\r\nYou may now begin working with Terraform. Try running \"terraform plan\" to see\r\nany changes that are required for your infrastructure. All Terraform commands\r\nshould now work.\r\n\r\nIf you ever set or change modules or backend configuration for Terraform,\r\nrerun this command to reinitialize your working directory. If you forget, other\r\ncommands will detect it and remind you to do so if necessary.<\/mark><\/pre>\r\n\r\n\r\n\r\n
Next, test that the configuration is ready to deploy by running the terraform plan<\/em> command.<\/p>\r\n\r\n\r\n\r\n
terraform plan<\/pre>\r\n\r\n\r\n\r\n
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the\r\nfollowing symbols:\r\n  +<\/mark> create\r\n <-<\/mark> read (data resources)\r\n\r\nTerraform will perform the following actions:\r\n\r\n  # data.upcloud_kubernetes_cluster.example<\/strong> will be read during apply\r\n  # (config refers to values not yet known)\r\n \r\n...\r\n\r\nPlan:<\/strong> 4 to add, 0 to change, 0 to destroy.\r\n\r\nChanges to Outputs:\r\n  +<\/mark> cluster_id = (known after apply)<\/pre>\r\n\r\n\r\n\r\n
The above example output has been truncated for brevity.<\/p>\r\n\r\n\r\n\r\n
Lastly, if the plan looks all correct and Terraform didn’t report any issues, go ahead and deploy the setup. Confirm the deployment by answering yes when prompted.<\/p>\r\n\r\n\r\n\r\n
terraform apply<\/pre>\r\n\r\n\r\n\r\n
You will then see a confirmation of the configuration followed by the deployment process. Running apply will create a network, a cluster, and a Kubernetes namespace in the new cluster.<\/p>\r\n\r\n\r\n\r\n
...\r\n\r\nPlan:<\/strong> 4 to add, 0 to change, 0 to destroy.\r\n\r\nChanges to Outputs:\r\n  +<\/mark> cluster_id = (known after apply)\r\nupcloud_network.example: Creating...\r\nupcloud_network.example: Creation complete after 2s [id=03e416f9-0812-48bb-b58b-cf4ac74161eb]\r\nupcloud_kubernetes_cluster.example: Creating...\r\nupcloud_kubernetes_cluster.example: Still creating... [10s elapsed]\r\n...\r\nupcloud_kubernetes_cluster.example: Creation complete after 6m57s [id=0d1f7c52-4910-4970-b150-a07dce8615e2]\r\ndata.upcloud_kubernetes_cluster.example: Reading...\r\nupcloud_kubernetes_node_group.group: Creating...\r\ndata.upcloud_kubernetes_cluster.example: Read complete after 0s [id=0d1f7c52-4910-4970-b150-a07dce8615e2]\r\nlocal_file.kubeconfig[0]: Creating...\r\nlocal_file.kubeconfig[0]: Creation complete after 0s [id=68796076a5b3afcce490db2a9464019b94a662ad]\r\nupcloud_kubernetes_node_group.group: Creation complete after 1s [id=0d1f7c52-4910-4970-b150-a07dce8615e2\/medium]\r\n\r\nApply complete! Resources: 4 added, 0 changed, 0 destroyed.\r\n\r\nOutputs:<\/mark>\r\n\r\ncluster_id = \"0d1f7c52-4910-4970-b150-a07dce8615e2\"<\/pre>\r\n\r\n\r\n\r\n
That’s it! You should now have a fully functional Managed Kubernetes cluster running on your UpCloud account just waiting for a workload to run.<\/p>\r\n","protected":false},"featured_media":34478,"comment_status":"open","ping_status":"closed","template":"","community-category":[114,118,127],"class_list":["post-32923","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry","community-category-kubernetes","community-category-terraform","community-category-managed-services"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/32923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=32923"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media\/34478"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=32923"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=32923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}