How to allow multiple bots in X-Robots-tag header?

[sarveswarreddy]

I want to allow twitterbot and facebookbot in the header X-Robots-Tag and block all other bots to index or follow the url in my ingress controller. I don't find syntax to do that through the helm chart. Anyone have ideas how I can do that ?

I can add a header something like X-Robots-Tag: noindex or X-Robots-Tag: noindex, nofollow , but how can I specify specific bots in the header value.

[k8s-ci-robot]

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-sigs/prow repository.

[longwuyuan]

Look at the template of a new bug report and answer the questions asked in that template. You can edit the description of this issue and answer those questions in markdown format. At least the readers will know which controller and which version of the controller is used.

The short description you typed is better used in a chat on the Kubernetes slack. So please engage there because there are more engineers and developers there with knowledge and time. There are very few resources here. Since this is not tracking any action item, until at least the issue description is a little helpful on the environment and the context,, I will close this for now.

You can re-open the issue after you have edited the issue description to answer the questions (in markdown format) asked in a new bug report template. thanks

/close
/kind support
/triage needs-information

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

Look at the template of a new bug report and answer the questions asked in that template. You can edit the description of this issue and answer those questions in markdown format. At least the readers will know which controller and which version of the controller is used.

The short description you typed is better used in a chat on the Kubernetes slack. So please engage there because there are more engineers and developers there with knowledge and time. There are very few resources here. Since this is not tracking any action item, until at least the issue description is a little helpful on the environment and the context,, I will close this for now.

You can re-open the issue after you have edited the issue description to answer the questions (in markdown format) asked in a new bug report template. thanks

/close
/kind support
/triage needs-information

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-sigs/prow repository.