David Xia

I tried making a PR, but I'm not that good at go :(

I just found the [Slack 1.6 announcement with support for K8s 1.22](https://kubeflow.slack.com/archives/C7REE0ETX/p1659106007846429). And [this release page](https://github.com/kubeflow/community/tree/master/releases/release-1.6#timeline). This can probably be closed.

@jyoder-deloitte ah, where do you see them missing the dates?

@Nbelles thanks, hoping the maintainer(s) notice and reply :)

Thanks. Numbers in YAML were being parsed into IntNodes. I won’t have time to contribute this feature myself though.

On closer look, it seems like our tool that deploys K8s manifests to clusters can use the decimal or octal notation. So we should be able to upgrade this library...

My K8s YAML is below. ``` apiVersion: apps/v1 kind: Deployment metadata: name: test-service namespace: test-namespace spec: selector: matchLabels: app: test-service template: metadata: labels: app: test-service spec: volumes: - name: test-service-account...

Thanks for reviewing. I just want the API to include the head IP when getting or listing clusters so that users don’t have to do it themselves which requires knowledge...

> Any ideas how to accommodate this use case? Can we make API return both Pod and Service IP?

> I am not exactly sure what you mean by wanting the API to expose the IP address. Would something like kubectl get pod -owide -l=rayNodeType=head work in your case,...