Update Documentation for the feature https://github.com/kubernetes/kubernetes/issue…

[smrutiranjantripathy]

Hi Team,
I'm updating the document for the feature Support Elastic Ips in NLB.
kubernetes/kubernetes#63959

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @smrutiranjantripathy!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign kbhawkey
You can assign the PR to them by writing /assign @kbhawkey in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit e035639

https://deploy-preview-20906--kubernetes-io-master-staging.netlify.app

[RA489]

/check-cla

[smrutiranjantripathy]

I signed it

[jimangel]

@smrutiranjantripathy is this documented anywhere on AWS? I would think an external link would be a better solution given the SIG Docs 3rd party content KEP/ issue.

[onlydole]

+1 - I agree with @jimangel

[smrutiranjantripathy]

@smrutiranjantripathy is this documented anywhere on AWS? I would think an external link would be a better solution given the SIG Docs 3rd party content KEP/ issue.

Its not documented on AWS docs. It was a lot of trouble in finding the PR, so I thought of putting in the kubernete main document.

[sftim]

@smrutiranjantripathy I strongly recommend that you update either https://github.com/kubernetes/cloud-provider-aws/tree/master/docs/book or https://github.com/awsdocs/amazon-eks-user-guide/blob/master/doc_source/load-balancing.md - or attempt that - and then if that lands you change the Kubernetes documentation to hyperlink there.

If neither of those places accepts the change you want then in terms of updating the Kubernetes website your options are limited: the policy on documenting third party details is to hyperlink rather than to put that documentation into the website itself. What we can do from a SIG perspective is add some weight to your request to document this change elsewhere.

[zparnold]

@smrutiranjantripathy just to keep things clear, I'm going to close this, but we really do want your contribution! So if you have a chance to address the comments and reopen this PR I'd be happy to help you get this merged!

/close

[k8s-ci-robot]

@zparnold: Closed this PR.

In response to this:

@smrutiranjantripathy just to keep things clear, I'm going to close this, but we really do want your contribution! So if you have a chance to address the comments and reopen this PR I'd be happy to help you get this merged!

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