Thank you for letting me know about this option. tbh I am really thin right now. We are benchmarking many ml platforms,

Since [the easyness of] deployment is our most important criteria, I better reproduce the exact desploy instructions.

When are you planning to work on this issue? tbh I 'd prefer to deploy Flyte from the updated repo

> so I removed state for the resources that were complaining, like terraform state rm helm_release.flyte-core so, would you recommend me to remove the resources and re-run 'terraform apply'?

> So if you could create an Issue to capture this problem it'd be grea Sure, can you please share the most relevant link/reference

Here is the output - it is very long:

kubectl_manifest.cert-manager-issuer will be created

• resource "kubectl_manifest" "cert-manager-issuer" {
  • api_version = "http://cert-manager.io/v1|cert-manager.io/v1"
  • apply_only = false
  • field_manager = "kubectl"
  • force_conflicts = false
  • force_new = false
  • id = (known after apply)
  • kind = "Issuer"
  • live_manifest_incluster = (sensitive value)
  • live_uid = (known after apply)
  • name = "letsencrypt-production"
  • namespace = "flyte"
  • server_side_apply = false
  • uid = (known after apply)
  • validate_schema = true
  • wait_for_rollout = true
  • yaml_body = (sensitive value)
  • yaml_body_parsed = <<-EOT apiVersion: http://cert-manager.io/v1|cert-manager.io/v1 kind: Issuer metadata: name: letsencrypt-production namespace: flyte spec: acme: email: mailto:roman@vinci4d.ai|roman@vinci4d.ai privateKeySecretRef: name: letsencrypt-production server: https://acme-v02.api.letsencrypt.org/directory solvers:
    • http01: ingress: ingressClassName: nginx EOT
  • yaml_incluster = (sensitive value) }

Plan: 9 to add, 0 to change, 0 to destroy.

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.

> I guess other resources were already created? I I have created a new GCP project and only installed what is required by the flyte deploy. I have run terraform apply several, it failed on missing service APIs which I installed and re-run terraform apply.

terraform version Terraform v1.5.7

there are other GKE k8s clusters in our domain. My GCP project is fresh new, no other resources besides Flyte deploy were allocated.

Could my problem be solved?

I ran the flyte deploy on a newly created Google Cloud project and a new bucket

> so it fails reaching out the GKE cluster, but it finished creating the cluster?

I was running 'terraform apply', waiting for ten minutes after installing the services, which showed it had 9 (out of the initial 61) resources left to install.

This seems a better channel for my problem.

For the dns-domain, I use the http://comanyname.com|comanyname.com . Not sure if it needed, but I can also create DNS server on GCP.