Problem description
We adopted gateway-api. The gatewayApi field for the DNS extension on the stackit_ske_cluster resource is not implemented yet.
Proposed solution
When the stackit_ske_cluster.extensions.dns.gatewayApi (boolean) field is true, the DNS extension takes gateway-api objects into account.
resource "stackit_ske_cluster" "cluster" {
project_id = local.current_project_config.project_id
name = "somecluster"
kubernetes_version_min = "1.34"
extensions = {
dns = {
enabled = true
gatewayApi = true # <- NEW optional field
}
}
}
Alternative solutions (optional)
Workaround (has to be run after every tf apply)
tmp_dir="$(mktemp -d)"
trap 'rm -rf "$tmp_dir"' RETURN
stackit ske cluster generate-payload --project-id "$project_id" --cluster-name "$cluster_id" > "$tmp_dir/config.json"
jq '.extensions.dns.gatewayApi = true' "$tmp_dir/config.json" > "$tmp_dir/new_config.json"
stackit ske cluster update --project-id "$project_id" "$cluster_id" --payload "@$tmp_dir/new_config.json"
Additional information
Official Docs: Activate the STACKIT DNS extension on your SKE cluster
Problem description
We adopted gateway-api. The gatewayApi field for the DNS extension on the stackit_ske_cluster resource is not implemented yet.
Proposed solution
When the
stackit_ske_cluster.extensions.dns.gatewayApi(boolean) field istrue, the DNS extension takes gateway-api objects into account.Alternative solutions (optional)
Workaround (has to be run after every tf apply)
Additional information
Official Docs: Activate the STACKIT DNS extension on your SKE cluster