JCNR Default Helm Chart
Default Helm Chart
This is the JCNR release 24.2 default Helm chart values.yaml from the Juniper Networks Software Download site.
Note:
This is not a working sample. Customize it for your deployment.
####################################################################
# Common Configuration (global vars) #
####################################################################
global:
registry: enterprise-hub.juniper.net/
# uncomment below if all images are available in the same path; it will
# take precedence over "repository" paths under "common" section below
#repository: path/to/allimages/
repository: jcnr-container-prod/
# uncomment below if you are using a private registry that needs authentication
# registryCredentials - Base64 representation of your Docker registry credentials
# secretName - Name of the Secret object that will be created
#imagePullSecret:
#registryCredentials: <base64-encoded-credential>
#secretName: regcred
common:
vrouter:
repository: jcnr-container-prod/
tag: 24.2.0.354
crpd:
repository: jcnr-container-prod/
tag: 24.2R1.14
jcnrcni:
repository: jcnr-container-prod/
tag: 24.2-20240510-d06afc1
telemetryExporter:
repository: jcnr-container-prod/
tag: 24.2.0.354
tools:
repository:
tag: 24.2.0.354
jcnrinit:
repository: jcnr-container-prod/
tag: 24.2.0.354
# Number of replicas for cRPD; this option must be used for multinode clusters
# JCNR will take 1 as default if replicas is not specified
#replicas: "3"
#noLocalSwitching: [700]
# Set AWS IAM Role for EKS PAYG deployments
#iamrole: arn:aws:iam::298183613488:role/jcnr-payg-metering-role
# fabricInterface: provide a list of interfaces to be bound to dpdk
# You can also provide subnets instead of interface names. Interfaces name take precedence over
# Subnet/Gateway combination if both specified (although there is no reason to specify both)
# Subnet/Gateway combination comes handy when the interface names vary in a multi-node cluster
fabricInterface:
#########################
# L2 only
#- eth1:
# ddp: "auto" # ddp parameter is optional; options include auto or on or off; default: off
# interface_mode: trunk
# vlan-id-list: [100, 200, 300, 700-705]
# storm-control-profile: rate_limit_pf1
# native-vlan-id: 100
# no-local-switching: true
#- eth2:
# ddp: "auto" # ddp parameter is optional; options include auto or on or off; default: off
# interface_mode: trunk
# vlan-id-list: [700]
# storm-control-profile: rate_limit_pf1
# native-vlan-id: 100
# no-local-switching: true
#- bond0:
# ddp: "auto" # auto/on/off # ddp parameter is optional; options include auto or on or off; default: off
# interface_mode: trunk
# vlan-id-list: [100, 200, 300, 700-705]
# storm-control-profile: rate_limit_pf1
# #native-vlan-id: 100
# #no-local-switching: true
#########################
# L3 only
#- eth1:
# ddp: "off" # ddp parameter is optional; options include auto or on or off; default: off
#- eth2:
# ddp: "off" # ddp parameter is optional; options include auto or on or off; default: off
########################
# L2L3
#- eth1:
# ddp: "auto" # ddp parameter is optional; options include auto or on or off; default: off
#- eth2:
# ddp: "auto" # ddp parameter is optional; options include auto or on or off; default: off
# interface_mode: trunk
# vlan-id-list: [100, 200, 300, 700-705]
# storm-control-profile: rate_limit_pf1
# native-vlan-id: 100
# no-local-switching: true
##################################
# Provide subnets instead of interface names
# Interfaces will be auto-detected in each subnet
# Only one of the interfaces or subnet range must
# be configured. This form of input is particularly
# helpful when the interface names vary in a multi-node
# K8s cluster
#- subnet: 10.40.1.0/24
# gateway: 10.40.1.1
# ddp: "off" # ddp parameter is optional; options include auto or on or off; default: off
#- subnet: 192.168.1.0/24
# gateway: 192.168.1.1
# ddp: "off" # ddp parameter is optional; options include auto or on or off; default: off
##################################
# fabricWorkloadInterface is applicable only for Pure L2 deployments
#
#fabricWorkloadInterface:
#- enp59s0f1v0:
# interface_mode: access
# vlan-id-list: [700]
#- enp59s0f1v1:
# interface_mode: trunk
# vlan-id-list: [800, 900]
#########################
# defines the log severity. Possible options: DEBUG, INFO, WARN, ERR
log_level: "INFO"
# "log_path": this directory will contain various jcnr related descriptive logs
# such as contrail-vrouter-agent.log, contrail-vrouter-dpdk.log etc.
log_path: "/var/log/jcnr/"
# "syslog_notifications": absolute path to the file that will contain syslog-ng
# generated notifications in json format
syslog_notifications: "/var/log/jcnr/jcnr_notifications.json"
# core pattern to denote how the core file will be generated
# if left empty, JCNR pods will not overwrite the default pattern
#corePattern: "core.%e.%h.%t"
# path for the core file; vrouter considers /var/crash as default value
#coreFilePath: /var/crash
# nodeAffinity: Can be used to inject nodeAffinity for vRouter, cRPD and syslog-ng pods
# You may label the nodes where we wish to deploy JCNR and inject affinity accodingly
#nodeAffinity:
#- key: node-role.kubernetes.io/worker
# operator: Exists
#- key: node-role.kubernetes.io/master
# operator: DoesNotExist
#- key: kubernetes.io/hostname
# operator: In
# values:
# - example-host-1
# cni_bin_dir: Path where the CNI binary will be put; default: /opt/cni/bin
# this may be overriden in distributions other than vanilla K8s
# e.g. OpenShift - you may use /var/lib/cni/bin or /etc/kubernetes/cni/net.d
#cni_bin_dir: /var/lib/cni/bin
# grpcTelemetryPort: use this parameter to override cRPD telemetry gRPC server default port of 50053
#grpcTelemetryPort: 50053
# grpcVrouterPort: use this parameter to override vRouter gRPC server default port of 50052
#grpcVrouterPort: 50060
# vRouterDeployerPort: use this parameter to override vRouter deployer port default port of 8081
#vRouterDeployerPort: 8082
jcnr-vrouter:
# do not configure cpu_core_mask if you wish to use Kubernetes CPU manager static policy (pod with Guaranteed QoS) for vRouter DPDK
# cpu_core_mask is the vRouter forward core mask i.e. if specified, vRouter will be run using the mentioned cores
cpu_core_mask: "2,3,22,23"
# configure guaranteedVrouterCpus if you wish to use CPU manager static policy (pod with Guaranteed QoS) for vRouter DPDK
#guaranteedVrouterCpus: 4
# configurable parameter for dpdk control threads
#dpdkCtrlThreadMask: "2,3"
# configurable parameter for service core mask
#serviceCoreMask: "2,3"
# no of cpus to be assigned to service and control threads if serviceCoreMask, dpdkCtrlThreadMask and cpuCoreMask are not provided
#numServiceCtrlThreadCPU: 1
# restoreInterfaces: setting this to true will restore the interfaces
# back to their original state in case vrouter pod crashes or restarts
restoreInterfaces: false
# Enable bond interface configurations L2 only or L2 L3 deployment
#bondInterfaceConfigs:
# - name: "bond0"
# mode: 1 # ACTIVE_BACKUP MODE
# slaveInterfaces:
# - "enp59s0f0v0"
# - "enp59s0f0v1"
# primaryInterface: "enp59s0f0v0"
# slaveNetworkDetails: # This section only applies, when network attachment definition is used as the input
# - name: srif0net0
# namespace: default
# MTU for all physical interfaces( all VF’s and PF’s)
mtu: "9000"
# rate limit profiles for bum traffic on fabric interfaces in bytes per second
stormControlProfiles:
rate_limit_pf1:
bandwidth:
level: 0
#rate_limit_pf2:
# bandwidth:
# level: 0
dpdkCommandAdditionalArgs: "--yield_option 0"
# enable monitoring thread example:
# - logs appear every 100 seconds
# - log nl_counter & profile_histogram
# loggingMask explanation:
# 0b001 = nl_counter
# 0b010 = lcore_timestamp
# 0b100 = profile_histogram
# dpdk_monitoring_thread_config:
# loggingMask: 5
# loggingInterval: 100
# Set ddp to enable Dynamic Device Personalization (DDP)
# Provides datapath optimization at NIC for traffic like GTPU, SCTP etc.
# Options include auto or on or off; default: off
ddp: "auto"
# Set true/false to Enable or Disable QOS, note: QOS is not supported on X710 NIC.
qosEnable: false
# uio driver will be vfio-pci or uio_pci_generic
vrouter_dpdk_uio_driver: "vfio-pci"
# agentModeType will be dpdk or xdp. set agentModeType dpdk will bringup dpdk datapath. set agentModeType to xdp to use ebpf.
agentModeType: dpdk
# fabricRpfCheckDisable: Set this flag to false to enable the RPF check on all the fabric interfaces of the JNCR, by default RPF check is disabled
#fabricRpfCheckDisable: false
#telemetry:
# disable: false
# metricsPort: 8072
# logLevel: info #Possible options: warn, warning, info, debug, trace, or verbose
# gnmi:
# enable: true
# port: 8076
#vrouter:
# telemetry:
# metricsPort: 8070
# logLevel: info #Possible options: warn, warning, info, debug, trace, or verbose
# gnmi:
# enable: true
# port: 8075
# persistConfig: set this flag to true if you wish jcnr-operator generated pod configuration to persist even after uninstallation
# use this option only in case of l2 mode
# default value is false if not specied
# to enable persist config
#persistConfig: true
################### jcnr-operator/windriver section ###################
# Interface bound type (0 - unbound interface, 1 - sriov pre-bound interface)
# For WRCP deployment with pre-bound interface please set the field (interfaceBoundType: 1)
#interfaceBoundType: 1
# NetworkDetails - list of network attachment definition
#networkDetails:
# - ddp: "off" # ddp parameter is optional; options include on or off; default: off
# name: srif0net0 # network attachment definition name
# namespace: default # namespace name where the network attachment definition is created
# - ddp: "on"
# name: srif1net1
# namespace: default
# NetworkDeviceResources
#networkResources:
# limits:
# intel.com/pci_sriov_net_datanet0: "1"
# intel.com/pci_sriov_net_datanet1: "1"
# requests:
# intel.com/pci_sriov_net_datanet0: "1"
# intel.com/pci_sriov_net_datanet1: "1"
#
contrail-tools:
#set it to true to install contrail-tools
install: false