< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />
🚀 KubeSphere v4.1.2 with Enhancements and Bug Fixes is available now. Read the release notes for v4.1.2 → close
  • English
    • English
    • 简体中文
    1. 1.Create a KubeSphere Cloud account and log in to the platform.
    2. 2.In the upper-right corner, click Console, and then click Lite Cluster on the left.
    3. 3.Create a K8s cluster with KubeSphere installed.
    4. 4.Access KubeSphere with the default account and password (admin/P@88w0rd).
  •  Star
  1. Docs / 
  2. Documentation / 
  3. Extension User Guide / 
  4. KubeSphere Gateway / 
  5. Cluster Gateway / 
  6. Appendix: Gateway Logs Not Showing Data in Member Clusters

Documentation

Last updated:
    Edit

    Appendix: Gateway Logs Not Showing Data in Member Clusters

    If the "Gateway Logs" tab in the "Cluster Gateway" details page of a member cluster does not display data, you can resolve the issue using the following methods.

    1. Enable the NodePort access mode for the whizard-telemetry-apiserver service on the host cluster.

      1. Under the application workloads menu on the host cluster, click Services to enter the services page.

      2. Search for the service whizard-telemetry-apiserver, click more > Edit External Access.

      3. In the Edit External Access dialog, select NodePort, and then click OK.

    2. Modify the configuration of the KubeSphere Gateway extension, set backend.config.gateway.logSearchEndpoint to the access address of the whizard-telemetry-apiserver service on the host cluster.

      backend:
  enabled: true
  config:
    gateway:
      namespace: kubesphere-controls-system
      valuesOverride:
        controller:
          image:
            registry: ""
            image: kubesphereio/nginx-ingress-controller
            tag: "v1.4.0"
            pullPolicy: IfNotPresent
            digest: ""
      exposeNodeLabelKey: "node-role.kubernetes.io/control-plane"
      versionConstraint: ">= 4.3.0, < 4.5.0"
      logSearchEndpoint: "http://whizard-telemetry-apiserver.extension-whizard-telemetry.svc:9090" # Replace it with http://<node-ip>:<whizard-telemetry-apiserver-nodeport>

    3. On the member cluster, restart the gateway gateway-agent-backend-apiserver.

      kubectl -n extension-gateway rollout restart deploy gateway-agent-backend-apiserver

    4. Refresh the Gateway Logs tab on the member cluster to see the gateway log data.

    Receive the latest news, articles and updates from KubeSphere


    Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

    Previous : Disable Cluster Gateway
    What’s on this Page