feat: proxy for renaming 3rd party resources #23
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diafour
force-pushed
the
feat/rewrite_kv_resources
branch
from
a900e45 to
171004c
Compare
universal-itengineer
added
build/github/ubuntu
diafour
force-pushed
the
feat/rewrite_kv_resources
branch
from
7bdbb07 to
951e6d9
Compare
diafour
added
build/github/ubuntu
universal-itengineer
added
build/github/ubuntu
diafour
force-pushed
the
feat/rewrite_kv_resources
branch
4 times, most recently
from
ad44ca2 to
3ca8c10
Compare
- Resource renaming allows to avoid naming clashes. Signed-off-by: Ivan Mikheykin <[email protected]>
Signed-off-by: Yaroslav Borbat <[email protected]>
++ fixes and patches ++ non buffered writer for watch streams of objects without rewrite Signed-off-by: Ivan Mikheykin <[email protected]>
Signed-off-by: yaroslavborbat <[email protected]>
++ patch port in kubevirt webhooks, remove WEBHOOK_PROXY=no, add rules with all known webhook paths Signed-off-by: Ivan Mikheykin <[email protected]>
- Use KUBECONFIG env in all CDI and Kubevirt controllers. - One template for no-webhook-proxy configuration. - Cleanups. Signed-off-by: yaroslavborbat <[email protected]>
++ vm-controller: force application/json ++ simplify ownerReferences renaming ++ fix proxy in virtualization-controler deployment ++ make proxy container first in virtualization-controller, add default-container annotations ++ fix goroutines deadlock and possible DATA RACEs in kube proxy ++ cleanup debugging and dev time code Signed-off-by: Ivan Mikheykin <[email protected]>
Signed-off-by: yaroslavborbat <[email protected]>
diafour
force-pushed
the
feat/rewrite_kv_resources
branch
from
864242a to
1840445
Compare
|
Close in favor of #73 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
New image with kube-api-proxy component. This proxy sits between some controller and a Kubernetes API Server to make controller request original resources while resoures in cluster are renamed.
New and updated components:
images/kube-api-proxy— new image for sidecar container that sits between controller and Kubernetes API serverimages/vmi-router— refactor to use IP address from VMs, moved to refactor(vmi-router): Use IP from our VirtualMachine #69artifact:toimage:in werf.inc.yamlcdikubevirtvirtualization-controllerWhy do we need it, and what problem does it solve?
Resource renaming allows to avoid naming clashes.
What is the expected result?
Checklist