Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use actual hostname when creating network e2e test pod #47143

Merged

Conversation

ethernetdan
Copy link
Contributor

@ethernetdan ethernetdan commented Jun 7, 2017

What this PR does / why we need it:
This changes a e2e framework network test Pod use the actual hostname value to match the kubernetes.io/hostname label in it's NodeSelector. Currently it assumes the Node name will match that hostname label which is not true in all environments.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
Fixes coreos/tectonic-installer#1018

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 7, 2017
@k8s-github-robot k8s-github-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. release-note-none Denotes a PR that doesn't merit a release note. labels Jun 7, 2017
@ethernetdan ethernetdan changed the title use NodeName rather than NodeSelector with hostname for network test Pod Use actual hostname when creating network e2e test pod Jun 7, 2017
@ethernetdan
Copy link
Contributor Author

ethernetdan commented Jun 7, 2017

Updated to be in line with the changes in #35937

@ethernetdan ethernetdan requested a review from zmerlynn June 7, 2017 21:28
@ethernetdan ethernetdan added this to the v1.7 milestone Jun 7, 2017
@ethernetdan ethernetdan added sig/testing Categorizes an issue or PR as relevant to SIG Testing. kind/bug Categorizes issue or PR as related to a bug. labels Jun 7, 2017
@zmerlynn
Copy link
Member

zmerlynn commented Jun 7, 2017

/lgtm /approve

@spiffxp
Copy link
Member

spiffxp commented Jun 8, 2017

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 8, 2017
@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ethernetdan, spiffxp, zmerlynn

Associated issue: 1018

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

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

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 k8s-github-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 8, 2017
@k8s-github-robot
Copy link

Automatic merge from submit-queue (batch tested with PRs 47065, 47157, 47143)

@k8s-github-robot k8s-github-robot merged commit f21cbfa into kubernetes:master Jun 8, 2017
@ethernetdan ethernetdan deleted the net_pod_use_nodename branch June 8, 2017 21:57
@ethernetdan ethernetdan restored the net_pod_use_nodename branch June 15, 2017 21:07
k8s-github-robot pushed a commit that referenced this pull request Jun 15, 2017
…47143-upstream-release-1.6

Automatic merge from submit-queue

Automated cherry pick of #47143

Cherry pick of #47143 on release-1.6.

#47143: use actual hostname in NodeSelector for network test Pod
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hostname mismatch causes conformance failures on AWS
7 participants