Support CoreOS with http proxy #3032
Comments
17 tasks
k8s-github-robot
pushed a commit
that referenced
this issue
Aug 7, 2017
Automatic merge from submit-queue Add support for cluster using http forward proxy #2481 Adds support for running a cluster where access to external resources must be done through an http forward proxy. This adds a new element to the ClusterSpec, `EgressProxy`, and then sets up environment variables where appropriate. Access to API servers is additionally assumed to be done through the proxy, in particular this is necessary for AWS VPCs with private topology and egress by proxy (no NAT), at least until Amazon implements VPC Endpoints for the APIs. Additionally, see my notes in #2481 TODOs - [x] Consider editing files from nodeup rather than cloudup - [x] Add support for RHEL - [x] Validate on RHEL - [x] ~Add support for CoreOS~ See #3032 - [x] ~Add support for vSphere~ See #3071 - [x] Minimize services effected - [x] ~Support seperate https_proxy configuration~ See #3069 - [x] ~Remove unvalidated proxy auth support (save for future PR)~ See #3070 - [x] Add Documentation - [x] Fill in some sensible default exclusions for the user, allow the user to extend this list - [x] Address PR review comments - [x] Either require port or handle nil - [x] ~Do API validation (or file an issue for validation)~ See #3077 - [x] Add uppercase versions of proxy env vars to cover our bases - [x] ~File an issue for unit tests~ 😬 See #3072 - [x] Validate cluster upgrades and updates - [x] Remove ftp_proxy (nothing uses)
|
@KashifSaadat can we close this? |
|
Yeah, this issue can be closed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are moving HTTP Proxy support in soon, but I have zero idea how to support CoreOS. If someone wants to have support, feel free to submit a PR.
The text was updated successfully, but these errors were encountered: