ON THIS PAGE
Manage Juniper Cloud-Native Router
Upgrading JCNR
You can upgrade from Cloud-Native Router release 23.2 to 23.3 using the following steps:
-
Download the tarball, Juniper_Cloud_Native_Router_release_number.tgz, to the directory of your choice. You must perform the file transfer in binary mode when transferring the file to your server, so that the compressed tar file expands properly.
-
Expand the file Juniper_Cloud_Native_Router_release-number.tgz.
tar xzvf Juniper_Cloud_Native_Router_release-number.tgz
-
Change directory to Juniper_Cloud_Native_Router_release-number.
cd Juniper_Cloud_Native_Router_release-number
Note: All remaining steps in the upgrade assume that your current working directory is now Juniper_Cloud_Native_Router_release-number. -
Customize the helm chart for your deployment using the
helmchart/values.yaml
file to match the helm chart configuration in your current installation. -
Deploy the Juniper Cloud-Native Router using the helm chart. Navigate to the helmchart directory and run the following command:
helm upgrade jcnr . Release "jcnr" has been upgraded. Happy Helming! NAME: jcnr LAST DEPLOYED: Thu Sep 21 03:58:28 2023 NAMESPACE: default STATUS: deployed REVISION: 2 TEST SUITE: None
-
Confirm Juniper Cloud-Native Router deployment.
helm ls
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION jcnr default 2 2023-09-21 03:58:28.024244633 -0400 EDT deployed jcnr-23.3.0 23.3.0
Downgrading JCNR
Currently, there is no procedure for downgrading to an older version. To change from a current version to an older version, you must uninstall the current version and install an older version.
Uninstalling JCNR
Cloud-Native Router can be uninstalled by using the following command:
helm uninstall jcnr
Uninstalling Cloud-Native Router restores interfaces to their original state by unbinding from DPDK and binding back to the original driver. It also delete contents of Cloud-Native Router directories, deletes cRPD created interfaces and removes any Kubernetes objects created for JCNR.
The jcnr namespace is not deleted as a part of the helm uninstallation and must be deleted manually.
helm uninstall jcnr--
no-
hooks kubectl delete <ds/name> kubectl delete <job/jobname> kubectl delete ns jcnrops