question-mark
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 can't find tlsSecret for Ingress resource

See original GitHub issue

Describe the bug Hello, when I’m trying to create Ingress resource with TLS enables using the manifest below:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: kubia-ambassador-ingress
  annotations:
    kubernetes.io/ingress.class: ambassador
spec:
  tls:
  - hosts:
      - host.example.com
    secretName: example-tls-secret
  rules:
  - host: host.example.com
    http:
      paths:
      - path: /kubia
        pathType: Prefix
        backend:
          service:
            name: kubia-service
            port:
              number: 80

I’m getting the following error:

2021-12-02 16:50:31 diagd 2.0.5 [P21TAEW] ERROR: Secret example-tls-secret.default unknown
2021-12-02 16:50:31 diagd 2.0.5 [P21TAEW] ERROR: Host kubia-ambassador-ingress-0-0: invalid TLS secret example-tls-secret, marking inactive

At the same time if I will use native emissary resources then all is Ok with the same secret:

apiVersion: getambassador.io/v3alpha1
kind: Host
metadata:
  name: minimal-host
spec:
  tlsSecret:
    name: example-tls-secret
  hostname: host.example.com
  mappingSelector:
    matchLabels:
      examplehost: host
  requestPolicy:
    insecure:
      action: Route
---
apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  name: quote-backend
spec:
  hostname: "*"
  prefix: /backend/
  service: kubia-service:80

Also I’ve tried to obtain TLS certificate automatically using cert-manager and in such case I’m getting the absolutely same error.

I have a bunch of my test resources in namespace default and emissary-ingress in a separate one. Do I miss something or may this be a bug? Can you please help to understand.

To Reproduce Steps to reproduce the behavior: Deploy Ingress resource with TLS secret presented.

Expected behavior Ingress resource works absolutely the same way as Host + Mapping resources.

Versions (please complete the following information):

  • Ambassador: 2.0.5
  • Azure Kubernetes Service
  • Version v1.19.11
  • Helm Chart version emissary-ingress-7.1.10

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

4reactions
cindymullins-dwcommented, Apr 23, 2022

Closing to prioritize issues without available workarounds.

1reaction
AliceProxycommented, Oct 10, 2022

Let’s not just close issues because they have a workaround. Closing means we’re not going to do anything about the issue. Not the same as de-prioritizing it over other items.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Emissary loading a secret in a separate namespace doesn' ...
I saw docs said The Host and the TLSContext must name the same Kubernetes Secret; if not, Emissary-ingress will disable TLS for the...
Read more >
Configuring Emissary-ingress Communications
TLS can appear intractable if you haven't set up certificates correctly. If you're having trouble with TLS, always check the logs of your...
Read more >
TLS/HTTPS - NGINX Ingress Controller - Kubernetes
Anytime we reference a TLS secret, we mean a PEM-encoded X.509, RSA (2048) secret. Warning. Ensure that the certificate order is leaf->intermediate->root, ...
Read more >
Ingress Configuration - Declarative GitOps CD for Kubernetes
The API server should be run with TLS disabled. Edit the argocd-server deployment to add the --insecure flag to the argocd-server command, or...
Read more >
Creating an API Gateway using Emissary-Ingress and ...
Once created, these can be placed in our Host and TLSContext resources. tls-context.yaml. Note: for our project, we've decided to configure ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found