Upgrading CRDs

[MaciekLeks]

The problem is generic but I will use istio example just because it's my task to cope with.

Terraform version, Kubernetes provider version and Kubernetes version

Terraform version: latest stable
Helm Provider version: latest stable
Kubernetes version: latest stable

Terraform configuration

not needed here

Question

I've wrapped Install Istio with Helm using the provider and now I need to upgrade not only the version Istio but most of all its CRDs. According to the istio documenations on this task I need to:

Upgrade the Kubernetes custom resource definitions (CRDs):

$ kubectl apply -f manifests/charts/base/crds

Upgrade the Istio base chart:

$ helm upgrade istio-base manifests/charts/base -n istio-system --skip-crds

Regular upgrading with helm_release does not upgrade CRDs of course, so the problems stays: How to do this in fully automated environment?
Do we have any pattern on this problem while it seems to be a common problem with helm?

[alexsomesan]

I would normally recommend to render the CRDs via the helm_template data-source and apply them using kubernetes_manifest and otherwise follow the Istio recommended steps.

However, Helm seems to have a bug that is preventing the correct rendering of CRDs from the Istio project. Even attempting this with helm CLI yelds the wrong results.

I've raised the issue with Helm. Let's see how they resolve it and then I can share an example of how to implement these steps in Terraform.

[MaciekLeks]

Thank you Alex.

I've figured out the same, but I've been waiting for dealing with my VPC Service Control in GCP (could not get istio charts from outside GCS Bucket).So I did not even test the code:

data "helm_template" "istio_crds" {
  name       = "istio-base"
  repository = var.istio_helm_charts_repository
  chart      = "base"
  version    = var.chart_version
  namespace  = var.ns

  set {
    name  = "base.enableCRDTemplates"
    value = true
  }

  show_only = [
    "templates/crds.yaml",
  ]
}


resource "kubectl_manifest" "istio_crds" {
  for_each  = data.helm_template.istio_crds.manifests
  yaml_body = each.value
}

So it would end with many bugs. I confirm your observations. I've added comment tothe related issue.

[MaciekLeks]

@alexsomesan as far as I see there is no progress in this matter on the helm side. Do we have any workaround?

[github-actions]

Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you!

[MaciekLeks]

Waiting for a resolution to helm/helm#11321

[github-actions]

Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you!