The TAP device plugin provides the ability to create tap devices in containers. A TAP device provides frame reception and transmission for user space programs. It can be seen as an interface, which, instead of receiving frames from a traditional network interface, receives them from user space applications, and instead of sending frames via a traditional network interface, writes them to the user space application. For more information please see here: https://www.kernel.org/doc/html/v5.8/networking/tuntap.html
Installing
The feature will be available in OpenShift 4.13 as Developer Preview. No further installation steps are required.
Configuring a TAP device
A sample TAP device CNI plugin configuration is shown below:
{
"type": "tap",
"multiQueue": true,
"selinuxcontext": "system_u:system_r:container_t:s0"
"owner": 0,
"group": 0,
"ipam": {...}
}
Below is an explanation of the individual attributes of the configuration section:
- Type - type of plugin: “tap.”
- MultiQueue - enable multiqueue.
- SELinuxcontext - for systems with the SELinux security module enabled, the context under which to create the TAP device.
- Owner - the user owning the TAP device. If not specified the TAP device will have no owner assigned. If specified, the owner will be user with the specified user id, with 0 being the root user.
- Group - the group owning the tap device. If not specified the TAP device will have no owner assigned. If specified, the group will be user with the specified group id.
To configure a TAP plugin in OpenShift a network-attachment-definition must be created:
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
name: tap
namespace: mmirecki
spec:
config: '{
"cniVersion": "0.4.0",
"name": "tap",
"plugins": [
{
"type": "tap",
"owner": 0,
"group": 0,
"multiQueue": true,
"selinuxcontext": "system_u:system_r:container_t:s0"
"ipam": {...}
}
]
}'
The above created network must then be specified in the networks annotation of a pod:
---
apiVersion: v1
kind: Pod
metadata:
annotations:
k8s.v1.cni.cncf.io/networks: '[
{
"name": "tap",
"namespace": "mmirecki",
"interface": "ext0",
"mac": "50:00:00:00:00:10"
}
]'
Example use case
A sample use case for tap devices is creating TAP devices for use with DPDK applications.
Some DPDK applications use regular kernel networking to send low-volume traffic such as logs or messages. The DPDK application can use a TAP device for the slow path communication between the DPDK workload and the kernel networking.
Status
The TAP device feature will be available in OpenShift 4.13 as Developer Preview.
The use cases for the feature and available options are based on limited customer feedback. Additional feedback on possible use cases and missing functionality are welcome. Please contact your Red Hat account manager for further details.
About the author
Browse by channel
Automation
The latest on IT automation for tech, teams, and environments
Artificial intelligence
Updates on the platforms that free customers to run AI workloads anywhere
Open hybrid cloud
Explore how we build a more flexible future with hybrid cloud
Security
The latest on how we reduce risks across environments and technologies
Edge computing
Updates on the platforms that simplify operations at the edge
Infrastructure
The latest on the world’s leading enterprise Linux platform
Applications
Inside our solutions to the toughest application challenges
Original shows
Entertaining stories from the makers and leaders in enterprise tech
Products
- Red Hat Enterprise Linux
- Red Hat OpenShift
- Red Hat Ansible Automation Platform
- Cloud services
- See all products
Tools
- Training and certification
- My account
- Customer support
- Developer resources
- Find a partner
- Red Hat Ecosystem Catalog
- Red Hat value calculator
- Documentation
Try, buy, & sell
Communicate
About Red Hat
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
Select a language
Red Hat legal and privacy links
- About Red Hat
- Jobs
- Events
- Locations
- Contact Red Hat
- Red Hat Blog
- Diversity, equity, and inclusion
- Cool Stuff Store
- Red Hat Summit