-
Notifications
You must be signed in to change notification settings - Fork 16
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
Merge tag directxman12/v0.4.1 into openshift/master #8
Merge tag directxman12/v0.4.1 into openshift/master #8
Conversation
Update README to container resource metrics API
Support custom ca certificate to talk to Prometheus
Add a separate flag for 'start' parameter
Often prometheus is gated by some proxy requiring an auth bearer token. Currently there is no possibility to configure one except for providing a full-fledged kubeconfig. This fixes it by adding a new flag pointing to an optional file containing the auth bearer for prometheus communication.
cmd/adapter: add prometheus bearer token configuration
Fix empty pod or node list resulting in an error
@mxinden the easier, the better! 👍 Back then the hacky way was necessary as the merge wasn't that easy. |
@mxinden now I have finally a bit more air to explain more context. Note that in the past the merge wasn't easy, hence the above "fancy" method. The above commands simply create a commit object as per https://git-scm.com/book/en/v2/Git-Internals-Git-Objects#_git_commit_objects without any merge logic applied. You need to make sure yourself though that the tree is properly merged somehow as you recognized. Back then creating a merge commit manually was simply easier than going through git's internal merge conflict resolution commit by commit. The prerequisite was nevertheless to introduce a proper merge commit manually, which in PR #3 was this commit: c3ac351. The "fancy" commands just ensure that there is a common commit object pointing to both trees in the commit history retaining original authors and original commit hashes. also cc @bison fyi |
Thanks @s-urbaniak for the details. Merging this branch locally ( @brancz would we need an exception to get this merged?
|
When the merge is big or if I have doubts, I compare the upstream tag and the PR like this: kubernetes-sigs/prometheus-adapter@v0.4.1...mxinden:merge-directxman12 The diff is usually small enough that I can review it and spot merge conflicts that weren't resolved properly. |
As this is a bug fix, no need for exception. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brancz, mxinden The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Tested basic |
Instead of using the fancy method by @s-urbaniak:
this PR simply does a:
as suggested by @simonpasquier.
Reasoning behind this is that #7 is missing #6 and thereby the Dockerfiles in the root of the directory. Doing a
git log --full-history -- Dockerfile
reveals that the merge commit itself deletes them.Do people have thoughts on the way we want to proceed here?