Skip to content

[deckhouse-cli] Backport kubectl plugin fix to release-0.32 - #506

Merged
yalosev merged 1 commit into
release-0.32from
fix/kubectl-plugin-lookup-backport-to-0.32
Oct 8, 2026
Merged

yalosev merged 1 commit into
release-0.32from
fix/kubectl-plugin-lookup-backport-to-0.32

Conversation

@Glitchy-Sheep

Copy link
Copy Markdown
Contributor

Summary

Backport #505 to release-0.32 for DKP 1.76.

d8 k argo rollouts get searched for kubectl-k-argo-rollouts instead of the installed kubectl-argo-rollouts. The fix removes the k or kubectl command word before plugin lookup and passes the remaining arguments to the plugin.

The conflict around ConfigFlags keeps the release branch's existing configuration. The helper and tests match the original fix.

Tests

Both commands passed on this branch:

CGO_ENABLED=0 GOPRIVATE=flant.internal go test -p 2 -count=1 -tags='clionly dfrunsecurity dfrunnetwork dfrunmount dfssh containers_image_openpgp' ./cmd/commands
GOPRIVATE=flant.internal task build:dev:linux:amd64:cross -- -p 2

Notes

The separate plugin lookup in embedded delivery-kit remains unchanged. Updating that dependency is a separate task.

d8 k passed the whole d8 argv to kubectl's plugin lookup, so the "k"
word became part of the plugin name: `d8 k argo rollouts get` searched
PATH for kubectl-k-argo-rollouts and never found kubectl-argo-rollouts.
Since Deckhouse 1.76 nodes alias kubectl to `d8 k`, so every kubectl
plugin stopped working there.

Drop the "k"/"kubectl" word before the lookup. Every other d8 command
now passes no arguments to this lookup, so the d8 k command tree no
longer runs kubectl-<name> for `d8 <name>`.

(cherry picked from commit b3f6fe3)

Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
Signed-off-by: Roman Berezkin <roman.berezkin@flant.com>
@Glitchy-Sheep Glitchy-Sheep self-assigned this Oct 8, 2026
@yalosev
yalosev merged commit 3cf6970 into release-0.32 Oct 8, 2026
9 checks passed
@yalosev
yalosev deleted the fix/kubectl-plugin-lookup-backport-to-0.32 branch October 8, 2026 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants