Summary

ReceiverPort is defined as a complex struct which mimics the need of defining a port for a generic service. The CLO controls all aspects of the receiver so it should need to have this complexity; users should only need to define potentially the port upon which to listen. Modify the API and code to convert 'receiverPort' into an int

Acceptance Criteria

HTTPReceiver API to be something like:

// HTTPReceiver receives encoded logs as a HTTP endpoint.
type HTTPReceiver struct {
	// ReceiverPort specifies parameters for the Service fronting the HTTPReceiver
	// +required
	ReceiverPort int `json:"receiverPort"`
	// Format is the format of incoming log data.
	//
	// +kubebuilder:validation:Enum:=kubeAPIAudit
	// +required
	Format string `json:"format"`
}

Notes

• Does it need to be required? Can we not default a value