Add ray head service endpoints in status for expose raycluster's head node endpoints

[scarlet25151]

Why are these changes needed?

Related issue number

Closes #223

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(

[Jeffwan]

Let's try to make the PR title self explainable. add service port is too vague and people doesn't know more details from the title.

[Jeffwan]

@scarlet25151 please rebase the master changes. What's wrong with the compatibility tests?

[scarlet25151]

/cc @davidxia @daikeshi ,I've pushed the feature of adding service endpoints in rayclusters' status in the repos, PTAL.

[davidxia]

@scarlet25151 thanks! I think there's a bug and made a draft #383.

Are there plans to include the head node's pod IP in the API Cluster response too? Happy to make a PR for that if we're OK with it.

[scarlet25151]

@scarlet25151 thanks! I think there's a bug and made a draft #383.

Are there plans to include the head node's pod IP in the API Cluster response too? Happy to make a PR for that if we're OK with it.

@davidxia Great, I think the draft is reasonable and thank you for the draft. I think it's a good idea to include the head node's pod IP in the API cluster response. It would be greate that you would make a PR. Btw, from the point of extensibility, I would recommend we add a string map like: map<string, string> metadata in the protobuf definition so in the future we would not change the protobuf so much if we would like to add some more information, and we may restore the head node pod IP in some way of key value pairs. WDYT? /cc @Jeffwan

[davidxia]

@scarlet25151 nice, #383 is now ready for review.

I've also drafted davidxia#1 for adding a status.metadata object. Lmk if that approach looks good enough to proceed.