Last modified November 27, 2024
'kubectl gs get releases' command reference
Note This command relates to our vintage product and is not relevant for Clusters based on Cluster API.
Like with all get
commands in kubectl
, this command can be used to get details on one item, a release in this case, or list several of them.
Usage
Get a list of releases
Execute
kubectl gs get releases
to list some information on all releases available to you in the current installation.
Here is some example output:
VERSION STATUS AGE KUBERNETES CONTAINER LINUX COREDNS CALICO
v14.2.1 ACTIVE 2d 1.19.9 2765.2.3 1.6.5 3.15.3
v14.2.2 ACTIVE 2d 1.19.9 2605.12.0 1.6.5 3.15.3
v15.0.0 DEPRECATED 3d 1.20.8 2765.2.6 1.6.5 3.15.3
v15.1.0 DEPRECATED 4d 1.20.9 2765.2.6 1.8.3 3.15.5
v15.1.1 DEPRECATED 4d 1.20.9 2765.2.6 1.8.3 3.15.5
v15.2.0 ACTIVE 20d 1.20.9 2765.2.6 1.8.3 3.15.5
v15.2.1 ACTIVE 21d 1.20.9 2765.2.6 1.8.3 3.15.5
Get specific release
When used with a release version as additional argument, the command will show details for a single release. Example:
kubectl gs get releases v15.2.1
Note: As an alternative to get releases
, get release
will also work.
Output
The standard tabular output format features these columns:
VERSION
: Unique identifier of the release.STATUS
: The state of the release. Possible states are:ACTIVE
: A stable release, fully supported.PREVIEW
: A preview for testing purposes only, not yet considered stable.WIP
: Work in progress, a release in development.DEPRECATED
: Has been replaced by a successor release. No longer recommended.
AGE
: How long ago was the release created.KUBERNETES
: The version of Kubernetes provided by this releaseCONTAINER LINUX
: The version of container linux provided by this releaseCOREDNS
: The version of CoreDNS provided by this releaseCALICO
: The version of Calico provided by this release
Flags
Here we document the flags that have a particular meaning for the get releases
command. Use kubectl gs get releases --help
for a full list.
--active-only
If present, list only the releases that are currently marked as active.
--output/-o
kubectl
commonly allows to specify the output format for all get
subcommands. kubectl gs get releases
is no different.
Similar to other get
subcommands, you can specify the output format of kubectl gs get releases
using the --output
flag.
YAML output
To inspect a release’s main custom resource in YAML notation, add the --output yaml
flag (or -o yaml
in short) to the command.
The following example command would print the main resource for release v15.2.1
.
kubectl gs get releases v15.2.1 --output yaml
When applied without a release version argument, the output will be a list of resources. Example:
$ kubectl gs get releases --output yaml
apiVersion: v1
kind: List
items:
- apiVersion: release.giantswarm.io/v1alpha1
kind: Release
...
Related
kubectl gs login
- Ensure an authenticated kubectl context.
Need help, got feedback?
We listen to your Slack support channel. You can also reach us at support@giantswarm.io. And of course, we welcome your pull requests!