automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
Pods in the uipath namespace stuck when enabling custom node taints
Automation Suite on EKS/AKS Installation Guide
Last updated Dec 18, 2024
Pods in the uipath namespace stuck when enabling custom node taints
Pods in the
<uipath>
namespace are not running when custom node taints are enabled. The pods cannot talk to the adminctl webhook that injects
pod tolerations in an EKS env.
To fix the issue, create a network policy to allow traffic into the
admctl
webhook from the cluster CIDR or 0.0.0.0/0
.
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
name: allow-all-ingress-to-admctl
namespace: <uipath>
spec:
podSelector:
matchLabels:
app: admctl-webhook
ingress:
- from:
- ipBlock:
cidr: <cluster-pod-cdr> or "0.0.0.0/0"
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
name: allow-all-ingress-to-admctl
namespace: <uipath>
spec:
podSelector:
matchLabels:
app: admctl-webhook
ingress:
- from:
- ipBlock:
cidr: <cluster-pod-cdr> or "0.0.0.0/0"