-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Operator supports proxied clusters
-
False
-
False
-
Done
-
OCPPLAN-7777 - Operator-SDK has first-class support for OLM
-
OCPPLAN-7777Operator-SDK has first-class support for OLM
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
S
Goal:
Provides scaffolding/generation of code that allows an Operator to support running on a proxied cluster.
Why is this important:
Complete our e2e story for Operator supports "proxy-aware" infrastructure.
Production environments can deny direct access to the Internet and instead have an HTTP or HTTPS proxy available. OpenShift users can configure a cluster-wide proxy by modifying the Proxy object for existing clusters or by configuring the proxy settings in the install-config.yaml file for new clusters.
To support proxied clusters, OLM reads the cluster proxy config and populates the config as the environment variables in Operator’s deployment with HTTPS_PROXY or HTTP_PROXY.
In order to fully support proxied clusters end-to-end, those environment variables would also need to be passed down from the Operator deployment (added by the OLM) to the Operands as environment variables to pick up the proxy server by reading them off.
Desired Outcome:
- Option 1. SDK supports scaffolding/generation of code for an operand deployment + a solution to pass-down env vars or volume mounts from the Operator to the Operand either by default or when a certain config is there (e.g. proxy = true)
- Option 2. A solution to pass down env var to operand perhaps in operator-lib + we document the use case/usage guide for support proxied clusters
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>