kubernetes-sigs/cluster-api-provider-aws

Document or support running in environments with TLS intercepting proxies

Open

#491 opened on Jan 13, 2019

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Go (689 forks)auto 404
help wantedkind/documentationkind/featureneeds-triagepriority/backlogpriority/important-longterm

Repository metrics

Stars
 (723 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature

Describe the solution you'd like As a result of triaging on an issue in Slack by @ashish-amarnath, it was found a user could not run the AWS provider because the network they were running in used TLS intercepting transparent proxies.

This is fairly common in enterprise environments, up to and including the target AWS infrastructure.

We should either document image customisation in these scenarios, and/or provide a mechanism to inject a CA Certificate into the certificate bundle that will be used to make AWS API requests.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-aws version: v1.0.0-alpha.4
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.