Platform specific fields in BYOHost CRD

[sachinkumarsingh092]

What this PR does / why we need it:
We need platform-specific info regarding the host in BYOHost CRDs.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #469

Additional information

Changes in brief:

• /apis/infrastructure/v1beta1/byohost_types.go: We introduce new type HostStatus which has all the platformspecific details like OS name, Kernel version, architecture etc. We introduce a new field in ByoHostStatus with this type.
• /config/crd/bases/infrastructure.cluster.x-k8s.io_byohosts.yaml: Using make generate, we let controller-gen introduce these new fields in the CRDs automatically.
• /apis/infrastructure/v1beta1/zz_generated.deepcopy.go: Autogenerated implementation of the deepcopy methods for type HostStatus.

Special notes for your reviewer

<none>

[mayur-tolexo]

Just curious, why host OS and Arch details are not a part of Spec and added in Status of ByoHost?

[sachinkumarsingh092]

why host OS and Arch details are not a part of Spec and added in Status of ByoHost

@mayur-tolexo according to kubebuilder docs, Spec holds desired state, so any inputs to our controller goes here while Status holds observed state and contains any information we want users or other controllers to be able to easily obtain.
By these definitions, OS and Arch details should be in Status, right?

[mayur-tolexo]

@sachinkumarsingh092, thanks for clarifying. Ya make sense to provide only status subresource access to other controllers for HostInfo.

[anusha94]

lgtm

[dharmjit]

lgtm