Issue with k8s.io/docs/tasks/tools/install-kubectl-linux/

[neilgierman]

The instructions for adding kubernetes to Debian-based distributions is still pointing to the old https://apt.kubernetes.io website. That needs to be changed to https://packages.cloud.google.com/apt/ since now the previous server has SSL certificate issues.

[k8s-ci-robot]

@neilgierman: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, 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.

[utkarsh-singh1]

/assign

[raghu-manne]

@utkarsh-singh1 Are you working on this?

[utkarsh-singh1]

Yeah @raghu-manne

[utkarsh-singh1]

Hi @neilgierman , I have tried installing kubectl in both debian -10 and debian-11 and https://apt.kubernetes.io automatically redirects to the https://packages.cloud.google.com/apt/.

[sftim]

There is a related problem, which is that https://packages.cloud.google.com/apt/ is in fact not exactly an official Kubernetes artifact repository (it belongs instead to Google).

See kubernetes/release#913 (comment) for more context.

[sftim]

I don't think we should change the docs. I think we should change things on the release and artifacts side, where possible.

[sftim]

/language en
/sig release
/kind bug

[neilgierman]

It is fixed now but when I filed the bug, the ssl certificate that was being served by apt.kubernetes.io was in fact issued to a site with the address YouTube.kubertetes.io and causing an SSL handshake error and apt would not download from it. The only way I could update/install kubectl was by changing my config to use the google mirror directly instead of letting apt.kubernetes.io redirect to it.

[utkarsh-singh1]

@neilgierman if the issue has been resolved please can you close it.

[neilgierman]

I am reluctant to close the issue based on comments from @sftim. This is no longer a documentation issue since right now the docs work again, however is redirecting to Google the correct action?

[sftim]

I don't think there's anything to fix here. SIG Release are already tracking the work to move away from the existing artifacts release process and hosting for Linux packages.

@neilgierman I recommend you close this. If you want to suggest work, or contribute, https://github.com/kubernetes/release/issues/ is the place for that.