[probonopd]

Repository: https://github.com/Shman4ik/kubeNimbus

A fast, open-source Kubernetes desktop client (.NET + Avalonia, NativeAOT)

• Stars: 5
• Release with the AppImage: v0.6.0 (2026-10-04T20:28:44Z)
• AppImage asset: kubeNimbus-0.6.0-linux-x64.AppImage
• License: MIT

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

[github-actions]

❌ Test failure

@Shman4ik: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Tested:

• kubeNimbus-0.6.0-linux-x64.AppImage from release v0.6.0

Compatibility: not self-contained: uses the C library of the system; references glibc 2.38

Names:

WARNING: AppImage name 'kubeNimbus-0.6.0-linux-x64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')

• The AppImage was built on a system that is too new. Please build it on the oldest still-supported Ubuntu LTS release so that it runs on all supported systems.
• The application quit or crashed right after starting. The error below usually shows why.
• Please check the remarks about the names below.

First error in the log:

/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/AppRun)

The application showed no window, but may be a system tray application (usr/bin/kubeNimbus: StatusNotifierItem); running it again with a system tray
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/AppRun)
No icon appeared in the system tray either
ERROR: The application exited within 11 seconds instead of showing a window

What next: once the AppImage is fixed (e.g. in a new release), comment /retest here to test it again. If it should not be in the catalog after all, close this pull request; an app that is already in the catalog can be removed by a maintainer with /remove.

Commit 0499350. Full log

[Shman4ik]

/retest

[github-actions]

✅ Test passed

Please check that the screenshot shows the application's main window.

kubeNimbus

Tested:

• kubeNimbus-0.8.0-x86_64.AppImage from release v0.8.0

Compatibility: not self-contained: uses the C library of the system; references glibc 2.34

Commit 0499350. Full log

[Shman4ik]

Confirmed: that screenshot is kubeNimbus's main window. The command bar (Applications / Resources / Open a cluster), the search field and the status bar are the real UI.

It shows "No kubeconfig contexts found" because the test runner has no kubeconfig, which is the expected first-run screen; the "Explore demo cluster" button opens the sample workload set that ships with the app.

Thanks for the re-test. 0.8.0 builds on Ubuntu 22.04 and names the AppImage -x86_64 / -aarch64 with update information and a published .zsync, which is what the first run asked for.

[probonopd]

/appstream

[github-actions]

How to add AppStream metadata (and your own screenshots)

The catalog page of an application can show a description, a summary, links and, above all, screenshots of your choice. They come from an AppStream metainfo file inside the AppImage.

1. Write the file. Save it as usr/share/metainfo/<id>.metainfo.xml inside the AppDir (the directory the AppImage is made from), where <id> is the <id> of the file, e.g. io.github.yourname.YourApp:

<?xml version="1.0" encoding="UTF-8"?>
<component type="desktop-application">
  <id>io.github.yourname.YourApp</id>
  <name>YourApp</name>
  <summary>One line saying what it does</summary>
  <metadata_license>CC0-1.0</metadata_license>
  <project_license>MIT</project_license>
  <description>
    <p>A few sentences about the application.</p>
  </description>
  <launchable type="desktop-id">yourapp.desktop</launchable>
  <url type="homepage">https://github.com/yourname/YourApp</url>
  <screenshots>
    <screenshot type="default">
      <caption>The main window</caption>
      <image>https://raw.githubusercontent.com/yourname/YourApp/main/screenshots/main.png</image>
    </screenshot>
  </screenshots>
  <releases>
    <release version="1.0.0" date="2024-01-31"/>
  </releases>
</component>

• <launchable> names the .desktop file of the AppImage.
• The screenshot is a web address (https://…) of a PNG image that stays there, e.g. a file in your repository. The file itself does not go into the AppImage.
• <project_license> is the license of the application, as an SPDX identifier.

2. Check it: appstreamcli validate --no-net usr/share/metainfo/<id>.metainfo.xml (from the appstream package of your distribution).

3. Put it into the AppImage.

• appimagetool, linuxdeploy, and other tools that build from an AppDir: copy the file to AppDir/usr/share/metainfo/ before building. appimagetool checks it while building.
• electron-builder: add it to the AppImage with extraFiles, e.g. in package.json: "linux": { "extraFiles": [ { "from": "build/<id>.metainfo.xml", "to": "usr/share/metainfo/<id>.metainfo.xml" } ] }.
• Other tools: see https://docs.appimage.org/packaging-guide/optional/appstream.html

4. Publish a new release with the new AppImage, then comment /retest on the pull request.

Note about screenshots: the automated test still runs the application and takes a screenshot of its own. The test needs it to check that the application starts and shows a window, so the test has to pass as before. But if the AppStream metadata names a screenshot, the catalog page shows that screenshot (the one marked type="default", else the first) instead of the automated one.

[Shman4ik]

Thank you for merging this. https://appimage.github.io/kubeNimbus/ still returns 404, and as far as I can tell the entry is not the cause: apps/kubeNimbus.md and database/kubeNimbus/ are on master. The site looks like it was last built on 17 October (Build website runs only when started by hand), so apps merged since then, Wevir, Wirely and md-editor among them, are 404 too. Could someone run Build website when it suits?

[probonopd]

Yes, the website gets rebuilt from time to time.