airship/armada
Code Issues Proposed changes
4e0f9009a8
armada/doc/source/commands/rollback.rst
Shoaib Nasir 7fb3b8d9ca Add support in Armada CLI to pass user bearer tokens to tiller 
Added a new option --bearer-token TEXT in the Armada CLI to allow
the users or applications to pass kubernetes-api bearertokens via
tiller to the kubernetes cluster. This is to allow armada to interact
with a kubernetes cluster that has been configured with an external
Auth-Backend like Openstack-keystone or OpenId Connect.

Bearer Tokens are Auth tokens issued by the identity backends
such as keystone which represent a users authorized access.
For better understanding of bearer tokens, an example case
of how they works can be found here
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#putting-a-bearer-token-in-a-request
https://docs.docker.com/registry/spec/auth/token/

Change-Id: I03623c7d3b58eda421a0660da8ec3ac2e86915f0
Signed-off-by: Shoaib Nasir <shoaib.nasir@windriver.com>
2019-02-01 15:33:18 -05:00

1010 B
Raw Blame History

Armada - Rollback

Commands

Usage: armada rollback [OPTIONS]

This command performs a rollback on the specified release.

To rollback a release, run:

    $ armada rollback --release my_release

Options:
  --dry-run                     Perform a dry-run rollback.
  --release TEXT                Release to rollback.
  --tiller-host TEXT            Tiller Host IP
  --tiller-port INTEGER         Tiller Host Port
  -tn, --tiller-namespace TEXT  Tiller Namespace
  --timeout INTEGER             Tiller Host IP
  --version INTEGER             Version of release to rollback to. 0 represents the previous release
  --wait                        Version of release to rollback to. 0 represents the previous release
  --bearer-token                User bearer token
  --help                        Show this message and exit.

Synopsis

The rollback command will perform helm rollback on the release.