---
title: "Discussion on \"Upgrading a GKE Cluster Without Changing the Release Channel\" | Hashnode"
description: "Discussion on \"Upgrading a GKE Cluster Without Changing the Release Channel\". In some situations, you might prefer not to change your GKE release channel. For example, your cluster is currently on a specific version in the Regular channel, and certain CVE fixes are available only in a minor version that belongs to the Rapid ch..."
url: "https://hashnode.com/posts/upgrading-a-gke-cluster-without-changing-the-release-channel/67dd51c1375ccec43dbe2412"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Upgrading a GKE Cluster Without Changing the Release Channel](https://bvakash.hashnode.dev/upgrading-a-gke-cluster-without-changing-the-release-channel?utm_source=hashnode&utm_medium=feed)

In some situations, you might prefer not to change your GKE release channel. For example, your cluster is currently on a specific version in the Regular channel, and certain CVE fixes are available only in a minor version that belongs to the Rapid ch...

Mar 21, 2025 · 3 min read · bvakash.hashnode.dev  
Read the article

-   [#gcp](https://hashnode.com/tag/gcp)
-   [#gke](https://hashnode.com/tag/gke)
-   [#gke-cluster](https://hashnode.com/tag/gke-cluster)
-   [#cluster-upgrade](https://hashnode.com/tag/cluster-upgrade)
-   [#google-cloud-shell](https://hashnode.com/tag/google-cloud-shell)

## Written by

[B V AKASH](https://hashnode.com/@bvakash)

@bvakash · Bangalore, India

  
[View profile](https://hashnode.com/@bvakash)

I design, architect, and maintain hybrid cloud environments.

I design, architect, and maintain hybrid cloud environments.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
