Managing objects with the rosa CLI | rosa CLI | Red Hat OpenShift Service on AWS

Managing objects with the rosa CLI, such as adding dedicated-admin users, managing clusters, and scheduling cluster upgrades.

Common commands and arguments

These common commands and arguments are available for the rosa CLI.

debug

Enables debug mode for the parent command.

Example

$ rosa create cluster --cluster=<cluster_name> --debug

help

Displays general help information for the rosa CLI and a list of available commands. This option can also be used as an argument to display help information for a parent command, such as version or create.

Examples

Displays general help for the rosa CLI:

$ rosa --help

Displays general help for version:

$ rosa version --help

interactive

Enables interactive mode.

Example

$ rosa create cluster --cluster=<cluster_name> --interactive

profile

Specifies an AWS profile from your credential file.

Example

$ rosa create cluster --cluster=<cluster_name> --profile string=myAWSprofile

v level

Specifies the log level for V logs.

Example

$ rosa create cluster --cluster=<cluster_name> --v <level>

version

Displays the rosa version.

Example

$ rosa version [arguments]

Parent commands

The rosa CLI uses parent commands with child commands to manage objects. The parent commands are create, edit, delete, list, and describe. Not all parent commands can be used with all child commands. For more information, see the specific reference topics that describes the child commands.

create

Creates an object or resource when paired with a child command.

Example

$ rosa create cluster --cluster-name=mycluster

edit

Edits options for an object, such as making a cluster private.

Example

$ rosa edit cluster=mycluster --private

delete

Deletes an object or resource when paired with a child command.

Example

$ rosa delete ingress --cluster=mycluster

list

Lists clusters or resources for a specific cluster.

Example

$ rosa list users --cluster=mycluster

describe

Shows the details for a cluster.

Example

$ rosa describe --cluster=mycluster

Create objects

This section describes the create commands for clusters and resources.

create admin

Create a cluster administrator with an automatically generated password that can log in to a cluster.

Syntax

$ rosa create admin --cluster=<cluster_name>

Table 1. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to add to the identity provider (IDP).

Table 2. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

Create a cluster administrator that can log in to a cluster named mycluster:

$ rosa create admin --cluster=mycluster

create cluster

Create a new cluster.

Syntax

$ rosa create cluster --cluster=<cluster_name> [arguments]

Table 3. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster. When used with the `create cluster` command, this argument is used to generate a sub-domain for your cluster on `openshiftapps.com`.
--channel-group	The channel group (string) is the name of the group where this image belongs, for example `stable` or `fast`. Default: `stable`
--compute-machine-type	The instance type (string) for the compute nodes. Determines the amount of memory and vCPU that are allocated to each compute node.
--compute-nodes	The number (integer) of worker nodes to provision per zone. Single-zone clusters require at least 2 nodes. Multi-zone clusters require at least 3 nodes. Default: `2` for single-az; `3` for multi-az
--disable-scp-checks	Indicates whether cloud permission checks are disabled when attempting to install a cluster.
--dry-run	Simulates creating the cluster.
--enable-autoscaling	Enables autoscaling of compute nodes. By default, autoscaling is set to `2` nodes. To set non-default node limits, use this argument with the `--min-replicas` and `--max-replicas` arguments.
--host-prefix	The subnet prefix length (integer) to assign to each individual node. For example, if host prefix is set to `23`, then each node is assigned a `/23` subnet out of the given CIDR.
--machine-cidr	Block of IP addresses (ipNet) used by OpenShift Container Platform while installing the cluster. Example: `10.0.0.0/16`
--max-replicas	Specifies the maximum number of compute nodes when enabling autoscaling. Default: `2`
--min-replicas	Specifies the minimum number of compute nodes when enabling autoscaling. Default: `2`
--multi-az	Deploys to multiple data centers.
--pod-cidr	Block of IP addresses (ipNet) from which pod IP addresses are allocated. Example: `10.128.0.0/14`
--private	Restricts master API endpoint and application routes to direct, private connectivity.
--region	The AWS region (string) where your worker pool will be located. This argument overrides the `AWS_REGION` environment variable.
--service-cidr	Block of IP addresses (ipNet) for services. Example: `172.30.0.0/16`
--subnet-ids	The subnet IDs (string) to use when installing the cluster. Subnet IDs must be in pairs with one private subnet ID and one public subnet ID per availability zone. Subnets are comma-delimited. Example: `--subnet-ids=subnet-1,subnet-2`. Leave the value empty for installer-provisioned subnet IDs.
--version	The version (string) of OpenShift Container Platform that will be used to install the cluster. Example: `4.3.10`

Table 4. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Create a cluster named mycluster:

$ rosa create cluster --cluster=mycluster

Create a cluster with a specific AWS region:

$ rosa create cluster --cluster=mycluster --region=us-east-2

Create a cluster with autoscaling enabled on the default worker machine pool:

$ rosa create cluster --cluster=mycluster -region=us-east-1 --enable-autoscaling --min-replicas=2 --max-replicas=5

create idp

Add an identity provider (IDP) to define how users log in to a cluster.

Syntax

$ rosa create idp --cluster=<cluster_name> [arguments]

Table 5. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to which the IDP will be added.
--ca	The path (string) to the PEM-encoded certificate file to use when making requests to the server.
--client-id	The client ID (string) from the registered application.
--client-secret	The client secret (string) from the registered application.
--mapping-method	Specifies how new identities (string) are mapped to users when they log in. Default: `claim`
--name	The name (string) for the identity provider.
--type	The type (string) of identity provider. Options: `github`, `gitlab`, `google`, `ldap`, `openid`

Table 6. GitHub arguments
Option	Definition
--hostname	The optional domain (string) to use with a hosted instance of GitHub Enterprise.
--organizations	Specifies the organizations for login access. Only users that are members of at least one of the listed organizations (string) are allowed to log in.
--teams	Specifies the teams for login access. Only users that are members of at least one of the listed teams (string) are allowed to log in. The format is `<org>/<team>`.

Table 7. GitLab arguments
Option	Definition
--host-url	The host URL (string) of a GitLab provider. Default: `https://gitlab.com`

Table 8. Google arguments
Option	Definition
--hosted-domain	Restricts users to a Google Apps domain (string).

Table 9. LDAP arguments
Option	Definition
--bind-dn	The domain name (string) to bind with during the search phase.
--bind-password	The password (string) to bind with during the search phase.
--email-attributes	The list (string) of attributes whose values should be used as the email address.
--id-attributes	The list (string) of attributes whose values should be used as the user ID. Default: `dn`
--insecure	Does not make TLS connections to the server.
--name-attributes	The list (string) of attributes whose values should be used as the display name. Default: `cn`
--url	An RFC 2255 URL (string) which specifies the LDAP search parameters to use.
--username-attributes	The list (string) of attributes whose values should be used as the preferred username. Default: `uid`

Table 10. OpenID arguments
Option	Definition
--email-claims	The list (string) of claims to use as the email address.
--extra-scopes	The list (string) of scopes to request, in addition to the `openid` scope, during the authorization token request.
--issuer-url	The URL (string) that the OpenID provider asserts as the issuer identifier. It must use the HTTPS scheme with no URL query parameters or fragment.
--name-claims	The list (string) of claims to use as the display name.
--username-claims	The list (string) of claims to use as the preferred username when provisioning a user.

Table 11. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Add a GitHub identity provider to a cluster named mycluster:

$ rosa create idp --type=github --cluster=mycluster

Add an identity provider following interactive prompts:

$ rosa create idp --cluster=mycluster --interactive

create ingress

Add an ingress endpoint to enable API access to the cluster.

Syntax

$ rosa create ingress --cluster=<cluster_name> [arguments]

Table 12. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to which the ingress will be added.
--label-match	The label match (string) for ingress. The format must be a comma-delimited list of key=value pairs. If no label is specified, all routes are exposed on both routers.
--private	Restricts application route to direct, private connectivity.

Table 13. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Add an internal ingress to a cluster named mycluster:

