*THIS PROJECT IS ABANDONED*. It has been superseded by sitewards/helm-chart. Please note, it may not work as anticipated, and new issues will not be resolved.
Make it trivial to create a Kubernetes deployment, following the littleman.co standards
None
It's hard generating consistant configuration over time. Let's make it easy
| License | Language |
| MIT | en-AU [lang] |
Some parts of it I haven't figured out how to boilerplate just yet (the boilr tool is pretty awesome). Anyway, until it gets support for multiple options, some of this is going to have to be manually filled out.
Also, the Kubernetes asset is numbered as I apply the entire Kubernetes folder every CI run, with something like:
$ kubectl apply -f build/kubernetes
The advantage of this is I always know what state the environment is in (at least, what state CI is trying to set it). The minor disadvantage is I have to make sure assets are created an order.
The order is documented at https://docs.littleman.co/Kubernetes/ (if the link is dead, try a Google search)
$ boilr template download boilr-k8sdeployment k8sdeploymentSwap foo and bar for your own values.
$ mkdir foo
$ cd foo
$ git init
$ git remote set-url origin git@github.com:foo/bar.git
$ boilr template use k8sdeployment .
$ git add .
$ git commit -m "Initial Commit"
$ git pushI update these templates regularly. If you need to fetch the newer version, try this:
$ boilr template download littlemanco/boilr-k8sdeployment k8sdeployment -f- The team behind boilr (https://github.com/tmrts/boilr)
Contributions are always welcome! Nothing is to small, and the best place to start is to open an issue.
| [lang] | Lingoes.net,. (2015). Language Code Table. Retrieved 4 June 2015, from http://www.lingoes.net/en/translator/langcode.htm |