h1. Feature Overview

• Need ability to use cluster-proxy addon while cluster-wide proxy is enabled

h2. Goals

• In the customers environment all of the clusters are behind a corporate firewall but they would like to take advantage of the cluster-proxy addon feature.

h2. Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

h2. (Optional) Use Cases

This Section:

• Utilization of cluster-proxy addon feature in cluster-wide proxied environment

h2. Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

h2. Assumptions

• ...

h2. Customer Considerations

• ...

h2. Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)? End user configuration docs
• Does this feature have a doc impact? Yes
• New Content, Updates to existing content, Release Note, or No Doc Impact: release note
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)? use of an existing feature in a limited environment
• What reference material might a customer want/need to complete [action]? none
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available. No
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)? Update existing