Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tanka: Our way of deploying to Kubernetes

grafana.com

Post reply on HN
Print view View original

81–90 of 124 posts

Re: Tanka: Our way of deploying to Kubernetes

#81

Post by [deleted] »

nodesocket wrote: post #58
jka wrote: post #10

Very interesting. I've been reluctant to adopt Helm for Kubernetes resource management because of a gut feeling that it's a heavyweight solution for what seems broadly like a templating problem. With ksonnet having gone quiet[0] this looks like a promising initiative. I'd imagine that it'll need something like a package manager (or at least a curated list of common packages) in order to gain good adoption. [0] - http…

I'd also recommended taking a look at using Terraform[1] to manage Kubernetes resources instead of yaml files and kubectl. [1] https://www.terraform.io/docs/providers/kubernetes/guides/ge...

[deleted]

Re: Tanka: Our way of deploying to Kubernetes

#83

Post by Aqua »

markbnj wrote: post #76

In our experience running production workloads on k8s for over three years templating (helm) and structured editing approaches both have their place, and both are valuable. We don't feel the need to replace declarative approaches with another imperative language, or to use complicated helm charts for straightforward service deployments. There are many ways to classify workloads, but one big distinction that we find v…

Totally agree. Helm is difficult enough to get up to speed with for engineers without prior experience with Kubernetes. Anything more complicated (and ksonnet was significantly more complicated, which is one of the reasons why it died out) is just not scalable. Helm is good enough and brings a decent balance between usability and complexity.

Re: Tanka: Our way of deploying to Kubernetes

#84

Post by vicjicama »

shorez wrote: post #70
vicjicama wrote: post #68

Thanks for sharing, I will try it and give you feedback. What I am doing for my env clusters is to have a versioned production yaml that acts as a source of truth, then if I need an env (regions, customer, dev, prod, feature, etc..) I take that source of truth, apply a transformation (usually a node script or bash... depending on the kubernetes entity) and then apply the resulting transformed yaml. Basically is: vers…

Downfalls of a bash based approach: You need to maintain it. And bash is hard to debug, especially when the house is on fire (production outage, etc) Integrating should be quite straigthforward. Install Tanka, create a new project (tk init), copy your source of truth YAML (without transformations) somewhere under lib/ (for example lib/foo). Then go to lib/foo/foo, and import each of those yaml files: { foo: { deploym…

Thank you, I saw the example on the repository prom-grafana, I think that this example is for focus on the stand alone functionality of Tanka.

Do you know if there is an example or open source cluster using Tanka that I can try on minikube or a test cluster?

it would be really helpful to see how is the workflow to move from feature to feature, how are the envs when there is a bug, how do you replace the volume info from the cloud provider to minikube and all the considerations of the patched envs

Re: Tanka: Our way of deploying to Kubernetes

#85

Post by dcchambers »

shorez wrote: post #52
dcchambers wrote: post #49

Getting a HSTS cert error on the site they link in the blog post - tanka.dev :(

Oh, too bad :( The site is hosted on Netlify and seems to be working for most other people. Maybe reset your browser cache, check your network or try on your phone using cellular data instead? If the issue persists, I'll take a closer look :D

Seems to only be an issue on the corp wifi. I'm able to load it over cell network without issue!

Re: Tanka: Our way of deploying to Kubernetes

#86

Post by shorez »

dcchambers wrote: post #85
shorez wrote: post #52

Earlier quoted context omitted.

Oh, too bad :( The site is hosted on Netlify and seems to be working for most other people. Maybe reset your browser cache, check your network or try on your phone using cellular data instead? If the issue persists, I'll take a closer look :D

Seems to only be an issue on the corp wifi. I'm able to load it over cell network without issue!

Glad to hear that :D

Re: Tanka: Our way of deploying to Kubernetes

#87

Post by 0xbadcafebee »

I'd like to request that nobody else make any more damn infrastructure tools that require writing code in order to use it, or require reading six manuals. I don't want to spend the rest of my life writing and editing glue and cruft, or spending two weeks researching and writing elaborate config files by hand just to make some software run.

It's like the infrastructure version of fine woodworking - building dovetails and screwless joints by hand, using chisels and hand planes and card scrapers and shit, to build a box. It may be "fun", but it's also needlessly complicated and time-consuming. Give me the power tools, pocket hole jigs, torx screws, nail guns, square clamps. Yes, the dovetails will make a more sturdy box - but do you need a box with dovetails? Probably not.

Re: Tanka: Our way of deploying to Kubernetes

#88

Post by arpa »

slig wrote: post #62
arpa wrote: post #46

Earlier quoted context omitted.

I would argue the same about yaml and whitespace being meaningful. Oh you forgot a single space? Your markup is screwed. Xml is much better...

I spend more time writing and reading files than figuring out syntax errors. Also yaml has comments.

Fair enough.

Re: Tanka: Our way of deploying to Kubernetes

#89

Post by gregwebs »

wikibob wrote: post #24

What are folks thoughts on CurLang these days? Anyone using it for serious configuration yet? https://cuelang.org/ It’s designed by the BCL/GCL author as a replacement (Jsonnet is apparently a copy of BCL/GCL)

I am using it for k8s deployment and overall am quite happy that I can safely configure deployments without boilerplate. The k8s integration makes it easy to get started with, including using existing yaml configuration. Certainly though you have to invest some time to learn it and I have discovered a few rough edges.

I haven't seen another appealing solution in the space. I recommend using Kustomize if you can, but it is very limited in what you can do with it. When I looked at dhall-kubernetes it was lacking some crucial defaulting features that are getting integrated into the language now.

Post reply on HN