Support for Custom kubeconfig Paths and Parallel Execution in OpenShift VSTS Plugin

[vishnutheja1998]

---

Issue Facing:
Hello,
I am currently using the OpenShift VSTS Plugin for Azure DevOps to manage deployments to an OpenShift cluster and have encountered a challenge when scaling my CI/CD pipeline to use multiple agents. We've noticed that when multiple agents are running tasks concurrently, there are conflicts with the .kube/config file, leading to authentication issues and failed deployments.

I have looked through the documentation and the plugin's settings but haven't found a clear way to configure the plugin to use custom kubeconfig paths or ensure safe parallel executions across multiple Azure DevOps agents. This feature is crucial for our CI/CD pipeline's scalability and reliability, especially as we increase the number of parallel jobs to speed up our deployment processes.

Specific Questions/Requests:
1: Custom kubeconfig Path Support: Is there a way to configure the plugin to use a different kubeconfig file for each task or job? This would allow each agent to operate independently without interfering with each other's authentication states.

2: Parallel Execution Support: Are there best practices or built-in mechanisms within the plugin to support parallel execution without causing conflicts, especially concerning shared resources like the kubeconfig file?

3: Workarounds or Recommendations: If the plugin currently does not support these features, could you recommend any workarounds or practices that could help mitigate these issues? Additionally, are there plans to include these features in future releases?

Any guidance or information you can provide would be greatly appreciated, as it would help us improve our CI/CD pipeline's efficiency and stability.

Thank you for your time and effort in maintaining this plugin.