helm-operator | controller — The Flux Helm Operator | Continuous Deployment library

by fluxcd Go Version: 1.4.2 License: Apache-2.0

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

kandi X-RAY | helm-operator Summary

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

:warning: Notice The Helm Operator is in maintenance mode, while we are investing into the future of GitOps by re-architecting our tooling from the ground up. The Helm Operator is a Kubernetes operator, allowing one to declaratively manage Helm chart releases. Combined with Flux this can be utilized to automate releases in a GitOps manner, but the usage of Flux is not a strict requirement. The desired state of a Helm release is described through a Kubernetes Custom Resource named HelmRelease. Based on the creation, mutation or removal of a HelmRelease resource in the cluster, Helm actions are performed by the operator.

Support

Quality

Security

License

Reuse

Support

helm-operator has a low active ecosystem.

It has 639 star(s) with 261 fork(s). There are 12 watchers for this library.

It had no major release in the last 12 months.

There are 101 open issues and 203 have been closed. On average issues are closed in 132 days. There are 16 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of helm-operator is 1.4.2

Quality

helm-operator has 0 bugs and 0 code smells.

Security

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

helm-operator code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

helm-operator 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-operator releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

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-operator

Get all kandi verified functions for this library.

helm-operator Key Features

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

helm-operator Examples and Code Snippets

No Code Snippets are available at this moment for helm-operator.

Community Discussions

Trending Discussions on helm-operator

How to create and use a new ConfigMap when calling a third party chart?

GitOps (Flex) install of standard Jenkins Helm chart in Kubernetes via HelmRelease operator

QUESTION

How to create and use a new ConfigMap when calling a third party chart?

Asked 2020-Nov-29 at 15:19

We have an instance of Concourse which is deployed to Kubernetes using Flux via a HelmRelease file, which holds our custom values and references the Concourse Helm Chart. Note: We're using Helm v3.

The chart allows you to specify addionalVolumes and additionalVolumneMounts; a feature I'm hoping to use to map /etc/Docker/Daemon.json to our worker pods to make them use our pull-through mirror proxy (i.e. to avoid Docker rate limit issues).

...

ANSWER

Answered 2020-Nov-29 at 15:19

I ended up resolving this by creating a configMap outside of the helm chart, then consuming it within.

Config Map:

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

QUESTION

GitOps (Flex) install of standard Jenkins Helm chart in Kubernetes via HelmRelease operator

Asked 2020-Feb-02 at 05:56

I've just started working with Weavework's Flux GitOps system in Kubernetes. I have regular deployments (deployments, services, volumes, etc.) working fine. I'm trying for the first time to deploy a Helm chart.

I've followed the instructions in this tutorial: https://github.com/fluxcd/helm-operator-get-started and have its sample service working after making a few small changes. So I believe that I have all the right tooling in place, including the custom HelmRelease K8s operator.

I want to deploy Jenkins via Helm, which if I do manually is as simple as this Helm command:

...

ANSWER

Answered 2020-Feb-02 at 05:56

Have you tried checking the logs on the fluxd and flux-helm-operator pods? I would start there to see what error message you're getting. One thing that i'm seeing is that you're using https for git. You may want to double check, but I don't recall ever seeing any documentation configuring chart pulls via git to use anything other than SSH. Moreover, I'd recommend just pulling that chart from the stable helm repository anyhow:

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

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

Vulnerabilities

No vulnerabilities reported

Install helm-operator

Get started installing the Helm Operator or just browse through the documentation.

Support

We welcome all kinds of contributions to the Helm Operator, be it code, issues you found, documentation, external tools, help and support or anything else really. The Helm Operator and other projects in the FluxCD umbrella adhere to the CNCF Code of Conduct. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Flux project maintainer, or the CNCF mediator, Mishi Choudhary mishi@linux.com.

Find more information at: