# Operator-internal

Operator-internal is a development framework for building Kubernetes operators, giving platform teams scaffolding, code generation, and lifecycle management to create reliable, maintainable operator projects. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6007/operator-internal

## Description

Operator-internal is a development framework for building Kubernetes operators, giving platform teams scaffolding, code generation, and lifecycle management to create reliable, maintainable operator projects.

## Platform availability

Available on 0 of 10 platforms.

## Health score

67/100 (Good), based on 5 of 5 factors.
- Maintained: 76 (last commit 128 days ago)
- Popular: 78 (7,689 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 80 (1 GB minimum RAM, runs on ARM)
- Security check: 69 (no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 5/10)

## Links

- Docker Hub: https://hub.docker.com/r/redislabs/operator-internal
- Official website: https://sdk.operatorframework.io
- GitHub: https://github.com/operator-framework/operator-sdk

## Common questions

### Do I need to set a namespace before installing operator-internal?

If you are not using the default Kubernetes namespace, set NAMESPACE and apply the Kustomize bundle first. Skipping this step can put resources in the wrong namespace.

### Which port should I expose for the metrics Service?

Point the example Service at port 8080. That is where the app serves metrics, so if the Service is missing or points to the wrong port, monitoring cannot reach it.

### Why can I access the app externally but not internally through a reverse proxy?

The destination for the proxy host should be the internal network IP and should use the service's designated port, such as 9443. If external IPv4 access works but internal access does not, check the proxy destination configuration.

### What should I check when a self-hosted workflow fails because of authentication?

Authentication failures are a common execution issue to troubleshoot in self-hosted automation workflows. You should also check network connectivity and resource limits.

---
Source: Our Local Host (https://ourlocalhost.com/app/6007/operator-internal), the self-hosted and open-source app directory.
