Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unexpected error when reading response body on terraform apply #1350

Open
amansharif opened this issue Apr 9, 2024 · 1 comment
Open

unexpected error when reading response body on terraform apply #1350

amansharif opened this issue Apr 9, 2024 · 1 comment
Labels

Comments

@amansharif
Copy link

amansharif commented Apr 9, 2024

Terraform, Provider, Kubernetes and Helm Versions

Terraform version: v1.7.5
Provider version: v2.13.0
Kubernetes version: v1.27.2

Affected Resource(s)

  • helm_release

Terraform Configuration Files

resource "helm_release" "victoria_metrics_cluster" {
  name       = "vm-cluster"
  chart      = "victoria-metrics-cluster"
  repository = "https://artifactory.build.dlt/artifactory/helm"
  values     = [
    templatefile("files/values.yaml", {

    })
  ]
  namespace        = "vm-ops"
  create_namespace = true
  version          = "0.11.14"
  timeout          = 600
}

module "cluster" {
  source = "../../globals"
}

module "globals" {
  source = "../../../../globals"
}

provider "helm" {
  kubernetes {
    config_context = module.cluster.context
  }
}

provider "kubernetes" {
  config_context = module.cluster.context
}

Debug Output

https://gist.github.com/amansharif/9f9ab53078b69600097042a798f0a29d

NOTE: In addition to Terraform debugging, please set HELM_DEBUG=1 to enable debugging info from helm.

Panic Output

Steps to Reproduce

  1. terraform apply

Expected Behavior

It should have been applied successfully.

Actual Behavior

terraform apply failed during helm modification.

I have tried to execute terraform apply from WSL, Powershell, CMD even from docker container but encountered the same error. I have also tried different internet provider as well and it seems nothing to do with ISP. Additionally, I'm able to execute kubectl command as well as helm commands meaning it's the terraform helm provider which is causing problem.

Important Factoids

I'm running on Open source Kubernetes and the servers are hosted in OVH Cloud.

@amansharif amansharif added the bug label Apr 9, 2024
@shuliakovsky
Copy link

Had you try to apply chart with regular helm?
This error looks like one of the k8s network wrong configuration error:

  • kube-proxy in ipvs mode bad configuration
  • k8s network policies bad configuration
    OR
    Insufficient CRD for chart deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants