<p>As per <a href="https://cloud.google.com/compute/docs/troubleshooting/known-issues#keyexpired" rel="nofollow noreferrer">compute/docs/troubleshooting/known-issues</a>:</p>
<blockquote>
<p>On Debian and Ubuntu based systems, including your local workstations,
you might encounter an error similar to the following example:
[...] The following signatures were invalid: XXXX [...]</p>
</blockquote>
<p>To resolve this error, get the latest valid <code>apt-key.gpg</code> key file from <code>https://packages.cloud.google.com</code> by running the following command:</p>
<pre><code>curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
</code></pre>

CC BY-SA 4.0
2021-04-05T13:13:19.550Z
My doubt was this if the key was changed or something more deep. Valeu Du.
Vader
CC BY-SA 4.0
2021-04-05T02:51:20.610Z
2021-04-05T02:51:20.610Z
Eduardo Baitello
<p>Heys dudes,</p>
<p>More someone got error when trying update cache of the Google K8s repositories?
I have been got the error about <strong>NO_PUBKEY</strong></p>
<pre><code>Err:10 https://packages.cloud.google.com/apt kubernetes-xenial InRelease        
  The following signatures were invalid: EXPKEYSIG 6A030B21BA07F4FB Google Cloud Packages Automatic Signing Key &lt;gc-team@google.com&gt; The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B57C5C2836F4BEB
</code></pre>
<p>and</p>
<pre><code>W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures were invalid: EXPKEYSIG 6A030B21BA07F4FB Google Cloud Packages Automatic Signing Key &lt;gc-team@google.com&gt; The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B57C5C2836F4BEB
W: Failed to fetch http://apt.kubernetes.io/dists/kubernetes-xenial/InRelease  The following signatures were invalid: EXPKEYSIG 6A030B21BA07F4FB Google Cloud Packages Automatic Signing Key &lt;gc-team@google.com&gt; The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B57C5C2836F4BEB
W: Some index files failed to download. They have been ignored, or old ones used instead.
</code></pre>
<p>Something was changed?</p>

<kubernetes>
Google K8s Mirror offline?
Vader
# Google K8s Mirror offline?

(Asked by: username_0 on 2021-04-01)

Heys dudes,
More someone got error when trying update cache of the Google K8s repositories?
I have been got the error about NO_PUBKEY
Err:10 https://packages.cloud.google.com/apt kubernetes-xenial InRelease        
  The following signatures were invalid: EXPKEYSIG 6A030B21BA07F4FB Google Cloud Packages Automatic Signing Key  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B57C5C2836F4BEB

and
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures were invalid: EXPKEYSIG 6A030B21BA07F4FB Google Cloud Packages Automatic Signing Key  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B57C5C2836F4BEB
W: Failed to fetch http://apt.kubernetes.io/dists/kubernetes-xenial/InRelease  The following signatures were invalid: EXPKEYSIG 6A030B21BA07F4FB Google Cloud Packages Automatic Signing Key  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B57C5C2836F4BEB
W: Some index files failed to download. They have been ignored, or old ones used instead.

Something was changed?

**Tags:** kubernetes


---

## 1 answers

### Answer by username_1 on 2021-04-05. Score: 1 | Accepted answer

As per compute/docs/troubleshooting/known-issues:

On Debian and Ubuntu based systems, including your local workstations,
you might encounter an error similar to the following example:
[...] The following signatures were invalid: XXXX [...]

To resolve this error, get the latest valid apt-key.gpg key file from https://packages.cloud.google.com by running the following command:
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -

> **Comments:**
> **username_0**: My doubt was this if the key was changed or something more deep. Valeu Du.  

---

