NetApp HCI Manual page 290

b. Enter the client ID as mnode-client.
c. Select Authorize to begin a session.
d. Close the authorization window.
3. Check for the latest upgrade package:
a. From the REST API UI, run POST /upgrade/rke-versions.
b. From the response, copy the task ID.
c. Run GET /task/{taskID} with the task ID from the previous step.
4. From the /task/{taskID} response, copy the latest version number you want to use for the upgrade.
5. Run the RKE upgrade:
a. From the REST API UI, run PUT /upgrade/rke/{version} with the latest version number from the
previous step.
b. Copy the task ID from the response.
c. Run GET /task/{taskID} with the task ID from the previous step.
The upgrade has finished successfully when the
the upgraded version number.
Apply node OS security updates
API commands
1. Initiate the check upgrades request:
curl -X GET "https://<mNodeIP>/k8sdeployer/1/upgrade/checkNodeUpdates"
-H "accept: application/json" -H "Authorization: Bearer <ID>"

You can find the bearer ID used by the APIs by running a GET command and retrieving it
from the curl response.
2. Get task status using task ID from previous command and verify a more recent version number is available
from the response:
curl -X GET "https://<mNodeIP>/k8sdeployer/1/task/<taskID>" -H "accept:
application/json" -H "Authorization: Bearer <ID>"
3. Apply the node updates:
curl -X POST "https://<mNodeIP>/k8sdeployer/1/upgrade/applyNodeUpdates"
-H "accept: application/json" -H "Authorization: Bearer"
For node OS, unattended upgrades for security patches are run on a daily basis but the

node is not rebooted automatically. By applying upgrades, you are rebooting each node
sequentially for the security updates to take effect.
PercentComplete
indicates
100 results
and indicates