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

Update use-node-public-ips.md #141

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

raghu-shukla
Copy link

Corrected line 124 , 129 130

--allowed-host-ports must be a space-separated list of port ranges in the format of /

raghu [ ~ ]$ az aks nodepool update --resource-group argrg --cluster-name argcl --name nodepool1 --allowed-host-ports 80/tcp,443/tcp,53/udp,40000-60000/tcp,40000-50000/udp --asg-ids "/
subscriptions/0f587ca2-06f1-4d72-91f0-5f4151909754/resourceGroups/argrg/providers/Microsoft.Network/applicationSecurityGroups/tstarg"
--allowed-host-ports must be a space-separated list of port ranges in the format of /: '80/tcp,443/tcp,53/udp,40000-60000/tcp,40000-50000/udp'

Corrected line 124 , 129 130

--allowed-host-ports must be a space-separated list of port ranges in the format of <port-range>/<protocol>


raghu [ ~ ]$ az aks nodepool update   --resource-group argrg --cluster-name argcl --name nodepool1 --allowed-host-ports 80/tcp,443/tcp,53/udp,40000-60000/tcp,40000-50000/udp   --asg-ids "/
subscriptions/0f587ca2-06f1-4d72-91f0-5f4151909754/resourceGroups/argrg/providers/Microsoft.Network/applicationSecurityGroups/tstarg"
--allowed-host-ports must be a space-separated list of port ranges in the format of <port-range>/<protocol>: '80/tcp,443/tcp,53/udp,40000-60000/tcp,40000-50000/udp'
Copy link
Contributor

@raghu-shukla : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link

Learn Build status updates of commit 77dd38e:

✅ Validation status: passed

File Status Preview URL Details
articles/aks/use-node-public-ips.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@phealy

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@JoeyC-Dev
Copy link
Contributor

JoeyC-Dev commented Jan 20, 2025

Your name and your cli style sounds like someone work as MSFT FTE.
As FTE, it is supposed to work internally instead of using public repo. I don't have access to that (as I am from a Vendor), but maybe you want to reach doc team.

Copy link

github-actions bot commented Feb 3, 2025

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@github-actions github-actions bot removed the inactive label Feb 25, 2025
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants