shareinto opened a new issue, #1374:
URL: https://github.com/apache/apisix-ingress-controller/issues/1374
```apiVersion: networking.k8s.io/v1
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
k8s.apisix.apache.org/svc-namespace: default
name: details
namespace: apisix
spec:
ingressClassName: apisix
rules:
- host: bar.com
http:
paths:
- backend:
service:
name: details
port:
number: 9080
path: /
pathType: Prefix
```
Like the example above, ingress is under the namespace apisix, and service
details is under the default namespace.
In actual production, we did encounter such a scenario, which is to use the
externalName type of Service that the nginx ingress controller can support. We
now want to migrate to apisix and use the old ingress api. There is a problem
with the externalName supported by the nginx ingress controller, that is, it
will resolve the service of another namespace into clusterIp, which will cause
the Layer 7 load balancing strategy to fail. So, it would be the best solution
to get the endpoint of another namespace.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
