Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Customize JCNR Helm Chart for GCP Deployment

SUMMARY Read this topic to learn about the deployment configuration available for the Juniper Cloud-Native Router when deployed on GCP.

You can deploy and operate Juniper Cloud-Native Router in L3 mode on GCP. You configure the deployment mode by editing the appropriate attributes in the values.yaml file prior to deployment.

Helm Chart Attributes and Descriptions

Customize the helm charts using the Juniper_Cloud_Native_Router_release-number/helmchart/values.yaml file. The configuration keys of the heml chart are shown in the table below.

Table 1: Helm Chart Attributes and Descriptions
Key Additional Key Configuration Description
registry   Defines the docker registry where the vRouter, cRPD and jcnr-cni container images are hosted. The default value is set to Juniper Enterprise Hub.
repository   Defines the repository path for the vRouter, cRPD and jcnr-cni container images. This is a global key and takes precedence over "repository" paths under "common" section. The default value is jcnr-container-prod/
imagePullSecret   (Optional) Defines the registry authentication credentials. You can configure credentials to either the Juniper repository or your private registry. View the Configure Repository Credentials topic for more information.
  registryCredentials Base64 representation of your Docker registry credentials.
  secretName Name of the Secret object that will be created.
common   Defines repository paths and tags for the vRouter, cRPD and jcnr-cni container images.
  repository Defines the repository path. The global repository key takes precedence if defined.

The default value is set to atom-docker/cn2/bazel-build/dev/.

  tag Defines the image tag. The default value is configured to the appropriate tag number for the JCNR release version.
replicas (Optional) Indicates the number of replicas for cRPD. If the value is not specified, then the default value 1 is considered.

The value for this key must be specified for multi-node clusters and must match the number of nodes to which JCNR must be deployed.


Not applicable for GCP deployments.

awsregion   Not applicable for GCP deployments.
noLocalSwitching Not applicable for GCP deployments.

Provide a list of interfaces to be bound to the DPDK. You can also provide subnets instead of interface names. If both the interface name and the subnet are specified, then the interface name takes precedence over subnet/gateway combination. The subnet/gateway combination is useful when the interface names vary in a multi-node cluster.


Use the L3 only section to configure fabric interfaces for GCP. The L2 only and L2-L3 sections are not applicable for GCP deployments.

For example:

  # L3  only
  - eth1:
      ddp: "off"                 
  - eth2:
      ddp: "off"                
  subnet An alternative mode of input for interface names. For example:
- subnet: 
  ddp: "off"    

The subnet option is applicable only for L3 interfaces. With the subnet mode of input, interfaces are auto-detected in each subnet. Specify either subnet/gateway or the interface name. Do not configure both. The subnet/gateway form of input is particularly helpful in environments where the interface names vary for a multi-node K8s cluster.


Not applicable for GCP deployments.

  interface_mode Not applicable for GCP deployments.

Not applicable for GCP deployments.


Not applicable for GCP deployments.

  native-vlan-id Not applicable for GCP deployments.
  no-local-switching Not applicable for GCP deployments.
fabricWorkloadInterface Not applicable for GCP deployments.
log_level Defines the log severity. Available value options are: DEBUG, INFO, WARN, and ERR.

Leave the log_level set to INFO unless instructed to change it by Juniper support.


The defined directory stores various JCNR related descriptive logs such as contrail-vrouter-agent.log, contrail-vrouter-dpdk.log, etc.


Indicates the absolute path to the file that stores syslog-ng generated notifications in JSON format.


Indicates the core pattern to denote how the core file is generated. If this configuration is left blank, then JCNR pods will not overwrite the default pattern.


Set the corePattern value on host before deploying JCNR. You may change the value in /etc/sysctl.conf. For example, kernel.core_pattern=/var/crash/core_%e_%p_%i_%s_%h_%t.gz

coreFilePath Indicates the path for the core file. If the value is left blank, then vRouter considers /var/crashes as the default value.

(Optional) Defines labels on nodes to determine where to place the vRouter pods. By default the vRouter pods are deployed to all nodes of a cluster.

In the example below, the node affinity label is defined as "key1=jcnr". You must apply this label to each node where JCNR must be deployed:

- key: key1
  operator: In
  - jcnr

This key is a global setting.

key Key-value pair that represents a node label that must be matched to apply the node affinity.
operator Defines the relationship between the node label and the set of values in the matchExpression parameters in the pod specification. This value can be In, NotIn, Exists, DoesNotExist, Lt, or Gt.
cni_bin_dir (Optional) The default path is /opt/cni/bin. You can override the default cni path with a path of used by your distribution e.g. /var/opt/cni/bin.

(Optional) Enter a value for this parameter to override cRPD telemetry gRPC server default port of 50051.

grpcVrouterPort (Optional) Enter a value for this parameter to override vRouter gRPC server default port of 50052.
restoreInterfaces Set the value of this key to true to restore the interfaces back to their original state in case the vRouter pod crashes or restarts.
vRouterDeployerPort   (Optional) Default value is 8081. Configure to override if the default port is unavailable.
bondInterfaceConfigs Not applicable for GCP deployments.
mtu Maximum Transmission Unit (MTU) value for all physical interfaces (VFs and PFs). Default value is 9000.

Indicates the vRouter forward core mask. If qos is enabled, you will need to allocate 4 CPU cores (primary and siblings).

stormControlProfiles Not applicable for GCP deployments.


Pass any additional dpdk cmd line parameters. The --yield_option 0 is set by default and it implies the dpdk forwarding cores will not yield the cpu cores it is assigned to. Additional common parameters that can be added are tx and rx descriptors and mempool. For example:

dpdkCommandAdditionalArgs: "--yield_option 0 --dpdk_txd_sz 2048 --dpdk_rxd_sz 2048 --vr_mempool_sz 131072"
ddp Not applicable for GCP deployments.

Set to false for GCP deployments.

vrouter_dpdk_uio_driver The uio driver is vfio-pci.


Can be dpdk or xdp. Setting agentModeType to dpdk will bringup dpdk datapath. Setting agentModeType to xdp uses ebpf. The default value is dpdk.


Set this flag to false to enable the RPF check on all the fabric interfaces of the JNCR. By default RPF check is disabled.


Set this flag to true if you wish jcnr-cni generated pod configuration to persist even after uninstallation. The option must be set only for L2 mode. The default value is false.


If you are installing JCNR on GCP, then update the dpdkCommandAdditionalArgs key and set tx and rx descriptors to 256. For example:

Sample Helm Charts

Sample GCP JCNR helm chart is provided below:

Helm Chart for GCP Deployment

A working GCP L3 helm chart sample is shown below. The configured sections are highlighted in bold: