Controller Deployment discovery rejects shorter pod-template hashes

Open Beginner friendly
#2,641 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

@c-kruse is already working on this.

Since Nov 20, 2026.

  • #2642 by @c-kruse — open

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from skupperproject/skupper

All issues in skupperproject/skupper

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.