Typo in keps/sig-api-machinery/1281-network-proxy

[gonzalovazquez]

Describe the issue

Small typo from on the documentation for 1281 network-proxy

Currently: We assume that for HTTP URL request,s it will be the proxy which does the DNS lookup.

Expected: We assume that for HTTP URL requests it will be the proxy which does the DNS lookup.

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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.

[Swapnil-2502]

Please could you give the exact file path because I cannot find the typo.

[Swapnil-2502]

Okay so the typo is in kubernetes/enhancements not in kubernetes/community

[T-Lakshmi]

@gonzalovazquez, @Swapnil-2502, Can you provide the exact file path/url for this issue.

/triage needs-information

[T-Lakshmi]

Page to update: keps/sig-api-machinery/1281-network-proxy

Moving it to kubernetes/enhancents as this issue is related to enhancements repository.

/transfer enhancements

[k8s-ci-robot]

@T-Lakshmi: You must be an org member to transfer this issue.

In response to this:

Page to update: keps/sig-api-machinery/1281-network-proxy

Moving it to kubernetes/enhancents as this issue is related to enhancements repository.

/transfer enhancements

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.

[T-Lakshmi]

/remove-triage needs-information /language en

[k8s-ci-robot]

@T-Lakshmi: The label(s) language/en cannot be applied, because the repository doesn't have them.

In response to this:

/language en

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.

[Swapnil-2502]

@T-Lakshmi Just ignore this issue and move to another issue.

[satyampsoni]

Is the issue still open to work on?

[Swapnil-2502]

@satyampsoni Don't think so this issue is still open.

[T-Lakshmi]

Hey @satyampsoni, @Swapnil-2502, I still see this issue exist Here.

PR that addressed this issue got closed without merge the changes. So welcome to anyone if you are interested to fix this issue.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.