@@ -222,11 +222,42 @@ before running `zypper update`. This procedure is described in more detail in
222
222
[Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/).
223
223
{{< /note > }}
224
224
225
- 2. Install kubectl using ` zypper` :
225
+ 2. Update ` zypper` and confirm the new repo addition:
226
+
227
+ ` ` ` bash
228
+ sudo zypper update
229
+ ` ` `
230
+
231
+ When this message appears, press ' t' or ' a' :
232
+
233
+ ` ` `
234
+ New repository or package signing key received:
235
+
236
+ Repository: Kubernetes
237
+ Key Fingerprint: 1111 2222 3333 4444 5555 6666 7777 8888 9999 AAAA
238
+ Key Name: isv:kubernetes OBS Project <isv:[email protected] >
239
+ Key Algorithm: RSA 2048
240
+ Key Created: Thu 25 Aug 2022 01:21:11 PM -03
241
+ Key Expires: Sat 02 Nov 2024 01:21:11 PM -03 (expires in 85 days)
242
+ Rpm Name: gpg-pubkey-9a296436-6307a177
243
+
244
+ Note: Signing data enables the recipient to verify that no modifications occurred after the data
245
+ were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
246
+ and in extreme cases even to a system compromise.
247
+
248
+ Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
249
+ you are not sure whether the presented key is authentic, ask the repository provider or check
250
+ their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
251
+ are using.
252
+
253
+ Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): a
254
+ ` ` `
255
+
256
+ 3. Install kubectl using ` zypper` :
226
257
227
- ` ` ` bash
228
- sudo zypper install -y kubectl
229
- ` ` `
258
+ ` ` ` bash
259
+ sudo zypper install -y kubectl
260
+ ` ` `
230
261
231
262
{{% /tab %}}
232
263
{{< /tabs > }}
0 commit comments