$ rosa create ingress --private --cluster=mycluster

Add a public ingress to a cluster named mycluster:

$ rosa create ingress --cluster=mycluster

Add an ingress with a route selector label match:s

$ rosa create ingress --cluster=mycluster --label-match="foo=bar,bar=baz"

create machinepool

Add a machine pool to an existing cluster.

Syntax

$ rosa create machinepool --cluster=<cluster_name> --replicas=<number> --name=<machinepool_name> [arguments]

Table 14. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to which the machine pool will be added.
--instance-type	The instance type (string) that should be used. Default: `m5.xlarge`
--labels	The labels (string) for the machine pool. The format must be a comma-delimited list of key=value pairs. This list overwrites any modifications made to node labels on an ongoing basis.
--name	Required: The name (string) for the machine pool.
--replicas	Required: The number (integer) of machines for this machine pool.

Table 15. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Interactively add a machine pool to a cluster named mycluster:

$ rosa create machinepool --cluster=mycluster --interactive

Add a machine pool that is named mp-1 to a cluster with autoscaling enabled:

$ rosa create machinepool --cluster=mycluster --enable-autoscaling --min-replicas=2 --max-replicas=5 --name=mp-1

Add a machine pool that is named mp-1 with 3 replicas of m5.xlarge to a cluster:

$ rosa create machinepool --cluster=mycluster --replicas=3 --instance-type=m5.xlarge --name=mp-1

Add a machine pool with labels to a cluster:

$ rosa create machinepool --cluster=mycluster --replicas=2 --instance-type=r5.2xlarge --labels =foo=bar,bar=baz" --name=mp-1

Edit objects

This section describes the edit commands for clusters and resources.

edit cluster

Allows edits to an existing cluster.

Syntax

$ rosa edit cluster [arguments]

Table 16. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to edit.
--private	Restricts a master API endpoint to direct, private connectivity.

Table 17. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Edit a cluster named mycluster to make it private.

$ rosa edit cluster --cluster=mycluster --private

Edit all cluster options interactively.

$ rosa edit cluster --cluster=mycluster --interactive

edit ingress

Edits the additional non-default application router for a cluster.

Syntax

$ rosa edit ingress [arguments]

Table 18. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to which the ingress will be added.
--label-match	The label match (string) for ingress. The format must be a comma-delimited list of key=value pairs. If no label is specified, all routes are exposed on both routers.
--private	Restricts the application route to direct, private connectivity.

Table 19. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Make an additional ingress with ID a1b2 as private on a cluster named mycluster.

$ rosa edit ingress --private --cluster=mycluster a1b2

Update the router selectors for the additional ingress with the ID a1b2.

$ rosa edit ingress --label-match=foo=bar --cluster=mycluster a1b2

Update the default ingress using the sub-domain identifier apps.

$ rosa edit ingress --private=false --cluster=mycluster apps

edit machinepool

Allows edits to the machine pool in a cluster.

Syntax

$ rosa edit machinepool --cluster=<cluster_name> <machinepool_ID> [arguments]

Table 20. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to edit on which the additional machine pool will be edited.
--enable-autoscaling	Enable or disable autoscaling of compute nodes. To enable autoscaling, use this argument with the `--min-replicas` and `--max-replicas` arguments. To disable autoscaling, use `--enable-autoscaling=false` with the `--replicas` argument.
--max-replicas	Specifies the maximum number of compute nodes when enabling autoscaling.
--min-replicas	Specifies the minimum number of compute nodes when enabling autoscaling.
--replicas	The number (integer) of machines for this machine pool.

Table 21. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Examples

Set 4 replicas on a machine pool named mp1 on a cluster named mycluster.

$ rosa edit machinepool --cluster=mycluster --replicas=4 --name=mp1

Enable autoscaling on a machine pool named mp1 on a cluster named mycluster.

$ rosa edit machinepool --cluster-name=mycluster --enable-autoscaling --min-replicas=3 --max-replicas=5 --name=mp1

Disable autoscaling on a machine pool named mp1 on a cluster named mycluster.

