Customize JCNR Helm Chart for EKS Deployment

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

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

Helm Chart Description for Amazon EKS Deployment

Customize the Helm chart using the Juniper_Cloud_Native_Router_<release>/helmchart/jcnr/values.yaml file. We provide a copy of the default values.yaml in JCNR Default Helm Chart.

Table 1 contains a description of the configurable attributes in values.yaml for an Amazon EKS deployment.

Key Description

global

registry

Defines the Docker registry for the JCNR container images.

The default value is set to:

enterprise-hub.juniper.net in Helm charts downloaded from the Juniper Networks software download site.
Amazon Elastic Container Registry (ECR) for Helm charts downloaded from the AWS Marketplace.

repository

(Optional) Defines the repository path for the JCNR container images. This is a global key that takes precedence over the repository paths under the common section. Default is jcnr-container-prod/.

imagePullSecret

(Optional) Defines the Docker registry authentication credentials. You can configure credentials to either the Juniper Networks enterprise-hub.juniper.net registry or your private registry.

Not applicable for AWS Marketplace subscriptions.

registryCredentials Base64 representation of your Docker registry credentials. See Configure Repository Credentials for more information.

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. Use the defaults.

repository

Defines the repository path. The global repository key takes precedence if defined.

The default value is set to:

jcnr-container-prod/ in Helm charts downloaded from the Juniper Networks software download site.
juniper-networks for AWS Marketplace subscriptions.

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. Default is 1. The value for this key must be specified for multi-node clusters. The value is equal to the number of nodes running JCNR.

noLocalSwitching

Not applicable.

iamrole

Not applicable.

fabricInterface

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.

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

For example:

  # L3  only
  - eth1:
      ddp: "off"                 
  - eth2:
      ddp: "off"

subnet

An alternative mode of input to interface names. For example:

- subnet: 10.40.1.0/24 
  gateway: 10.40.1.1 
  ddp: "off"

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 in a multi-node cluster.

ddp

Not applicable.

interface_mode

Not applicable.

vlan-id-list

Not applicable.

storm-control-profile

Not applicable.

native-vlan-id

Not applicable.

no-local-switching

Not applicable.

fabricWorkloadInterface

Not applicable.

log_level

Defines the log severity. Available value options are: DEBUG, INFO, WARN, and ERR.

Note:

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

log_path

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

syslog_notifications

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

corePattern

Indicates the core_pattern for the core file. If left blank, then JCNR pods will not overwrite the default pattern on the host.

Note:

Set the core_pattern on the host before deploying JCNR. You can 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 to the core file. Default is /var/crash.

nodeAffinity

(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 is to be deployed:

nodeAffinity:
  - key: key1
    operator: In
    values:
      - jcnr

Note:

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 path with the path in your distribution (for example, /var/opt/cni/bin).

grpcTelemetryPort

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

grpcVrouterPort

(Optional) Default is 50052. Configure to override.

vRouterDeployerPort

(Optional) Default is 8081. Configure to override.

cpu_core_mask

If present, this indicates that you want to use static CPU allocation to allocate cores to the forwarding plane.

This value should be a comma-delimited list of isolated CPU cores that you want to statically allocate to the forwarding plane (for example, cpu_core_mask: "2,3,22,23"). Use the cores not used by the host OS in your EC2 instance.

Comment this out if you want to use Kubernetes CPU Manager to allocate cores to the forwarding plane.

Note:

You cannot use static CPU allocation and Kubernetes CPU Manager at the same time. Using both can lead to unpredictable behavior.

guaranteedVrouterCpus

If present, this indicates that you want to use the Kubernetes CPU Manager to allocate CPU cores to the forwarding plane.

This value should be the number of guaranteed CPU cores that you want the Kubernetes CPU Manager to allocate to the forwarding plane. You should set this value to at least one more than the number of forwarding cores.

Comment this out if you want to use static CPU allocation to allocate cores to the forwarding plane.

Note:

You cannot use static CPU allocation and Kubernetes CPU Manager at the same time. Using both can lead to unpredictable behavior.

dpdkCtrlThreadMask

Specifies the CPU core(s) to allocate to vRouter DPDK control threads when using static CPU allocation. This list should be a subset of the cores listed in cpu_core_mask and can be the same as the list in serviceCoreMask.

CPU cores listed in cpu_core_mask but not in serviceCoreMask or dpdkCtrlThreadMask are allocated for forwarding.

Comment this out if you want to use Kubernetes CPU Manager to allocate cores to the forwarding plane.

serviceCoreMask

Specifies the CPU core(s) to allocate to vRouter DPDK service threads when using static CPU allocation. This list should be a subset of the cores listed in cpu_core_mask and can be the same as the list in dpdkCtrlThreadMask.

CPU cores listed in cpu_core_mask but not in serviceCoreMask or dpdkCtrlThreadMask are allocated for forwarding.

Comment this out if you want to use Kubernetes CPU Manager to allocate cores to the forwarding plane.

numServiceCtrlThreadCPU

Specifies the number of CPU cores to allocate to vRouter DPDK service/control traffic when using the Kubernetes CPU Manager.

This number should be smaller than the number of guaranteedVrouterCpus cores. The remaining guaranteedVrouterCpus cores are allocated for forwarding.

Comment this out if you want to use static CPU allocation to allocate cores to the forwarding plane.

restoreInterfaces

Set to true to restore the interfaces back to their original state in case the vRouter pod crashes or restarts or if JCNR is uninstalled.

bondInterfaceConfigs

Not applicable.

mtu

Maximum Transmission Unit (MTU) value for all physical interfaces (VFs and PFs). Default is 9000.

stormControlProfiles

Not applicable.

dpdkCommandAdditionalArgs

Pass any additional DPDK command line parameters. The --yield_option 0 is set by default and implies the DPDK forwarding cores will not yield their assigned CPU cores.

dpdk_monitoring_thread_config

(Optional) Enables a monitoring thread for the vRouter DPDK container. Every loggingInterval seconds, a log containing the information indicated by loggingMask is generated.

loggingMask

Specifies the information to be generated. Represented by a bitmask with bit positions as follows:

0b001 is the nl_counter
0b010 is the lcore_timestamp
0b100 is the profile_histogram

loggingInterval

Specifies the log generation interval in seconds.

ddp

Not applicable.

qosEnable

Set to false for EKS deployments.

vrouter_dpdk_uio_driver

The uio driver is vfio-pci.

agentModeType

Set to dpdk.

fabricRpfCheckDisable

Set to false to enable the RPF check on all JCNR fabric interfaces. By default, RPF check is disabled.

telemetry

(Optional) Configures cRPD telemetry settings. To learn more about telemetry, see Telemetry Capabilities .

disable

Set to true to disable cRPD telemetry. Default is false, which means that cRPD telemetry is enabled by default.

metricsPort

The port that the cRPD telemetry exporter is listening to Prometheus queries on. Default is 8072.

logLevel

One of warn, warning, info, debug, trace, or verbose. Default is info.

gnmi

(Optional) Configures cRPD gNMI settings.

enable

Set to true to enable the cRPD telemetry exporter to respond to gNMI requests.

vrouter

telemetry

(Optional) Configures vRouter telemetry settings. To learn more about telemetry, see Telemetry Capabilities .

metricsPort

Specify the port that the vRouter telemetry exporter listens to Prometheus queries on. Default is 8070.

logLevel

One of warn, warning, info, debug, trace, or verbose. Default is info.

gnmi	(Optional) Configures vRouter gNMI settings. enable - Set to true to enable the vRouter telemetry exporter to respond to gNMI requests.

persistConfig Set to true if you want JCNR operator generated pod configuration to persist even after uninstallation. This option can only be set for L2 mode deployments. Default is false.

interfaceBoundType Not applicable.

networkDetails Not applicable.

networkResources Not applicable.

contrail-tools

install Set to true to install contrail-tools (used for debugging).