6 ms·
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) Integrati
by shorez 7y ago
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: {
deployment: import "./deployment.yaml",
service: import "./service.yaml",
}
}
In environments/default/main.jsonnet:
(import "foo/foo.jsonnet") + {
// patch environment specific things here
// https://tanka.dev/tutorial/environments#patching
}
Then use `tk show` to verify it works.
Furthermore, follow the tutorial to get an in depth understanding of Tanka: https://tanka.dev/tutorial/overview https://tanka.dev/tutorial/overview
- vicjicama 7y agoThank 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