- play_arrow Configure Kubernetes and Contrail
- play_arrow CN2 Apstra Integration
- play_arrow CN2 Security
- play_arrow Advanced Virtual Networking
- Create an Isolated Namespace
- Configure Allowed Address Pairs
- Enable Packet-Based Forwarding on Virtual Interfaces
- Configure Reverse Path Forwarding on Virtual Interfaces
- Configure Fast Convergence
- Configure Graceful Restart and Long-Lived Graceful Restart
- vRouter Interface Health Check
- Kubernetes Ingress Support
- Deploy VirtualNetworkRouter in Cloud-Native Contrail Networking
- Configure Inter-Virtual Network Routing Through Route Targets
- Configure IPAM for Pod Networking
- Enable VLAN Subinterface Support on Virtual Interfaces
- Subinterface Support with Multus
- EVPN Networking Support
- Customize Virtual Networks for Pod Deployments, Services, and Namespaces
- Deploy Kubevirt DPDK Dataplane Support for VMs
- Pull Kubevirt Images and Deploy Kubevirt Using a Local Registry
- Static Routes
- VPC to CN2 Communication in AWS EKS
- Stickiness for Load-Balanced Flows
- Configure BFD Health Check for BGPaaS Sessions
- Configure a Service Account to Assume an IAM role
- play_arrow Configure DPDK
- play_arrow Configure eBPF
- play_arrow Analytics
- Contrail Networking Analytics
- Contrail Networking Metric List
- Kubernetes Metric List
- Cluster Node Metric List
- Contrail Networking Alert List
- vRouter Session Analytics in Contrail Networking
- Extend TLS Analytics
- Centralized Logging
- Port-Based Mirroring
- Flow-Based Mirroring
- Configurable Categories of Metrics Collection and Reporting (Tech Preview)
- Juniper CN2 Technology Previews (Tech Previews)
Configure ClusterIP Service by Assigning Endpoints
ClusterIP Service without a Selector and Manually Assigned Endpoints
Juniper® Cloud-Native Contrail Networking (CN2) supports the ClusterIP service to work with manually assigned endpoints without adding a selector in the service. ClusterIP is the default type of service, which is used to expose a service on an IP address internal to the cluster. Access is only permitted from within the cluster.
When creating the endpoint for the service, it's important to add the IP address and
targetRef
in the endpoint. The targetRef
should include the pod details such as kind, name, and namespace. Without these
details, connectivity to the ClusterIP service will not work.
Pod details provided in the targetRef
of the endpoint are used to
add the virtual machine interface (VMI) reference of the corresponding pod in the
service floating IP (FIP) object.
See the following example of pod details provided in targetRef
:
apiVersion: v1 kind: Endpoints metadata: labels: app: nginx name: nginx namespace: clusterip subsets: - addresses: - ip: 10.128.0.151 targetRef: kind: Pod name: nginx-7d79f94b45-9tfjm namespace: clusterip - ip: 10.128.0.175 targetRef: kind: Pod name: nginx-7d79f94b45-kcb4s namespace: clusterip ports: - name: http port: 8080 protocol: TCP