Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

emissary-ingress 2.0.4 not creating envoy listeners

See original GitHub issue

Describe the bug On installing emissary-ingress through Helm chart(version 7.1.9), which installs emissary-ingress versioned 2.0.4, the listeners are not getting created on envoy.

To Reproduce Steps to reproduce the behavior:

Install emissary-ingress using Helm chart(version 7.1.9)
Using following Helm values override :

values:
  service:
    type: LoadBalancer
    externalTrafficPolicy: Cluster
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-type: nlb
      service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
  agent:
    enabled: false
  crds:
    enabled: true
    create: true
  createDefaultListeners: true

Expected behavior Two listeners on Envoys to be created.

Versions (please complete the following information):

Ambassador: [2.0.4]
Kubernetes environment [EKS]
Version [1.19]

Additional context The default listeners are getting created as CRD objects.

➜ kubectl get listeners.getambassador.io -A
NAMESPACE        NAME                              PORT   PROTOCOL   STACK   STATSPREFIX   SECURITY   L7DEPTH
ambassador     emissary-ingress-http-listener    8080   HTTP                             XFP
ambassador     emissary-ingress-https-listener   8443   HTTPS                            XFP

The generated Envoy config file.

➜ kubectl exec -it emissary-ingress-74cb74f84b-5h2kr -- cat envoy/envoy.json
{
  "@type": "/envoy.config.bootstrap.v3.Bootstrap",
  "layered_runtime": {
    "layers": [
      {
        "name": "static_layer",
        "static_layer": {
          "envoy.reloadable_features.enable_deprecated_v2_api": true,
          "re2.max_program_size.error_level": 200
        }
      }
    ]
  },
  "static_resources": {
    "clusters": [
      {
        "alt_stat_name": "127_0_0_1_8877",
        "connect_timeout": "3.000s",
        "dns_lookup_family": "V4_ONLY",
        "lb_policy": "ROUND_ROBIN",
        "load_assignment": {
          "cluster_name": "cluster_127_0_0_1_8877_infrastructure",
          "endpoints": [
            {
              "lb_endpoints": [
                {
                  "endpoint": {
                    "address": {
                      "socket_address": {
                        "address": "127.0.0.1",
                        "port_value": 8877,
                        "protocol": "TCP"
                      }
                    }
                  }
                }
              ]
            }
          ]
        },
        "name": "cluster_127_0_0_1_8877_infrastructure",
        "type": "STRICT_DNS"
      }
    ],
    "listeners": []
  }
}

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:11 (3 by maintainers)

Top GitHub Comments

1reaction

kflynncommented, Dec 1, 2021

@isaac88 That’s great news, thanks for posting!

0reactions

kflynncommented, Mar 4, 2022

Closing, since the issue ultimately was the AMBASSADOR_LABEL_SELECTOR rather than Emissary.

Top Results From Across the Web

Emissary-ingress Release Notes | Ambassador

When an AuthService is applied in v2.Y of Emissary-ingress, Envoy would skip the ext_authz call for non-tls http request and would perform the...

emissary-ingress 8.3.1 · helm/datawire - Artifact Hub

Parameter Description Default replicaCount Number of Ambassador replicas 3 test.image Image to use for the test Pod busybox ingressClassResource.enabled true

ambassador - Go Packages

Emissary -Ingress is an open-source Kubernetes-native API Gateway + Layer 7 load balancer + Kubernetes Ingress built on Envoy Proxy. Emissary-ingress is a ......

Path traversal in authorization context in Emissary

Emissary -ingress can authenticate incoming requests before routing them to a backing service. I can already tell you that Emissary is secure and ......

How do you Integrate Emissary Ingress with OPA - InfraCloud

Emissary Ingress was earlier known as Ambassador API gateway, ... server that implements the Envoy External Authorization API, thus making ...