Skip to content
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

ServiceWeb not building #230

Open
vince-vibin opened this issue Jun 11, 2022 · 3 comments
Open

ServiceWeb not building #230

vince-vibin opened this issue Jun 11, 2022 · 3 comments

Comments

@vince-vibin
Copy link
Contributor

vince-vibin commented Jun 11, 2022

Hey so im deploying this on my raspberry pi cluster with this comand:
helm install --version '2.5.8' --namespace pihole --values values.yaml pihole mojo2600/pihole
but when i check the pods the ServiceWeb pods are stuck in pending:

NAME                      READY   STATUS    RESTARTS   AGE     IP           NODE          NOMINATED NODE   READINESS GATES
svclb-pihole-web-9nsfv    0/2     Pending   0          3m37s   <none>       <none>        <none>           <none>
svclb-pihole-web-gdllc    0/2     Pending   0          3m37s   <none>       <none>        <none>           <none>
svclb-pihole-web-z2t75    0/2     Pending   0          3m37s   <none>       <none>        <none>           <none>
svclb-pihole-web-xshwc    0/2     Pending   0          3m37s   <none>       <none>        <none>           <none>
svclb-pihole-dhcp-v8gkd   1/1     Running   0          3m37s   10.42.1.9    worker1       <none>           <none>
svclb-pihole-dhcp-5rj2v   1/1     Running   0          3m37s   10.42.0.33   raspberrypi   <none>           <none>
svclb-pihole-dhcp-vnqh5   1/1     Running   0          3m37s   10.42.2.9    worker2       <none>           <none>
svclb-pihole-dhcp-ptmxq   1/1     Running   0          3m37s   10.42.3.9    worker3       <none>           <none>
pihole-5f7b84cfb8-ms4w8   1/1     Running   0          3m37s   10.42.0.35   raspberrypi   <none>           <none>

also this is my values.yaml:

---
persistentVolumeClaim:
  enabled: true

ingress:
  enabled: true

serviceWeb:
  type: ClusterIP
  loadBalancerIP: 192.168.178.210
  annotations:
    metallb.universe.tf/allow-shared-ip: pihole-svc
  type: LoadBalancer

serviceDNS:
  loadBalancerIP: 192.168.178.211
  annotations:
    metallb.universe.tf/allow-shared-ip: pihole-svc
  type: LoadBalancer

serviceDhcp:
  loadBalancerIP: 192.168.178.212
  annotations:
    metallb.universe.tf/allow-shared-ip: pihole-svc
  type: LoadBalancer

podDnsConfig:
  enabled: true
  policy: "None"
  nameservers:
  - 8.8.8.8
  - 8.8.4.4

(Note that loadBalancerIP never is the IP of a node but a random free IP in the network and i dont really know if that is how it is supposed to be 😅)
When is describe a pod im getting this error:

0/4 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 3 node(s) didn't match Pod's node affinity/selector.

Do you guys have any idea?

@vince-vibin
Copy link
Contributor Author

so i think i actually just fixed in by just disabeling traefic. Maybe this is going to cause problems later so im going to keep you updated.
To disable i used this command:
kubectl delete -n kube-system helmcharts traefik
The thing is that i now have multiple adresses for each service and i think that should not be the case

NAME             TYPE           CLUSTER-IP      EXTERNAL-IP                                                       PORT(S)                      AGE
pihole-dhcp      LoadBalancer   10.43.144.208   192.168.178.200,192.168.178.201,192.168.178.202,192.168.178.203   67:32211/UDP                 2m30s
pihole-dns-tcp   LoadBalancer   10.43.186.24    192.168.178.200,192.168.178.201,192.168.178.202,192.168.178.203   53:31398/TCP                 2m30s
pihole-dns-udp   LoadBalancer   10.43.243.170   192.168.178.200,192.168.178.201,192.168.178.202,192.168.178.203   53:31275/UDP                 2m30s
pihole-web       LoadBalancer   10.43.19.61     192.168.178.200,192.168.178.201,192.168.178.202,192.168.178.203   80:30004/TCP,443:30006/TCP   2m30s

Any ideas about that?

@MoJo2600
Copy link
Owner

You have defined type twice. Maybe thats the issue?

serviceWeb:
  type: ClusterIP
  loadBalancerIP: 192.168.178.210
  annotations:
    metallb.universe.tf/allow-shared-ip: pihole-svc
  type: LoadBalancer

loadBalancerIP will be removed soon, as it is deprecrated.

I think your Metallb setup is not correct. If you remove the loadBalancerIP setting all the services should be deployed with one external IP.

@vince-vibin
Copy link
Contributor Author

vince-vibin commented Jul 1, 2022

i'm new to this so maybe i'm not really getting what you want me to do, but i now deployed the service like this

serviceWeb:
  type: LoadBalancer
  annotations:
    metallb.universe.tf/allow-shared-ip: pihole-svc

but its still just pending.
is there any documentation about the right metallb config?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants