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

Add version information for various components #39

Merged
merged 1 commit into from
Aug 6, 2018

Conversation

puneetguptanitj
Copy link
Contributor

Add version information for various components in MachineSpec

@puneetguptanitj puneetguptanitj force-pushed the private/add-component-version-info branch from 8ea63cc to cd1bd32 Compare August 6, 2018 16:28
type MachineComponentVersions struct {
NodeadmVersion string
EtcdadmVersion string
KubernetesVersion string
Copy link
Contributor

Choose a reason for hiding this comment

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

How does KubernetesVersion relate to the upstream MachineSpec.Versions field, which itself contains Kubelet and ControlPlane versions.

Copy link
Contributor Author

@puneetguptanitj puneetguptanitj Aug 6, 2018

Choose a reason for hiding this comment

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

Currently it is a much bigger super set, but eventually, once we move nodeadm and etcdadm to use range of versions, we should be able to move them out from this set and also remove flannel and handle it as an addon, then i think it would match upstream more closely (with only addition of etcd version)

@@ -154,6 +189,7 @@ func Convert_v1alpha1_MachineSpec_To_sshprovider_MachineSpec(in *MachineSpec, ou
func autoConvert_sshprovider_MachineSpec_To_v1alpha1_MachineSpec(in *sshprovider.MachineSpec, out *MachineSpec, s conversion.Scope) error {
out.Roles = *(*[]MachineRole)(unsafe.Pointer(&in.Roles))
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we work around/avoid using unsafe? I just noticed this and read up https://golang.org/pkg/unsafe/#Pointer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks Arun for taking a look, looked into the generators that we use to generate these files, there seems to be a command line option to skipUnsafe https://github.com/kubernetes/code-generator/blob/3541780c0c718ff0c54cadd8401bfd6402886100/cmd/conversion-gen/args/args.go#L70, the default is false. Have created #40 to see if we can update our make build to use skipUnsafe as true

@puneetguptanitj puneetguptanitj merged commit a04fd75 into master Aug 6, 2018
@puneetguptanitj puneetguptanitj deleted the private/add-component-version-info branch August 6, 2018 21:28
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.

3 participants