You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’d like to propose adding the ability to enable and configure Azure Kubernetes Service (AKS) add-ons directly within the Visual Studio Code AKS extension. This feature would enhance user experience and streamline cluster management, especially for developers working directly from their VS Code environments.
Current Scenario:
Currently, users need to use the Azure CLI, Azure portal, or ARM templates to enable add-ons such as:
Azure Monitor for containers
Azure Policy for Kubernetes
Ingress controllers
HTTP application routing
Open Service Mesh
Virtual nodes
Azure AD integration
While these tools are effective, having the ability to manage and configure add-ons directly from the VS Code AKS extension would reduce context switching and allow for more seamless integration with the development workflow.
Proposed Feature:
Add-On Discovery: Users can view a list of available add-ons for their AKS clusters, similar to how it’s displayed in the Azure portal.
Add-On Enablement: Users can enable or disable individual add-ons with a single click or through command palette options. The extension could offer a simple UI that mirrors the portal, but integrated directly in VS Code.
Add-On Configuration: Allow users to configure add-ons directly within the extension. For example, setting custom metrics or configuring security policies as part of the Azure Monitor or Azure Policy add-ons.
Real-Time Feedback: The extension should provide real-time feedback on the status of add-ons (enabled, disabled, or in progress), as well as alerting the user if an add-on requires further configuration.
Benefits:
Improved Developer Experience: Developers managing AKS clusters from VS Code would have all the necessary tools in one place, avoiding the need to switch to the Azure portal or CLI.
Increased Productivity: By enabling add-ons directly from VS Code, developers can streamline their workflows, save time, and manage clusters more efficiently.
Consistency with Other Tools: This feature would bring the AKS extension closer to the functionality already available in the Azure portal, ensuring consistency across Azure tools.
What do you all think?
The text was updated successfully, but these errors were encountered:
Feature Request:
I’d like to propose adding the ability to enable and configure Azure Kubernetes Service (AKS) add-ons directly within the Visual Studio Code AKS extension. This feature would enhance user experience and streamline cluster management, especially for developers working directly from their VS Code environments.
Current Scenario:
Currently, users need to use the Azure CLI, Azure portal, or ARM templates to enable add-ons such as:
While these tools are effective, having the ability to manage and configure add-ons directly from the VS Code AKS extension would reduce context switching and allow for more seamless integration with the development workflow.
Proposed Feature:
Add-On Discovery: Users can view a list of available add-ons for their AKS clusters, similar to how it’s displayed in the Azure portal.
Add-On Enablement: Users can enable or disable individual add-ons with a single click or through command palette options. The extension could offer a simple UI that mirrors the portal, but integrated directly in VS Code.
Add-On Configuration: Allow users to configure add-ons directly within the extension. For example, setting custom metrics or configuring security policies as part of the Azure Monitor or Azure Policy add-ons.
Real-Time Feedback: The extension should provide real-time feedback on the status of add-ons (enabled, disabled, or in progress), as well as alerting the user if an add-on requires further configuration.
Benefits:
What do you all think?
The text was updated successfully, but these errors were encountered: