[Feature] Add extra_status field in RayCluster CRD

[brucez-anyscale]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

In Ray cluster CRD, it is good to have another field.

ExtraStatus []byte `json:"extraStatus,omitempty"`

Use case

I want to customize the RayclusterReconciler to store some extra status inside CR.
A []byte field gives the flexibility to store any data.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[andrewsykim]

We have a new conditions API that was introduced in v1.2 and will be enabled by default in v1.3. It can be easily extended to add arbitrary conditions if you are customizing the reconciler anyways.

kuberay/ray-operator/apis/ray/v1/raycluster_types.go

Lines 178 to 183 in 7a768f9

	// Represents the latest available observations of a RayCluster's current state.
	// +patchMergeKey=type
	// +patchStrategy=merge
	// +listType=map
	// +listMapKey=type
	Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type"`

Let me know if that would work for you instead

[brucez-anyscale]

Do you suggest just use

Message string `json:"message" protobuf:"bytes,6,opt,name=message"`

field in the conditions to record the []bytes?
That could be a workaround.

[andrewsykim]

What's your use case for putting messages in the status?

[brucez-anyscale]

I want to some other actions and persistent in state to remember what are done and the info.
For example, run a raycluster, before starting any pods, I customize ray cluster reconciler to create a record into a mysql db, and then I want to store a dict of metadata of my db row into the Raycluster state.

[andrewsykim]

I want to some other actions and persistent in state to remember what are done and the info.
For example, run a raycluster, before starting any pods, I customize ray cluster reconciler to create a record into a mysql db, and then I want to store a dict of metadata of my db row into the Raycluster state.

I see, another approach you can take here is just store json payload in an annotation. It's not uncommon to do this for tracking arbitrary data on objects. Conditions can work too but it's not designed for your use-case