upstream/helm
1
0
Fork 0
mirror of https://github.com/helm/helm.git synced 2026-04-15 21:59:50 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
Helm - Package manager pour Kubernetes
8211 commits 65 branches 249 tags 137 MiB
Go 98.4%
Shell 1.3%
Makefile 0.3%
Find a file
Benoit Tigeot 6b5fa33633
debug log level is dynamic and set after Logger creation 
So we should use dynamic handler to set the log level after. With this
patch we can clearly see the output. Before we were always stuck in log
level "info" and not seeing debug log level

```
bin/helm upgrade --install --debug --wait frontend \
--namespace test \
--set replicaCount=2 \
--set backend=http://backend-podinfo:9898/echo \
podinfo/podinfo
level=DEBUG msg="getting history for release" release=frontend
level=DEBUG msg="preparing upgrade" name=frontend
level=DEBUG msg="performing update" name=frontend
level=DEBUG msg="creating upgraded release" name=frontend
level=DEBUG msg="checking resources for changes" resources=2
level=DEBUG msg="no changes detected" kind=Service name=frontend-podinfo
level=DEBUG msg="patching resource" kind=Deployment name=frontend-podinfo namespace=test
level=DEBUG msg="waiting for resources" count=2 timeout=5m0s
level=DEBUG msg="waiting for resource" name=frontend-podinfo kind=Deployment expectedStatus=Current actualStatus=Unknown
level=DEBUG msg="updating status for upgraded release" name=frontend
Release "frontend" has been upgraded. Happy Helming!
NAME: frontend
LAST DEPLOYED: Thu Apr 10 09:56:25 2025
NAMESPACE: test
STATUS: deployed
REVISION: 6
DESCRIPTION: Upgrade complete
```

Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>
2025-04-10 10:03:13 +02:00
.github Merge pull request #30688 from helm/dependabot/github_actions/main/actions/setup-go-5.4.0 2025-03-21 13:15:27 -07:00
cmd/helm Linting 2025-04-07 17:49:03 +02:00
internal Properly discard by default logs 2025-04-07 16:47:26 +02:00
pkg debug log level is dynamic and set after Logger creation 2025-04-10 10:03:13 +02:00
scripts Remove 'coveralls' 2025-03-01 16:48:21 -08:00
testdata Updating the certificates used for testing 2022-08-24 14:10:03 -04:00
.gitignore Add precommit config to .gitignore 2024-11-19 17:31:34 +00:00
.golangci.yml Updating to helm.sh/helm/v4 2024-12-26 16:33:51 -05:00
ADOPTERS.md Add Percona to the list of organizations using Helm 2025-02-07 11:47:48 +00:00
code-of-conduct.md Fixing the code of conduct pointer 2019-12-04 10:23:10 -05:00
CONTRIBUTING.md chore: update profiling doc in CONTRIBUTING.md 2025-02-17 10:27:11 +00:00
go.mod switch back to k8s rest mapper 2025-03-25 14:10:31 +00:00
go.sum switch back to k8s rest mapper 2025-03-25 14:10:31 +00:00
KEYS adding-my-key 2025-02-12 15:35:10 -05:00
LICENSE fix(LICENSE): add copyright year and authors 2016-06-22 10:24:25 -06:00
Makefile Move pkg/chart to pkg/chart/v2 to prepare for v3 charts 2025-02-25 15:20:44 -05:00
OWNERS Reorder triage ids 2024-10-13 13:37:20 +01:00
README.md fix: Fix go report card badge reference/link 2025-03-01 17:50:15 -08:00
SECURITY.md Adding security file 2020-01-28 10:58:27 -05:00

README.md

Helm

Build Status Go Report Card GoDoc CII Best Practices OpenSSF Scorecard

Helm is a tool for managing Charts. Charts are packages of pre-configured Kubernetes resources.

Use Helm to:

  • Find and use popular software packaged as Helm Charts to run in Kubernetes
  • Share your own applications as Helm Charts
  • Create reproducible builds of your Kubernetes applications
  • Intelligently manage your Kubernetes manifest files
  • Manage releases of Helm packages

Helm in a Handbasket

Helm is a tool that streamlines installing and managing Kubernetes applications. Think of it like apt/yum/homebrew for Kubernetes.

  • Helm renders your templates and communicates with the Kubernetes API
  • Helm runs on your laptop, CI/CD, or wherever you want it to run.
  • Charts are Helm packages that contain at least two things:
    • A description of the package (Chart.yaml)
    • One or more templates, which contain Kubernetes manifest files
  • Charts can be stored on disk, or fetched from remote chart repositories (like Debian or RedHat packages)

Helm Development and Stable Versions

Helm v4 is currently under development on the main branch. This is unstable and the APIs within the Go SDK and at the command line are changing. Helm v3 (current stable) is maintained on the dev-v3 branch. APIs there follow semantic versioning.

Install

Binary downloads of the Helm client can be found on the Releases page.

Unpack the helm binary and add it to your PATH and you are good to go!

If you want to use a package manager:

  • Homebrew users can use brew install helm.
  • Chocolatey users can use choco install kubernetes-helm.
  • Winget users can use winget install Helm.Helm.
  • Scoop users can use scoop install helm.
  • Snapcraft users can use snap install helm --classic.
  • Flox users can use flox install kubernetes-helm.

To rapidly get Helm up and running, start with the Quick Start Guide.

See the installation guide for more options, including installing pre-releases.

Docs

Get started with the Quick Start guide or plunge into the complete documentation

Roadmap

The Helm roadmap uses GitHub milestones to track the progress of the project.

The development of Helm v4 is currently happening on the main branch while the development of Helm v3, the stable branch, is happening on the dev-v3 branch. Changes should be made to the main branch prior to being added to the dev-v3 branch so that all changes are carried along to Helm v4.

Community, discussion, contribution, and support

You can reach the Helm community and developers via the following channels:

Contribution

If you're interested in contributing, please refer to the Contributing Guide before submitting a pull request.

Code of conduct

Participation in the Helm community is governed by the Code of Conduct.