Lokesh Bandi

related to https://github.com/nginxinc/kubernetes-ingress/issues/2421

As per an update from https://github.com/nginxinc/kubernetes-ingress/issues/5981, we were told that building an FIPS enabled image directly from the repository, i.e https://github.com/nginxinc/kubernetes-ingress broke things up, and told to "fetch" or "pull"...

1. k exec -it nginx-ingress-test-controller-6888b57b67-h45xc -- whoami 101 whoami: extra operand ‘101’ Try 'whoami --help' for more information. command terminated with exit code 1 2. i just tried same 3.6.1...

1. grep access.log /etc/nginx/conf.d/* `access_log /var/log/nginx/access.log main; access_log on;` 2. grep stdout /etc/nginx/nginx.conf ` access_log /dev/stdout main; access_log /dev/stdout stream-main;` 3. /var/log/nginx/access.log gets created but doesnt create symbolic link to...

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....

- we are adding as part of values.yaml in ingress template : `config: entries: ingress-template: | access_log /var/log/nginx/access.log main; ` - so i doubt its not creating symlinks as part...