LB can not access k8s api server in devstack
Bug #1777812 reported by
Lv Jiawei
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kuryr-kubernetes |
Fix Released
|
Undecided
|
Lv Jiawei | ||
Bug Description
After devstack install complete. It creates a k8s serivce with 443 port using haproxy LB.
Kuryr would create a port named kubelet-
I find that haproxy LB can not access k8s api server through the kubelet-
The reason is that the default security-group for that port didn't have a rule which pass related ingress packets for ipv4.
Therefore, can we create a particular security-group for kubelet-
| description: | updated |
| Changed in kuryr-kubernetes: | |
| status: | New → Invalid |
| Changed in kuryr-kubernetes: | |
| status: | Invalid → New |
| status: | New → Invalid |
| summary: |
- Pod can not access k8s api server in devstack + LB can not access k8s api server in devstack |
| description: | updated |
| Changed in kuryr-kubernetes: | |
| status: | Invalid → New |
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in kuryr-kubernetes: | |
| assignee: | nobody → Lv Jiawei (zhangoic) |
| description: | updated |
| description: | updated |
Revision history for this message
| Michal Dulko (michal-dulko-f) wrote | #1 |
| Changed in kuryr-kubernetes: | |
| status: | New → Fix Released |
To post a comment you must log in.
Isn't that fixed in https:/