tke-eni-agent, tke-eni-ipamd, and tke-eni-ip-scheduler. Typically, these three components share the same version. However, the tke-eni-ip-scheduler component undergoes fewer changes, so its version may lag slightly behind.# Check the version of tke-eni-agent.kubectl -nkube-system get ds tke-eni-agent -o jsonpath={.spec.template.spec.containers[0].image}# Check the version of tke-eni-ipamd.kubectl -nkube-system get deploy tke-eni-ipamd -o jsonpath={.spec.template.spec.containers[0].image}# Check the version of tke-eni-ip-scheduler.kubectl -nkube-system get deploy tke-eni-ip-scheduler -o jsonpath={.spec.template.spec.containers[0].image}
Version Number | Release Date | Change Content | Change Impact |
v3.13.0 | 2026-08-03 | The cross-tenant trunking ENI supports fixed IPs. ip-scheduler supports periodically synchronizing VPC subnet IP address capacity to improve scheduling accuracy when subnet IP addresses change. This fixes an issue where the failure of idempotency checks for cross-tenant trunking ENI could lead to duplicate card creation. This fixes an issue where vpcipclaim is repeatedly enqueued in cross-tenant trunking ENI scenarios. | No impact on business |
v3.12.0 | 2026-07-08 | The shared ENI mode supports assigning the primary IP address of a secondary ENI to a Pod, thereby improving IP address utilization per node. This fixes an issue where the gap in index cache synchronization prevents ENI information from being synchronized. In non-fixed IP address mode, eni-agent waits for node ENI configuration to be ready during initialization to prevent abnormal component termination. | No impact on business. |
v3.11.0 | 2026-06-03 | Optimize the fixed IP address scheduling logic to avoid centralized scheduling issues when workloads are created in an empty cluster. Support forcibly disabling specified subnets via vpc-cni.ipam.banned-subnets.In fixed IP address mode, cross-tenant Pod configuration supports subnet IDs in the pending state.Increase the retry delay when the EIP quota is exceeded to reduce invalid retries. | No impact on business |
v3.10.4 | 2026-05-28 | Optimizes the status display of scheduler cold standby Pods, implements traffic routing based on dynamic labels, and resolves the issue of abnormal console display for cold standby Pods. | No impact on business |
v3.10.3 | 2026-05-14 | This fixes an issue where insufficient subnet IP addresses in fixed IP address mode are not correctly identified. This fixes an issue that may cause leaks when cross-tenant trunking ENI are deleted. | No impact on business |
v3.10.0 | 2026-04-15 | Supports assigning user-defined cloud Tags to EIP resources. Optimize the fixed IP address allocation process for super node Pods. Supports automatically synchronizing non-fixed IP address warm-up configurations to existing nodes. Add the vpc-cni.route-eni.use-vpc-ip-quota configuration item to automatically align the per-ENI IP address quota with the VPC side.This fixes an issue where the associated eipclaim cannot be processed after the EIP is deleted. This fixes an issue where an error occurs because metadata returns an empty MAC address, and switches to a fallback policy to obtain it. | No impact on business. |
v3.9.5 | 2026-04-13 | Fixes the snapshot race condition issue in the ENI IP address direct assignment scenario. | No impact on business |
v3.9.4 | 2026-03-31 | This fixes an issue where the vpcipclaim corresponding to the trunking eni is not enqueued after node initialization. This fixes an issue where route loss occurs after eni-agent deletes the IP address of a secondary ENI device upon startup. | No impact on business |
v3.9.3 | 2026-03-23 | Fixes the issue where the IP address allocation process did not consider Pod-specified subnets (nominated-subnets). | No impact on business |
v3.9.2 | 2026-03-17 | Fixes the issue where eni-agent did not reconcile existing routing tables with IDs of 2000+ . | No impact on business |
v3.9.1 | 2026-03-13 | This fixes an issue where the CNI type for the IP address corresponding to a Pod does not meet expectations in cross-tenant scenarios. This fixes an issue where the agent.config.disable-setup-host configuration does not take effect. | No impact on business |
v3.9.0 | 2026-03-04 | Supports querying EIP quotas via the VPC API. Optimizes the allocation speed for ENI secondary IPs and secondary ENI primary IPs. eni-agent removes the dependency on obtaining MAC addresses from the metadata service. The Trunking ENI supports ipset. Supports synchronizing cloud Tags for incremental and existing ENIs. This fixes an issue where clusters with non-fixed IP address independent ENIs incorrectly delete ENIs when the kube-apiserver is under high load. | No impact on business |
v3.8.5 | 2026-04-27 | Enables the cross-tenant trunking ENI to support creating network cards using IP addresses from reserved IP ranges. | No impact on business |
v3.8.2 | 2026-02-11 | Fixes the issue where concurrent read/write operations during the scheduler's subnet remaining IP address quantity statistics cause components to exit abnormally. | No impact on business |
v3.8.1 | 2026-02-02 | This fixes an issue where the subnet ID is modified but the idempotency identifier (client-token) is not updated during trunking ENI creation. This fixes an issue where the ipset processing coroutine fails to exit properly when the dryrun mode exits. | No impact on business. |
v3.8.0 | 2026-01-12 | The base ID for ENI policy routing tables has been changed from 2000 to 4000 to avoid conflicts with the routing table IDs of Cilium (2004/2005) and DataPlaneV2 (3004). Supports ipset capability. Supports cross-tenant ENIs in Trunking ENI mode. Compatible with annotations related to super node fixed IP address. Optimizes eni-agent's strong dependency on the metadata service, and falls back to system calls to obtain ENI information when the metadata service encounters errors. Adds the agent.config.disable-setup-host configuration item. When it is enabled, eni-agent does not modify node kernel parameters or deploy netmgr configurations.Optimizes the node resource display logic for shared ENIs in non-fixed IP address mode. | No impact on business. After the upgrade, newly added ENIs use routing table IDs of 4000+, while existing routing tables with IDs of 2000+ remain compatible. |
v3.7.4 | 2025-12-17 | Adjusts the timeout for eni-agent to reclaim network resources of sandboxes not in the Running state to 30 minutes. This fixes an issue where repeated EIP binding during super node Pod termination leads to residual dirty data on the VPC side. | No impact on business |
v3.7.3 | 2025-11-20 | For super node Pods with EIP passthrough enabled (annotation eks.tke.cloud.tencent.com/eip-injection: true), pre-allocates EIPs and adds EIP annotations to avoid mutual dependency between Pod startup and EIP allocation. | No impact on business |
v3.7.2 | 2025-11-13 | Fixes the issue where node extended resources show as 0 in the independent ENIs non-fixed IP address mode. | No impact on business |
v3.7.1 | 2025-11-04 | Fixes the issue where eni-agent sets node extended resources to 0 after disconnecting from kubelet, causing abnormal status for existing Pods after kubelet restarts. | No impact on business |
v3.7.0 | 2025-10-10 | Supports automatic creation and binding of Anti-DDoS EIPs for Pods. The EIP creation input parameters now include Egress and AntiDDoSPackageId.The tke.cloud.tencent.com/cilium-overlay-ip-unavailable taint is automatically removed after the Cilium Overlay network is ready (PodCIDR allocation is successful).Supports compute cluster virtual nodes (vnode) and automatically ignores such nodes. This fixes an issue in non-fixed IP mode where eni-agent, during initialization, fails to set the node's maximum ENI quantity and pre-binding quantity, causing unintended IP address and ENI unbinding to be triggered when no Pod is in use. This fixes an issue where, after an asynchronous task for creating an EIP fails, the idempotency identifier is not updated, causing invalid retries to block EIP creation. | No impact on business |
v3.5.9 | 2025-07-08 | Supports disabling a shared ENI by adding the label tke.cloud.tencent.com/eni-allocated-banned=true. After the shared ENI is disabled, new IPs are no longer allocated from that ENI, while existing IPs remain unaffected.In non-fixed IP address mode, Pods on super nodes support multi-ENI binding by default. The number of ENIs (including the primary ENI) is specified via the annotation tke.cloud.tencent.com/serverless-eni-number.The EIP feature has been refactored. By default, it supports binding multiple EIPs to a single Pod. Currently, this is only supported for Pods on super nodes in non-fixed IP address mode. It supports obtaining temporary credentials via AssumeRole by configuring api-env.owner-uin and api-env.role-name in conjunction with SecretId and SecretKey. It also supports authorization by using the default role bound to the node CVM via api-env.use-cvm-default-role.It supports querying the instance types compatible with relay ENIs via the TencentCloud API. If the query fails, it automatically falls back to the local configuration. This fixes an issue in shared ENI mode where Pod egress traffic incorrectly uses the primary IP address of a secondary ENI (TS4 kernel). This fixes an issue where fixed IP addresses are lost due to fixed IP address subnet ENIs being repeatedly scheduled between super nodes and regular nodes. This fixes a timing issue during rolling updates for Pods with specified EIPs, preventing EIPs from being incorrectly unbound. This fixes an issue in subnet ENI mode where slow registration of node extended resources causes node pools to over-provision nodes. | No impact on business |
v3.5.8 | 2025-04-12 | It supports automatically configuring the annotation tke.cloud.tencent.com/desired-pod-num for nodes, controlled via cidr.auto-patch-desired-pod-num.It supports black-box monitoring for Pod IP allocation. A SucceedSetPodIP event is recorded upon successful allocation, while a FailedSetPodIP event is recorded if allocation failures persist for more than 5 minutes.It supports configuring the MTU for Pod ENIs via agent.config.pod-interface-mtu, covering shared ENIs, independent ENIs, cross-tenant ENIs, and relay subnet ENIs.It supports triggering seamless node security group synchronization via the node annotation tke.cloud.tencent.com/need-sync-security-groups=true.Support for SA3, SA4, S6, S7, and S8 instance types has been added to the relay subnet ENI mode. Subnet ENIs are automatically deleted and recreated when they remain in a PENDING state for more than 3 minutes, enabling self-healing. This fixes an issue where Pods in relay subnet ENI mode cannot be created because the Pod name exceeds 63 characters. This fixes an issue where Pods using shared ENIs/trunking ENIs/cross-tenant ENIs in fixed IP address mode become stuck in the Terminating state after being created and then immediately terminated. | No impact on business |
v3.5.7 | 2024-09-26 | Cross-tenant ENIs support IPv6 address binding. To enable this, specify "NeedIPv6":true in the cross-tenant ENI configuration.It supports specifying the node subnet via the node label tke.cloud.tencent.com/nominated-eni.subnet-xxxxxx="true".It supports configuring the polling timeout for VPC-side asynchronous tasks via resource-manage.vpc-task-polling-timeout.Pods with fixed IPs are allowed to reuse the reserved sandbox when switching between the tke-route-eni and tke-sub-eni CNI types. This fixes an issue where concurrent read/write operations during ENI synchronization in non-fixed IP address mode generate dirty data, and it supports automatic cleanup. This fixes an issue where a subnet specified for a single node in fixed IP address mode is incorrectly applied to all nodes, resulting in erroneous scheduling. | No impact on business. |
v3.5.6 | 2024-08-15 | It supports pre-creating sandboxes for super nodes, including sandbox-aware scheduling and pre-creating fixed IP address sandboxes. Pods with fixed IPs are allowed to switch between the tke-route-eni and tke-sub-eni CNI types. It supports the vpc-cni.route-eni.auto-disable-bm-eni configuration, which by default automatically disables the shared ENI capability for bare metal instances that do not support ENIs.It supports modifying the region for component access to TencentCloud API via api-env.region.The system automatically disables the use of relay ENIs on machine models that do not support them. Shared ENIs support the attachment of 15 auxiliary ENIs to 64-core instance types. By default, the rp_filter is no longer disabled for all ENIs: the primary ENI enables loose verification, and incremental auxiliary ENIs enable strict verification. You can disable it via agent.config.disable-rp-filter.This fixes an issue where an EIP returns an empty task ID due to quota or other reasons, causing invalid retries. | No impact on business. |
v3.5.5 | 2024-06-06 | It provides comprehensive support for the relay ENI mode, with related configurations including vpc-cni.trunking-eni.enable-sub-eni and vpc-cni.trunking-eni.pod-security-group-enforcing-mode.It supports disabling the early-demux kernel parameters on nodes via agent.config.disable-tcp-early-demux and agent.config.disable-udp-early-demux, resolving network connectivity issues between nodes and Pods in strict isolation scenarios.It supports modifying the service port of eni-agent via agent.config.server-port. The default port has been changed from 50050 to 61677.It provides protection against accidental deletion of EIPClaims, preventing EIPs from being unbound while the Pod is still in use. This supports reclaiming fixed IP addresses based on their status and fixes an issue where the timeout reclamation judgment for fixed IP address Pods is incorrect after they are repeatedly scheduled between super nodes and regular nodes. The case sensitivity of fixed IP address annotation values is no longer distinguished. | No impact on business. The default service port for eni-agent is changed from 50050 to 61677. If there are port access restrictions on the node side, they need to be opened accordingly. |
v3.5.4 | 2024-01-11 | The scheduler supports DaemonSet Pods injected into super nodes. It supports managing only nodes with the tke.cloud.tencent.com/tke-eni-managed=true label via vpc-cni.only-manage-labeled-nodes.It supports accessing TencentCloud API via api-env.secret-id and api-env.secret-key.It supports configuring the release of shared ENIs only after they have been idle for a specified duration via vpc-cni.resource-manage.free-eni-spare-duration.When a Pod specifies a subnet, the scheduler preferentially selects nodes that already have ENIs in the same subnet. The preference score can be configured via node-with-nominated-subs-score.Deletion protection is added for shared ENIs. Before deletion, all associated secondary IPs and related resources must be released first. This fixes an issue where repeatedly assigning IPs to the same Pod within a short period leads to the erroneous creation of ENIs. | No impact on business |
v3.5.3 | 2023-09-19 | It supports configuration items such as enable-tce to adapt to private cloud environments.It supports performing audit authorization for deletion requests of cloud resources and custom resources via resource-manage.admit-cloud-resource-deletion and resource-manage.admit-k8s-resource-deletion, and is enabled by default.Optimize the reclamation logic for IPs in the Reserved state by checking whether they are still in use before reclamation, and adjust the default timeout to 24 hours. ip-scheduler supports preferential scheduling based on subnet available IP addresses. Nodes with more remaining subnet IP addresses in the corresponding AZ receive higher scores. | No impact on business |
v3.5.2 | 2023-08-29 | It supports configuring subnet reserved IP addresses via vpc-cni.resource-manage.subnet-reserved-available-ip and vpc-cni.resource-manage.subnet-reserved-available-ip-ratio. Reserved IP addresses can only be assigned to specified IP addresses and the primary IP address of ENIs.It supports ensuring that IP addresses are released only after the Pod is deleted via vpc-cni.resource-manage.not-release-ip-until-pod-deleted.In fixed IP address mode, node-specified subnets are supported. When both node-specified and Pod-specified subnets exist, their intersection is taken. It supports the super node EIP passthrough annotation eks.tke.cloud.tencent.com/eip-injection: true.The EIP quota for CVM is synchronized only during node creation to support scenarios where the EIP quota is changed. It supports idempotent EIP creation and fixes the issue of EIP duplicate creation and leakage caused by VPC API exceptions. This fixes an issue where IP address scale-out fails for dual-stack clusters in shared ENI mode due to PENDING IP addresses. This fixes an issue where IP address scale-out fails after a single node is bound to more than 20 shared ENIs. | No impact on business |
v3.5.1 | 2023-05-12 | The garbage collection feature for fixed IPs is enabled by default. It supports setting the reclamation time individually via the annotation tke.cloud.tencent.com/claim-expired-duration.A ENI-level concurrency lock for EIP binding has been added to reduce errors from underlying APIs. In the shared ENI fixed IP address mode, the node automatically reclaims dirty IP addresses on the ENI each time it attempts to allocate a ENI. This fixes an issue where IP address synchronization fails with a low probability during node initialization in non-fixed IP address mode, resulting in IP addresses being practically unavailable. This fixes an issue where Pods with a purely numeric name suffix cannot bind to a specified EIP. This fixes CVE-2020-10749 by also disabling net.ipv6.conf.all.accept_ra on nodes by default in IPv4 mode. | No impact on business. |
v3.5.0 | 2023-01-12 | It supports the super node EIP annotation, aligns with the EIP TencentCloud API, and supports applying for EIPs with more input parameters. It supports configuring the QPS limit for the TencentCloud API client via cloud-client-qps, with a default value of 50.Unify the configurations of components such as eni-ipamd, eni-agent, and ip-scheduler into tke-network-conf.Monitoring metrics for the number of synchronizations and number of failures of each resource have been added. Non-fixed IP address mode reduces subnet queries and improves IP address allocation speed. Strengthen IP address unbinding validation to prevent IP addresses from being incorrectly unbound by dual eni-ipamd replicas due to high node IO load. This fixes multiple edge-case issues in global route synchronization under the multi-CIDR mode. This fixes an issue where ip-scheduler continuously exits abnormally after subnet deletion. | No impact on business. |
v3.4.7 | 2022-09-07 | It supports the ip-scheduler preferential scheduling policy. Pods with fixed IP addresses are preferentially scheduled to ENIs that match the subnet. eni-ipamd supports dry-run synchronization of existing custom resources (CRs) to promptly detect change anomalies. Optimize the polling logic for ENI and IP address binding to reduce errors caused by ongoing ENI/IP address binding operations. This fixes an issue where releasing a shared ENI in non-fixed IP address mode can, in rare cases, cause internal IP address allocation leakage. | No impact on business. |
v3.4.6 | 2022-07-26 | Supports native node pools. | No impact on business. |
v3.4.5 | 2022-06-28 | The shared ENI non-fixed IP address mode supports IPv6 dual-stack. In dual-stack mode, each Pod is assigned both a v6 IP address and a v4 IP address. This fixes an issue where EIPs become invalid due to nodeLost on super nodes. After the fix, the EIPs are rebound. | No impact on business |
v3.4.4 | 2022-06-06 | EIPs are tagged by default with tke-clusterId and tke-created-eip, and also inherit Tags from the TKE cluster by default.It supports unbinding ENIs from powered-off instances. Optimize the scheduler ip-scheduler to resolve the issue of slow startup caused by an excessive number of subnets. | No impact on business. |
v3.4.3 | 2022-04-13 | eni-ipamd and ip-scheduler support subnet disabling. Disabled subnets can only be assigned via nomination, which is configured through the startup parameter --only-nominated-eni-subnets.Fixed IP address mode supports Pod-specified subnets, which are designated via the annotation tke.cloud.tencent.com/nominated-eni-subnets. Multiple subnets are separated by ,.eni-agent supports protecting critical system kernel parameters by leveraging new features in TLinux to prevent modifications to key kernel parameters ( rp_filter, ip_forward).This fixes an issue where, with a low probability during node initialization in shared ENI mode, the node's eni-ip resource registration fails due to a kubelet restart. This fixes an issue where the IP address garbage collection mechanism fails due to a restart of the container runtime processes dockershim or containerd. | No impact on business. |
v3.4.2 | 2022-03-04 | Non-fixed IP address mode supports node-specified ENI subnets. eni-agent supports automatically and periodically setting critical kernel parameters such as ip_forward and rp_filter to prevent network failures caused by changes to these key parameters. This optimizes scheduling performance. In shared ENI mode, if a ENI is being bound, the system polls and waits, thereby reducing scheduling failures. This fixes an issue where, with a low probability under high node load, eni-ip extended resources are lost. Attempt to delete and recreate ENIs and IP addresses that have been in a Pending state for an extended period, thereby fixing the issue of prolonged ENI and IP address unavailability caused by underlying faults. | No impact on business |
v3.4.1 | 2022-01-21 | This supports fixed-IP Pods scaling to EKS nodes while retaining their IP addresses. It supports specifying EIPs via the annotation tke.cloud.tencent.com/eip-id-list.It supports security group binding for independent ENIs in non-fixed IP address mode. Upgrade the CRD APIVersion to v1 to support kubernetes 1.22. This fixes an issue where, with a low probability in fixed IP address mode, IP address states become out of sync. | No impact on business. |
v3.4.0 | 2021-12-08 | It supports multiple ENIs with fixed IPs. It supports hybrid cloud Underlay connectivity between on-premises and cloud environments, as well as elastic pod deployment. This fixes an issue where, with a low probability of concurrent CNI operations within the same pod, the CNI data plane is configured incorrectly. | No impact on business |
v3.3.9 | 2021-11-09 | This fixes the issue of duplicate EIP creation caused by network issues. It supports EIP binding for Pods that use independent ENIs in non-fixed IP address mode. Optimize the extended resource mechanism of eni-agent to make the management of extended resources more stable and robust. This fixes the issue caused by a discrepancy between the node's configured quota and its actual quota. Optimize the eni-agent IP address garbage collection mechanism so that, for a Pod being created, if there is a dirty container, the reclaimed IP address is allocated to the Pod's new container. Optimize the resource counting algorithm for IP addresses and ENIs already in use in non-fixed IP mode, and fix the issue of inaccurate resource counting caused by Pods in states such as Error, Evicted, and Completed. | No impact on business |
v3.3.8 | 2021-08-17 | It supports directly configuring the backend kube-apiserver address via the --master parameter, eliminating the dependency on kube-proxy.eni-agent supports configuring the QPS and Burst of the kube client via the parameters --kube-client-qps and --kube-client-burst. The default values have been increased to 10 and 20.If eni-agent detects that the updated extended resources are fewer than before, it proactively updates the latest extended resource information to the node status to avoid issues caused by kubelet's asynchronous updates. | No impact on business. |
v3.3.7 | 2021-08-13 | eni-ipamd supports the --enable-node-condition and --enable-node-taint parameters. When the parameters are enabled, if a node lacks required extended resources such as eni-ip or direct-eni, the node's condition or taints are set.EIP supports parsing new API parameters in json format. This fixes an issue where, under the containerd runtime, eni-agent's garbage collection incorrectly reclaims newly allocated IPs with a low probability. This fixes the ipamd panic issue that may be caused by the EIP API. This fixes an issue where, during an upgrade in non-fixed IP address mode, the disable-node-eni annotation may be incorrectly set, causing ENIs to be unbound. | No impact on business. |
v3.3.6 | 2021-07-26 | This fixes an issue where the eni-agent garbage collection mechanism may incorrectly reclaim newly allocated IPs and routes. This fixes an issue where, after cascading reclamation is enabled with --enable-ownerref in eni-ipamd, IPs may be released before their corresponding Pods when upper-level resources such as Deployments are deleted. | No impact on business. |
v3.3.5 | 2021-07-20 | This fixes an issue in non-fixed IP address mode where, for Pods using shared/exclusive ENIs, the accidental deletion of IP address or ENI resources prevents the deletion of local storage data. This fixes an issue in non-fixed IP address mode where the CNI information for shared/exclusive ENIs is not stored and verified for Pod ENI information. | No impact on business. |
v3.3.4 | 2021-07-07 | This fixes the issue where ENI unbinding is continuously retried when the CVM is powered off. This fixes the panic issue caused by synchronous writes in asynchronous logging. Optimize the ENI synchronization logic for non-fixed IP address mode to ensure internal data consistency and prevent the unbinding of ENIs that are in use. This fixes an issue where, in non-fixed IP address clusters upgraded from v3.2, insufficient subnet IPs prevent existing nodes from being allocated IP addresses. This fixes an issue where ENIs whose primary IP address is being used by a Pod may be incorrectly released. | No impact on business. |
v3.3.3 | 2021-06-07 | Supports hybrid cloud ipam and works in conjunction with the cilium overlay/underlay mode. | No impact on business. |
v3.3.2 | 2021-06-01 | ip-scheduler supports preemption, but only for preemption triggered by default resource insufficiency. It does not currently support preemption triggered by IP address resource insufficiency. Refactor the security group feature logic for shared ENIs to support strong synchronization with the node-configured security groups, ensuring that the binding order and priority of security groups align with user settings. Supports the cilium cni-chain mode. eni-agent supports the --port-mapping parameter to enable support for the Pod hostPort field.This feature supports setting a specific fixed IP address reclamation time by annotating a Pod with tke.cloud.tencent.com/claim-expired-duration. The Pod annotation only affects incremental Pods. | No impact on business. |
v3.3.1 | 2021-05-11 | It supports using multiple ENIs in shared ENI non-fixed IP address mode. It supports QPS limits for TencentCloud API calls, with a default limit of 50 QPS per cluster (applied by CVM, VPC, and TKE types). Supports awareness of IP address quota changes after scaling up in non-fixed IP address mode is performed. This feature supports the node annotation tke.cloud.tencent.com/desired-route-eni-pod-num for specifying the required number of route-eni IPs. After the value is written, the component automatically adjusts the node quota.This fixes the issue where VPC task polling times out due to the non-existence of the VPC task. This fixes the eni-ipamd panic issue caused by the failure of the ENI creation task. Optimize the route reconciliation logic to clear only the IP address routes managed by eni-agent. This fixes an abnormal panic issue that may occur when an independent ENI is released in non-fixed IP address mode due to the ENI already being released. | No impact on business. |
v3.3.0 | 2021-04-13 | Supports the custom GR mode, which supports multiple CIDRs for node clusters. | No impact on business. |
v3.2.6 | 2021-03-31 | Reduce the retry time for binding ENIs in exclusive ENI mode to improve binding efficiency. Through concurrency control, this reduces failures in concurrently binding and unbinding ENIs and improves the efficiency of these operations. This optimizes the ENI subnet allocation logic for non-fixed IP mode and fixes an issue where, when nodes are added concurrently, some nodes fail to obtain an IP address even when IP addresses are sufficient. The eni-agent garbage collection mechanism supports self-awareness of the underlying runtime and is compatible with containerd. | No impact on business |
v3.2.5 | 2021-02-22 | Add dnsConfig when deploying eni-ipamd and ip-scheduler to avoid issues caused by user-configured DNS. In shared ENI fixed IP address mode, the subnetID information of the ENI bound to each node is synchronized to the node's label, with the key being tke.cloud.tencent.com/route-eni-subnet-ids.eni-agent attempts to obtain the reason for IP address allocation failure, returns it to the CNI plugin, and ultimately reflects it in the Pod event. This supports specifying an IP address for a bare Pod, which can be designated via the annotation tke.cloud.tencent.com/nominated-vpc-ip.eni-agent supports periodically testing the connection to the APIServer and automatically restarts if a timeout occurs. This fixes the issue of IP address waste caused by internal data inconsistency. | No impact on business |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan