-
Notifications
You must be signed in to change notification settings - Fork 15
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
ip_forward is not enabled #31
Comments
Could you double check that the LB pods are created as expected with If those still look as expected, maybe try to run similar pod as the LB pods would be and see what |
@jnummelin I see where
Here is the output for one of the pods ...
|
Here is my test Deployment / Service yaml
As a data point, this works with metallb. |
Well, MetalLB does not use custom pods with iptables for routing so it works completely differently alltogether. :) So the LB pods do look like expected with the init containers trying to set apiVersion: v1
kind: Pod
metadata:
name: ip-forward-test
labels:
name: ip-forward-test
spec:
containers:
- name: test
command:
- sh
- -c
- sleep 60000
image: registry.pharos.sh/kontenapharos/akrobateo-lb:latest
imagePullPolicy: Always
name: sysctl
resources: {}
securityContext:
privileged: true
Then exec yourself into the pod with
|
Working correctly with a fresh install of Kubernetes v1.15.5. |
Synopsis
I am following the article at https://blog.kontena.io/akrobateo-general-purpose-loadbalancer-for-k8s/ to setup Akrobateo on my local Kubernetes cluster (bare metal) installed via RKE.
I have removed the default installed RKE ingress-nginx namespace and controller.
I applied 01_role.yaml, 02_service_account.yaml, 03_role_binding.yaml, and 04_operator.yaml without any issues.
I deployed my sample application.
Expected Behavior
Akrobateo should expose the application externally.
... should show an external IP address for each of my nodes.
Actual Behavior
Akrobateo pods failed to start. The logs show
ip_forward is not enabled
.Looking at
akrobateo/lb-image/entrypoint.sh
this will happen ifcat /proc/sys/net/ipv4/ip_forward
doesn't return0
.I have confirmed on all 3 nodes that...
The text was updated successfully, but these errors were encountered: