zsh completion missing __start_kubectl

[glanchow]

The zsh completion is not working for me in v1.22.0 or (stable) v1.22.2
I'm not sure if it's normal or a bug, here's the description.

curl -LO "https://dl.k8s.io/release/v1.22.0/bin/linux/amd64/kubectl"
./kubectl completion zsh | grep __start
== NOTHING ==

curl -LO "https://dl.k8s.io/release/v1.21.0/bin/linux/amd64/kubectl"
./kubectl completion zsh | grep __start
== OK ==
__start_kubectl()

[k8s-ci-robot]

@glanchow: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lauchokyip]

@marckhouzam can you take a look at this?

[marckhouzam]

@glanchow With kubectl 1.22, zsh completion is now native (no longer using the bash compatibility approach). It is therefore normal not to find the _start string in the script.

Can you describe what you do to setup completion so we can understand why it does not work?

If it helps, the help for the command mentions:

  # Load the kubectl completion code for zsh[1] into the current shell
  source <(kubectl completion zsh)
  # Set the kubectl completion code for zsh[1] to autoload on startup
  kubectl completion zsh > "${fpath[1]}/_kubectl"

[glanchow]

Hello,
Yes I had this line for months in my .zshrc source <(kubectl completion zsh)
I made dozen of tests this morning before creating an issue, but now it works..
It looks that I just had to re-open my terminals..
Sorry and thank you for your time