Skip to content
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

Configuring an Ingress for Custom Header Transmission to Upstream Server #10939

Open
sajith-madhusanka opened this issue Jan 29, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@sajith-madhusanka
Copy link

sajith-madhusanka commented Jan 29, 2024

What do you want to happen?

My requirement is to configure an ingress to send the client certificate to the upstream server in a custom HTTP header. I have followed the instructions in [1] to send a custom header to the upstream server using the following configuration.

apiVersion: v1
data:
  X-CLIENT-CERTIFICATE: $ssl_client_escaped_cert
kind: ConfigMap
metadata:
  name: custom-headers
  namespace: ingress-nginx

Since this applies globally to all the ingresses deployed in my deployment, I need a way to configure a specific ingress to send custom headers to the upstream server.

[1] https://kubernetes.github.io/ingress-nginx/examples/customization/custom-headers/

Thanks & Regards
Sajith M

@sajith-madhusanka sajith-madhusanka added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 29, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jan 29, 2024
Copy link

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Feb 29, 2024
@sajith-madhusanka
Copy link
Author

Hi Team,

Any updates regarding this?

Thanks & Regards
Sajith M

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

2 participants