-
Notifications
You must be signed in to change notification settings - Fork 269
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
Haproxy-ingress with AWS NLB #713
Comments
Hi, it seems the container file system has some restriction. Please edit the issue and add a few more details on how you've provisioned the controller. |
Hi, Below are the details:
Please let me know you need more details |
Yes, how (steps) and where (kind, k3d, gke, eks, ?) you provisioned HAProxy Ingress? |
I can reproduce the following error running HAProxy Ingress as an uid != 0 and also != 1001
However I couldn't reproduce a Please share a bit more information about the restrictions of the environment, eg uid running the controller or any other restriction to the file system. In the mean time I'll remove diff --git a/rootfs/start.sh b/rootfs/start.sh
index 8112ad0c..ff33bee7 100755
--- a/rootfs/start.sh
+++ b/rootfs/start.sh
@@ -21,6 +21,6 @@ if [ $# -gt 0 ] && [ "$(echo $1 | cut -b1-2)" != "--" ]; then
exec "$@"
else
# Copy static files to /etc/haproxy, which cannot have static content
- cp -R -p /etc/lua /etc/haproxy/
+ cp -R /etc/lua /etc/haproxy/
exec /haproxy-ingress-controller "$@"
fi |
I have changed some configMap after following Thanks for your help :) |
How we can configure haproxy-ingress with AWS NLB. I tried many times but unable to get lucky. Getting below error:
cp: can't preserve ownership of '/etc/haproxy/lua/auth-request.lua': Operation not permitted
cp: can't preserve ownership of '/etc/haproxy/lua/send-response.lua': Operation not permitted
cp: can't preserve ownership of '/etc/haproxy/lua/services.lua': Operation not permitted
cp: can't preserve ownership of '/etc/haproxy/lua': Operation not permitted
I1229 13:50:57.608421 6 launch.go:203]
Name: HAProxy
Release: v0.11.1
The text was updated successfully, but these errors were encountered: