fix: remove null creationTimestamp from CRD metadata

[omerap12]

What type of PR is this?
bug

Which issue does this PR fix?:
issue #3017

What does this PR do / Why do we need it?:
Removes metadata.creationTimestamp: null field from CustomResourceDefinition to resolve kubeconform validation errors. This field is automatically managed by Kubernetes and should not be explicitly set to null in the CRD definition.

Testing done on this change:

Will this PR introduce any new dependencies?:

Will this break upgrades or downgrades? Has updating a running cluster been tested?:

Does this change require updates to the CNI daemonset config files to work?:

Does this PR introduce any user-facing change?:

NONE

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[orsenthil]

Looks like createTimestamp was added automatically when using controller-gen.kubebuilder.io/version: v0.11.3

• This is tracked as an upstream kubernetes issue - creationTimestamp: null is invalid since it isn't a string  kubernetes/kubernetes#109427 - giving the details, and possible fix here Make creationTimestamp a pointer kubernetes/kubernetes#67610 that can satisfy kubeconform tools.

Since creationTimeStamp is populated by system https://github.com/kubernetes/apimachinery/blob/master/pkg/apis/meta/v1/types.go#L179-L188 it is okay to remove it from CRD file.

	// CreationTimestamp is a timestamp representing the server time when this object was
	// created. It is not guaranteed to be set in happens-before order across separate operations.
	// Clients may not set this value. It is represented in RFC3339 form and is in UTC.
	//
	// Populated by the system.
	// Read-only.
	// Null for lists.
	// More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
	// +optional
	CreationTimestamp Time `json:"creationTimestamp,omitempty" protobuf:"bytes,8,opt,name=creationTimestamp"`

[orsenthil]

LGTM