Merge pull request #47407 from fcsgehrke/patch-1

Update SUSE install-kubectl-linux.md
This commit is contained in:
Kubernetes Prow Robot 2024-08-13 16:34:42 -07:00 committed by GitHub
commit 1a23d13de7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 35 additions and 4 deletions

View File

@ -222,11 +222,42 @@ before running `zypper update`. This procedure is described in more detail in
[Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/).
{{< /note >}}
2. Install kubectl using `zypper`:
2. Update `zypper` and confirm the new repo addition:
```bash
sudo zypper update
```
```bash
sudo zypper install -y kubectl
```
When this message appears, press 't' or 'a':
```
New repository or package signing key received:
Repository: Kubernetes
Key Fingerprint: 1111 2222 3333 4444 5555 6666 7777 8888 9999 AAAA
Key Name: isv:kubernetes OBS Project <isv:kubernetes@build.opensuse.org>
Key Algorithm: RSA 2048
Key Created: Thu 25 Aug 2022 01:21:11 PM -03
Key Expires: Sat 02 Nov 2024 01:21:11 PM -03 (expires in 85 days)
Rpm Name: gpg-pubkey-9a296436-6307a177
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): a
```
3. Install kubectl using `zypper`:
```bash
sudo zypper install -y kubectl
```
{{% /tab %}}
{{< /tabs >}}