Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accept version strings with and without a 'v' prefix #109

Merged

Conversation

chess-knight
Copy link
Contributor

When using ClusterClasses, Version is propagated from cluster.Spec.Topology into the kamajicontrolplane.Spec with a "v" prefix and then Kamaji complains about the wrong version format. See CAPI defaulting webhook https://github.com/kubernetes-sigs/cluster-api/blob/main/internal/webhooks/cluster.go#L100

@chess-knight chess-knight force-pushed the fix/tolerate_version_prefix branch from fb0647e to c5b6448 Compare June 12, 2024 13:05
Copy link
Member

@prometherion prometherion left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution, highly appreciated!

Versioning of the Kubernetes cluster always puzzled me, especially with Cluster API: what's the correct way, in the end, naked (with no v prefix) or the opposite? 🤔

@chess-knight
Copy link
Contributor Author

Thanks for the contribution, highly appreciated!

Versioning of the Kubernetes cluster always puzzled me, especially with Cluster API: what's the correct way, in the end, naked (with no v prefix) or the opposite? 🤔

IMO the opposite is the correct way, i.e. v1.30.1

@prometherion prometherion added this to the v0.10.0 milestone Jun 13, 2024
@prometherion prometherion merged commit 4dff1e2 into clastix:master Jun 13, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants