Skip to content

Conversation

@bennerv
Copy link
Contributor

@bennerv bennerv commented Nov 11, 2025

Once Azure/azure-cli-extensions#9415 is merged, it is no longer necessary to specify the --server option as it edits the kubeconfig in place to point to the correct server.

@prmerger-automator
Copy link
Contributor

@bennerv : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @abell

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit b51106e:

✅ Validation status: passed

File Status Preview URL Details
articles/bastion/bastion-connect-to-aks-private-cluster.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Updates Azure Bastion documentation to reflect changes in the aks-preview extension (version 19.0.0b16+) where the --server option is no longer required for kubectl commands when connecting to AKS private clusters through Bastion tunnels.

  • Simplified kubectl command example by removing the --server parameter
  • Added a note explaining the version-specific behavior for older aks-preview extensions
  • Updated code block language identifiers from pwsh to azurecli and bash for better syntax highlighting

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

```

> [!NOTE]
> For aks-preview versions 19.0.0b15 and below, you have to specify the `--server=https://localhost:<LocalMachinePort>` on all `kubectl` commands.
Copy link

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The note should clarify what behavior to expect with version 19.0.0b16 and above, not just what's required for older versions. Consider rephrasing to: 'For aks-preview versions 19.0.0b15 and below, you must specify the --server=https://localhost:<LocalMachinePort> option on all kubectl commands. Version 19.0.0b16 and above automatically configures the kubeconfig to point to the correct server.'

Suggested change
> For aks-preview versions 19.0.0b15 and below, you have to specify the `--server=https://localhost:<LocalMachinePort>` on all `kubectl` commands.
> For aks-preview versions 19.0.0b15 and below, you must specify the `--server=https://localhost:<LocalMachinePort>` option on all `kubectl` commands. Version 19.0.0b16 and above automatically configures the kubeconfig to point to the correct server.

Copilot uses AI. Check for mistakes.
@ShannonLeavitt
Copy link
Contributor

@AbdullahBell

Can you review the proposed changes?

Due to the upcoming conference, all merging and publishing is on hold until the morning of 18 November 2025.

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Nov 12, 2025
@bennerv
Copy link
Contributor Author

bennerv commented Nov 12, 2025

We should /hold on this as the version in the note might change based on https://github.com/Azure/azure-cli-extensions/pull/9415/files

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