-
Notifications
You must be signed in to change notification settings - Fork 451
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
gep-1762: Add attachTo
to in cluster deployments GEP
#2945
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: howardjohn The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This feels awfully similar to #1863 - it seems like we shouldn't try to tackle one of the problems (Gateway merging) without the other (Gateway Service attachment) given the significant overlap. Unfortunately I think we've run out of time in the v1.1 release cycle to fit something this big in, but I'd like to aim to get both concepts in as one of our first topics post v1.1 release. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closed this PR. In response to this:
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-sigs/prow repository. |
What type of PR is this?
/kind gep
What this PR does / why we need it:
This is a followup to #1757. This was stripped out to get things into 1.0
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: