Weird ordering in API type

[SchwarzM]

external-arbiter-operator/pkg/api/arbiter/v1alpha1/remotearbiter_types.go

Lines 101 to 115 in fdda4f8

	type RemoteArbiter struct {
	// spec defines the desired state of RemoteArbiter
	// +required
	Spec RemoteArbiterSpec `json:"spec"`
	metav1.TypeMeta `json:",inline"`
	// metadata is a standard object metadata
	// +optional
	metav1.ObjectMeta `json:"metadata,omitempty,omitzero"`
	// status defines the observed state of RemoteArbiter
	// +optional
	Status RemoteArbiterStatus `json:"status,omitempty,omitzero"`
	}

Normally any k8s object orders these fields

• TypeMeta
• ObjectMeta
• Spec
• Status

I do not have a clue on why this is done different here.

[aiivashchenko]

Addressed

[github-actions]

This issue is stale because it has been open for 90 days with no activity.