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

Add tiller resource #134

Closed
luisdavim opened this issue Oct 20, 2018 · 7 comments
Closed

Add tiller resource #134

luisdavim opened this issue Oct 20, 2018 · 7 comments

Comments

@luisdavim
Copy link

Hi,

I think it would be great if you could manage the deployment of tiller across different namespaces with a dedicated resource.

@rporres
Copy link

rporres commented Oct 23, 2018

This makes a lot of sense and would actually solve issues like #109. We would need to iron details as what to do with release/tiller dependencies as we want to make sure that tiller is always installed before the release

@gaui
Copy link

gaui commented Oct 24, 2018

Yeah, it would make much more sense than this...

module.vsphere.module.cluster.module.kubernetes.module.helm.kubernetes_service_account.tiller: Provisioning with 'local-exec'...
module.vsphere.module.cluster.module.kubernetes.module.helm.kubernetes_service_account.tiller (local-exec): Executing: ["/bin/sh" "-c" "helm init --tiller-image gcr.io/kubernetes-helm/tiller:v2.11.0 --service-account tiller --upgrade --wait"]
module.vsphere.module.cluster.module.kubernetes.module.helm.kubernetes_service_account.tiller (local-exec): $HELM_HOME has been configured at /root/.helm.
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (10s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (20s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (30s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (40s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (50s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (1m0s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (1m10s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (1m20s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (1m30s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (1m40s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (1m50s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (2m0s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (2m10s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (2m20s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (2m30s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (2m40s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (2m50s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (3m0s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (3m10s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (3m20s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (3m30s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (3m40s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (3m50s elapsed)
module.vsphere.cluster.kubernetes.helm.kubernetes_service_account.tiller: Still creating... (4m0s elapsed)

@iorlas
Copy link

iorlas commented Nov 2, 2018

I'm about to try it out. I will need tiller set and running on k8s cluster via terraform anyway, so this suggestion make so much sense

@Jeeppler
Copy link

@iorlas any updates on this topic?

@giorgiosironi
Copy link

This would also solve the problem of installing only Tiller and no other charts, in case you don't want to manage those charts in the Terraform state.

My current workaround for this is:

  "data": {  
    "helm_repository": {
      "incubator": {
        "url": "https://kubernetes-charts-incubator.storage.googleapis.com",
        "name": "incubator"
      }
    }
  },
  "resource": {
    "helm_release": {
      "raw_hello_world": {
        "depends_on": [
          "kubernetes_cluster_role_binding.tiller"
        ],
        "name": "hello-world",
        "repository": "${data.helm_repository.incubator.metadata.0.name}",
        "chart": "incubator/raw"
      }
    }
  }

which installs an empty release of incubator/raw, a chart dedicated to adding any Kubernetes resource.

@aareet
Copy link
Contributor

aareet commented Apr 8, 2020

We're only accepting enhancements for Helm 3 from this point on.

@ghost
Copy link

ghost commented May 9, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators May 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants