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

v1alpha1: one port forward object may contain multiple forwards #4489

Merged
merged 5 commits into from
Apr 30, 2021

Conversation

maiamcc
Copy link
Contributor

@maiamcc maiamcc commented Apr 29, 2021

as per #4483 (comment), when we have one pf API object per pair of ports to forward between, it can get awkward to diff existing vs. desired in the subscriber.

this PR has the api object behaving more in line with the current port forward subscriber behavior -- one PF API object contains one or more forwards to run on the specified pod.

@maiamcc maiamcc requested review from milas and nicks April 29, 2021 20:51
@maiamcc maiamcc force-pushed the maiamcc/api-portforward-per-pod branch from d2c6c36 to 555f4f3 Compare April 29, 2021 20:52
@maiamcc
Copy link
Contributor Author

maiamcc commented Apr 29, 2021

(note that this new data organization doesn't ENFORCE "one PortForward API object per pod", but it does allow the PortForwardSubscriber to create one per pod, which will make it easier to track/diff PFs against each other)

@maiamcc maiamcc force-pushed the maiamcc/api-portforward-per-pod branch from d24b602 to 76195ff Compare April 30, 2021 18:36
@maiamcc maiamcc merged commit 325dbf8 into master Apr 30, 2021
@maiamcc maiamcc deleted the maiamcc/api-portforward-per-pod branch April 30, 2021 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants