You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/01/29 07:47:45 UTC
[GitHub] [apisix-ingress-controller] tokers opened a new issue #217: bug: should use service port name as the last component of upstream name
tokers opened a new issue #217:
URL: https://github.com/apache/apisix-ingress-controller/issues/217
### Issue description
### Environment
* your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`);
* your Kubernetes cluster version (output of `kubectl version`);
* if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (`uname -a`).
### Minimal test code / Steps to reproduce the issue
1.
2.
3.
### What's the actual result? (including assertion message & call stack if applicable)
### What's the expected result?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #217: bug: should use service port name as the last component of upstream name
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #217:
URL: https://github.com/apache/apisix-ingress-controller/issues/217#issuecomment-773717441
Since service port name is optional when the service only exposes one port, so it's not feasible.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers closed issue #217: bug: should use service port name as the last component of upstream name
Posted by GitBox <gi...@apache.org>.
tokers closed issue #217:
URL: https://github.com/apache/apisix-ingress-controller/issues/217
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #217: bug: should use service port name as the last component of upstream name
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #217:
URL: https://github.com/apache/apisix-ingress-controller/issues/217#issuecomment-773717441
Since service port name is optional when the service only exposes one port, so it's not feasible.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers closed issue #217: bug: should use service port name as the last component of upstream name
Posted by GitBox <gi...@apache.org>.
tokers closed issue #217:
URL: https://github.com/apache/apisix-ingress-controller/issues/217
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org