Closed kahirokunn closed 1 month ago
I have same issues.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has not seen any activity since it was marked stale. Closing.
/reopen
Bug report
General Information
Cilium CLI version (run
cilium version
) cilium-cli: 0.13.2 compiled with go1.20.2 on darwin/arm64 cilium image (default): v1.13.1 cilium image (stable): v1.13.1 cilium image (running): v1.13.1Orchestration system version in use (e.g.
kubectl version
, ...)Platform / infrastructure information AWS・EKS
Link to relevant artifacts (policies, deployments scripts, ...)
Generate and upload a system zip:
cilium sysdump
How to reproduce the issue
You can check the error by preparing two clusters built with the following values in Helm.
Solution
The Private IPs of CLB and NLB can be obtained by executing the following command.
If you could not get the IP, you can do it for each vendor. For example, in case of AWS, you can get the Private IP without going through DNS by doing the following.
Reference: https://dev.classmethod.jp/articles/check_elb_private_ip/
NLB
Result
CLB
Whether the deployed LB is NLB or CLB is included in the ELB information.