helm | [ WIP ! ]

by sorellabs JavaScript Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | helm Summary

helm is a JavaScript library typically used in Template Engine applications. helm has no bugs, it has a Permissive License and it has low support. However helm has 10 vulnerabilities. You can download it from GitHub.

A safe HTML templating embedded domain specific language.

Support

Quality

Security

License

Reuse

Support

helm has a low active ecosystem.

It has 9 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 8 have been closed. On average issues are closed in 329 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of helm is current.

Quality

helm has no bugs reported.

Security

helm has 10 vulnerability issues reported (2 critical, 0 high, 5 medium, 3 low).

License

helm is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

helm releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of helm

Get all kandi verified functions for this library.

helm Key Features

No Key Features are available at this moment for helm.

helm Examples and Code Snippets

No Code Snippets are available at this moment for helm.

Community Discussions

Trending Discussions on helm

Deployment stops after creation of few resources

Specifying local helm dependency

helm charting - how to render a same template more than once?

Patching Ingress Resource returns no change

how do I send notes.txt output to a file instead of dumping it to the console?

when installing bitnami mongodb-sharded, i got error from PVCs: no persistent volumes available for this claim and no storage class is set

Standard Wordpress installation migrate to Kubernetes bitnami/wordpress

How to expose kubernetes POD's Rest URL to a helm hook?

Helm upgrade not working when upgrading from 2.10.0 to 3.1.0

How to access variable out of current range control in helm template

QUESTION

Deployment stops after creation of few resources

Asked 2021-Jun-13 at 13:15

I am instantiating a deployment from Helm. a few pods are getting created but the deployment stops right after creating few pods. Although I cannot share much info on the deployment as it is related to my company, how can I debug this kind of issue? The created pods have no problem as seen from logs and events.

...

ANSWER

Answered 2021-Jun-13 at 13:15

to debug your application you should first of all :

Check the pods logs using sh kubectl logs pod
check the event using sh kubectl get events .....

Sometimes if a pods crush you can find the logs or events so you need to add a flag to logs command : sh kubectl logs pods --previous=true

I hope that can help you to resolve your issue.

Source https://stackoverflow.com/questions/67955867

QUESTION

Specifying local helm dependency

Asked 2021-Jun-11 at 11:33

I am trying to add a rabbitmq service using a bitnami helm chart. the chart contains one dependent helm chart which is called common. The whole application itself is deployed using a parent helm chart and each service has its own separate helm chart. the Helm chart structure looks like this-

...

ANSWER

Answered 2021-Jun-11 at 11:33

You don't need to unpack the charts/*.tgz file. If they're in that directory (and still packed up) then Helm will use them to run the deployment. Helm won't contact the external chart repository on its own, only when you run the helm dependency commands.

After you run helm dep up your filesystem layout should look like

Source https://stackoverflow.com/questions/67912506

QUESTION

helm charting - how to render a same template more than once?

Asked 2021-Jun-11 at 11:13

I wish to create a helm chart to deploy an app that has multiple different pods (hence multiple deployment manifests). Here's the structure of the chart:

...

ANSWER

Answered 2021-Jun-11 at 11:13

You can use any templating constructs you want inside the template files. A file can include (or generate) multiple YAML files (or none); if it's more than one you need to make sure each begins with the --- YAML start-of-document marker.

If you wanted to generate multiple Deployments based on values, for example, you can specify

Source https://stackoverflow.com/questions/67932132

QUESTION

Patching Ingress Resource returns no change

Asked 2021-Jun-10 at 14:17

I have 2 helm deployments (node-app-blue-helm-chart node-app-green-helm-chart ) and my ingress resource is seperate and like this:

...

ANSWER

Answered 2021-Jun-10 at 14:17

serviceName is not the recent representation. Changing it to service/name fixed problem.

Source https://stackoverflow.com/questions/67898731

QUESTION

how do I send notes.txt output to a file instead of dumping it to the console?

Asked 2021-Jun-10 at 09:42

I want helm to write the output of notes.txt to a local file instead of just dumping it to the console. I want to write a json file that is going to be read by another system (that is going to send a slack message)

If that is not possible is there a separate helm command that just outputs notes.txt without having to do a full deploy?

I dont want to have to try to capture and parse it out of the entire deployment output

...

ANSWER

Answered 2021-Jun-10 at 09:42

helm status will show you the state of a release. This also contains the notes.txt output.

Helm offers the ability to specify the output format of the helm status command (doc). So by running:

Source https://stackoverflow.com/questions/67909726

QUESTION

when installing bitnami mongodb-sharded, i got error from PVCs: no persistent volumes available for this claim and no storage class is set

Asked 2021-Jun-09 at 21:30

I am trying to install my rancher(RKE) kubernetes cluster bitnami/mongodb-shared . But I couldn't create a valid PV for this helm chart.

The error that I am getting: no persistent volumes available for this claim and no storage class is set

