Feature: Connect with Portal Azure instead of relying on Kubeconfig

[anime-shed]

🔖 Feature description

The proposed feature involves enabling users to connect and manage Kubernetes clusters and container registries directly through the Azure Portal by creating a dedicated application, rather than relying on importing Kubeconfig files. This would allow the app to have specific permissions for viewing and editing Kubernetes resources, streamlining access and configuration in a unified interface.

🎤 Pitch / Usecases

Implementing this feature would enhance user efficiency by providing a more integrated and secure method for managing Kubernetes environments within Azure, reducing the need for manual file imports that can lead to errors or security vulnerabilities 1.. For instance, developers could use this to quickly deploy and scale applications in a Kubernetes cluster for a web service, where real-time editing of cluster configurations ensures seamless updates without downtime 3. In enterprise settings, it would support scenarios like CI/CD pipelines, where teams automate registry updates for container images, improving collaboration and reducing setup time for projects involving microservices 4. This integration would also bolster Azure's appeal for hybrid cloud strategies, as it simplifies monitoring and editing for large-scale deployments, potentially increasing adoption among organizations migrating from on-premises systems 5.

🔄️ Alternative

One alternative solution is to continue using Kubeconfig imports for Kubernetes access, which involves generating and uploading configuration files to authenticate and manage clusters, though this can be less secure and more error-prone for frequent updates 6. Another option is leveraging Azure CLI or Azure PowerShell for direct command-line interactions with Kubernetes resources, offering programmatic control without a graphical interface, but this may require additional scripting and lacks the centralized dashboard experience 7. Additionally, tools like kubectl with Azure Arc could serve as a workaround, enabling cluster management across environments, yet it still demands separate configurations and might not fully integrate with Azure's portal features 8.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct