When running the self-hosted Kubernetes agent successfully, users may see failing ArgoCD rollouts errors while not using this tool.
Error polling argocd rollouts from Kubernetes API
io.kubernets.client.openapi.ApiException:
[...]
at com.brainera.k8sSDKClient.getArgoRollouts(k8sClient.kt:101) ~[app:/na]
Cortex logs this exception for verbosity - this error is harmless if not using ArgoCD tool. These are non-blocking errors that do not impact the core functionality of the Kubernetes agent or deployment process.
If you are using ArgoCD and want to resolve these errors, ensure your ClusterRole includes the necessary permissions:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: cortex-agent-service-account
rules:
- apiGroups: ["apps", "argoproj.io", "batch"]
resources: ["deployments", "services", "pods", "replicationcontrollers", "statefulsets", "rollouts", "cronjobs"]
verbs: ["get", "watch", "list"]
This configuration provides the necessary permissions for the agent to list and watch Argo Rollouts and other Kubernetes resources.