add fieldSelector podIP

[dixudx]

What this PR does / why we need it:
Currently the fieldSelector for Pod only support metadata.name, metadata.namespace, spec.nodeName, spec.restartPolicy and status.phase.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #50075

Special notes for your reviewer:
/cc @wojtek-t @caesarxuchao @justinsb @lilic

Release note:

add fieldSelector podIP

[k8s-ci-robot]

@dixudx: GitHub didn't allow me to request PR reviews from the following users: LiliC.

Note that only kubernetes members can review this PR, and authors cannot review their own PRs.

In response to this:

What this PR does / why we need it:
Currently the fieldSelector for Pod only support metadata.name, metadata.namespace, spec.nodeName, spec.restartPolicy and status.phase.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #50075

Special notes for your reviewer:
/cc @wojtek-t @caesarxuchao @justinsb @lilic

Release note:

add fieldSelector podIP

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @dixudx. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[justinsb]

/ok-to-test

/lgtm

[dixudx]

/test pull-kubernetes-e2e-gce-etcd3

[caesarxuchao]

/retest

[dixudx]

@deads2k @wojtek-t Needs your approval. Thanks.

[dixudx]

/assign @deads2k @wojtek-t

[deads2k]

/approve

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, dixudx, justinsb

Associated issue: 50075

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• pkg/registry/OWNERS [deads2k]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 50091, 50231, 50238, 50236, 50243)

[k8s-ci-robot]

@dixudx: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-kops-aws	c6cafa5	link	/test pull-kubernetes-e2e-kops-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[asymmetric]

How come this was not included in 1.7.4? Is it related to the test failure above or did it just get merged too late?

[dixudx]

@asymmetric You can rebase this PR into v1.7.4. Or @wojtek-t shall we cherry-pick this PR into v1.7.4 or release-1.7?

[wojtek-t]

I don't think this should be cherrypicked. This is not a bug fix - it's a feature.

[asymmetric]

@wojtek-t @dixudx so is the best course of action to just wait for a new release?

Or can this somehow be backported?

[dixudx]

@asymmetric Prefer to rebuild apiserver by yourself instead of waiting for the new release. It could take couple of weeks or months to get it released.

Cherry-pick this PR into your desired Kubernetes version and make kube-apiserver.

[asymmetric]

@dixudx I'm not asking for a cluster I'm running, rather for an operator I'm building that needs to run against upstream API servers.