helm-release | Helm Plugin for automatic versioning of helm charts | Continuous Deployment library

by sstarcher Go Version: 0.3.3 License: Apache-2.0

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

kandi X-RAY | helm-release Summary

helm-release is a Go library typically used in Devops, Continuous Deployment, Docker applications. helm-release has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Provides simple semantic versioning based from previous git tags. This allows you to run a single command and package the next version of your chart. This project allows you to combine your Dockerfile and Helm Chart in a single repository and automatically version the Helm chart on a build.

Support

Quality

Security

License

Reuse

Support

helm-release has a low active ecosystem.

It has 48 star(s) with 11 fork(s). There are 3 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 14 have been closed. On average issues are closed in 48 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of helm-release is 0.3.3

Quality

helm-release has 0 bugs and 0 code smells.

Security

helm-release has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

helm-release code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

helm-release is licensed under the Apache-2.0 License. This license is Permissive.

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

Reuse

helm-release releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 723 lines of code, 35 functions and 7 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed helm-release and discovered the below as its top functions. This is intended to give you an instant insight into helm-release implemented functionality, and help decide if they suit your requirements.

UpdateChart updates the Chart s version .
initConfig initializes config file .
init executes the Cobra command .
NextVersion returns the next version .
findChart returns a Chart for the given directory .
New returns a ChartInterface for the given directory .
validate validates the given directory .
NewNextType returns the next available type
Execute executes the root command
Runs the main process

Get all kandi verified functions for this library.

helm-release Key Features

No Key Features are available at this moment for helm-release.

helm-release Examples and Code Snippets

Source,Install without internet

Lines of Code : 3

License : Permissive (Apache-2.0)

Copy

  $ eval $(helm env) # Get helm environment variable for plugin location $HELM_PLUGINS
  $ mkdir /Users/sstarcher/Library/helm/plugins/helm-release
  $ tar -xvf DOWNLOADED_TAR_GZ -C /Users/sstarcher/Library/helm/plugins/helm-release

Helm Release,Install

Lines of Code : 1

License : Permissive (Apache-2.0)

Copy

$ helm plugin install https://github.com/sstarcher/helm-release

Source,Uninstall

Lines of Code : 1

License : Permissive (Apache-2.0)

Copy

$ helm plugin remove release

Community Discussions

Trending Discussions on helm-release

CronJob created as job in k8s 1.19.11

3 pods, when Replicas is set to 2

Execution failed for task... void kotlin.jvm.internal.MutablePropertyReference1Impl.(java.lang.Class, java.lang.String, java.lang.String, int)

QUESTION

CronJob created as job in k8s 1.19.11

Asked 2021-Sep-08 at 05:06

I have what seems like an API issue that results in not being to be able to create a job from a cron job.

I have a CronJob Helm file using the API like so:

...

ANSWER

Answered 2021-Sep-08 at 05:06

CronJobs is generally available (GA) in Google Kubernetes Engine (GKE) version 1.21 and later.

the version you should use apiVersion: batch/v1

https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/

CronJobs was promoted to general availability in Kubernetes v1.21. If you are using an older version of Kubernetes, please refer to the documentation for the version of Kubernetes that you are using, so that you see accurate information. Older Kubernetes versions do not support the batch/v1 CronJob API.

You can check the support Kubernetes API versions using

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

QUESTION

3 pods, when Replicas is set to 2

Asked 2021-May-11 at 19:34

I am running on prem kubernetes. I have a release that is running with 3 pods. At one time (I assume) I deployed the helm chart with 3 replicas. But I have since deployed an update that has 2 replicas.

When I run helm get manifest my-release-name -n my-namespace, it shows that the deployment yaml has replicas set to 2.

But it still has 3 pods when I run kubectl get pods -n my-namespace.

What is needed (from a helm point of view) to get the number of replicas down to the limit I set?

Update
I noticed this when I was debugging a crash loop backoff for the release.

This is an example of what a kubectl describe pod looks like on one of the three pods.

...

ANSWER

Answered 2021-May-11 at 19:34

What is needed (from a helm point of view) to get the number of replicas down to the limit I set?

Your pods need to be in a "healthy" state. Then they are in your desired number of replicas.

First, you deployed 3 replicas. This is managed by a ReplicaSet.

Then you deployed a new revision, with 2 replicas. A "rolling deployment" will be performed. First pods with your new revision will be created, but replicas of your old ReplicaSet will only be scaled down when you have healthy instances of your new revision.

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

QUESTION

Execution failed for task... void kotlin.jvm.internal.MutablePropertyReference1Impl.(java.lang.Class, java.lang.String, java.lang.String, int)

Asked 2020-Nov-15 at 20:38

I'm trying to build a Gradle plugin for packing helm charts. After packaging I want to upload the chart using fuel. However as soon as I execute Fuel.upload(url) I hit the following exception.

...

ANSWER

Answered 2020-Oct-09 at 06:59

According to Fuel 2.3.0 release note:

This won't be compatible with Kotlin 1.3.72

So you have to either downgrade to Fuel 2.2.0 and Kotlin 1.3.72 or wait until Gradle fix this issue (hopefully in version 6.8)

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

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

Vulnerabilities

No vulnerabilities reported

Install helm-release

You can install a specific release version:.
Grab the tar file for your system from the releases

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: