Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: failed to deploy resources from k8s-addons directory #360

Open
3 tasks done
kvvit opened this issue Dec 11, 2024 · 0 comments
Open
3 tasks done

fix: failed to deploy resources from k8s-addons directory #360

kvvit opened this issue Dec 11, 2024 · 0 comments
Assignees

Comments

@kvvit
Copy link

kvvit commented Dec 11, 2024

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Expected Behavior

Update terrafrom code to fix the issue

Current Behavior

Running command terragrunt apply in directory k8s-addons finished with error.

Failure Information (for bugs)

I get next error when I run terragrunt apply in k8s-addons directory:

│ Error: 1 error occurred:
│       * Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-controller-webhook-service.aws-load-balancer-controller.svc:443/mutate-v1-service?timeout=10s": no endpoints available for service "aws-load-balancer-controller-webhook-service"
│ 
│ 
│ 
│   with helm_release.external_secrets[0],
│   on eks-external-secrets.tf line 143, in resource "helm_release" "external_secrets":
│  143: resource "helm_release" "external_secrets" {
│ 
╵
╷
│ Error: 4 errors occurred:
│       * Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-controller-webhook-service.aws-load-balancer-controller.svc:443/mutate-v1-service?timeout=10s": no endpoints available for service "aws-load-balancer-controller-webhook-service"* Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-controller-webhook-service.aws-load-balancer-controller.svc:443/mutate-v1-service?timeout=10s": no endpoints available for service "aws-load-balancer-controller-webhook-service"* Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-controller-webhook-service.aws-load-balancer-controller.svc:443/mutate-v1-service?timeout=10s": no endpoints available for service "aws-load-balancer-controller-webhook-service"* Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-controller-webhook-service.aws-load-balancer-controller.svc:443/mutate-v1-service?timeout=10s": no endpoints available for service "aws-load-balancer-controller-webhook-service"
│ 
│ 
│ 
│   with helm_release.loki_stack[0],
│   on eks-loki-stack.tf line 169, in resource "helm_release" "loki_stack":
│  169: resource "helm_release" "loki_stack" {

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

  1. step 1 - clone code to local computer
  2. step 2 - prepare infrastructure by deploying VPC, EKS cluster with Karpenter
  3. step 3 - deploy k8s-addons with curent settings
@kvvit kvvit self-assigned this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant