Resolved Issues in 5.11.0
Issue | Fix Description |
|---|---|
E-145841 | Finished Kubelink pods kept in cache Kubelink kept pods in the Succeeded phase in its cache and continued to deliver policy to them. This issue was resolved by treating pods in the Succeeded phase as deleted and removing them from the Kubelink cache. |
E-145135 | Kubelink in CrashLoopBackoff during uninstallation Kubelink rejected the |
E-142197 | Kubelink storage crash preventing authentication to ETCD after restart Some storage pods triggered an automatic restart that resulted in authentication status errors. This issue was resolved by correcting a syscall command and checking if ETCD already enabled authentication before executing ETCD commands. |
E-140139 | NodePort flow entries showing mismatched source or destination hostnames Kubernetes inter-node forwarding traffic produced flow entries with mismatched traffic direction, causing inaccurate visibility in the PCE. This issue was resolved by clearing the NodePort mark after initial logging so subsequent forwarding traffic retained the correct direction and hostnames. |