-
Given the following install
```
╰─○ helm install elasticsearch-logging
---> Running `kubectl create -f` ...
services/elasticsearch-logging
services/kibana-logging
replicationcontrollers/elasticsearch…
-
```
[WARN] No support for kind DaemonSet. Ignoring.
---> Running `kubectl create -f` ...
---> Done
```
-
Obviously daemon controller is the way to go here but have you guys actually tried that yet? Should this work if I use a daemon controller manifest to start it?
-
We are starting to discuss formalizing / defining how an application is deployed onto Kube (via config files, examples, deployment-manager, Helm, and OpenShift templates). Many of those applications …
-
So for some reason the `daemonset` I have been working on requires me to pass in `-validate=false` for it to work.
That got me thinking that we might want to accept kubectl params into helm install. …
-
What's the purpose of this script? I cant find where its being called but it looks like it should be used.
-
Right now, dependency resolution works like this:
- fetch grabs a chart, and checks the direct dependencies
- if the dependencies are not satisfied, it emits a warning
And install works similarly:
- …
-
Implement the CI/CD and image bakery parts of the Kubernetes-based cloud native architecture that we are investigating through the integration of Deployment Manager with Spinnaker, if possible. Build …
-
e.g. v1, v1beta1.
For the first pass, we could use flags like this to alert the user that they must have particular things enabled on their cluster. Combined with @rimusz's suggested `helm show` comm…
-
After install, we can add an (optional?) check to make sure that all manifests we installed resulted in created resources.