pkg/asset/manifests/proxy: Create new proxy manifest#1866
pkg/asset/manifests/proxy: Create new proxy manifest#1866openshift-merge-robot merged 3 commits intoopenshift:masterfrom
Conversation
|
/cc @abhinavdahiya |
|
The asset currently is not being pushed to the cluster.. this assets needs to be wired like other config.openshift.io objects like installer/pkg/asset/manifests/operators.go Line 124 in a99bd59 secondly another commit that updates the assets dep graph https://github.com/openshift/installer/blob/master/docs/design/assetgeneration.md#dependency-graph will be nice. |
Update vendor dir to pull in the ProxyStatus which was added to proxies.config.openshift.io.
ddcb42a to
285272f
Compare
I have updated the graph. manifests.Proxy shows up but I don't see an installConfig.Proxy. Should installConfig.Proxy be in the graph as well? My branch is up-to-date. |
EDIT: added sorting to status.noProxy values |
285272f to
ca992ab
Compare
@patrickdillon |
Update the design doc asset graph to include the addition of the proxy manifest.
ca992ab to
598008d
Compare
I removed the I should probably remove the Also did you see my question about installConfig.Proxy in the graph: #1866 (comment)? |
The dependency graph is better assets... Not parts of assets. So I think it's expected that manifest.proxy which is an asset has dependency on entire install config asset. |
Yes. I think you can net.ParseURL and then use Host field to add to NoProxy list... |
Create a proxy manifest asset for proxies.config.openshift.io. The Proxy spec is based on values read from the install config. This commit introduces logic to create the NoProxy status value by combining the user-provided values from the install config with default values for the cluster, such as the internal API server. These values are combined into a comma-separated string of unique values. JIRA: CORS-1074 & CORS-1075
598008d to
ddb589f
Compare
|
|
|
@patrickdillon: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, patrickdillon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Add proxy manifest to create config files and Proxy CR when users have a proxy for their cluster.
This PR uses a similar template to other manifests. There is some special logic for handling the NO_PROXY values. First, it generates values that need to be added to the NO_PROXY. Then there is a check to make sure if the user added those values, we will only include it once. I'm not sure if this check is necessary. (There is not currently a check to make sure the user's values are unique, but we could handle that in validation.)
JIRA: CORS-1074