Port K8s Exporter
Port K8s Exporter is a Helm chart that deploys an exporter to send Kubernetes cluster data to Port, giving teams centralized visibility into their Kubernetes…
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.
53/100 Fair
- Maintained
- 98last commit 19 days ago
- Popular
- 3030 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 201 serious finding, 4 minor, CI, tests
Based on 4 of 5 factors.
Security check: 1 serious finding
- A private key is committed in the source code (pkg/parsers/sensitive.go:14)
Automated checks on commit f084b50, 15 Nov 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 30
- Open issues
- 25
- Last commit
- 2026-11-02
- Latest release
- v0.8.1
- License
- Apache-2.0
- Activity
- rising
Checked 15 days ago - source: GitHub (port-labs/port-k8s-exporter)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Make and fill in the .env file Copy .env.example to .env, then fill in your Port access keys (the client ID and client secret that identify your account). This is the main settings file the app reads at startup; if it is missing or empty, the app cannot connect to Port. source
- Get machine credentials for automated runs If you will run the exporter in an automated pipeline, request a Port OAuth token (a short-lived pass that lets the program sign in) using your client ID and client secret. Without it, automated jobs cannot authenticate and Port rejects their requests. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do Port blueprints need to exist before deploying the port-k8s-exporter Helm chart?
Yes. The chart lists, watches, and exports Kubernetes objects to Port entities of existing blueprints.
What Kubernetes information can the exporter expose in Port?
It streams Kubernetes resource data to the relevant Port entity. The docs describe representing a running cluster, seeing namespaces, and seeing services.
Where should I look for chart-specific troubleshooting for port-k8s-exporter?
The Helm charts common issues guide covers problems specific to port-k8s-exporter and issues common across Port charts.
Does a Kubernetes port that works from the host always work from inside Docker?
No. A Kubernetes port exposed with port forwarding can work from the host but fail when accessed from inside a Docker container.
Answers sourced from deepwiki.com, github.com, stackoverflow.com, www.port.io
Community
Collected 48 days ago - public community threads