$ rosa edit machinepool --cluster-name=mycluster  --enable-autoscaling=false --replicas=3 --name=mp1

Modify the autoscaling range on a machine pool named mp1 on a cluster named mycluster.

$ rosa edit machinepool --max-replicas=9 --cluster=mycluster --name=mp1

Delete objects

This section describes the delete commands for clusters and resources.

delete admin

Deletes a cluster administrator from a specified cluster.

Syntax

$ rosa delete admin --cluster=<cluster_name>

Table 22. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to add to the identity provider (IDP).

Table 23. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

Delete a cluster administrator from a cluster named mycluster.

$ rosa delete admin --cluster=mycluster

delete cluster

Deletes a cluster.

Syntax

$ rosa delete cluster --cluster=<id> | <name> [arguments]

Table 24. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to delete.
--watch	Watches the cluster uninstallation logs.

Table 25. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.

Examples

Delete a cluster named mycluster.

$ rosa delete cluster --cluster=mycluster

delete idp

Deletes a specific identity provider (IDP) from a cluster.

Syntax

$ rosa delete idp <id> | <name> [arguments]

Table 26. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster from which the IDP will be deleted.

Table 27. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.

Example

Delete an identity provider named github from a cluster named mycluster.

$ rosa delete idp github --cluster=mycluster

delete ingress

Deletes a non-default application router (ingress) from a cluster.

Syntax

$ rosa delete ingress [arguments]

Table 28. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster from which the ingress will be deleted.

Table 29. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.

Examples

Delete an ingress with ID a1b2 from a cluster named mycluster.

$ rosa delete ingress --cluster=mycluster a1b2

Delete a secondary ingress with the subdomain name apps2 from a cluster named mycluster.

$ rosa delete ingress --cluster=mycluster apps2

delete machinepool

Deletes a machine pool from a cluster.

Syntax

$ rosa delete machinepool --cluster=<cluster_name> <machine_pool_id>

Table 30. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the machine pool will be deleted from.

Table 31. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--interactive	Enables interactive mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.

Example

Delete the machine pool with ID mp-1 from a cluster named mycluster.

$ rosa delete machinepool --cluster=mycluster mp-1

Install and uninstall add-ons

This section describes how to install and uninstall Red Hat managed service add-ons to a cluster.

install addon

Installs a managed service add-on on a cluster.

Syntax

$ rosa install addon [arguments]

Table 32. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster where the add-on will be installed.

Table 33. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Uses a specific AWS profile (string) from your credentials file.
--v level	Log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.

Examples

Add the codeready-workspaces add-on installation to a cluster named mycluster.

$ rosa install addon --cluster=mycluster codeready-workspaces

uninstall addon

Uninstalls a managed service add-on from a cluster.

Syntax

$ rosa uninstall addon [arguments]

Table 34. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the add-on will be uninstalled from.

Table 35. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Uses a specific AWS profile (string) from your credentials file.
--v level	Log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.

Examples

Remove the codeready-workspaces add-on installation from a cluster named mycluster.

$ rosa uninstall addon --cluster=mycluster codeready-workspaces

List and describe objects

This section describes the list and describe commands for clusters and resources.

list addon

List the managed service add-on installations.

Syntax

$ rosa list addons --cluster=<cluster_name>

Table 36. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to list the add-ons for.

Table 37. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

list clusters

List all of your clusters.

Syntax

$ rosa list clusters [arguments]

Table 38. Arguments
Option	Definition
--count	The number (integer) of clusters to display. Default: `100`

Table 39. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

list idps

List all of the identity providers (IDPs) for a cluster.

Syntax

$ rosa list idps [arguments]

Table 40. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the IDPs will be listed for.

Table 41. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all identity providers (IDPs) for a cluster named mycluster:

$ rosa list idps --cluster=mycluster

list ingresses

List all of the API and ingress endpoints for a cluster.

Syntax

$ rosa list ingresses --cluster=mycluster [arguments]

Table 42. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the IDPs will be listed for.

Table 43. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all API and ingress endpoints for a cluster named mycluster:

$ rosa list ingresses --cluster=mycluster

list machinepools

List the machine pools configured on a cluster.

Syntax

$ rosa list machinepools [arguments]

Table 44. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the machine pools will be listed for.

Table 45. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all of the machine pools on a cluster named mycluster:

$ rosa list machinepools --cluster=mycluster

list regions

List all of the available regions for the current AWS account.

Syntax

$ rosa list regions [arguments]

Table 46. Arguments
Option	Definition
--multi-az	Lists regions that provide support for multiple availability zones.

Table 47. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all of the available regions:

$ rosa list regions

list upgrades

List all available and scheduled cluster version upgrades.

Syntax

$ rosa list upgrades [arguments]

Table 48. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the available upgrades will be listed for.

Table 49. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all of the available upgrades for a cluster named mycluster:

$ rosa list upgrades --cluster=mycluster

list users

List the cluster administrator and dedicated administrator users for a specified cluster.

Syntax

$ rosa list users [arguments]

Table 50. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the cluster administrators will be listed for.

Table 51. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all of the cluster administrators and dedicated administrators for a cluster named mycluster:

$ rosa list users --cluster=mycluster

list versions

List all of the OpenShift versions that are available for creating a cluster.

Syntax

$ rosa list versions [arguments]

Table 52. Arguments
Option	Definition
--channel-group	Lists only versions from the specified channel group (string). Default: `stable`

Table 53. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

List all of the OpenShift Container Platform versions:

$ rosa list versions

describe admin

Show the details of a specified cluster-admin user and a command to log in to the cluster.

Syntax

$ rosa describe admin <id> | <name> [arguments]

Table 54. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster to which the cluster-admin belongs.

Table 55. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

Describe the cluster-admin user for a cluster named mycluster:

$ rosa describe admin --cluster=mycluster

describe addon

Show the details of a managed service add-on.

Syntax

$ rosa describe addon <id> | <addon_name> [arguments]

Table 56. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

Describe an add-on named codeready-workspaces:

$ rosa describe addon codeready-workspaces

describe cluster

Shows the details for a cluster.

Syntax

$ rosa describe cluster <id> | <name> [arguments]

Table 57. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster.

Table 58. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--profile	Specifies an AWS profile (string) from your credentials file.
--v <level>	The log level for V logs.

Example

Describe a cluster named mycluster:

$ rosa describe cluster --cluster=mycluster

Upgrade and delete upgrade for clusters

This section describes the upgrade command usage for clusters.

upgrade cluster

Schedule a cluster upgrade.

Syntax

$ rosa upgrade cluster [arguments]

Table 59. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the upgrade will be scheduled for.
--interactive	Enables interactive mode.
--version	The version (string) of OpenShift Container Platform that the cluster will be upgraded to.
--schedule-date	The next date (string) when the upgrade will run at the specified time. Format: `yyyy-mm-dd`
--schedule-time	The next time the upgrade will run on the specified date. Format: `HH:mm`
--node-drain-grace-period	Sets a grace period (string) for how long the pod disruption budget-protected workloads are respected during upgrades. After this grace period, any workloads protected by pod disruption budgets that have not been successfully drained from a node will be forcibly evicted. Default: `1 hour`

Table 60. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.

Examples

Interactively schedule an upgrade on a cluster named mycluster:

$ rosa upgrade cluster --cluster=mycluster --interactive

Schedule a cluster upgrade within the hour:

$ rosa upgrade cluster --cluster=mycluster --version 4.5.20

 [id="rosa-delete-upgrade-cluster_{context}"]
== delete upgrade

Cancel a scheduled cluster upgrade:

Syntax

$ rosa delete upgrade --cluster=<cluster_name>

Table 61. Arguments
Option	Definition
--cluster	Required: The name or ID (string) of the cluster that the upgrade will be cancelled for.

Table 62. Optional arguments inherited from parent commands
Option	Definition
--help	Shows help for this command.
--debug	Enables debug mode.
--v level	Log level for V logs.
--yes	Automatically answers `yes` to confirm the operation.