[BUG] nebula/etcd cluster has no secret for connection

[JashBook]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. create cluster

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: nebula-jjuzhw
  namespace: default
spec:
  clusterDef: nebula
  topology: default
  terminationPolicy: WipeOut
  componentSpecs:
    - name: console
      serviceVersion: v3.5.0
      replicas: 2
      resources:
        requests:
          cpu: 100m
          memory: 0.5Gi
        limits:
          cpu: 100m
          memory: 0.5Gi
    - name: graphd
      serviceVersion: v3.5.0
      replicas: 1
      resources:
        requests:
          cpu: 100m
          memory: 0.5Gi
        limits:
          cpu: 100m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: logs
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
    - name: metad
      serviceVersion: v3.5.0
      replicas: 3
      resources:
        requests:
          cpu: 100m
          memory: 0.5Gi
        limits:
          cpu: 100m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
        - name: logs
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
    - name: storaged
      serviceVersion: v3.5.0
      replicas: 3
      resources:
        requests:
          cpu: 100m
          memory: 0.5Gi
        limits:
          cpu: 100m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
        - name: logs
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi

3. Click on '....'
4. Scroll down to '....'
5. See error

kubectl get secrets -l app.kubernetes.io/instance=nebula-jjuzhw    
No resources found in default namespace.


➜  ~ kubectl exec -it nebula-jjuzhw-console-0 --namespace default -- sh  
/ # env|grep USER
/ # env|grep PASS
/ # 

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[JashBook]

etcd cluster also has the same issue

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: etcdr-bszddm
  namespace: default
spec:
  terminationPolicy: WipeOut
  componentSpecs:
    - name: etcd
      componentDef: etcd-3-1.0.0-alpha.0
      tls: false
      replicas: 3
      resources:
        requests:
          cpu: 100m
          memory: 0.5Gi
        limits:
          cpu: 100m
          memory: 0.5Gi
      volumeClaimTemplates:
        - name: data
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi

see error

kubectl get secrets -l app.kubernetes.io/instance=etcdr-bszddm
No resources found in default namespace.

There is no svc that can be accessed externally

kubectl get svc -l app.kubernetes.io/instance=etcdr-bszddm
No resources found in default namespace.

[shanshanying]

not planned for greptimedb，weaviate , nebula and etcd.