-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Nginx-plus ingress controller doesnt create symbolic link for access.log for stdout #5569
Comments
Hi @reddyblokesh thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
Hi @reddyblokesh, are you using Ingress or custom resources? I haven't been able to reproduce on 3.4.3, I can see that |
|
to reproduce this we tried to upgrade nginx ingress controller to nginx plus in another namespace running a different app in backend and we faced the same issue even there. so it looks like a bug ? can you please confirm or should we build a custom image but adding a symlink similar to what we have in docker-mn ? |
@reddyblokesh just to understand your use-case are you using Ingress or VirtualServer (custom resources), and are you using the snippets feature? If you are not using snippets to add We currently do not manually add symlinks, but they are added upstream in the OSS container that we build from, so we can investigate adding the links to our Plus images. |
|
@reddyblokesh to clarify:
For now, I recommend you either build a custom image with the symlink, or change your example above to use Is there a reason that you use |
@jasonwilliams14 fyi |
Describe the bug
Nginx-plus ingress controller doesnt create symbolic link for access.log -> /dev/stdout
To Reproduce
Steps to reproduce the behavior:
Expected behavior
should be able to redirect to stdout and in k logs -f
Your environment
Client Version: v1.28.4
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.26.13
Additional context
nginx config has access.log configured:
grep access.log /etc/nginx/nginx.conf
The text was updated successfully, but these errors were encountered: