From c3227178addbeea2e0527ad63a494360d88e8469 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Palet?= Date: Thu, 1 Aug 2024 15:49:48 +0100 Subject: [PATCH] Revert "docs: add guide to retrieve outgoing ske ip-address (#476)" (#490) This reverts commit 3c530797b472972463066fb93d91aa6ee9794f39. --- docs/guides/outgoing_ske_ip.md | 58 ------------------------ templates/guides/outgoing_ske_ip.md.tmpl | 58 ------------------------ 2 files changed, 116 deletions(-) delete mode 100644 docs/guides/outgoing_ske_ip.md delete mode 100644 templates/guides/outgoing_ske_ip.md.tmpl diff --git a/docs/guides/outgoing_ske_ip.md b/docs/guides/outgoing_ske_ip.md deleted file mode 100644 index ea6c8980..00000000 --- a/docs/guides/outgoing_ske_ip.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -page_title: "Retrieving SKE outgoing IP address with Terraform" ---- -# Retrieving SKE outgoing IP address with Terraform - -To retrieve the outgoing IP address of your STACKIT Kubernetes Engine (SKE) cluster, you have two options based on your initial SKE setup. - -## Default Setup - -If you haven't configured any organisational network settings, you can use the default setup. It is necessary to use the Terraform OpenStack provider in conjunction with the STACKIT provider. - -```hcl -resource "stackit_ske_cluster" "ske_cluster_01" { - project_id = var.project_id - name = var.cluster_name - kubernetes_version_min = "1.29.6" - node_pools = [...] -} - -data "openstack_networking_router_v2" "router" { - name = "shoot--${substr(sha256(var.project_id), 0, 10)}--${var.cluster_name}" -} - -locals { - cluster_outgoing_ip = data.openstack_networking_router_v2.router.external_fixed_ip.0.ip_address -} -``` - -## Organizational SNA Setup - -If your project is within an organizational STACKIT Network Area (SNA), you can attach a `stackit_network` to the SKE cluster: - -```hcl -resource "stackit_network" "ske_network" { - project_id = var.project_id - name = "ske-network" - nameservers = ["1.1.1.1", "8.8.8.8"] - ipv4_prefix_length = 24 -} - -resource "stackit_ske_cluster" "ske_cluster_01" { - project_id = var.project_id - name = var.cluster_name - kubernetes_version_min = "1.29.6" - node_pools = [...] - - network = { - id = stackit_network.ske_network.network_id - } -} - -locals { - cluster_outgoing_ip = stackit_network.ske_network.public_ip -} -``` - -In both examples, the attribute `cluster_outgoing_ip` will provide the outgoing IP address of your cluster. -The specific configuration depends on whether your setup is within an organizational SNA or a default setup. \ No newline at end of file diff --git a/templates/guides/outgoing_ske_ip.md.tmpl b/templates/guides/outgoing_ske_ip.md.tmpl deleted file mode 100644 index ea6c8980..00000000 --- a/templates/guides/outgoing_ske_ip.md.tmpl +++ /dev/null @@ -1,58 +0,0 @@ ---- -page_title: "Retrieving SKE outgoing IP address with Terraform" ---- -# Retrieving SKE outgoing IP address with Terraform - -To retrieve the outgoing IP address of your STACKIT Kubernetes Engine (SKE) cluster, you have two options based on your initial SKE setup. - -## Default Setup - -If you haven't configured any organisational network settings, you can use the default setup. It is necessary to use the Terraform OpenStack provider in conjunction with the STACKIT provider. - -```hcl -resource "stackit_ske_cluster" "ske_cluster_01" { - project_id = var.project_id - name = var.cluster_name - kubernetes_version_min = "1.29.6" - node_pools = [...] -} - -data "openstack_networking_router_v2" "router" { - name = "shoot--${substr(sha256(var.project_id), 0, 10)}--${var.cluster_name}" -} - -locals { - cluster_outgoing_ip = data.openstack_networking_router_v2.router.external_fixed_ip.0.ip_address -} -``` - -## Organizational SNA Setup - -If your project is within an organizational STACKIT Network Area (SNA), you can attach a `stackit_network` to the SKE cluster: - -```hcl -resource "stackit_network" "ske_network" { - project_id = var.project_id - name = "ske-network" - nameservers = ["1.1.1.1", "8.8.8.8"] - ipv4_prefix_length = 24 -} - -resource "stackit_ske_cluster" "ske_cluster_01" { - project_id = var.project_id - name = var.cluster_name - kubernetes_version_min = "1.29.6" - node_pools = [...] - - network = { - id = stackit_network.ske_network.network_id - } -} - -locals { - cluster_outgoing_ip = stackit_network.ske_network.public_ip -} -``` - -In both examples, the attribute `cluster_outgoing_ip` will provide the outgoing IP address of your cluster. -The specific configuration depends on whether your setup is within an organizational SNA or a default setup. \ No newline at end of file