Support http proxy configuration using a topology webhook #30
Comments
|
Brilliant idea! How would a cluster opt in to this though? Label selector? Possibly using annotation? Thinking about multiple clusters in same NS, that have different proxies to use. |
|
@dlipovetsky Why is |
|
@jimmidyson Looks like I grabbed that string from our an internal e2e test, which happens to run in AWS. |
|
Done! |
supershal
added a commit
to dlipovetsky/capi-runtime-extensions
that referenced
this issue
Apr 5, 2024
…nix-cloud-native#23) * test: unit test for individual patch generator * test: package level unit test for HTTPProxy * test: move region and httpproxy patch generator unit test invocation * fix: linting errors * test: move all AWS patch unit tests to their own packages (nutanix-cloud-native#24) * test: move instanceprofile tests to its own package * test: move instancetype unit tests to its own package * test: move ami unit tests to its own package * test: move aws network tests to its own package * test: move controlplaneloadbalancer unit tests to its own package * test: move aws cni unit tests to its own package * test: fix linting errors * test: unit tests for AWS security groups * test: move customimage unit tests to their own package (nutanix-cloud-native#30) * test: move all Nutanix patch handler unit tests (nutanix-cloud-native#32) * test: move controlplane endpoint unit tests * test: move PC endpoint unit tests * test: nove machinedetails unit tests * test: move generic patch unit tests to own packages (nutanix-cloud-native#31) * test: move audit policy tests to their own package * test: move etcd unit tests to their own package * test: move extra api server cert sans to its own package * test: move image registry unit tests to its own package * test: move kubernetes image repository unit tests * test: move mirror unit tests * test: move users unit tests * test: remove gereric unit tests from nutanix meta patch handler * test: cleaned up meta level unit test suites
jimmidyson
pushed a commit
that referenced
this issue
Apr 11, 2024
* test: unit test for individual patch generator * test: package level unit test for HTTPProxy * test: move region and httpproxy patch generator unit test invocation * fix: linting errors * test: move all AWS patch unit tests to their own packages (#24) * test: move instanceprofile tests to its own package * test: move instancetype unit tests to its own package * test: move ami unit tests to its own package * test: move aws network tests to its own package * test: move controlplaneloadbalancer unit tests to its own package * test: move aws cni unit tests to its own package * test: fix linting errors * test: unit tests for AWS security groups * test: move customimage unit tests to their own package (#30) * test: move all Nutanix patch handler unit tests (#32) * test: move controlplane endpoint unit tests * test: move PC endpoint unit tests * test: nove machinedetails unit tests * test: move generic patch unit tests to own packages (#31) * test: move audit policy tests to their own package * test: move etcd unit tests to their own package * test: move extra api server cert sans to its own package * test: move image registry unit tests to its own package * test: move kubernetes image repository unit tests * test: move mirror unit tests * test: move users unit tests * test: remove gereric unit tests from nutanix meta patch handler * test: cleaned up meta level unit test suites
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To configure the cluster control and data plane to use an HTTP proxy, users need to provide two pieces of information:
HTTP_PROXY,HTTPS_PROXYenv vars)NO_PROXYenv var)Providing (1) is trivial.
Providing (2) is not; values include localhost names and IPs, the cluster Pod network CIDR, Services CIDR, the cluster DNS zone, the "metadata service," and some infrastructure-dependent values. A typical value for a cluster in AWS might be:
A user can discover these different values, but doing so is a lot of work. A topology webhook should be able to derive most (hopefully, all) the required values for the user, and allow the user to provide optional values in addition to the required ones.
The text was updated successfully, but these errors were encountered: