Cloudflare Tunnel addon does not appear in the Addon UI after installation

[yukebrillianth]

Describe the bug

I followed the official instructions to install the Cloudflare Tunnel addon in Kubero. The deployment seems to have been applied correctly, but the addon is not showing up in the Addon section of the Kubero web UI.

To Reproduce

Steps to reproduce the behavior:

1. Installed Kubero on my microk8s Kubernetes cluster.
2. Followed the guide to deploy the Cloudflare Tunnel addon.
3. The pod runs successfully, and the tunnel works, but the addon does not appear in the Addon UI.

Expected behavior

The addon should appear in the Addon UI after it is deployed and detected by Kubero.

Environment

• Kubero version: latest
• Kubernetes version: using microk8s in ubuntu 24 fresh install
• Installation method: Manual deployment via kubectl apply

Additional context

• There are no apparent errors in the Kubero logs.
• The app is running fine, but I’d like it to be manageable via the UI.

Let me know if you need more logs or details. Thanks!

[mms-gianni]

Just to be sure: It is inactive like on my screenshot?

I can see the same behaviour. It cot detected but remains inactive.
Something might have changed in the Operator.

[yukebrillianth]

Just to be sure: It is inactive like on my screenshot?

I can see the same behaviour. It cot detected but remains inactive. Something might have changed in the Operator.

Yes, it's the same as your screenshot — the addon remains inactive and does not appear in the dashboard initially.

However, after I rebooted the node/server, the Cloudflare Tunnel addon finally appeared and became active in the Addon UI.

So it seems like a restart is required for it to be detected properly. Let me know if there's a way to avoid needing a reboot.

[mms-gianni]

This is in deed required, since the status is loaded during startup. And the operator pods need to be up and running. I really should state that somewhere.

Just found out, the installation instructions do not fit anymore. I will fix that with version 3.0.0

I will keep that bug open.