Make `emissary-ingress-apiext` optional
See original GitHub issuePlease describe your use case / problem.
I want to install Emissary-ingress without being forced to use emissary-ingress-apiext
.
Describe the solution you’d like
There is a way to install Emissary-ingress with getambassador.io/v3alpha1
CRDs only.
Additional context
I am installing Emissary-ingress on a cluster that do not have any getambassador.io/v2
custom resources, so I don’t need support for migrating between versions.
Issue Analytics
- State:
- Created a year ago
- Reactions:32
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Getting Started with Emissary-ingress
Learn how to install Emissary-ingress with either Helm or kubectl to get started routing traffic from the edge of your Kubernetes cluster to ......
Read more >Step-by-Step Solution Install with Kubernetes - SoFy Docs
The below commands install Emissary-ingress CRDs in the emissary-system namespace; Commands to install ... Create a namespace for your solution (optional).
Read more >Microservices Authentication Using Ambassador API Gateway ...
The Ambassador Edge Stack makes securing microservices easy with ... plane (API Server) is trying to call emissary-apiext.emissary-system.svc:443 but the ...
Read more >Creating an API Gateway using Emissary-Ingress and Linkerd ...
The goal of our project was to create a lightweight API Gateway to route requests from clients to various services.
Read more >datawire/ambassador - Gitter
Hi All, Can anyone suggest me , How can I use envoy as ingress in kubernetes. ... @neverfox Right, just wanted to make...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah +1 to this request. I experienced a similar issue to what Alan01252 is describing above. This did help (https://stackoverflow.com/a/70608787/18679153) but I shouldn’t have to manually change my Firewall rules to permit apiext to run. I’d rather not have the main source for all production traffic to be reliant on a service that might not actually be needed in my particular use case.
I do think it’s a fantastic addition, especially with assisting those moving from Version X to Version Y, but I think it’d be a better place to have it as an optional deployment that can be enabled / disabled in the values file (as opposed to installing it via the https://app.getambassador.io/yaml/emissary/2.2.2/emissary-crds.yaml file).
I also had this issue @caddymofo. I fixed it by removing v1 versions from the CRDs https://github.com/emissary-ingress/emissary/blob/327dca4f771c0ec80b263768a12a4098e6944382/manifests/emissary/emissary-crds.yaml.in#L295-L302
This is also something I don’t get, what’s the point of keeping the v1 versions there?