• Apollo
    • Search documentation
    karat

    +

    K

    ReferenceApollo CLIapollo-cli helm-chart validate [Experimental]

    apollo-cli helm-chart validate [Experimental]

    This command is Experimental. To enable this command, run the apollo-cli configure command and enable V2 experimental commands.

    Runs a set of validation checks on the supplied helm chart to ensure compatibility with an Apollo environment

    Copied!
    1
apollo-cli helm-chart validate [flags]

    Flags

    FlagUse
    --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 validate
    --key-fileHelm pull: identify HTTPS client using this SSL key file
    --nameHelm chart name. If the chart resides in a remote OCI repository, this must be the full OCI URL (e.g. oci://repo/chartName)
    --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
    --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