SommoKubeSommoKube · Support
Need a hand?
For questions, technical problems or privacy requests, contact Michele Tagliabue, the developer of SommoKube, directly.
The button opens your email app. Nothing is sent until you send the message. If no email app is configured, copy the address above.
What to include
Include your device model, iOS / iPadOS or macOS version, SommoKube version, the feature involved and steps to reproduce the issue. Share a sanitized error message or a screenshot with fictional data if helpful.
Do not send kubeconfigs, access or refresh tokens, passwords, private keys, client identities, confidential cluster names, logs or shell output. Redact screenshots before sharing them.
Quick answers
Why can’t I reach my cluster?
Check your VPN, DNS and network access first. The endpoint must use HTTPS with a valid certificate for its hostname. Private-root endpoints may require an exact-host policy in the app build; importing or syncing a new context does not create that policy. Never work around the problem by disabling certificate checks.
What is the difference between 401 and 403?
401 indicates a rejected or expired authentication credential: sign in again when requested. 403 usually means the authenticated identity lacks permission for the operation. Ask your cluster administrator for the appropriate access; SommoKube does not bypass RBAC.
Why are CPU, memory or replicas unavailable?
Resource metrics require a working metrics API and permission to read it. Replica counts require access to supported workload owners. Unavailable data is shown as unavailable rather than a fabricated zero. Charts collect session samples while the pod detail is open; fresh values also depend on the server’s sampling interval.
Do logs, Watch or monitoring continue in the background?
No. Log Follow, pod Watch, shell sessions and metrics polling stop when the app becomes inactive or their view closes. Visible pod metrics can resume when you return. Live Activity and the Mac monitor show paused or stale data while inactive; there is no SommoKube push backend.
What does configuration sync share?
It is on by default and can be paused in Settings. Selected context names, API endpoints, public CA/trust settings and authentication configuration can sync through iCloud Keychain, including a configured basic-auth username and Microsoft tenant/client/server identifiers. Credentials, namespace favorites and usage stay local. Use the same Apple Account with iCloud Keychain enabled, and sign in separately on each device.
How do I remove a connection?
Open connection details and confirm Forget. This removes its local credentials and preferences and records a configuration deletion for syncing devices when sync resumes. Delivery can take time. Pausing sync does not delete existing records, and Forget does not revoke Microsoft sessions or other credentials on the server.
What should I know before Restart or Exec?
Only act on resources you are authorized to manage. Restart changes a supported workload’s pod template and requires confirmation; an unknown outcome must be checked before trying again. Exec opens the confirmed container’s shell and requires v5 WebSocket support. Disconnecting may leave remote child processes running.