Warum werden SyncLoadBalancerFailed-Fehler beim Erstellen eines VPC-Clusters angezeigt?
Beheben Sie Probleme, wenn die Synchronisierung des Netzwerk-Load-Balancers (NLB) in Ihrem Cluster fehlschlägt.
Beim Einrichten der Lastverteilung in meinem VPC-Cluster wird eine Fehlermeldung angezeigt, die dem folgenden Beispiel ähnelt.
Warning CreatingCloudLoadBalancerFailed 55s ibm-cloud-provider Error on cloud load balancer kube-<CLUSTERID>-<SERVICE_UUID> for service <NAMESPACE>/<SERVICE_NAME> with UID <SERVICE_UUID>: Failed ensuring LoadBalancer: FindLoadBalancer failed: FindLoadBalancer failed: An error occurred while performing the 'authenticate' step: 400 Bad Request [{"incidentID":"XXX","code":"XXX","description":"Error message from IAM: '401 Unauthorized. Transaction-Id: XXX Details: {\"errorCode\":\"BXNIM0430E\",\"errorMessage\":\"User login from given IP address is not permitted.\",\"errorDetails\":\"The user has configured IP address restriction for login. The given IP address 'XXXX' is not contained in the list of allowed IP addresses.\",\"context\":...,"type":"Authentication"}]
Warning SyncLoadBalancerFailed 55s service-controller Error syncing load balancer: failed to ensure load balancer: Error on cloud load balancer kube-<CLUSTERID>-<SERVICE_UUID> for service <NAMESPACE>/<SERVICE_NAME> with UID <SERVICE_UUID>:: Failed ensuring LoadBalancer: FindLoadBalancer failed: FindLoadBalancer failed: An error occurred while performing the 'authenticate' step: 400 Bad Request [{"incidentID":"XXX","code":"XXX","description":"Error message from IAM: '401 Unauthorized. Transaction-Id: XXX Details: {\"errorCode\":\"BXNIM0430E\",\"errorMessage\":\"User login from given IP address is not permitted.\",\"errorDetails\":\"The user has configured IP address restriction for login. The given IP address 'XXX' is not contained in the list of allowed IP addresses.\",\"context\":...,"type":"Authentication"}]
Dieser Fehler tritt auf, wenn Ihre IAM-Zulassungsliste die erforderliche Kommunikation zur IP-Adresse der Steuerebene nicht zulässt.
Um dieses Problem zu beheben, fügen Sie die Netzwerkzone Kubernetes Service Ihrer IAM-Zulassungsliste hinzu.