Merge master into Cassandra feature branch #101
Conversation
* Modify RBAC templates to allow navigator controller to create events for leader election and for sync messages. * Add a SuccessSync message to the ElasticSearch control. * Test for those events.
Automatic merge from submit-queue. Permit logging of events when RBAC is enabled * Modify RBAC templates to allow navigator controller to create events for leader election and for sync messages. * Add a SuccessSync message to the ElasticSearch control. * Test for those events. Fixes: #89 **Release note**: ```release-note NONE ```
Automatic merge from submit-queue. Only run Travis-CI tests for PRs and when master branch changes Fixes: #76 This PR should only run the Travis-CI tests once, for the PR not for the branch. Should speed up the time it takes to approve and merge small PRs **Release note**: ```release-note NONE ```
Automatic merge from submit-queue. Allow controller to patch events Fixes #95 ```release-note NONE ```
Automatic merge from submit-queue. Elasticsearch Pilot RBAC policies **What this PR does / why we need it**: Creates RBAC policies for created Pilot resources **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Fixes #92 **Release note**: ```release-note Automatically create RBAC policies for Pilots ```
|
/lgtm |
|
@wallrj: you cannot LGTM your own PR. In response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wallrj The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
Ah - it appears the submit queue is blocked because the |
|
@wallrj: The following test failed, say
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. I understand the commands that are listed here. |
|
Trying a PR from my fork instead: #103 |
…and-PRs Automatic merge from submit-queue. Revert "Only run Travis-CI tests for PRs and when master branch changes" Reverts #77 It appears we're not always running the `/pr` test any more (see #101). I'm reverting this change as I've not had this problem before we added this section. ```release-note NONE ```
Merge latest master, including:
Release note: