Controller Deployment discovery rejects shorter pod-template hashes
Maintainers usually reply within 4 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go, kubernetes
- Domain
- backend, distributed-systems
Research direction
Find the controller code that parses HOSTNAME to derive the owning Deployment name, then inspect its related tests. Reproduce the failure with skupper-controller-bccd6f5c-7thwg; done when discovery accepts any nonempty alphanumeric hash while retaining the five-character Pod suffix requirement and the tests pass.
Written by the indexing model from the issue text.
Description
The controller derives its owning Deployment name from HOSTNAME using a pattern that requires a nine- or ten-character pod-template hash. The hash segment is not guaranteed to have either length.
For example, skupper-controller-bccd6f5c-7thwg has an eight-character hash. Even when Deployment skupper-controller exists, discovery rejects this Pod name before looking it up.
As a result, the controller loses the owning Deployment's name and UID. When no explicit controller name is configured, its logical identity also falls back to the Pod hostname. The controller warns that some resources may require manual deletion when it is removed.
Expected behavior: discover the owning Deployment for any nonempty alphanumeric hash segment. Keep the existing five-character Pod suffix requirement.
- Dominant language
- Go
- Stars
- 702
- Forks
- 93
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from skupperproject/skupper
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
skupperproject/skupper#2596 ·
Maintainers usually reply within 4 days
-
Controller drops informer deletion tombstonesPossibly taken @c-kruse claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
skupperproject/skupper#2639 ·
Maintainers usually reply within 4 days
-
Grant server autoconfigure fails permanently when two controller pods race on createPossibly taken @AryanP123 claimed this 2 days ago. Open
skupperproject/skupper#2636 · 3 comments · 1 assignee ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
skupperproject/skupper#2635 ·
Maintainers usually reply within 4 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
skupperproject/skupper#2632 ·
Maintainers usually reply within 4 days
All issues in skupperproject/skupper
Similar issues
-
area/import-export area/projects concern/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
go-vikunja/vikunja#4455 · 1 comment ·
Maintainers usually reply within 2 days
-
Dependabot PRs no longer merge automaticallyPossibly taken @dwisiswant0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectdiscovery/urlfinder#160 ·
Maintainers usually reply within 1 day
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chnm/legal-modernism#450 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug ready-for-triage ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
RedHatInsights/insights-ingress-go#946 · 4 comments ·
Maintainers usually reply within 1 day