LB POD Crashloop about akrobateo HOT 7 OPEN

The only way for the LB pods to crash without any log entries is on this line: https://github.com/kontena/akrobateo/blob/master/lb-image/entrypoint.sh#L8

And yes, if that is the case it really should log something. :)

The change between loadbalancer and nodeport is currently unhandled as you noticed. We need to handle that too at some point. If possible, could you separate that into another issue to track it properly.

from akrobateo.

Thanks for the reply.. I will check this again.

I have opened a separate case for the Daemonset not been deleted after service type is changed back to NodePort.

from akrobateo.

#23 introduced some logging for the case of ip forwarding not enabled. could you test with the latest image?

from akrobateo.

Hi,

Yes I can see some logs now, but strangely I am seeing 2 containers inside the service-lb pods (echo & echo2)..

service-lb-echoserver-7bltj   2/2     Running   0          13m
service-lb-echoserver-gpjdj   2/2     Running   0          13m
service-lb-echoserver-kw9zk   2/2     Running   0          13m
service-lb-echoserver-rm6hb   2/2     Running   0          13m
service-lb-echoserver-tdqrj   2/2     Running   0          13m

Is this normal?

from akrobateo.

Do you have multiple ports defined in the service? The lb pods have a container per port

from akrobateo.

No I am the test-service template in the git repo (echoserver), I did not modify the file at all

from akrobateo.

The test-service does have two ports defined:

apiVersion: v1
kind: Service
metadata:
  name: echoserver
spec:
  type: LoadBalancer
  ports:
  - name: echo
    port: 8080
    targetPort: 8080
    protocol: TCP
  - name: echo2
    port: 9090
    targetPort: 8080
    protocol: TCP
  selector:
    app: echoserver

So Akrobateo will create the pods so that there's a container for each port, two in this case.

from akrobateo.