forked from openshift/origin
-
Notifications
You must be signed in to change notification settings - Fork 0
Buildlogs fix #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged by openshift-bot
…viewers Merged by openshift-bot
…-access-review Merged by openshift-bot
Using build-go should only build the primary binaries. The only place where image binaries need to be built is during build-cross via the release image. Removing the image binaries from build-go speeds up typical local builds. Closes openshift#1044
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
…tils Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
…_admission Merged by openshift-bot
Merged by openshift-bot
Now you can run `source hack/export-certs.sh <path_to_cert_dir>` and the proper certs are set in your env
Need to work with go-systemd to see if we can abstract the syscall.CloseOnExec which is not supported on windows.
Nodes will now assume the master is a DNS server (unless OPENSHIFT_DNS_ADDR is set) and will pass that value in to the containers they run. The master will listen on 53 (if it can bind to it) or 8053 to serve DNS queries.
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
Need to work with go-systemd to see if we can abstract the syscall.CloseOnExec which is not supported on windows.
It currently is impossible to use two healthz handlers on different ports in the same process. This removes the global variables in favor of requiring the consumer to specify all health checks up front.
Reflects an upstream change to weed out inconsistency in the cluster.
Author
|
Sorry to wrong branch, fixed in #9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to fix your problem from here regarding build logs. The problem is that upstream adds currently
http://by default in the redirector (see here) but they didn't (see here)It's flaky IMHO, they should allow you to set the Scheme for yourself, don't you think?