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 Wind River Deployment

SUMMARY Read this topic to learn about the deployment configuration available for the Juniper Cloud-Native Router on a Wind River Deployment.

You can deploy and operate Juniper Cloud-Native Router in the L3 mode on a Wind River deployment. 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 helm chart are shown in the table below.
Table 1: Helm Chart Attributes and Descriptions
Key Additional Key Configuration Description
registry   Defines the docker registry for the vRouter, cRPD and jcnr-cni container images. The default value is The images provided in the tarball are tagged with the default registry name. If you choose to host the container images to a private registry, replace the default value with your registry URL.
repository   (Optional) 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.
  registryCredentials Base64 representation of your Docker registry credentials. View the Configure Repository Credentials topic for more information.
  secretName Name of the secret object that will be created.
common   Defines repsitory paths and tags for the vRouter, cRPD and jcnr-cni container images. Use default unless using a private registry.
  repository Defines the repository path. The default value is atom-docker/cn2/bazel-build/dev/. The global repository key takes precedence if defined.
  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. The value must be equal to the number of nodes to which JCNR must be deployed.
storageClass Not applicable for non-cloud deployments.
awsregion   Not applicable for non-EKS deployments.
noLocalSwitching (Optional) Prevents interfaces in a bridge domain from transmitting and receiving ethernet frame copies. Enter one or more comma separated VLAN IDs to ensure that the interfaces belonging to the VLAN IDs do not transmit frames to one another. This key is specific for L2 and L2-L3 deployments. Enabling this key provides the functionality on all access interfaces. For enabling the functionality on trunk interfaces, configure the no-local-switching key in the fabricInterface key.

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.

For example:

  # L3  only
  - eth1:
      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.


(Optional) Indicates the interface-level Dynamic Device Personalization (DDP) configuration. DDP provides datapath optimization at NIC for traffic like GTPU, SCTP, etc.

Setting options include auto, on, or off. The default setting is off.


The subnet/interface level ddp takes precedence over the global ddp configuration.

  interface_mode Not applicable for Wind River deployment.

Not applicable for Wind River deployment.


Not applicable for Wind River deployment.

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

Leave the log_level set to the default 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. The default value is /var/log/jcnr/.


Indicates the absolute path to the file that stores syslog-ng generated notifications in JSON format. The default value is /var/log/jcnr/jcnr_notifications.json.


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 Set the value to /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.
vRouterDeployerPort   (Optional) Default value is 8081. Configure to override if the default port is unavailable.
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.
bondInterfaceConfigs Not applicable for Wind River deployment.
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 Configure the rate limit profiles for BUM traffic on fabric interfaces in bytes per second.


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"

(Optional) Indicates the global Dynamic Device Personalization (DDP) configuration. DDP provides datapath optimization at NIC for traffic like GTPU, SCTP, etc. For a bond interface, all slave interface NICs must support DDP for the DDP configuration to be enabled.

Setting options include auto, on, or off. The default setting is off.


The interface level ddp takes precedence over the global ddp configuration.


Set to false for Wind River Deployment.

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.

Sample Helm Charts

Helm Chart for L3 Only Deployment on Wind River Deployment

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