Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tools installation docs are not entirely true about apt repository signing key and Kubernetes version #49049

Open
slabstone opened this issue Dec 12, 2024 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@slabstone
Copy link

This is a Bug Report

Problem:
https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-using-native-package-management says

The same signing key is used for all repositories so you can disregard the version in the URL:

This is not entirely true, as the current key is only present in versions 1.28 and above, while 1.27 and below have expired key. I understand that versions below 1.27 are no longer supported, but it's likely that the same problem occurs after the current key expires on 2026-12-29, only with different version numbers.

Proposed Solution:
Rephrase the statement about signing key and Kubernetes version so it's clear that it's not the same key for all repositories, e. g. changing it to "all supported versions".

Page to Update:
https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-using-native-package-management

@slabstone slabstone added the kind/bug Categorizes issue or PR as related to a bug. label Dec 12, 2024
@k8s-ci-robot
Copy link
Contributor

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 12, 2024
@sftim
Copy link
Contributor

sftim commented Dec 12, 2024

What repositories are you thinking of @slabstone? I don't think there's a repository for v1.27 Kubernetes, at least not one published by the Kubernetes project.

The docs don't cover third party repositories.

@slabstone
Copy link
Author

slabstone commented Dec 12, 2024

What repositories are you thinking of @slabstone? I don't think there's a repository for v1.27 Kubernetes, at least not one published by the Kubernetes project.

You can add repository for versions 1.24 through 1.27 using the current docs and install kubectl if you bypass apt signature verification.

Selected version '1.24.17-1.1' (isv:kubernetes:core:stable:v1.24:pkgs.k8s.io [amd64]) for 'kubectl'
...
Get:1 https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.24/deb  kubectl 1.24.17-1.1 [9543 kB]

@sftim
Copy link
Contributor

sftim commented Dec 12, 2024

AIUI we don't document that https://prod-cdn.packages.k8s.io/ works; this is an internal implementation detail. You should not rely on this.

For the documented ways to download Kubernetes, see https://kubernetes.io/releases/download/

@sftim
Copy link
Contributor

sftim commented Dec 12, 2024

/priority awaiting-more-evidence

@k8s-ci-robot k8s-ci-robot added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

3 participants