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

Error: Could not download chart cluster_proportional_autoscaler with module CoreDNS #1061

Closed
1 task done
AErmie opened this issue Oct 16, 2022 · 4 comments
Closed
1 task done
Labels
question Further information is requested stale

Comments

@AErmie
Copy link

AErmie commented Oct 16, 2022

Description

I believe this issue is related to all the helm chart issues that are occurring.

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: v4.13.0

  • Terraform version: 1.2.9 (because of the breaking changes with experimental code in v1.3.x)

  • Provider version(s):

  • Installed terraform-aws-modules/http v2.4.1 (self-signed, key ID B2C1C0641B6B0EB7)
  • Installed hashicorp/helm v2.7.1 (signed by HashiCorp)
  • Installed hashicorp/tls v3.4.0 (signed by HashiCorp)
  • Installed hashicorp/aws v4.34.0 (signed by HashiCorp)
  • Installed hashicorp/random v3.4.3 (signed by HashiCorp)
  • Installed hashicorp/cloudinit v2.2.0 (signed by HashiCorp)
  • Installed hashicorp/kubernetes v2.14.0 (signed by HashiCorp)
  • Installed hashicorp/local v2.2.3 (signed by HashiCorp)
  • Installed gavinbunney/kubectl v1.14.0 (self-signed, key ID AD64217B5ADD572F)
  • Installed hashicorp/null v3.1.1 (signed by HashiCorp)
  • Installed hashicorp/time v0.9.0 (signed by HashiCorp)

Reproduction Code [Required]

locals {
  cluster_version= "1.23"
}

module "eks_blueprints_kubernetes_addons" {
  source = "github.com/aws-ia/terraform-aws-eks-blueprints//modules/kubernetes-addons?ref=v4.13.0"

  eks_cluster_id = module.eks_blueprints.eks_cluster_id

  # EKS Addons
  enable_amazon_eks_coredns = true
  amazon_eks_coredns_config = {
    most_recent        = true
    kubernetes_version = local.cluster_version
    resolve_conflicts  = "OVERWRITE"
  }
}

Steps to reproduce the behavior:

  1. terraform init
  2. terraform plan
  3. terraform apply

Expected behaviour

I expect the CoreDNS EKS add-on to be fully deployed.

Actual behaviour

Even though the CoreDNS add-on is actually installed correctly into the cluster, the output from terraform apply indicates that the cluster_proportional_autoscaler component (which I guess is auto-included in the deployment of CoreDNS), fails to install, and therefore causes Terraform to report a failed apply operation.

Terminal Output Screenshot(s)

TerraformApplyResults

Additional context

This is being run in an Azure Pipeline, using Azure DevOps (online, not server).

@bryantbiggs
Copy link
Contributor

The chart repository is valid hashicorp/terraform-aws-hashicorp-vault-eks-addon#10

Can you try running

helm repo add cluster-proportional-autoscaler https://kubernetes-sigs.github.io/cluster-proportional-autoscaler
helm repo update

And then re-run terraform

@bryantbiggs bryantbiggs added the question Further information is requested label Oct 18, 2022
@ZeroDeth
Copy link

@bryantbiggs Facing the same issue with all new helm updates, and the only solution is to run manually from the shell.
unfortunately, start breaking our pipelines with every bumping version. Thanks

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Dec 18, 2022
@github-actions
Copy link
Contributor

Issue closed due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested stale
Projects
None yet
Development

No branches or pull requests

3 participants