Terraform – How to Fix ‘Failed to Initialize Kubernetes Configuration’ Error

terraform

I've migrated my old terraform install from some 1.0 version (sadly, don't remember which exactly) to latest, installed with nix

terraform -v                                                                                                                      
Terraform v1.1.7
on linux_amd64

After issuing terraform plan i'm getting the following error:

Error: Failed to initialize kubernetes configuration: context "redacted-context" does not exist

My main.tf configured with k8s backend as following:

terraform {
  required_version = ">=0.13.0"
  backend "kubernetes" {
    secret_suffix    = "redacted-suffix"
    load_config_file = true
    config_context   = "redacted-context"
    namespace        = "redacted-namespace"
  }
}

Using strace -f terraform plan i don't see any attempts to read ~/.kube/config

How can i make terraform to read and use deafault kubeconfig?

Best Answer

Setting KUBE_CONFIG_PATH=~/.kube/config forces terraform to read specific config, as per https://www.terraform.io/language/settings/backends/kubernetes#configuration-variables

It's unclear, however, why this issue happened in a first place

Related Solutions

Terraform plan wants to destroy security groups after importing them with terraform import

So the import for network ACL and security group break things out like

resource "aws_security_group" "production_servers" {}
resource "aws_security_group_rule" "production_servers-1" {}
resource "aws_security_group_rule" "production_servers" {}

You mentioned you had all the rules in the aws_security_group which is perfectly fine. I prefer them outside since its more readable if you make a rule change and have like 10-15 rules in a group.

So whats going on is terraform wrote a blank aws_security_group with no rules and has a bunch of external aws_security_group_rule in the state file which is different then your TF config.

So on a plan it'll say I need to destroy these and then it will create them in the resource itself.

You might get a minor blip of no security group rules but in the end it'll clean up on an apply. Just look at the plan for your aws_security_group I would bet all your rules are listed in there

Add second network to vsphere terraform plan

You should add one more network_interface block to your vsphere_virtual_machine resource:

resource "vsphere_virtual_machine" "vm" {
  name   = ""
  folder = ""
  vcpu   = ""
  memory = ""
  datacenter = ""
  cluster = ""
  resource_pool = ""

  network_interface {
    label = "${var.network1}"
  }

  network_interface {
    label = "${var.network2}"
  }

  disk {
    datastore = ""
    template = ""
  }
}

Best Answer

Related Solutions

Terraform plan wants to destroy security groups after importing them with terraform import

Add second network to vsphere terraform plan

Related Topic