Obsyk Operator
Kubernetes operator that connects your cluster to the Obsyk observability platform
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
27/100 Low
- Maintained
- 45last commit 281 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 0
- Open issues
- 11
- Last commit
- 2026-02-13
- Latest release
- v0.3.7
- License
- Apache-2.0
- Activity
- stale
Checked 15 days ago - source: GitHub (Obsyk/obsyk-operator)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install Install the obsyk-operator Helm chart from Artifact Hub, then configure it to stream cluster metadata to Obsyk. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why might Obsyk not show resources from certain Kubernetes namespaces?
Check whether namespace filtering is configured, because a namespace selector can limit which namespaces are visible.
What permission issue should I check if the operator cannot read cluster resources?
Verify that the operator has the required RBAC permissions in the cluster.
How do I provide the operator's private key when deploying it?
Save the private key to a file such as private-key.pem, then create the secret in the obsyk namespace.
Answers sourced from docs.obsyk.ai, github.com
Community
Collected 48 days ago - public community threads