operator: custom install namespaces are experimental until faithful upgrade e2e covers them
- Dominant language
- Go
- Stars
- 28
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 55
Description
Installing Unbounded into a non-default namespace is supported via manifest rewriting plus the POD_NAMESPACE-aware `internal/unbounded.SystemNamespace()` helper. However, the faithful upgrade e2e (`hack/operator-upgrade-e2e/e2e.py`, run by the `operator-upgrade-e2e` workflow) only exercises the default `unbounded-system` namespace.
Follow-up:
- Extend the faithful upgrade e2e to install and migrate into a **non-default** namespace end to end.
- Once that path is exercised in CI, drop the 'experimental' caveat for custom install namespaces.
Context: split out of the umbrella `unbounded-system` integration PR #388.
Contributor guide
Research direction
Start with hack/operator-upgrade-e2e/e2e.py and the operator-upgrade-e2e workflow, then review internal/unbounded.SystemNamespace() and the existing default unbounded-system flow. The work is complete when the faithful upgrade e2e installs and migrates an instance in a non-default namespace and CI exercises that path, allowing the experimental caveat to be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, python
- Domain
- devops, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100