Bug: `runtime/client.(*Impersonator).CanImpersonate` does not take kubeconfig into account
Maintainers usually reply within 1 day
@yuminn-k is already working on this.
Since Oct 31, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 49/100
Research direction
Start with runtime/client.(*Impersonator).CanImpersonate and trace how it checks for the ServiceAccount during Kustomization finalization. Compare the current-cluster lookup with the kubeconfig case, using the linked helm-controller issue for context. Done means the method recognizes a ServiceAccount in the remote cluster when spec.kubeConfig is configured, so finalization can collect remote garbage.
Written by the indexing model from the issue text.
Description
xref: https://github.com/fluxcd/helm-controller/issues/1250
This method is used by kustomize-controller during the finalization of a Kustomization to know if it can impersonate the configured spec.serviceAccountName for the operation. The method simply takes the existence of the ServiceAccount in the current cluster as the answer to this question. When spec.kubeConfig is configured, spec.serviceAccountName is supposed to exist in the remote cluster, and not in the current cluster. This means that if anybody is using both fields and the ServiceAccount does not exist in the current cluster (but correctly exists in the remote cluster), kustomize-controller does not collect the garbage in the remote cluster when the Kustomization is deleted.
- Dominant language
- Go
- Stars
- 63
- Forks
- 162
- Avg merge
- 9h 54m
- Merged PRs (30d)
- 29
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 fluxcd/pkg
-
ssa: wait errors drop the kstatus message, so health check failures don't say whyPossibly taken @schdief claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
ssa/jsondiff: honor ignored fields before dry-run validationPossibly taken @lubronzhan claimed this 31 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Improve `make release` to support major version bumpsPossibly taken @Iam-Karan-Suresh claimed this 175 days ago. Openarea/ci
fluxcd/pkg#1172 · 3 comments · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Pin and verify Security Insights schema in lintinsights targetPossibly taken @imshubham22apr-gif claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gemaraproj/gemara#618 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
a2aproject/a2a-go#597 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
scopes: GetAllowedTopics, GetProtectedTopics, and GetScopedTopics include empty topic names and do not trim whitespace charactersPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/networking kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
siderolabs/talos#14972 ·
Maintainers usually reply within 1 day