hashicorp / terraform-provider-kubernetes

Terraform Kubernetes provider
https://www.terraform.io/docs/providers/kubernetes/
Mozilla Public License 2.0
1.57k stars 967 forks source link

context deadline exceeded for kubernetes_config_map_v1 #2349

Open prashantkalkar opened 7 months ago

prashantkalkar commented 7 months ago

Terraform Version, Provider Version and Kubernetes Version

Terraform version: 1.4.6
Kubernetes provider version: 2.23.0
Kubernetes version: v1.25.5

Affected Resource(s)

kubernetes_config_map_v1

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

resource "kubernetes_config_map_v1" "node_exporter_dashboard" { metadata { name = "node-exporter-dashboard" labels = var.dashboard_labels annotations = { grafana_folder: "Infrastructure" } namespace = var.dashboard_namespace } data = { "node-dashboard.json" = file("${path.module}/node-exporter-full.json") } }

The file the config is referring to is around 665 KB.

Debug Output

Panic Output

Error: Failed to update Config Map: Timeout: request did not complete within requested timeout - context deadline exceeded This is happening during existing configMap update.

Steps to Reproduce

This is happening for configMap with large file for data.

Expected Behavior

What should have happened? - Should apply Config Map changes

Actual Behavior

What actually happened? - The operation timed out and there seems to be no way to increase or change it.

Important Factoids

References

Community Note

arybolovlev commented 7 months ago

Hi @prashantkalkar,

I was not able to reproduce this issue. The observed error message comes from the Kubernetes cluster. How long does it take before you get this error message? Have you tried to reproduce this issue on a different cluster or with kubectl?

Thanks.

zack-is-cool commented 4 months ago

able to reproduce this when uploading a large binary configmap ~ 1MB through an SSH tunnel against an EKS cluster