request help: To understand why the admin api might be creating the username as namespace_consumername

[taherbohri]

Issue description

consumer -

apiVersion: apisix.apache.org/v2
kind: ApisixConsumer
metadata:
  name: apisixtestcon
  namespace: apisix-ns
spec:
  ingressClassName: "apisix"
  authParameter:
        keyAuth:
          value:
            key: *****

consumer inside the admin api calll -

{
            "username": "apisix-ns_apisixtestcon",
            "modifiedIndex": 1763266140636,
            "plugins": {
                "key-auth": {}

When ever a new consumer is added the username gets created inside the apisix admin as namespace_consumername, due to this when ever we are trying to whitelist any consumer in the route we have to add the whitelisted consumer name as namespace_consumername , we just want the consumer name which we are creating should be taken as username instead of what is being created , please let me know if any changes I can do to achieve the above .

Environment

Environment

APISIX version: 3.13.0
APISIX Ingress Controller: 2.0.0-rc5
Deployment mode: Standalone (apisix-standalone provider)
Gateway API: v1
Platform: Kubernetes

[AlinsRan]

ApisixConsumer is a namespace level resource that appears in different namespaces with the same name.

[taherbohri]

Ok thanks for looking into this , is there any way to avoid the namespace addition in the consumer name ?

[AlinsRan]

There is currently no way to avoid it. Unless we redesign the way the username of ApisixConsumer is generated.

[taherbohri]

Thanks for the update.