GitHub user mark-duggan closed a discussion: Kubernetes traefik ingress 
controller not creating Public IP

ACS 4.20.0
Kubernetes 1.30.3

Running CloudStack in a homelab where then "main" network is 192.168.50.0/24. 
This is where the ACS management server and hosts reside, but it's also shared 
with everyday devices like laptops, phones etc. Planning a move toa new 
locationsoon and will change this network layout, but for now this "is what it 
is". A subset of this range is used as the "Public IP" for my CloudStack 
deployment

An Isolated Network has been deployed in Cloudstack and also Kubernetes within 
this isolated network. Connectivity is available via kubectl, pods can be 
provisioned etc.

I am attempting to deploy the traefik ingress controller but it is timing out 
attempting to reach the management host API.  

`kubectl describe svc traefik` shows a "SyncLoadBalancerFailed" Warning, with a 
timeout to the management server API

Noted similar errors when running `kubectl -n kube-system logs 
pod/cloud-controller-manager-xxxx` 

I deployed a pod to the same kube-system namespace for testing with kubectl exec

Attempts to access internet to perform apt updates and curling sites on the 
internet , from this pod, are successful. However, attempts to access any 
resources in the "home" network of 192.168.50.0/24 are unsuccessful. 

Noted that the pods deployed in the kube-system namepaces have an 192.168.x.x 
address

I connected to the virtual router for this network and running tcpdump shows 
traffic from cloud-controller-manager and test pod ingressing on eth0 but from 
there it seems to be dropped. 

I've tried looking at the iptables on the virtual router but this I'm running 
into limits on my understanding of how iptables rules work. 

I did also notice that internet bound traffic seemed to come from the 
10.100.0.x address of the k8s node on which the pod has been provisioned, 
suggesting some kind of NAT being applied for this traffic but, traffic 
intended for 192.168.50.x, shows the ip address of the pod in the tcpdump

This may not be a supported or recommended network configuration, but any 
guidance on how to possibly resolve would be welcome

GitHub link: https://github.com/apache/cloudstack/discussions/11000

----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Reply via email to