fix: added node security group additional rule to allow all traffic i… #359
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t version for external secrets
|
|
@mglotov during the tests I get next error when I deployed k8s-addons: I added |
mglotov
reviewed
Nov 27, 2024
| @@ -154,4 +154,5 @@ resource "helm_release" "external_secrets" { | |||
| local.external_secrets_values | |||
| ] | |||
|
|
|||
| depends_on = [helm_release.aws_loadbalancer_controller] | |||
There was a problem hiding this comment.
Because during terragrunt apply I get next error:
│ 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: 3 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"
│
│
│
│ with helm_release.ingress_nginx[0],
│ on eks-ingress-nginx-controller.tf line 202, in resource "helm_release" "ingress_nginx":
│ 202: resource "helm_release" "ingress_nginx" {
│
╵
╷
│ 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" {
│
After added these depends_on error has vanished. I deploy k8s-addons with these depens_on twice, and everything was okay (without errors).
| depends_on = [kubectl_manifest.kube_prometheus_stack_operator_crds] | ||
| depends_on = [ | ||
| kubectl_manifest.kube_prometheus_stack_operator_crds, | ||
| helm_release.aws_loadbalancer_controller |
There was a problem hiding this comment.
Same answer, as in the comment above.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added node security group additional rule to allow all traffic inside the group
PR Description
Please explain the changes you made here and link to any relevant issues.
Fixes # (issue)
Type of change
Delete options that are not relevant.
Checklist