Support Azure Workload Identity in port-ocean Helm Chart for AKS
Milan Dewilde
Currently, the port-ocean Helm chart requires Azure authentication via Client ID and Client Secret to export information from Azure to Port. When running port-ocean in an AKS (Azure Kubernetes Service) cluster, we would like to use Azure Workload Identity for authentication instead of static credentials. Workload Identity is a more secure and Kubernetes-native approach, reducing the risk associated with managing and rotating secrets, and aligns with best practices for cloud-native deployments.