The RTF appliance upgrade performs in a rolling fashion. If the gravity binary is not upgraded yet on a node (not the installer node) but the upgrade failed on the node, I will need to use the newer gravity binary to get verbose output on the node. How can I get the gravity binary on the node without downloading the whole package?
$ gravity package list --ops-url=https://gravity-site.kube-system.svc.cluster.local:3009 --insecure [gravitational.io] ------------------ ... * gravitational.io/gravity:5.5.36 99MB * gravitational.io/gravity:5.5.38 100MB ...
> gravity package export --insecure --ops-url=https://gravity-site.kube-system.svc.cluster.local:3009 gravitational.io/gravity:5.5.38 gravity > chmod +x ./gravityThe newer gravity binary is under the current directory.
$ sudo ./gravity plan rollback --phase /nodes/VM-PRD-MEL-INTEG-RFWORKER-01/system-upgrade $ sudo ./gravity plan execute --phase /nodes/VM-PRD-MEL-INTEG-RFWORKER-01/system-upgrade --debug
001116606

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.