Namespace configured for agent is different than the one defined for the Kubernetes cloud. Bee Bot July 13, 2022 13:38 Updated The content of this article has moved to the new documentation site. Related articles Build Agents are not getting provisioned when using .Agents.SeparateNamespace Kubernetes Plugin: Authenticate with a ServiceAccount to a remote cluster Kubernetes Plugin: KubernetesClientException provisioning error Build fails with 'process apparently never started' error dedicated agents are not able to connect Comments 0 comments Please sign in to leave a comment.
Comments
0 comments
Please sign in to leave a comment.