A Helm release is a named application instance created when Helm installs a chart into a Kubernetes cluster. The release name identifies that deployed instance, and multiple instances can coexist. section 2.2
A Helm release supports several operational workflows:
- Install a chart and record its deployed name, status, namespace, revision, and chart version. section 2.2
- List releases to inspect which named application instances exist in the cluster. section 2.2
- Represent environment configuration declaratively, with tools such as helmfile defining releases and synchronizing them into a cluster. section 4.1.4
Installing the Conference release
Running `helm install conference oci://docker.io/salaboy/conference-app --version v1.0.0` creates the `conference` release. Helm reports it as deployed in the `default` namespace at revision 1, with the chart version and access instructions. section 2.2
Listing 2.1 Helm installed the chart conference-app version 1.0.0
> helm install conference oci://docker.io/salaboy/conference-app --version v1.0.0 Pulled: registry-1.docker.io/salaboy/conference-app:v1.0.0 Digest: sha256:e5dd1a87a867fd7d6c6caecef3914234a12f23581c5137edf63bfd9add7d5459 NAME: conference LAST DEPLOYED: Mon Jun 26 08:19:15 2023 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: Cloud-Native Conference Application v1.0.0 Chart Deployed: conference-app - v1.0.0 Release Name: conference For more information visit: https://github.com/salaboy/platforms-on-k8s Access the Conference Application Frontend by running 'kubectl port-forward svc/frontend -n default 8080:80'
Inspect the installation output to see the release name, chart version, namespace, deployment status, revision, and generated access note. section 2.2
