You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "monlor (via GitHub)" <gi...@apache.org> on 2023/07/06 05:12:34 UTC

[GitHub] [apisix-ingress-controller] monlor opened a new issue, #1887: bug: Empty spec object after applying ApisixUpstream with external service

monlor opened a new issue, #1887:
URL: https://github.com/apache/apisix-ingress-controller/issues/1887

   ### Current Behavior
   
   I followed the steps outlined in the document [https://apisix.apache.org/en/docs/ingress-controller/tutorials/external-service/] to apply an ApisixUpstream containing an external service to my cluster. However, after applying it to the cluster, I noticed that the spec object is empty.
   <img width="1096" alt="image" src="https://github.com/apache/apisix/assets/20394007/233e2140-c09f-4354-bdef-ce58c71d838c">
   
   
   ### Expected Behavior
   
   _No response_
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   ```
   k apply -f - <<-EOF
   # httpbin-upstream.yaml
   apiVersion: apisix.apache.org/v2
   kind: ApisixUpstream
   metadata:
     name: httpbin-upstream
   spec:
     externalNodes:
     - type: Domain
       name: httpbin.org
   EOF
   ```
   
   ### Environment
   
   Deployment via apisix helm chart v2.0.0
   - APISIX version: v3.3.0
   - Operating system: docker v3.3.0-debain
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] monlor commented on issue #1887: bug: Empty spec object after applying ApisixUpstream with external service

Posted by "monlor (via GitHub)" <gi...@apache.org>.
monlor commented on issue #1887:
URL: https://github.com/apache/apisix-ingress-controller/issues/1887#issuecomment-1623053750

   Thank you, I found it was an issue with Kubesphere's display. The output from the kubectl command line was correct.Thank you, I found it was an issue with Kubesphere's display. The output from the kubectl command line was correct.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] Revolyssup commented on issue #1887: bug: Empty spec object after applying ApisixUpstream with external service

Posted by "Revolyssup (via GitHub)" <gi...@apache.org>.
Revolyssup commented on issue #1887:
URL: https://github.com/apache/apisix-ingress-controller/issues/1887#issuecomment-1623018781

   I see that the screenshot shows apiVersion as `v2beta3`. `externalNodes` is not supported on `v2beta3`. Please change the apiVersion to `*/v2` instead. Although in the command you pasted, you are using the correct apiVersion so I don't know how you have the wrong apiVersion in screenshot.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] monlor closed issue #1887: bug: Empty spec object after applying ApisixUpstream with external service

Posted by "monlor (via GitHub)" <gi...@apache.org>.
monlor closed issue #1887: bug: Empty spec object after applying ApisixUpstream with external service
URL: https://github.com/apache/apisix-ingress-controller/issues/1887


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org