Open geniusxiong opened 8 months ago
Issues go stale after 60d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.
@geniusxiong 大佬,这个bug目前还存在么?
@geniusxiong 大佬,这个bug目前还存在么?
还是存在的
Issues go stale after 60d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.
Issues go stale after 60d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.
Bug Report
1.13.0,自定义VPC,kubevirt创建的虚机,解绑安全组后,安全组还是生效
Expected Behavior
kubevirt创建的虚机,解绑安全组后,安全组不生效
Actual Behavior
Steps to Reproduce the Problem
倆虚机,10.50.1.17和10.50.1.9,10.50.1.9是能正常ssh到10.50.1.17
创建安全组(禁止tcp22端口访问)
kubevirt 创建虚机并绑定安全组 虚机的yaml
virt-launcher的yaml
绑定安全组,重启虚机后,安全组生效,ssh不成功
解绑安全组,并重启虚机
重启后 虚机的yaml
virt-launcher的yaml
可见,虚机的yaml和virt-launcher的yaml上已经没有 metadata: annotations: ovn.kubernetes.io/port_security: "true" ovn.kubernetes.io/security_groups: sg-zcf3qmd8 但是还是安全组还是生效的,无法ssh,正常解绑了应该能够ssh
Additional Info
Kubernetes version:
Output of
kubectl version
:operation-system/kernel version:
Output of
awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release
: Output ofuname -r
: