Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Oct 29, 2019

Drop the wording from aa39bf3 (#16635), because the network operator explicitly supports both the http and https schemes since openshift/cluster-network-operator@42dbcf8955 (openshift/cluster-network-operator#245), which landed before release-4.2 split off from the network operator's master. This should be backported to 4.2 as well.

CC @bergerhoffer, @danehans

Drop the wording from aa39bf3 (OSDOCS-640: Adding docs for
configuring proxy during installation, 2019-09-12, openshift#16635), because
the network operator explicitly supports both the 'http' and 'https'
schemes since openshift/cluster-network-operator@42dbcf8955 (Refactors
PR to focus on http/https/no proxy reconciliation, 2019-08-06,
openshift/cluster-network-operator#245), which landed before
release-4.2 split off from the network operator's master.
@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 29, 2019
@wking
Copy link
Member Author

wking commented Oct 29, 2019

And I'm still not clear on why you can't use https for httpProxy, but at least that documented restriction is reflected in the current network-operator validation.

@wking
Copy link
Member Author

wking commented Oct 30, 2019

Also discussion here. It's not clear to me if/where the "old Git's don't like HTTPS proxies" limitation is tracked outside of the Bugzilla, but I think calling it out in as a build limitation (for some builds? All builds?) makes more sense than saying that it's completely unsupported (maybe folks are running clusters where HTTPS proxies are important but which won't use builds?).

@wking
Copy link
Member Author

wking commented Oct 30, 2019

Here are the release docs for the limitation. Not sure if/how we want to reference those from this master-branch PR. Thoughts?

@bergerhoffer
Copy link
Contributor

@danehans Since you originally asked for this restriction, can you confirm that it's okay to remove and to update the examples to use https? Thanks!

@wking And I'm on the fence about calling out the git clone known issue in these sections. We don't necessarily repeat the known issues in the relevant doc sections. But if you think it's a big enough restriction that we think users will frequently run into, then we could just mention it right in the descriptions here for httpsProxy.

@kalexand-rh
Copy link
Contributor

@danehans, will you PTAL?

@vikram-redhat
Copy link
Contributor

@danehans BUMP.

@wking can you rebase?

@wking
Copy link
Member Author

wking commented Oct 12, 2020

#25438 landed the softening, so we don't need this PR anymore.

/close

@openshift-ci-robot
Copy link

@wking: Closed this PR.

Details

In response to this:

#25438 landed the softening, so we don't need this PR anymore.

/close

Instructions 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.

@wking wking deleted the httpsProxy-allow-https branch October 12, 2020 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.2 branch/enterprise-4.3 size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants