[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-835002006 @tokers The above my errors are caused by not setting config.apisix.baseURL when installing apisix-ingress-controller by helm. Now I set the local url to reinstall apisix-ingress-controller. It’s all right now, thanks! -- 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: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-825364797 @tokers And why APISIX logs many upstream 404 request？ ``` 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/152e4f9e HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/606b3be0 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/76a75cec HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/76a75cec HTTP/1.1" 404 39 0.002 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/857c0d11 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/fcd5c4d6 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/5b9e2a1 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/10986d9 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/5b6fae7c HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; 10.233.99.187 - - [23/Apr/2021:03:31:13 +] apisix-admin:9180 "GET /apisix/admin/upstreams/7abcf232 HTTP/1.1" 404 39 0.001 "-" "Go-http-client/1.1" - - - "http://apisix-admin:9180; ``` -- 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: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-825362843
> @wjx8382 Have you ever seen how many routes are there in APISIX?
```
{"node":{"dir":true,"key":"\/apisix\/routes","nodes":{}},"action":"get","count":"1"}
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-825359611
@tokers I reinstalled APISIX again,and now logs this error
```
2021-04-23T11:12:25+08:00warncontroller/apisix_route.go:205 sync
ApisixRoute failed, will retry {"object":
{"Type":1,"Object":{"Key":"tools/httpserver-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null},
"error": "2 errors occurred:\n\t* Get
http://apisix-admin:9180/apisix/admin/routes: dial tcp: lookup apisix-admin on
169.254.25.10:53: no such host\n\t* Get
http://apisix-admin:9180/apisix/admin/routes: dial tcp: lookup apisix-admin on
169.254.25.10:53: no such host\n\n"}
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-823721227
> > > From the configuration snippet the `allow_admin` was rendered
correctly, so it should work, would you like to try the `0.5.0` version, it was
released few days ago.
> >
> >
> > After using the `0.5.0` version,apisix-ingress-controller logs
> > ```
> > 2021-04-20T15:26:34+08:00warncontroller/apisix_route.go:205
sync ApisixRoute failed, will retry {"object":
{"Type":1,"Object":{"Key":"tools/httpserver-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null},
"error": "2 errors occurred:\n\t* object missing primary index\n\t* object
missing primary index\n\n"}
> > ```
> >
> >
> > In addition, why `helm install apisix` will also generate
apisix-ingress-controller, but its version is `0.4.0`, `helm install
apisix-ingress-controller` will generate apisix-ingress-controller which
version is `0.5.0`, which should I use?
>
> The error `object missing primary index` occurred basically due to you
wrote some route on apisix-dashboard. It's **NOT** a recommended way.
>
> > In addition, why helm install apisix will also generate
apisix-ingress-controller, but its version is 0.4.0, helm install
apisix-ingress-controller will generate apisix-ingress-controller which version
is 0.5.0, which should I use?
>
> We recommend you to use the `0.5.0` release.
I did not write anything on apisix-dashboard.After I installed APISIX and
apisix-ingress-controller,i just running `kubectl apply -f httpbin-route.yaml
-n tools`
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-823055957
> From the configuration snippet the `allow_admin` was rendered correctly,
so it should work, would you like to try the `0.5.0` version, it was released
few days ago.
After using the `0.5.0` version,apisix-ingress-controller logs
```
2021-04-20T15:26:34+08:00warncontroller/apisix_route.go:205 sync
ApisixRoute failed, will retry {"object":
{"Type":1,"Object":{"Key":"tools/httpserver-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null},
"error": "2 errors occurred:\n\t* object missing primary index\n\t* object
missing primary index\n\n"}
```
In addition, why `helm install apisix` will also generate
apisix-ingress-controller, but its version is `0.4.0`, `helm install
apisix-ingress-controller` will generate apisix-ingress-controller which
version is `0.5.0`, which should I use?
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-822263319 > @wjx8382 Could you please paste the `config-default.yaml` and `config.yaml` in the APISIX pod? ``` kind: ConfigMap apiVersion: v1 metadata: name: apisix namespace: tools labels: app.kubernetes.io/managed-by: Helm annotations: meta.helm.sh/release-name: apisix meta.helm.sh/release-namespace: tools data: config.yaml: >- # # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # apisix: node_listen: 9080 # APISIX listening port enable_heartbeat: true enable_admin: true enable_admin_cors: true enable_debug: false enable_dev_mode: false # Sets nginx worker_processes to 1 if set to true enable_reuseport: true # Enable nginx SO_REUSEPORT switch if set to true. enable_ipv6: true config_center: etcd # etcd: use etcd to store the config value # yaml: fetch the config value from local yaml file `/your_path/conf/apisix.yaml` #proxy_protocol: # Proxy Protocol configuration # listen_http_port: 9181# The port with proxy protocol for http, it differs from node_listen and port_admin. # This port can only receive http request with proxy protocol, but node_listen & port_admin # can only receive http request. If you enable proxy protocol, you must use this port to # receive http request with proxy protocol # listen_https_port: 9182 # The port with proxy protocol for https # enable_tcp_pp: true # Enable the proxy protocol for tcp proxy, it works for stream_proxy.tcp option # enable_tcp_pp_to_upstream: true # Enables the proxy protocol to the upstream server proxy_cache: # Proxy Caching configuration cache_ttl: 10s # The default caching time if the upstream does not specify the cache time zones: # The parameters of a cache - name: disk_cache_one # The name of the cache, administrator can be specify # which cache to use by name in the admin api memory_size: 50m # The size of shared memory, it's used to store the cache index disk_size: 1G# The size of disk, it's used to store the cache data disk_path: "/tmp/disk_cache_one" # The path to store the cache data cache_levels: "1:2" # The hierarchy levels of a cache # - name: disk_cache_two #memory_size: 50m #disk_size: 1G #disk_path: "/tmp/disk_cache_two" #cache_levels: "1:2" allow_admin: # http://nginx.org/en/docs/http/ngx_http_access_module.html#allow - 127.0.0.1/24 - 172.16.110.186 - 10.233.99.249 # - "::/64" port_admin: 9180 # Default token when use API to call for Admin API. # *NOTE*: Highly recommended to modify this value to protect APISIX's Admin API. # Disabling this configuration item means that the Admin API does not # require any authentication. admin_key: # admin: can everything for configuration data - name: "admin" key: edd1c9f034335f136f87ad84b625c8f1 role: admin # viewer: only can view configuration data - name: "viewer" key: 4054f7cf07e344346cd3f287985e76a2 role: viewer router: http: 'radixtree_uri' # radixtree_uri: match route by uri(base on radixtree) # radixtree_host_uri: match route by
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-821036181
> > @tokers After I tweak the `allow.ipList` in
`apisix-helm-chart/charts/apisix/values.yaml`,there are still errors.
> > ```
> > allow:
> > # The ip range for allowing access to Apache APISIX
> > ipList:
> > - 127.0.0.1/24
> > - 172.16.110.186
> > - 10.233.99.249
> > ```
> >
> >
> > apisix-ingress-controller logs
> > ```
> > 2021-04-16T14:31:58+08:00warnapisix/upstream.go:113
upstream not found{"fullname": "tools_httpbin-85d57ddd75-wtmwh_80", "url":
"http://apisix-admin:9180/apisix/admin/upstreams/5e521191;, "cluster": ""}
> > 2021-04-16T14:31:58+08:00error state/builder.go:191failed
to create upstream tools_httpbin-85d57ddd75-wtmwh_80: unexpected status code
403; error message:
> > 403 Forbidden
> >
> > 403 Forbidden
> > openresty
> >
> >
> > ```
> >
> >
> > APISIX logs
> > ```
> > 10.233.99.249 - - [16/Apr/2021:06:31:45 +] apisix-admin:9180 "GET
/apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.000 "-"
"Go-http-client/1.1" - - - "http://apisix-admin:9180;
> > 10.233.99.249 - - [16/Apr/2021:06:31:58 +] apisix-admin:9180 "GET
/apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.002 "-"
"Go-http-client/1.1" - - - "http://apisix-admin:9180;
> > ```
>
> Are you sure the IP of apisix-ingress-controller is configured correctly?
I see that the IP in the APISIX log is the IP that I configured，and the
error before and after configuration is different.
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-820950898
@tokers After I tweak the ```allow.ipList``` in
```apisix-helm-chart/charts/apisix/values.yaml```,there are still errors.
```
allow:
# The ip range for allowing access to Apache APISIX
ipList:
- 127.0.0.1/24
- 172.16.110.186
- 10.233.99.249
```
apisix-ingress-controller logs
```
2021-04-16T14:31:58+08:00warnapisix/upstream.go:113 upstream not
found{"fullname": "tools_httpbin-85d57ddd75-wtmwh_80", "url":
"http://apisix-admin:9180/apisix/admin/upstreams/5e521191;, "cluster": ""}
2021-04-16T14:31:58+08:00error state/builder.go:191failed to
create upstream tools_httpbin-85d57ddd75-wtmwh_80: unexpected status code 403;
error message:
403 Forbidden
403 Forbidden
openresty
```
APISIX logs
```
10.233.99.249 - - [16/Apr/2021:06:31:45 +] apisix-admin:9180 "GET
/apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.000 "-"
"Go-http-client/1.1" - - - "http://apisix-admin:9180;
10.233.99.249 - - [16/Apr/2021:06:31:58 +] apisix-admin:9180 "GET
/apisix/admin/upstreams/5e521191 HTTP/1.1" 404 39 0.002 "-"
"Go-http-client/1.1" - - - "http://apisix-admin:9180;
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-819337168
> @wjx8382 Your APISIX Admin API doesn't allow apisix-ingress-controller to
access it. Please tweak the `allow.ipList` option,
https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/values.yaml#L124.
Now logs
```
2021-04-14T16:22:38+08:00warnapisix/upstream.go:113 upstream not
found {"fullname": "tools_httpbin-85d57ddd75-wtmwh_80", "url":
"http://apisix-admin:9180/apisix/admin/upstreams/5e521191;, "cluster": ""}
2021-04-14T16:22:38+08:00error state/builder.go:191failed to
create upstream tools_httpbin-85d57ddd75-wtmwh_80: unexpected status code 403;
error message:
403 Forbidden
403 Forbidden
openresty
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-819198021
> Maybe there are some internal bugs, could you paste the error log of
apisix-ingress-controller.
>
> Just paste the result of `kubectl logs -f {apisix-ingress-controller pod
name}`.
```
2021-04-14T11:00:29+08:00error apisix/upstream.go:119 failed to get
upstream from APISIX {"fullname": "tools_httpbin-85d57ddd75-wtmwh_80",
"url": "http://apisix-admin:9180/apisix/admin/upstreams/5e521191;, "cluster":
"", "error": "unexpected status code 403; error message:
\r\n403
Forbidden\r\n\r\n403
Forbidden\r\nopenresty\r\n\r\n\r\n",
"errorCauses": [{"error": "unexpected status code 403"}, {"error": "error
message: \r\n403
Forbidden\r\n\r\n403
Forbidden\r\nopenresty\r\n\r\n\r\n"}]}
2021-04-14T11:00:29+08:00error state/builder.go:174failed to find
upstream tools_httpbin-85d57ddd75-wtmwh_80: unexpected status code 403; error
message:
403 Forbidden
403 Forbidden
openresty
2021-04-14T11:00:29+08:00infocontroller/apisix_route.go:193 sync
ApisixRoute failed, will retry {"object":
{"Type":1,"Object":{"Key":"tools/httpserver-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2alpha1"},"Tombstone":null}}
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-819170124
> Maybe there are some internal bugs, could you paste the error log of
apisix-ingress-controller.
>
> Just paste the result of `kubectl logs -f {apisix-ingress-controller pod
name}`.
No error log,only
```[GIN] 2021/04/14 - 10:06:19 | 200 | 56.195µs | 172.16.110.186 | GET
"/healthz"```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818479508
> I found these routes were created by apisix-dashboard, just do not mix the
use of apisix-ingress-controller and manual configurations from
apisix-dashboard.
>
> Also, the route you pasted doesn't contain the one in the YAML
configuration:
>
> ```yaml
> # httpbin-route.yaml
> apiVersion: apisix.apache.org/v2alpha1
> kind: ApisixRoute
> metadata:
> name: httpserver-route
> spec:
> http:
> - name: rule1
> match:
> hosts:
> - local.httpbin.org
> paths:
> - /*
> backend:
> serviceName: httpbin-85d57ddd75-wtmwh
> servicePort: 80
> ```
I deleted those routes created by apisix-dashboard,then running`kubectl
apply -f httpbin-route.yaml -n tools`,routes still doesn't contain this route.
```{"node":{"key":"\/apisix\/routes","nodes":{},"dir":true},"action":"get","count":"1"}```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818391921
> > @tokers Why does `kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 --
curl http://127.0.0.1:9080/headers -H 'Host: local.httpbin.org'` returns
`{"error_msg":"404 Route Not Found"}`
> > ```
> > # httpbin-route.yaml
> > apiVersion: apisix.apache.org/v2alpha1
> > kind: ApisixRoute
> > metadata:
> > name: httpserver-route
> > spec:
> > http:
> > - name: rule1
> > match:
> > hosts:
> > - local.httpbin.org
> > paths:
> > - /*
> > backend:
> > serviceName: httpbin-85d57ddd75-wtmwh
> > servicePort: 80
> > ```
>
> Could you access the apisix admin API by
>
> ```
> kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 -- curl
http://127.0.0.1:9180/apisix/admin/routes
> ```
>
> To see the routes?
`kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 -- curl
http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key:
edd1c9f034335f136f87ad84b625c8f1'` returns
```
{"node":{"key":"\/apisix\/routes","nodes":[{"value":{"update_time":1615967207,"uris":["\/hello"],"id":"1","status":1,"create_time":1615797004,"name":"hello","upstream_id":"346344795876098996","plugins":{"fault-injection":{"disable":true,"delay":{"duration":3}},"proxy-rewrite":{"disable":false,"scheme":"https","regex_uri":["^\/samplePrefix\/get(.*)","\/hello$1"]}},"vars":{}},"key":"\/apisix\/routes\/1","modifiedIndex":1902,"createdIndex":39},{"value":{"priority":0,"uri":"\/grpctest","methods":["GET"],"status":1,"create_time":1615878242,"update_time":1615878242,"upstream":{"pass_host":"pass","nodes":{"127.0.0.1:50051":1},"hash_on":"vars","type":"roundrobin"},"plugins":{"grpc-transcode":{"deadline":0,"service":"helloworld.Greeter","proto_id":"1","method":"SayHello"}},"id":"111"},"key":"\/apisix\/routes\/111","modifiedIndex":1350,"createdIndex":1350},{"value":{"update_time":1618212271,"uris":["\/httpbin"],"id":"350111307409654788","methods":["GET","HEAD","POST","PUT","DELETE","OPTIONS
","PATCH"],"status":1,"hosts":["local.httpbin.org"],"create_time":1618212201,"name":"httpbin","upstream_id":"350111087426798596","vars":{}},"key":"\/apisix\/routes\/350111307409654788","modifiedIndex":18185,"createdIndex":18182},{"value":{"update_time":1618210980,"uris":["\/get"],"id":"5","status":1,"create_time":1615789201,"name":"test","upstream_id":"50","plugins":{"http-logger":{"uri":"http:\/\/127.0.0.1:80\/postendpoint?param=1","disable":false},"limit-conn":{"rejected_code":503,"conn":1,"burst":0,"disable":true,"key":"remote_addr","default_conn_delay":0.1},"basic-auth":{"disable":true},"fault-injection":{"disable":true,"abort":{"http_status":403,"body":"Fault
Injection!\n","vars":[[["arg_name","==","jack"]]]}},"proxy-rewrite":{"scheme":"https","disable":false},"authz-keycloak":{"token_endpoint":"http:\/\/127.0.0.1:8090\/auth\/realms\/{client_id}\/protocol\/openid-connect\/token","disable":true,"audience":"Client
ID","permissions":["resource name#scope name"]},"ip-restriction":{
"whitelist":["172.16.110.186","127.0.0.1"],"disable":false},"serverless-pre-function":{"phase":"rewrite","functions":["return
function() ngx.log(ngx.ERR, \"serverless pre function\");
end"],"disable":false},"limit-count":{"rejected_code":503,"key":"remote_addr","count":2,"disable":true,"time_window":60},"batch-requests":{"disable":false},"cors":{"disable":false},"uri-blocker":{"block_rules":["get"],"disable":true},"key-auth":{"disable":true},"serverless-post-function":{"phase":"rewrite","functions":["return
function() ngx.log(ngx.ERR, \"serverless post function\");
end"],"disable":false},"request-id":{"include_in_response":true,"disable":false},"prometheus":{"disable":false},"limit-req":{"rate":1,"key":"remote_addr","burst":2,"disable":true,"rejected_code":503},"request-validation":{"disable":true,"body_schema":{"required":["required_payload"],"type":"object","properties":{"required_payload":{"type":"string"},"boolean_payload":{"type":"boolean","jwt-auth":{"disable":true}},"vars
":{}},"key":"\/apisix\/routes\/5","modifiedIndex":18159,"createdIndex":16}],"dir":true},"action":"get","count":"5"}
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818384772
> > @tokers Why does `kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 --
curl http://127.0.0.1:9080/headers -H 'Host: local.httpbin.org'` returns
`{"error_msg":"404 Route Not Found"}`
> > ```
> > # httpbin-route.yaml
> > apiVersion: apisix.apache.org/v2alpha1
> > kind: ApisixRoute
> > metadata:
> > name: httpserver-route
> > spec:
> > http:
> > - name: rule1
> > match:
> > hosts:
> > - local.httpbin.org
> > paths:
> > - /*
> > backend:
> > serviceName: httpbin-85d57ddd75-wtmwh
> > servicePort: 80
> > ```
>
> Could you access the apisix admin API by
>
> ```
> kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 -- curl
http://127.0.0.1:9180/apisix/admin/routes
> ```
>
> To see the routes?
It returns
```
401 Authorization Required
401 Authorization Required
openresty
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356:
URL:
https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-818383007
@tokers Why does `kubectl exec -it -n tools apisix-7987b5b7f-tmrk7 -- curl
http://127.0.0.1:9080/headers -H 'Host: local.httpbin.org'` returns
`{"error_msg":"404 Route Not Found"}`
```
# httpbin-route.yaml
apiVersion: apisix.apache.org/v2alpha1
kind: ApisixRoute
metadata:
name: httpserver-route
spec:
http:
- name: rule1
match:
hosts:
- local.httpbin.org
paths:
- /*
backend:
serviceName: httpbin-85d57ddd75-wtmwh
servicePort: 80
```
--
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:
us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-817562226 I have installed APISIX, how can I access httpbin through apisix > > > apisix-ingress-controller itself is not the proxy component but the controller to control the proxy plane (APISIX), you should access APISIX instead. By the way, did you install APISIX? > > > > > > Our service is client-->nginx-->ingress-nginx-->service-->pod. I want to replace ingress-nginx with apisix. Should I use APISIX instead of apisix-ingress-controller? (I have installed APISIX:2.3-alpine) > > No, you need both the apisix-ingress-controller and APISIX. Just as I said above, apisix-ingress-controller is the control plane and APISIX is the data plane that processes the traffic. Even in ingress-nginx, there are two components, the one is nginx (DP) and the other is the controller (CP). I have installed APISIX, how can I access httpbin through apisix? -- 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: us...@infra.apache.org
[GitHub] [apisix-ingress-controller] wjx8382 commented on issue #356: request help: KubeSphere setup
wjx8382 commented on issue #356: URL: https://github.com/apache/apisix-ingress-controller/issues/356#issuecomment-817440406 > apisix-ingress-controller itself is not the proxy component but the controller to control the proxy plane (APISIX), you should access APISIX instead. By the way, did you install APISIX? Our service is client-->nginx-->ingress-nginx-->service-->pod. I want to replace ingress-nginx with apisix. Should I use APISIX instead of apisix-ingress-controller? (I have installed APISIX:2.3-alpine) -- 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: us...@infra.apache.org