This is the helm chart documentation section about PersistenceVolume: https://github.com/bitnami/charts/tree/master/bitnami/mongodb-sharded/#persistence

This is the StorageClass and PersistentVolume yamls that I created for this helm chart PVCs':

...

ANSWER

Answered 2021-Jun-07 at 15:00

The chart exposes two parameters that allow you to choose the StorageClass you want to use for your PVC(s) (otherwise it will use the 'default' one):

configsvr.persistence.storageClass
shardsvr.persistence.storageClass

Find more information in the Parameters section of the README.md

So basically you need to install the chart setting these parameters accordingly.

Source https://stackoverflow.com/questions/67862431

QUESTION

Standard Wordpress installation migrate to Kubernetes bitnami/wordpress

Asked 2021-Jun-09 at 13:39

I have stanard wordpress installation on my server with all plugins, themes and stuff. Now I want to migrate to kubernetes server where I have already installed bitnami/wordpress. I see a bit other structure of files in bitnami/Wordpress installation on kubernetes where is only wp-content and config file in main folder of wordpress.

Can I copy normal Wordpress installation to Kubernetes image bitnami/wordpress installation from image installed by helm? How will be to do it best? Should I do it like normal wordpress website or other technique and tools?

...

ANSWER

Answered 2021-Jun-09 at 13:39

Bitnami Engineer here,

The app's files are now inside the /opt/bitnami/wordpress directory. We recently updated all our WordPress cloud solutions to have the same directory structure. However, it seems that you have a previous version of the solution deployed in the cloud our you used the Bitnami installer in your server.

The easiest way to migrate your data from your current server to the k8s deployment is by using the All in One WP Migration plugin. The plugin takes care of saving all the necessary data so you just need to recover that data in the new deployment. You won't need to copy any other file from the deployment when using this plugin.

Source https://stackoverflow.com/questions/67899585

QUESTION

How to expose kubernetes POD's Rest URL to a helm hook?

Asked 2021-Jun-09 at 08:17

I have a use case wherein I have a Rest API running on a POD inside kubernetes cluster, and the helm pre-upgrade hook which runs a k8s Job needs to access Rest API, What is the best way to expose this URL so that helm hook can access it. I do not want to hardcode any Ip.

...

ANSWER

Answered 2021-Jun-09 at 08:17

Posting this as a community wiki, feel free to edit and expand it for better experience.

As David Maze and Lucia pointed out in comments, services are accessible by their IPs and URLs based on service names.

This part is covered and well explained in official kubenetes documentation DNS for services and pods

Source https://stackoverflow.com/questions/67776086

QUESTION

Helm upgrade not working when upgrading from 2.10.0 to 3.1.0

Asked 2021-Jun-08 at 22:50

I was running the older 2.16.0 version of ChartMuseum Helm Chart. I am trying to update it to use newer 3.1.0. When I try to upgrade using helm upgrade -n , the upgradation fails with the following error:

...

ANSWER

Answered 2021-Jun-08 at 22:50

That's not from Helm, that's a Kubernetes error. This chart does not support clean upgrades or your values are not matching what you had before. If you can take the downtime, delete the offending deployment and let Helm recreate it. Otherwise you have to look up the right dance of orphan deletes and whatnot.

Source https://stackoverflow.com/questions/67894813

QUESTION

How to access variable out of current range control in helm template

Asked 2021-Jun-08 at 18:21

I have a helm template like this,

...

ANSWER

Answered 2021-Jun-08 at 09:17

You can use $ to get to the root scope. So instead of .type you can use $.type. Here you used $type, that is why it's showing undefined (undefined variable "$type", rather it would be $.type.

Source https://stackoverflow.com/questions/67884564

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

CVE-2021-21303 MEDIUM

Helm is open-source software which is essentially "The Kubernetes Package Manager". Helm is a tool for managing Charts. Charts are packages of pre-configured Kubernetes resources. In Helm from version 3.0 and before version 3.5.2, there a few cases where data loaded from potentially untrusted sources was not properly sanitized. When a SemVer in the `version` field of a chart is invalid, in some cases Helm allows the string to be used "as is" without sanitizing. Helm fails to properly sanitized some fields present on Helm repository `index.yaml` files. Helm does not properly sanitized some fields in the `plugin.yaml` file for plugins In some cases, Helm does not properly sanitize the fields in the `Chart.yaml` file. By exploiting these attack vectors, core maintainers were able to send deceptive information to a terminal screen running the `helm` command, as well as obscure or alter information on the screen. In some cases, we could send codes that terminals used to execute higher-order logic, like clearing a terminal screen. Further, during evaluation, the Helm maintainers discovered a few other fields that were not properly sanitized when read out of repository index files. This fix remedies all such cases, and once again enforces SemVer2 policies on version fields. All users of the Helm 3 should upgrade to the fixed version 3.5.2 or later. Those who use Helm as a library should verify that they either sanitize this data on their own, or use the proper Helm API calls to sanitize the data.

