You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2020-08-28-openfaas-arkade.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,15 @@ dark_background: true
14
14
15
15
The OpenFaaS community is building a tool for Kubernetes developers, learn how it can help you install OpenFaaS, along with complementary CLIs and applications to your cluster
> [arkade](https://get-arkade.dev) - "Your one-stop CLI for Kubernetes"
20
20
21
21
## Solving pain
22
22
23
23
The popular essay [Cathedral and the Bazaar](http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/) was written over 20 years ago by author and then open source activist Eric Steven Raymond. In it, he contrasts the development of proprietary software within a corporation (the cathedral) to that of an open-source model (the bazaar). One of the key points he makes is that most open-source software starts when a developer has an itch they need to scratch or finds a pain-point that they can solve.
24
24
25
-
arkade has evolved since it was first created to install OpenFaaS, to now install 3 dozen different applications using their preferred installation method.
25
+
[arkade](https://get-arkade.dev) has evolved since it was first created to install OpenFaaS, to now install 3 dozen different applications using their preferred installation method.
26
26
27
27
* OpenFaaS - [helm3](https://helm.sh)
28
28
* Linkerd - its own CLI
@@ -32,6 +32,8 @@ It then gained the ability to install CLIs such as `faas-cli` and `kubectl` whic
32
32
33
33
Now if you're anything like us, then you will be re-creating a cluster several times per day or per week to test a PR or change to your project, you may even be creating a cluster in a CI job to test each incoming commit. arkade is built for developers to rapidly get a working system with whatever they need. You can use it in production, or in a pipeline, but you may find that a GitOps style more suitable using a tool like [ArgoCD](https://argoproj.github.io/argo-cd/) or [Flux](https://fluxcd.io).
34
34
35
+
> ⭐️Star/fork [arkade](https://get-arkade.dev) on GitHub
36
+
35
37
### Helm 2 - insecure by default
36
38
37
39
Since around 2017, OpenFaaS was packaged with a [helm](https://helm.sh) chart, and back in those days, you used to have to install a very insecure component to your cluster ([Tiller](https://v2.helm.sh/docs/install/)), which ran in a kind of "God mode." If someone accessed Tiller, and it was very easy to do so, then it would be game over. This wasn't just a problem for OpenFaaS, but for any other helm chart you wanted to install.
@@ -243,7 +245,7 @@ Find out more on the [inlets PRO landing page](https://inlets.dev/), there's als
243
245
244
246
## Wrapping up
245
247
246
-
arkade was written to make the life of developers easier, it can install many different applications, which may involve using Helm, kubectl, or an additional CLI. It gives helpful usage information, and tries to prevent you doing things you shouldn't, like installing an application to your Raspberry Pi cluster that isn't built for ARM CPUs. It makes the tedious task of downloading dozens of CLIs much quicker.
248
+
[arkade](https://get-arkade.dev) was written to make the life of developers easier, it can install many different applications, which may involve using Helm, kubectl, or an additional CLI. It gives helpful usage information, and tries to prevent you doing things you shouldn't, like installing an application to your Raspberry Pi cluster that isn't built for ARM CPUs. It makes the tedious task of downloading dozens of CLIs much quicker.
247
249
248
250
Looking forward, arkade will continue to be maintained by the OpenFaaS community and is accepting PRs and suggestions. It evolved to solve a clear pain-point, and as we approach 1000 stars on GitHub, it has proven useful to the community so far.
0 commit comments