Hello Dray,
This is already been resolve. The issue was the script.
Regards
Hello jomel2013.
Thank you for reaching out!
The error seems to be related to the failure of a webhook call which is essential for the provisioning process:
Error: 1 error occurred: * Internal error occurred: failed calling webhook "vingress.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-webhook-service.kube-system.svc:443/validate-networking-v1-ingress?timeout=10s": no endpoints available for service "aws-load-balancer-webhook-service"
This error indicates that the Kubernetes service responsible for handling this webhook, aws-load-balancer-webhook-service, is not available or not responding. Here are a few steps to troubleshoot and resolve this issue:
1. Check Service Status:
- Use kubectl get svc -n kube-system to check if the aws-load-balancer-webhook-service is available in the kube-system namespace.
- If the service is not listed, there may have been an issue during the setup of the AWS Load Balancer Controller. You may need to reinstall or verify the installation steps.
2. Review Controller Logs:
- Check the logs of the AWS Load Balancer Controller to identify any errors or warnings that could indicate why the webhook service is not functional. Use the command:
bash kubectl logs -n kube-system -l app.kubernetes.io/name=aws-load-balancer-controller
3. Check Webhook Configurations:
- Verify the MutatingWebhookConfiguration and ValidatingWebhookConfiguration using:
bash kubectl get mutatingwebhookconfigurations,validatingwebhookconfigurations
- Look for entries related to the aws-load-balancer-controller and check if they reference the correct service and namespace.
4. Network Policies and Firewall Rules:
- Ensure that network policies or firewall rules do not block communication to and from the webhook service.
5. Endpoint Check:
- Sometimes, the endpoints might not be set correctly for services. Verify the endpoints using:
bash kubectl get endpoints -n kube-system aws-load-balancer-webhook-service
- If no endpoints are available, this suggests an issue with the service or related pods not registering themselves correctly.
6. Reinstall AWS Load Balancer Controller:
- If the above steps do not resolve the issue, consider reinstalling the AWS Load Balancer Controller. Ensure that the Kubernetes cluster role and role bindings are correctly configured as per the AWS documentation.
7. Kubernetes and EKS Versions:
- Since you are using Kubernetes version 1.28, ensure that all associated components and controllers are compatible with this version, as incompatibilities might lead to services not functioning correctly.
After resolving the issue with the webhook service, attempt the Sisense installation again. If you continue to encounter issues, consider reaching out to AWS support for more detailed analysis specific to your EKS environment, or you may also want to engage with Sisense support if the issue seems related to application configuration or bugs in the deployment scripts.
I hope that helps. If you need any more help please let us know.
Have a great day!
