Search documentation
karat

+

K

apollo-cli product-release helm-chart init

Initializes a new helm-chart product manifest from a local chart or remote chart repository

Copied!
1 apollo-cli product-release helm-chart init [flags]

Flags

FlagUse
--as-tgzIf set, the output will be an Apollo product TGZ with the extension ".config.tgz" in the specified output directory.
--ca-fileHelm pull: verify certificates of HTTPS-enabled servers using this CA bundle
--cert-fileHelm pull: identify HTTPS client using this SSL certificate file
--chart-pathPath to either a local packaged chart or an unpacked chart directory
-h, --helpHelp for init
--image-pre-pull-config-timeoutSets the timeout for pre-pulling images (ex: '3m'). Minumum: 1m, Maximum: 90m
--key-fileHelm pull: identify HTTPS client using this SSL key file
--maven-coordinateMaven coordinate for the artifact
--nameHelm chart name. If the chart resides in a remote OCI repository, this must be the full OCI URL (e.g. oci://repo/chartName)
--output-dirDirectory where artifacts are written
--pass-credentialsHelm pull: pass credentials to all domains
--passwordHelm pull: chart repository password where to locate the requested chart
--repository-urlHelm repository URL where the requested chart can be located
--resource-readiness-timeoutSets the length of time the Apollo agent will wait for all resources to become ready after applying changes to Kubernetes (e.g., '5m', '1h', '90m'). This does not affect the Helm timeout for applying changes and running hooks, only the wait for resources to become ready post-apply. Minimum: 3m, Maximum: 4h. Cannot be used with rollout-strategy 'applyChangesNoWait'
--rollout-strategyRollout strategy manifest extension: valid values are 'manageRollout' (default) and 'applyChangesNoWait'
--usernameHelm pull: chart repository username where to locate the requested chart
--valuesHelm template: Specify values in a YAML file. Note that values are only used to render chart templates locally. Default configs will need to be added in Apollo before installation.
--versionHelm chart version

Flags inherited from parent commands

FlagUse
--apollo-client-idClient ID to use for generating Bearer Token
--apollo-client-secretClient secret to use for generating Bearer Token
--apollo-tokenBearer Token to use for authenticated endpoints
--apollo-token-providerSpecifies how the Bearer Token used for authenticated Apollo endpoint calls is provided. Valid values are "auto", "static", "service-user", or "sso" (default "auto"). If "auto" is specified, the mode is picked from what is configured: "static" if "apollo-token" is set, "service-user" if "apollo-client-id" and "apollo-client-secret" are both set, otherwise "sso" (interactive browser login). Errors if both a bearer token AND (client id OR client secret) are set. If "static" is specified, the token provided by "apollo-token" is used. If "service-user" is specified, "apollo-client-id" and "apollo-client-secret" are used to generate a token from Multipass. If "sso" is specified, an interactive browser-based SSO login against Multipass is used (supports hardware keys like YubiKey); the resulting token is cached per profile and refreshed silently. The login flow is triggered automatically the first time a command needs a token and no valid cached token exists.
--apollo-urlBase URL for Apollo that is used to derive the API endpoints
--debugEnable debug level logging
-e, --environmentEnvironment ID (including suffix) to use for environment-scoped commands
--http-timeoutTimeout in minutes for all apollo requests
-k, --insecure-skip-verifySkip verification of server certificate
-o, --outputOutput format (json,yaml,pretty)
--profileUse a specific profile from your configuration file
--quietDo not print log output to stderr
--space-idSpace ID to use for certain space-scoped commands

See also