[Serve][Doc] Add Ray Service CR inspection

[sihanwang41]

Why are these changes needed?

Related issue number

Checks

• [ ] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• [ ] I've run scripts/format.sh to lint the changes in this PR.
• [ ] I've included any doc changes needed for https://docs.ray.io/en/master/.
  • [ ] I've added any new APIs to the API Reference. For example, if I added a method in Tune, I've added it in doc/source/tune/api/ under the corresponding .rst file.
• [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • [ ] Unit tests
  • [ ] Release tests
  • [ ] This PR is not tested :(

[sihanwang41]

@edoakes @shrekris-anyscale @zcin please take look,

[sihanwang41]

Hi @akshay-anyscale , can you take a look?

[akshay-anyscale]

can you rebase with @angelinalg's latest changes

[akshay-anyscale]

while we are changing this, can you update the example to not use deployment graphs?

[sihanwang41]

while we are changing this, can you update the example to not use deployment graphs?

Currently the deployments are fairly easy. Is there any reasons to change the example?

[akshay-anyscale]

while we are changing this, can you update the example to not use deployment graphs?

Currently the deployments are fairly easy. Is there any reasons to change the example?

It's because deployment graphs are still in alpha and not very completely supported. We're also moving them down in the documentation

[sihanwang41]

while we are changing this, can you update the example to not use deployment graphs?

Currently the deployments are fairly easy. Is there any reasons to change the example?

It's because deployment graphs are still in alpha and not very completely supported. We're also moving them down in the documentation

Sg, I will go for separate pr to do it.