Hot to add kubernetes widget/service ?

[emoxam]

Description

That's all that i have
https://gethomepage.dev/latest/widgets/info/kubernetes/
what to do with it ? Add it to the widgets.yaml and then ? I get API error
and that's what i get at the log
error: <kubernetes-widget> Error getting ingresses: NaN undefined undefined

homepage version

v0.8.12 (12ec1cf, Apr 17, 2024)

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

error: <kubernetes-widget> Error getting ingresses: NaN undefined undefined

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

To address the API error you're encountering with the Kubernetes widget on your Homepage installation, let's go through a few troubleshooting steps based on the context provided:

1. Check the widgets.yaml Configuration: Ensure that the Kubernetes widget is correctly configured in your widgets.yaml file. The structure should match the example provided in the documentation. Here's an example configuration snippet for the Kubernetes widget:

   - kubernetes:
       cluster:
         show: true
         cpu: true
         memory: true
         showLabel: true
         label: "cluster"
       nodes:
         show: true
         cpu: true
         memory: true
         showLabel: true

   Make sure that the indentation is correct, as YAML is sensitive to indentation.

2. Verify URL Formatting: According to the troubleshooting guide, ensure that the URLs in your configuration do not end with a trailing slash or other API path, as this can result in an error.

3. Check Network Connectivity: Verify that the Homepage installation can connect to the Kubernetes API. You can do this by executing a ping from within the Docker container to the Kubernetes API endpoint.

4. Use curl to Test API Output: If you have confirmed network connectivity, you can test the API output directly using curl. This may need to be done from inside the container if your networking setup requires it. Remember to install curl with apk add curl if it's not already present in the container.

5. Review Container Logs: Check the container logs for more detailed error messages that could provide insight into the issue. You can view the logs with the command docker logs <container_name>.

6. Check for Updates: Ensure that you are running the latest version of Homepage, as updates may contain fixes for issues like the one you're experiencing.

7. Consult the Homepage AI Bot: If you're still having trouble, consider using the Homepage AI Bot for additional support. It can be accessed via the 'Ask AI' button on the documentation pages, GitHub discussions, or the Discord channel.

If you've gone through these steps and are still facing issues, please provide more detailed information about your configuration, container logs, and any browser logs if available. This will help in diagnosing the problem more effectively.

This comment was generated by Glime.

[EAnsy]

What URL or curl do you talk about?
That YAML doesn't include almost any values other than boolean or description.
The widget is unusable for now... some defaults, access rights needed or examples would be helpful.

[emoxam]

I can't remember what the problem it was, now all is good.

[StrikeZW]

Did you ever solved this? I do receive the same error. All manual steps to debug this perform well ....

[emoxam]

I can't remember what the problem it was, now all is good.
That's what is at my records..)
docker run -d -p 3000:3000 -v /home/emoxam/homepage/config/:/app/config -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/gethomepage/homepage:latest

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.