pioneer-hash commented on issue #403:
URL:
https://github.com/apache/apisix-ingress-controller/issues/403#issuecomment-825353590
> As per the error log, your ApisixUpstream object was created in the
**default** namespace, while the `web2` service is in `gray-ns` namespace.
>
> > 2021-04-23T10:33:14+08:00 warn controller/apisix_upstream.go:182 sync
ApisixUpstream failed, will retry {"object":
{"Type":3,"Object":"default/web2","Tombstone":{"metadata":{"name":"web2","namespace":"**default**","selfLink":"/apis/apisix.apache.org/v1/namespaces/default/apisixupstreams/web2","uid":"e1fd33bf-5b04-4460-b9b6-dfb2db6183b3","resourceVersion":"38021690","generation":1,"creationTimestamp":"2021-04-23T02:31:51Z","annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{"apiVersion":"apisix.apache.org/v1","kind":"ApisixUpstream","metadata":{"annotations":{},"name":"web2","namespace":"default"},"spec":{"loadbalancer":{"hashOn":"header","key":"user-agent","type":"chash"}}}\n"}},"spec":{"loadbalancer":{"type":"chash","hashOn":"header","key":"user-agent"}}}},
"error": "service "web2" not found"}
But my configuration specifies that the namespace is gray-ns.
```
[root@host-172-21-9-35 ~]# kubectl get au -n gray-ns
NAME AGE
web2 30m
[root@host-172-21-9-35 ~]# kubectl describe au web2 -n gray-ns
Name: web2
Namespace: gray-ns
Labels: <none>
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"apisix.apache.org/v1","kind":"ApisixUpstream","metadata":{"annotations":{},"name":"web2","namespace":"gray-ns"},"spec":{"lo...
API Version: apisix.apache.org/v1
Kind: ApisixUpstream
Metadata:
Creation Timestamp: 2021-04-23T02:35:11Z
Generation: 1
Resource Version: 38022730
Self Link:
/apis/apisix.apache.org/v1/namespaces/gray-ns/apisixupstreams/web2
UID: 39436281-c440-42a3-b87d-26e7362268a1
Spec:
Loadbalancer:
Hash On: header
Key: user-agent
Type: chash
Events: <none>
```
--
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:
[email protected]