https://github.com/helm/helm/security/advisories/GHSA-c38g-469g-cmgx

https://github.com/helm/helm/releases/tag/v3.5.2

https://github.com/helm/helm/commit/6ce9ba60b73013857e2e7c73d3f86ed70bc1ac9a

CVE-2020-15187 MEDIUM

In Helm before versions 2.16.11 and 3.3.2, a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack. To perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection). This issue has been patched in Helm 2.16.11 and Helm 3.3.2. As a possible workaround make sure to install plugins using a secure connection protocol like SSL.

https://github.com/helm/helm/security/advisories/GHSA-c52f-pq47-2r9j

https://github.com/helm/helm/commit/d9ef5ce8bad512e325390c0011be1244b8380e4b

CVE-2020-15186 LOW

In Helm before versions 2.16.11 and 3.3.2 plugin names are not sanitized properly. As a result, a malicious plugin author could use characters in a plugin name that would result in unexpected behavior, such as duplicating the name of another plugin or spoofing the output to `helm --help`. This issue has been patched in Helm 3.3.2. A possible workaround is to not install untrusted Helm plugins. Examine the `name` field in the `plugin.yaml` file for a plugin, looking for characters outside of the [a-zA-Z0-9._-] range.

https://github.com/helm/helm/commit/809e2d999e2c33e20e77f6bff30652d79c287542

https://github.com/helm/helm/security/advisories/GHSA-m54r-vrmv-hw33

CVE-2020-15185 LOW

In Helm before versions 2.16.11 and 3.3.2, a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository. To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection). This issue has been patched in Helm 3.3.2 and 2.16.11. A possible workaround is to manually review the index file in the Helm repository cache before installing software.

https://github.com/helm/helm/security/advisories/GHSA-jm56-5h66-w453

https://github.com/helm/helm/commit/055dd41cbe53ce131ab0357524a7f6729e6e40dc

CVE-2020-15184 LOW

In Helm before versions 2.16.11 and 3.3.2 there is a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart. This issue has been patched in Helm 3.3.2 and 2.16.11. A possible workaround is to manually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters.

https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850

https://github.com/helm/helm/security/advisories/GHSA-9vp5-m38w-j776

CVE-2020-4053 MEDIUM

In Helm greater than or equal to 3.0.0 and less than 3.2.4, a path traversal attack is possible when installing Helm plugins from a tar archive over HTTP. It is possible for a malicious plugin author to inject a relative path into a plugin archive, and copy a file outside of the intended directory. This has been fixed in 3.2.4.

https://github.com/helm/helm/commit/0ad800ef43d3b826f31a5ad8dfbb4fe05d143688

https://github.com/helm/helm/releases/tag/v3.2.4

https://github.com/helm/helm/security/advisories/GHSA-qq3j-xp49-j73f

CVE-2020-11013 MEDIUM

Their is an information disclosure vulnerability in Helm from version 3.1.0 and before version 3.2.0. `lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates. The documented behavior of `helm template` states that it does not attach to a remote cluster. However, a the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior. Running `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability. A malicious chart author could inject a `lookup` into a chart that, when rendered through `helm template`, performs unannounced lookups against the cluster a user's `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`. This issue has been fixed in Helm 3.2.0

https://github.com/helm/helm/security/advisories/GHSA-q8q8-93cv-v6h8

https://github.com/helm/helm/releases/tag/v3.2.0

CVE-2019-18658 CRITICAL

In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a maliciously designed chart to include sensitive content such as /etc/passwd, or to execute a denial of service (DoS) via a special file such as /dev/urandom, via symlinks. No version of Tiller is known to be impacted. This is a client-only issue.

https://helm.sh/blog/2019-10-30-helm-symlink-security-notice/

CVE-2019-1010275 CRITICAL

helm Before 2.7.2 is affected by: CWE-295: Improper Certificate Validation. The impact is: Unauthorized clients could connect to the server because self-signed client certs were aloowed. The component is: helm (many files updated, see https://github.com/helm/helm/pull/3152/files/1096813bf9a425e2aa4ac755b6c991b626dfab50). The attack vector is: A malicious client could connect to the server over the network. The fixed version is: 2.7.2.

https://github.com/helm/helm/pull/3152/files/1096813bf9a425e2aa4ac755b6c991b626dfab50

https://github.com/helm/helm/pull/3152

https://github.com/helm/helm/releases/tag/v2.7.2

CVE-2019-1000008 MEDIUM

All versions of Helm between Helm >=2.0.0 and < 2.12.2 contains a CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in The commands `helm fetch --untar` and `helm lint some.tgz` that can result when chart archive files are unpacked a file may be unpacked outside of the target directory. This attack appears to be exploitable via a victim must run a helm command on a specially crafted chart archive. This vulnerability appears to have been fixed in 2.12.2.

https://helm.sh/blog/helm-security-notice-2019/index.html

Install helm

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: