Skip to content

Conversation

@shanduur
Copy link
Member

@shanduur shanduur commented Dec 29, 2025

Allow overriding K8s version in the command.

Closes #12257

Signed-off-by: Mateusz Urbanek [email protected]

Allow overriding K8s version in the  command.

Signed-off-by: Mateusz Urbanek <[email protected]>
@shanduur shanduur force-pushed the feat/k8s-version-bundle branch from 14cdbd3 to cc2dd36 Compare December 29, 2025 10:18
@shanduur shanduur marked this pull request as ready for review December 29, 2025 12:47
@talos-bot talos-bot moved this from To Do to In Review in Planning Dec 29, 2025
}))
)

// if k8sVersion is defined, then we don't print components versions - there's no simple way to correlate patch-to-patch.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these versions are set by Talos, and they don't depend on Kubernetes version?

I'm trying to understand why we don't print them

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should be printing them at all here - should those be part of talos-bundle? If so, how do we ensure that we print correct version when overriding Talos version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

talosctl images default should accept --version

3 participants