jx step helm apply

jx step helm apply

Applies the helm chart in a given directory

Synopsis

Applies the helm chart in a given directory.

This step is usually used to apply any GitOps promotion changes into a Staging or Production cluster.

Environment Variables:

• JX NO DELETE TMP DIR=“true” - prevents the removal of the temporary directory.

jx step helm apply [flags]

Examples

  # apply the chart in the env folder to namespace jx-staging
  jx step helm apply --dir env --namespace jx-staging

Options

      --boot                          In Boot mode we load the Version Stream from the 'jx-requirements.yml' and use that to replace any missing versions in the 'requirements.yaml' file from the Version Stream
      --clone-https git@foo/bar.git   Clone the environment Git repo over https rather than ssh which uses git@foo/bar.git (default true)
  -d, --dir string                    The directory containing the helm chart to apply (default ".")
  -f, --force                         Whether to to pass '--force' to helm to help deal with upgrading if a previous promote failed (default true)
      --git-provider string           The Git provider for the environment Git repository (default "github.com")
  -h, --help                          help for apply
  -n, --name string                   The name of the release
      --namespace string              The Kubernetes namespace to apply the helm chart to
      --no-helm-version               Don't set Chart version before applying
      --no-masking                    The effective 'values.yaml' file is output to the console with parameters masked. Enabling this flag will show the unmasked secrets in the console output
      --no-vault                      Disables loading secrets from Vault. e.g. if bootstrapping core services like Ingress before we have a Vault
      --provider-values-dir string    The optional directory of kubernetes provider specific override values.tmpl.yaml files a kubernetes provider specific folder
      --remote                        If enabled assume we are in a remote cluster such as a stand alone Staging/Production cluster
      --vault                         Helm secrets are stored in vault
      --wait                          Wait for Kubernetes readiness probe to confirm deployment (default true)

Options inherited from parent commands

  -b, --batch-mode   Runs in batch mode without prompting for user input
      --verbose      Enables verbose output. The environment variable JX_LOG_LEVEL has precedence over this flag and allows setting the logging level to any value of: panic, fatal, error, warn, info, debug, trace

SEE ALSO

• jx step helm - helm [command]

Auto generated by spf13/cobra on 2-Sep-2020

Feedback

Was this page helpful?

Yes No

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.