Client Certificate Authentification documentation bug

[stanislavvv]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG

There is no mention that the CA file name should be exactly ca.crt for client certificate authentification

NGINX Ingress controller version:
0.17.1

Kubernetes version (use kubectl version):
1.11.1

Environment:

• Cloud provider or hardware configuration: standalone vm
• OS (e.g. from /etc/os-release): Ubuntu 16.04.5 LTS
• Kernel (e.g. uname -a): Linux kdm1 4.4.0-131-generic add docs for ingress.kubernetes.io/proxy-body-size annotation #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
• Install tools:
• Others:

What happened:

1. made and check Ingress for website
2. add secret by kubectl create secret generic ca-cert --from-file=./CA.crt
3. insert into ingress from 1) annotations from example with right secret name

after this get 403 in browser and # error obtaining certificate: local SSL certificate default/ca-cert was not found in nginx.conf

What you expected to happen:

400 No required SSL certificate was sent in browser

How to reproduce it (as minimally and precisely as possible):

create secret for client authentification with any name but ca.crt and use it in annotation

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.