-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] vpc网关pod删除后,pod使用的弹性外网ip未释放 #4200
Comments
v1.12.17 上也有这问题, 创建vpc-gw时会连续分配多个IP,但后期没回收:
|
恢复途径: |
@author970 Could you please try the latest v1.12 version? The image tags are v1.12.19-x86 and v1.12.19-arm. |
OK. When we subsequently upgrade kube-ovn to v1.12.19 and subsequent versions, we will conduct verification and reply with the verification results. |
Issues go stale after 60d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed. |
After verification, it is found that by upgrading kube-ovn to version v1.12.22, this issue has been resolved. |
Kube-OVN Version
v1.12.11
Kubernetes Version
v1.27.6
Operation-system/Kernel Version
Linux node152 5.10.0-136.12.0.86.4.hl202.x86_64 #1 SMP Fri Mar 10 14:42:11 CST 2023 x86_64 x86_64 x86_64 GNU/Linux
Description
1、创建vpc-nat-vpc资源,自动创建statefulSet及Pod,通过命令kubectl get ip -A 可查看到一个vpc subnet ip(即LanIP)和一个macvlan类型(弹性外网)subnet的子网的ip被使用,其中弹性外网ip没有mac地址;
2、重启vpc-nat-gw资源对应的Pod,再通过命令kubectl get ip -A可查看到新的macvlan类型(弹性外网)subnet的子网的ip被使用,查询弹性外网subnet资源status中可用ip资源,发现1中的弹性外网IP,并未变为可用。
Steps To Reproduce
1、创建vpc-nat-vpc资源,自动创建statefulSet及Pod,通过命令kubectl get ip -A 可查看到一个vpc subnet ip(即LanIP)和一个macvlan类型(弹性外网)subnet的子网的ip被使用,其中弹性外网ip没有mac地址;
2、重启vpc-nat-gw资源对应的Pod,再通过命令kubectl get ip -A可查看到新的macvlan类型(弹性外网)subnet的子网的ip被使用,查询弹性外网subnet资源status中可用ip资源,发现1中的弹性外网IP,并未变为可用。
Current Behavior
vpc网关重启后,未释放弹性外网ip
Expected Behavior
vpc网关重启后,可正常释放弹性外网ip。
The text was updated successfully, but these errors were encountered: