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

remove GCE cloud provider dependency to pkg/master/ports #73611

Merged
merged 1 commit into from
Feb 1, 2019

Conversation

andrewsykim
Copy link
Member

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Duplicates the proxy port value to remove dependencies to k8s.io/kubernetes in the GCE provider.

Which issue(s) this PR fixes:
Part of #69585

Special notes for your reviewer:
Not ideal to duplicate the port value there but it will unblock us from being able to move the GCE provider out-of-tree. I think it's worth the trade-off.

Does this PR introduce a user-facing change?:

NONE

/assign @cheftako @bowei

@k8s-ci-robot k8s-ci-robot added the release-note-none Denotes a PR that doesn't merit a release note. label Jan 31, 2019
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Jan 31, 2019
// NOTE: Please keep the following port in sync with ProxyHealthzPort in pkg/master/ports/ports.go
// ports.ProxyHealthzPort was not used here to avoid dependencies to k8s.io/kubernetes in the
// GCE cloud provider which is required as part of the out-of-tree cloud provider efforts.
lbNodesHealthCheckPort = 10256
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not ideal to duplicate the port value there but it will unblock us from being able to move the GCE provider out-of-tree. I think it's worth the trade-off.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the ports move to some common api-like repository? E.g. well-known constants. Maybe we can drive that, rather than break these depedencies...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally yes, but this seems like something that would go through API change reviews. There are also differing opinions on where those port values should live and I would prefer not to be blocked on this for too long. Can we add a TODO here and I will try to follow-up on putting the ports in a common api-like repo (maybe k8s.io/api/v1/well_known_constants.go`)?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also we should not be using the hard-coded port as it's override-able at runtime. So this constant won't qualify for that repo either

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for adding a TODO
I believe we should have a default but can be over-riden.
However switching it to a default seems a separate effort from Andrew's dependency break.

@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 31, 2019
@dims
Copy link
Member

dims commented Jan 31, 2019

/lgtm
/hold

( for @cheftako )

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 31, 2019
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 31, 2019
@cheftako
Copy link
Member

cheftako commented Feb 1, 2019

/lgtm
Would be nice to get the TODO in.

@bowei
Copy link
Member

bowei commented Feb 1, 2019

@dims what would be the right home for this constant?

@dims
Copy link
Member

dims commented Feb 1, 2019

@bowei ProxyHealthzPort itself is the default right? and the actual port can be specified in the command line, so we need to be looking up the real port set by the user instead of using lbNodesHealthCheckPort everywhere. right?

@dims
Copy link
Member

dims commented Feb 1, 2019

@andrewsykim can you please add a TODO? and then we can get this in?

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 1, 2019
@andrewsykim
Copy link
Member Author

TODO added

@dims
Copy link
Member

dims commented Feb 1, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 1, 2019
@bowei
Copy link
Member

bowei commented Feb 1, 2019

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewsykim, bowei

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dims
Copy link
Member

dims commented Feb 1, 2019

/hold cancel

thanks @bowei @cheftako

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 1, 2019
@k8s-ci-robot k8s-ci-robot merged commit 495ee5e into kubernetes:master Feb 1, 2019
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/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants