4 ms·

How would I integrate it into existing setup that uses tools like terraform, along with helm? See, there's a bunch of stuff that I deploy using terraform (VPC,

How would I integrate it into existing setup that uses tools like terraform, along with helm? See, there's a bunch of stuff that I deploy using terraform (VPC, DNS, EKS) and a bunch of stuff that I deploy with FluxCD. But in between, there's some awkward stuff like the monitoring stack that requires cloudy things and Kube things, and they're tightly coupled. Right now I end up going with terraform and the awful helm provider. Many of these helm charts have sub-charts, nested values etc, but thankfully the monitoring stack doesn't change that much. It's still not ideal but it works as a one-shot deployment that sets up buckets, policies, IAM roles for service accounts, more policies for the roles, and finally the helm charts with values from the outputs of those clouds resources.

momothereal 2y ago
What is awful about the Helm provider for Terraform?
- linkdd 2y ago
  I'd say both Helm and Terraform :)
  - raffraffraff 2y ago
    ;) I've tamed terraform, mostly. Individual providers can be awful though.
- raffraffraff 2y ago
  When you make a change to a gigantic values yaml, it shows you the worst possible diff: the entire block removed, a whole new block added, even for a 1 line change. https://github.com/hashicorp/terraform-provider-helm/issues/1121 https://github.com/hashicorp/terraform-provider-helm/issues/... Any time I touch the monitoring stack, which has several helm releases with large values blocks (kube-prometheus-stack, promtail, Loki, Mimir), it's absolutely nightmarish. The plan can be hundreds of lines that have to be diffed manually.
pmig 2y ago
Instead of using the Terraforms Helm provider, you can simply install the Glasskube package controller and provision package custom resource definitions via Flux. This is also how we manage our internal clusters. I recommend giving Glasskube a try with Minikube locally and join our Discord to interact with the community.
- raffraffraff 2y ago
  Does glasskube create any of the AWS resources? Or does it have a terraform provider that's better than the helm provider? If neither are "yes" then I didn't get my point across, or you didn't parse out the important point. I want a single code project that describes and deploys my monitoring stack. With terraform and the helm provider I can create cloud resources with terraform and deploy the kube resources using the terraform helm provider, using values that come from the outputs of the terraform cloud resources, in a single operation. I don't think glasskube can replace helm in this instance. Wouldn't I have to split my monitoring stack into cloud ops and Kube ops, and manually paste outputs from terraform into glasskube configs?

momothereal 2y ago

What is awful about the Helm provider for Terraform?

linkdd 2y ago
I'd say both Helm and Terraform :)
- raffraffraff 2y ago
  ;) I've tamed terraform, mostly. Individual providers can be awful though.
raffraffraff 2y ago
When you make a change to a gigantic values yaml, it shows you the worst possible diff: the entire block removed, a whole new block added, even for a 1 line change. https://github.com/hashicorp/terraform-provider-helm/issues/1121 https://github.com/hashicorp/terraform-provider-helm/issues/... Any time I touch the monitoring stack, which has several helm releases with large values blocks (kube-prometheus-stack, promtail, Loki, Mimir), it's absolutely nightmarish. The plan can be hundreds of lines that have to be diffed manually.

pmig 2y ago

Instead of using the Terraforms Helm provider, you can simply install the Glasskube package controller and provision package custom resource definitions via Flux. This is also how we manage our internal clusters. I recommend giving Glasskube a try with Minikube locally and join our Discord to interact with the community.

raffraffraff 2y ago
Does glasskube create any of the AWS resources? Or does it have a terraform provider that's better than the helm provider? If neither are "yes" then I didn't get my point across, or you didn't parse out the important point. I want a single code project that describes and deploys my monitoring stack. With terraform and the helm provider I can create cloud resources with terraform and deploy the kube resources using the terraform helm provider, using values that come from the outputs of the terraform cloud resources, in a single operation. I don't think glasskube can replace helm in this instance. Wouldn't I have to split my monitoring stack into cloud ops and Kube ops, and manually paste outputs from terraform into glasskube configs?