### Helm Install Command Example

Source: https://github.com/bitnami/charts/blob/main/bitnami/multus-cni/README.md

Example of how to install the Multus CNI Helm chart using the `helm install` command with `--set` arguments to override default values. This example demonstrates setting the scheduler name.

```bash
helm install my-release \
  --set schedulerName=high-priority \
    oci://REGISTRY_NAME/REPOSITORY_NAME/multus-cni
```

--------------------------------

### Helm Install Command Example

Source: https://github.com/bitnami/charts/blob/main/bitnami/parse/README.md

Example of how to install the Parse Helm chart using `helm install` with the `--set` argument to configure parameters like dashboard username and password. This demonstrates overriding default chart values.

```bash
helm install my-release \
  --set dashboard.username=admin,dashboard.password=password \
    oci://REGISTRY_NAME/REPOSITORY_NAME/parse
```

--------------------------------

### Helm Install with Values File Example

Source: https://github.com/bitnami/charts/blob/main/bitnami/multus-cni/README.md

Example of how to install the Multus CNI Helm chart using the `helm install` command with a custom `values.yaml` file. This method is useful for managing multiple configuration overrides.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/multus-cni
```

--------------------------------

### Helm Install Command Example

Source: https://github.com/bitnami/charts/blob/main/bitnami/memcached/README.md

Demonstrates how to install the Bitnami Memcached Helm chart with custom parameter values using the `--set` flag. This is the primary method for configuring the chart during deployment.

```bash
helm install my-release --set auth.username=user,auth.password=password oci://REGISTRY_NAME/REPOSITORY_NAME/memcached
```

--------------------------------

### Example Quickstart Contour Configuration

Source: https://github.com/bitnami/charts/blob/main/bitnami/contour/README.md

This YAML configuration provides a starting point for setting up Contour. It includes options for in-cluster detection, kubeconfig path, request timeouts, TLS settings, and logging formats. It also shows default proxy timeout settings.

```yaml
configInline:
  # should contour expect to be running inside a k8s cluster
  # incluster: true
  #
  # path to kubeconfig (if not running inside a k8s cluster)
  # kubeconfig: /path/to/.kube/config
  #
  # Client request timeout to be passed to Envoy
  # as the connection manager request_timeout.
  # Defaults to 0, which Envoy interprets as disabled.
  # Note that this is the timeout for the whole request, not an idle timeout.
  # request-timeout: 0s
  # disable ingressroute permitInsecure field
  disablePermitInsecure: false
  tls:
    #   minimum TLS version that Contour will negotiate
    #   minimum-protocol-version: "1.1"
    # Defines the Kubernetes name/namespace matching a secret to use
    # as the fallback certificate when requests which don't match the
    # SNI defined for a vhost.
    fallback-certificate:
  #   name: fallback-secret-name
  #   namespace: projectcontour
  # The following config shows the defaults for the leader election.
  # leaderelection:
  #   configmap-name: leader-elect
  #   configmap-namespace: projectcontour
  ### Logging options
  # Default setting
  accesslog-format: envoy
  # To enable JSON logging in Envoy
  # accesslog-format: json
  # The default fields that will be logged are specified below.
  # To customise this list, just add or remove entries.
  # The canonical list is available at
  # https://godoc.org/github.com/projectcontour/contour/internal/envoy#JSONFields
  # json-fields:
  #   - "@timestamp"
  #   - "authority"
  #   - "bytes_received"
  #   - "bytes_sent"
  #   - "downstream_local_address"
  #   - "downstream_remote_address"
  #   - "duration"
  #   - "method"
  #   - "path"
  #   - "protocol"
  #   - "request_id"
  #   - "requested_server_name"
  #   - "response_code"
  #   - "response_flags"
  #   - "uber_trace_id"
  #   - "upstream_cluster"
  #   - "upstream_host"
  #   - "upstream_local_address"
  #   - "upstream_service_time"
  #   - "user_agent"
  #   - "x_forwarded_for"
  #
  # default-http-versions:
  # - "HTTP/2"
  # - "HTTP/1.1"
  #
  # The following shows the default proxy timeout settings.
  # timeouts:
  #   request-timeout: infinity
  #   connection-idle-timeout: 60s
  #   stream-idle-timeout: 5m
  #   max-connection-duration: infinity
  #   connection-shutdown-grace-period: 5s
```

--------------------------------

### Install ScyllaDB Chart with Helm --set

Source: https://github.com/bitnami/charts/blob/main/bitnami/scylladb/README.md

Example of installing the ScyllaDB Helm chart using the `helm install` command with the `--set` argument to override default values. This method allows for inline configuration of chart parameters.

```bash
helm install my-release \
    --set dbUser.user=admin,dbUser.password=password \
    oci://REGISTRY_NAME/REPOSITORY_NAME/scylladb
```

--------------------------------

### Helm Install Command for KeyDB

Source: https://github.com/bitnami/charts/blob/main/bitnami/keydb/README.md

Example of how to install the Bitnami KeyDB Helm chart using the `helm install` command with specific parameter overrides. This command demonstrates setting authentication to enabled and providing a password, along with specifying the chart's OCI location.

```bash
helm install my-release \
    --set auth.enabled=true \
    --set auth.password=secretpassword \
    oci://REGISTRY_NAME/REPOSITORY_NAME/keydb
```

--------------------------------

### Install Ghost Helm Chart with Values File

Source: https://github.com/bitnami/charts/blob/main/bitnami/ghost/README.md

Example of installing the Ghost Helm chart using the `helm install` command with a YAML values file. This method is useful for managing a larger set of configurations.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/ghost
```

--------------------------------

### Install Argo CD with Helm using --set

Source: https://github.com/bitnami/charts/blob/main/bitnami/argo-cd/README.md

Use the `--set` argument to override default chart values during installation. This example sets the controller replica count and enables server metrics.

```bash
helm install my-release \
  --set controller.replicaCount=2 \
  --set server.metrics.enabled=true \
    oci://REGISTRY_NAME/REPOSITORY_NAME/argo-cd
```

--------------------------------

### Helm Install with Parameters

Source: https://github.com/bitnami/charts/blob/main/bitnami/mariadb-galera/README.md

Installs the MariaDB Galera Helm chart using the `helm install` command with specific parameters set via the `--set` argument. This example demonstrates setting the root password and database user.

```bash
helm install my-release \
  --set rootUser.password=secretpassword \
  --set db.user=app_database \
    oci://REGISTRY_NAME/REPOSITORY_NAME/mariadb-galera
```

--------------------------------

### Configure Helm Chart with YAML Values

Source: https://github.com/bitnami/charts/blob/main/bitnami/grafana-k6-operator/README.md

This example shows how to install a Helm chart by providing a YAML file containing the configuration values. This method is an alternative to using `--set` arguments for each parameter and is useful for managing complex configurations.

```bash
helm install my-release -f values.yaml REGISTRY_NAME/REPOSITORY_NAME/grafana-k6-operator
```

--------------------------------

### Install Ghost Helm Chart with Custom Values

Source: https://github.com/bitnami/charts/blob/main/bitnami/ghost/README.md

Example of installing the Ghost Helm chart using the `helm install` command with custom values provided via the `--set` flag. This allows for inline configuration of various chart parameters.

```bash
helm install my-release \
  --set ghostUsername=admin,ghostPassword=password,mysql.auth.rootPassword=secretpassword \
    oci://REGISTRY_NAME/REPOSITORY_NAME/ghost
```

--------------------------------

### Helm Install with --set Arguments

Source: https://github.com/bitnami/charts/blob/main/bitnami/elasticsearch/README.md

Example of installing an Elasticsearch Helm release using the `helm install` command with `--set` arguments to override default values. This demonstrates how to specify parameters like cluster name and service port directly on the command line.

```bash
helm install my-release \
  --set name=my-elastic,client.service.port=8080 \
  oci://REGISTRY_NAME/REPOSITORY_NAME/elasticsearch
```

--------------------------------

### Define Init Containers

Source: https://github.com/bitnami/charts/blob/main/bitnami/cilium/README.md

Provides an example of how to configure init containers that run before the main application container starts.

```yaml
agent:
  initContainers:
  - name: your-image-name
    image: your-image
    imagePullPolicy: Always
    ports:
      - name: portname
        containerPort: 1234
```

--------------------------------

### Install Cassandra Helm Chart with CLI parameters

Source: https://github.com/bitnami/charts/blob/main/bitnami/cassandra/README.md

Demonstrates how to install the Cassandra Helm chart using the --set flag to define configuration parameters directly in the command line.

```console
helm install my-release \
    --set dbUser.user=admin,dbUser.password=password \
    oci://REGISTRY_NAME/REPOSITORY_NAME/cassandra
```

--------------------------------

### Add Extra Init Container for Pre-run Setup

Source: https://github.com/bitnami/charts/blob/main/bitnami/mariadb-galera/README.md

Configures an extra init container to perform pre-run setup tasks. This example shows an init container that uses 'curl' to report to an external API service that the database is starting, useful for scenarios like non-root user permission adjustments on volumes.

```yaml
extraInitContainers:
- name: initcontainer
  image: bitnami/minideb
  command: ["/bin/sh", "-c"]
  args:
    - install_packages curl && curl http://api-service.local/db/starting;
```

--------------------------------

### Install Cassandra Helm Chart with YAML file

Source: https://github.com/bitnami/charts/blob/main/bitnami/cassandra/README.md

Demonstrates how to install the Cassandra Helm chart using a values.yaml file to provide configuration parameters.

```console
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/cassandra
```

--------------------------------

### Define Init Containers for HAProxy Pod

Source: https://github.com/bitnami/charts/blob/main/bitnami/haproxy/README.md

This example shows how to add init containers to the HAProxy pod. Init containers run to completion before the main application container starts, useful for setup tasks. The `initContainers` parameter defines the container's image, name, and ports.

```yaml
initContainers:
  - name: your-image-name
    image: your-image
    imagePullPolicy: Always
    ports:
      - name: portname
        containerPort: 1234

```

--------------------------------

### Install Whereabouts Helm Chart

Source: https://github.com/bitnami/charts/blob/main/bitnami/whereabouts/README.md

Commands to install the Whereabouts chart using Helm. The first command shows a specific Bitnami registry example, while the second shows the generic installation command.

```console
helm install my-release oci://registry-1.docker.io/bitnamicharts/whereabouts
```

```console
helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/whereabouts
```

--------------------------------

### Helm Install with values.yaml File

Source: https://github.com/bitnami/charts/blob/main/bitnami/elasticsearch/README.md

Example of installing an Elasticsearch Helm release using the `helm install` command with a custom `values.yaml` file. This method is useful for managing a larger set of configurations.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/elasticsearch
```

--------------------------------

### Install Bitnami Kube Prometheus Helm Chart

Source: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/README.md

Installs the Bitnami Kube Prometheus Helm chart for a working Prometheus setup, necessary for metrics integration.

```console
helm install bitnami/kube-prometheus
```

--------------------------------

### Install Odoo Helm Chart with CLI Arguments

Source: https://github.com/bitnami/charts/blob/main/bitnami/odoo/README.md

Demonstrates how to install the Odoo chart using the helm install command with specific configuration parameters passed via the --set flag.

```console
helm install my-release \
  --set odooPassword=password,postgresql.postgresPassword=secretpassword \
    oci://REGISTRY_NAME/REPOSITORY_NAME/odoo
```

--------------------------------

### Install ScyllaDB Chart with Helm -f values.yaml

Source: https://github.com/bitnami/charts/blob/main/bitnami/scylladb/README.md

Example of installing the ScyllaDB Helm chart using the `helm install` command with the `-f` argument to specify a custom `values.yaml` file. This is useful for managing complex configurations.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/scylladb
```

--------------------------------

### Helm Install with --set for Cassandra Storage

Source: https://github.com/bitnami/charts/blob/main/bitnami/zipkin/README.md

Demonstrates how to install the Zipkin Helm chart and configure Cassandra storage using the `--set` command-line argument. This method allows for inline specification of configuration values.

```bash
helm install my-release \
    oci://REGISTRY_NAME/REPOSITORY_NAME/zipkin \
    --set cassandra.enabled=true \
    --set cassandra.cluster.datacenter=datacenter1 \
    --set cassandra.keyspace=bitnami_zipkin \
    --set cassandra.dbUser.user=bn_zipkin \
    --set cassandra.dbUser.password="" \
    --set cassandra.service.ports.cql=9042
```

--------------------------------

### Install SeaweedFS using a values file

Source: https://github.com/bitnami/charts/blob/main/bitnami/seaweedfs/README.md

Demonstrates how to install the SeaweedFS Helm chart by providing a custom values.yaml file to override default configurations.

```console
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/seaweedfs
```

--------------------------------

### Helm Install with --set for Kibana

Source: https://github.com/bitnami/charts/blob/main/bitnami/kibana/README.md

Example of installing the Kibana Helm chart using the `--set` flag to configure parameters like the admin user. This method allows for inline configuration of chart values during installation.

```console
helm install my-release \
  --set admin.user=admin-user oci://REGISTRY_NAME/REPOSITORY_NAME/kibana
```

--------------------------------

### Install Kafka with Values File

Source: https://github.com/bitnami/charts/blob/main/bitnami/kafka/README.md

Installs the Kafka chart using a values.yaml file for configuration. Remember to substitute REGISTRY_NAME and REPOSITORY_NAME with your specific registry and repository references.

```console
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/kafka
```

--------------------------------

### Install Fluentd Chart with values.yaml

Source: https://github.com/bitnami/charts/blob/main/bitnami/fluentd/README.md

Example of installing the Fluentd Helm chart by providing a custom YAML values file. This method is useful for managing multiple configuration options.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/fluentd
```

--------------------------------

### Install Airflow Chart with Helm CLI Arguments

Source: https://github.com/bitnami/charts/blob/main/bitnami/airflow/README.md

Demonstrates how to install the Airflow Helm chart using the `helm install` command with specific `--set` arguments to configure parameters such as authentication credentials and Fernet keys. This method allows for direct inline configuration during deployment.

```console
helm install my-release \
               --set auth.username=my-user \
               --set auth.password=my-passsword \
               --set auth.fernetKey=my-fernet-key \
               --set auth.secretKey=my-secret-key \
               oci://REGISTRY_NAME/REPOSITORY_NAME/airflow
```

--------------------------------

### Utilize Preset Pod Affinity Configurations

Source: https://github.com/bitnami/charts/blob/main/bitnami/kube-arangodb/README.md

This example demonstrates using preset configurations for Pod affinity, Pod anti-affinity, and Node affinity. By setting parameters like 'podAffinityPreset', users can leverage predefined scheduling rules provided by the bitnami/common chart.

```yaml
podAffinityPreset: "hard"
podAntiAffinityPreset: "soft"
nodeAffinityPreset:
  type: "required"
  key: "topology.kubernetes.io/zone"
  values:
  - us-east-1a
```

--------------------------------

### Install Prometheus Operator Helm Chart (TL;DR)

Source: https://github.com/bitnami/charts/blob/main/bitnami/kube-prometheus/README.md

Quick command to install the Prometheus Operator Helm chart with a release name. This is a common starting point for deployment.

```console
helm install my-release oci://registry-1.docker.io/bitnamicharts/kube-prometheus
```

--------------------------------

### Get Pods for Verification

Source: https://github.com/bitnami/charts/blob/main/bitnami/oauth2-proxy/templates/NOTES.txt

Run this command to verify that oauth2-proxy has started. Replace with your namespace.

```bash
kubectl --namespace={{ .Release.Namespace }} get pods
```

--------------------------------

### Install Helm Chart with Inline Configuration

Source: https://github.com/bitnami/charts/blob/main/bitnami/grafana-mimir/README.md

Demonstrates how to install a Helm chart while overriding specific configuration parameters directly via the command line using the --set flag.

```console
helm install my-release \
  --set mimir.image.debug=true \
  oci://REGISTRY_NAME/REPOSITORY_NAME/grafana-mimir
```

--------------------------------

### Helm Install with values.yaml

Source: https://github.com/bitnami/charts/blob/main/bitnami/kiam/README.md

Illustrates installing the Kiam Helm chart by providing a custom `values.yaml` file. This approach is recommended for managing complex configurations.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/kiam
```

--------------------------------

### Helm Install with values.yaml for Kibana

Source: https://github.com/bitnami/charts/blob/main/bitnami/kibana/README.md

Example of installing the Kibana Helm chart by providing a YAML file with custom values. This approach is useful for managing a larger set of configurations or for repeatable deployments.

```console
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/kibana
```

--------------------------------

### Install Helm Chart with Values File

Source: https://github.com/bitnami/charts/blob/main/bitnami/cadvisor/README.md

Demonstrates how to provide a custom values.yaml file during chart installation. This is the recommended approach for managing complex configurations.

```console
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/cadvisor
```

--------------------------------

### Install Helm Chart with YAML Values File

Source: https://github.com/bitnami/charts/blob/main/bitnami/schema-registry/README.md

Demonstrates how to install a Helm chart by providing a custom values.yaml file to override default configurations.

```console
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/schema-registry
```

--------------------------------

### Example values.yaml for Cassandra Storage

Source: https://github.com/bitnami/charts/blob/main/bitnami/zipkin/README.md

An example YAML configuration file for the Bitnami Zipkin Helm chart, specifying settings for Cassandra as the storage backend. This file can be used with the `helm install -f values.yaml` command.

```yaml
cassandra:
  enabled: true
  cluster:
    datacenter: datacenter1
  keyspace: bitnami_zipkin
  dbUser:
    user: bn_zipkin
    password: ""
    existingSecret: ""
  service:
    ports:
      cql: 9042
  resourcesPreset: medium
  resources: {}
  initDB: {}
  extraEnvVars: []
```

--------------------------------

### Install Helm Chart with Custom Parameters

Source: https://github.com/bitnami/charts/blob/main/bitnami/phpmyadmin/README.md

Demonstrates how to install a Helm chart while overriding default values using the --set flag. This is useful for specifying database host and port configurations directly in the command line.

```bash
helm install my-release \
  --set db.host=mymariadb,db.port=3306 oci://REGISTRY_NAME/REPOSITORY_NAME/phpmyadmin
```

--------------------------------

### Helm Install with values.yaml File

Source: https://github.com/bitnami/charts/blob/main/bitnami/kube-state-metrics/README.md

Illustrates installing the kube-state-metrics Helm chart by providing a YAML file containing configuration values. This approach is recommended for managing complex configurations.

```bash
helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/kube-state-metrics
```

--------------------------------

### Helm Install with --set Arguments

Source: https://github.com/bitnami/charts/blob/main/bitnami/argo-workflows/README.md

Example of installing the Argo Workflows Helm chart using the `--set` argument to specify configuration values directly on the command line. This method is useful for quick overrides or scripting.

```bash
helm install my-release \
  --set argo-workflowsUsername=admin \
  --set argo-workflowsPassword=password \
  --set mysql.auth.rootPassword=secretpassword \
    oci://REGISTRY_NAME/REPOSITORY_NAME/argo-workflows
```

--------------------------------

### Replicate Container Startup Scripts

Source: https://github.com/bitnami/charts/blob/main/bitnami/mongodb-sharded/templates/NOTES.txt

Execute the container startup scripts to replicate the entrypoint and run commands.

```bash
/opt/bitnami/scripts/mongodb-sharded/entrypoint.sh /opt/bitnami/scripts/mongodb-sharded/run.sh
```

--------------------------------

### Install Fluentd Chart with --set Argument

Source: https://github.com/bitnami/charts/blob/main/bitnami/fluentd/README.md

Example of installing the Fluentd Helm chart using the `--set` argument to override default values. This command customizes the aggregator port and specifies the chart's OCI location.

```bash
helm install my-release \
  --set aggregator.port=24444 oci://REGISTRY_NAME/REPOSITORY_NAME/fluentd
```

--------------------------------

### Custom Init Scripts Configuration (Console)

Source: https://github.com/bitnami/charts/blob/main/bitnami/fluentd/README.md

This example shows how to configure custom init scripts for the Bitnami Fluentd chart using console commands. It demonstrates specifying a ConfigMap (`initScriptsCM`) and a Secret (`initScriptsSecret`) for mounting custom scripts into the `/docker-entrypoint.init-db` directory. This is useful for advanced initialization tasks.

```console
initScriptsCM=special-scripts
initScriptsSecret=special-scripts-sensitive
```

--------------------------------

### Helm Install with Custom Values

Source: https://github.com/bitnami/charts/blob/main/bitnami/tensorflow-resnet/README.md

Demonstrates how to install a Helm chart with custom configuration values using the `--set` flag. This allows for fine-grained control over individual chart parameters during installation. Replace placeholders with your specific registry and repository details.

```bash
helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/tensorflow-resnet --set imagePullPolicy=Always
helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/tensorflow-resnet --set service.ports.restApi=8501 --set metrics.enabled=true
```