Skip to content

"kops upgrade cluster" does not suggest the latest recommended production ready Kubernetes version #17417

@stl-victor-sudakov

Description

@stl-victor-sudakov

/kind bug

1. What kops version are you running? The command kops version, will display
this information.

Client version: 1.32.0 (git-v1.32.0)

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

v1.32.4

3. What cloud provider are you using?

AWS

4. What commands did you run? What is the simplest way to reproduce this issue?

kops upgrade cluster

5. What happened after the commands executed?

kops output:

$ kops upgrade cluster
Using cluster from kubectl context: dev2.XXXX

ITEM                                    PROPERTY        OLD                                                                             NEW
InstanceGroup/control-plane-us-west-2c  Image           099720109477/ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20250305 099720109477/ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20250502.1
InstanceGroup/nodes-us-west-2c          Image           099720109477/ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20250305 099720109477/ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20250502.1

Must specify --yes to perform upgrade

6. What did you expect to happen?

I expected "kops upgrade cluster" to suggest an upgrade to Kubernetes v1.32.5 because it says in the "kops upgrade cluster" documentation: "his upgrades a cluster to the latest recommended production ready Kubernetes version. "

7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.

I can provide it on request if it is deemed relevant to the "kops upgrade cluster" behaviour.

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.

https://termbin.com/up3w

9. Anything else do we need to know?

I think it was the expected "kops upgrade cluster" behaviour before to suggest a Kubernetes version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions