chartmuseum | helm chart repository server | Continuous Deployment library

by helm Go Version: v0.16.0 License: Apache-2.0

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

kandi X-RAY | chartmuseum Summary

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

ChartMuseum is an open-source Helm Chart Repository server written in Go (Golang), with support for cloud storage backends, including Google Cloud Storage, Amazon S3, Microsoft Azure Blob Storage, Alibaba Cloud OSS Storage, Openstack Object Storage, Oracle Cloud Infrastructure Object Storage, Baidu Cloud BOS Storage, Tencent Cloud Object Storage, Netease Cloud NOS Storage, DigitalOcean Spaces, Minio, and etcd. Works as a valid Helm Chart Repository, and also provides an API for uploading charts.

Support

Quality

Security

License

Reuse

Support

chartmuseum has a medium active ecosystem.

It has 3223 star(s) with 367 fork(s). There are 59 watchers for this library.

It had no major release in the last 12 months.

There are 91 open issues and 251 have been closed. On average issues are closed in 234 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chartmuseum is v0.16.0

Quality

chartmuseum has 0 bugs and 0 code smells.

Security

chartmuseum has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chartmuseum code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chartmuseum 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

chartmuseum releases are available to install and integrate.

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

It has 5840 lines of code, 215 functions and 37 files.

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

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 chartmuseum

Get all kandi verified functions for this library.

chartmuseum Key Features

No Key Features are available at this moment for chartmuseum.

chartmuseum Examples and Code Snippets

No Code Snippets are available at this moment for chartmuseum.

Community Discussions

Trending Discussions on chartmuseum

Helm upgrade not working when upgrading from 2.10.0 to 3.1.0

Why does Helm push with "--dependency-update" not find the repository by name but "helm dependency update" does?

kubelet stop post node status and node "k8sslave1" not found with kubelet in kubernetes

How to push helm packages in a chartmuseum through a ci-cd pipeline?

Helm: when to push a chart

Jx Boot Fails Step `install-jenkins-x` w/ Command "sh -c jx step helm apply --boot --remote --name jenkins-x --provider-values-dir ../kubeProviders"

Jenkins on EKS can't connect to external EC2 server as Jenkins worker-node: ERROR `port:50000 is not reachable`

OpenShift: Accessing mounted file-system as non-root

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

Why does Helm push with "--dependency-update" not find the repository by name but "helm dependency update" does?

Asked 2020-Dec-10 at 12:32

I have a Chart.yaml with the following:

Chart.yaml

...

ANSWER

Answered 2020-Dec-10 at 12:32

This is a community wiki answer. Feel free to expand on it.

The --dependency-update flag for the helm push plugin is currently not working properly due to the fact that it does not omit the @ symbol when checking the name of the repository.

As a workaround, you could use the Helm Dependency Update with a --repository-config string flag:

path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")

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

QUESTION

kubelet stop post node status and node "k8sslave1" not found with kubelet in kubernetes

Asked 2020-Jul-26 at 05:31

My local machine kubernetes cluster running fine yesterday util I install some component, my slave1 and slave2 only have 4G for each, and I check the free memory only have 100MB+, then I stop the VM and increase the KVM virtual machine memory to 8GB. And recheck the free memory to make sure it have 2GB+ free for each node. Now the slave1 and slave2 node not running fine,this is the node status:

...

ANSWER

Answered 2020-Jul-26 at 05:31

are you using kubeadm? if you are using kubeadm; you can follow the next steps:

Delete slaves nodes

kubecl delete node k8sslave1
From the slaves' nodes, execute:

kubeadm reset
Then you need to join the slaves' nodes to the cluster, in the master node execute:

token=$(kubeadm token generate)

kubeadm token create $token --ttl 2h --print-join-command
Paste the output of the command in the slaves nodes.

kubectl join ...
Review that the nodes are join to the cluster and the new state is Ready.

ubuntu@kube-master:~$ kubectl get nodes

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

QUESTION

How to push helm packages in a chartmuseum through a ci-cd pipeline?

Asked 2020-Jun-14 at 20:14

i want to configure a ci-cd pipeline, that should contains a stage for placing the helm charts in a chartmuseum (which is in an aws s3 Bucket for example). i have already the operation configured with helm s3 plugin(which uses aws s3 as a helm repository and push direct the charts into it through the pipeline execution:

...

ANSWER

Answered 2020-Jun-14 at 20:14

After you have stood up your charmuseum instance, add something like the following lines to your CI/CD pipeline.

helm repo add chartmuseum http://[host]

helm push chart/ chartmuseum

Or push a particular version:
helm push chart/ --version="[version]" chartmuseum

Docs from:
https://github.com/chartmuseum/helm-push

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

QUESTION

Helm: when to push a chart

Asked 2020-May-27 at 16:52

I don't quite to figure out when a helm chart has to be pushed on a chartmuseum or any other repo.

I mean:

each time an app version changes, regardless of whether internal resources and values have not changed? For example, a new image version has changed.
or each time chart handles a new (or remove, or change) resource, or add a new value...?

I hope I've explained so well.

...

ANSWER

Answered 2020-May-27 at 16:52

In general, it is up to chart maintainers to push chart in any of that cases. More info about charts and verioning.

In your case, you will:

change appVersion field in Chart.yaml file when the app image changes
change version field in Chart.yaml file when chart resources are modified.

Make sure you follow SemVer 2 standard when modifying any of those.

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

QUESTION

Jx Boot Fails Step `install-jenkins-x` w/ Command "sh -c jx step helm apply --boot --remote --name jenkins-x --provider-values-dir ../kubeProviders"

Asked 2020-May-14 at 21:54

I'm currently trying to install Jenkins X into my GKE Kubernetes Cluster. But jx boot is failing on step "install-jenkins-x".

My jx version output is:

...

ANSWER

Answered 2020-May-14 at 21:54

This is a known issue in jx boot on Windows - https://github.com/jenkins-x/jx/issues/7156. Have you tried it using Windows Subsystem for Linux?

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

QUESTION

Jenkins on EKS can't connect to external EC2 server as Jenkins worker-node: ERROR `port:50000 is not reachable`

Asked 2020-Apr-01 at 16:28

My main task is to create a Jenkins Node from an EC2 instance/server.

Jenkins server it's on EKS deployed via jx

...

ANSWER

Answered 2020-Apr-01 at 16:28

After experimenting all day...

I came with a solution, it's not the best or straight forward but at least it's working. My slave is connected! INFO: Connected

So, I edited the jenkins-agent service and from type: ClusterIP I changed to type: LoadBalancer. That gave me a new fresh loadbalancer and after I decided to add the port 8080 because in the service yaml file it's using the same selector as in jenkins service.

(jenkins-agent service yaml)

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

QUESTION

OpenShift: Accessing mounted file-system as non-root

Asked 2020-Jan-04 at 07:54

I am trying to run Chart Museum as a non-root user in OpenShift. Here is a snapshot of my YAML.

...

ANSWER

Answered 2020-Jan-03 at 08:24

It's related to Kubernetes and how the given Persistent Volume is defined. You can check all the discussion and possible workarounds in the related GH Issue.

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

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