-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Create default Mixer config YAMLs #866
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question/nit (non blocking): Can we bundle logs, metrics, prometheus as one YAML ? Does it make sense to deploy them individually, such that one can be used without the other? If not, I suggest using a single mixer-metrics-addon.yaml (Not even sure if this should be an addon or just be enabled by default).
Even if prometheus is unavailable, mixer keeps collecting metrics right? So, we can have it on by default.
@rshriram I don't want to bundle logs with any of the metrics stuff. It arguably could be two files itself (one for the adapter config, one for the logentry). But it is distinct, in the Mixer sense, from the metrics stuff. The metrics stuff can be used separately from @mandarjog thoughts on the |
We should bundle prometheus with related metrics. Regarding using fully qualified instance and handler names inside actions, namespace can be elided from those names. We do this is configs checked into Mixer repo. Let us get some feedback from users if short names are desirable over fully qualified names while operating within a namespace. |
PTAL. I moved the "default" Mixer YAMLs for metrics and logs into the template for mixer itself. This simplifies the number of files, etc. I also stripped some of the explicit namespacing. |
I don't fully like the idea of installing config resources in a namespace of our choice - That said, this does get us back to parity with 0.1. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mandarjog Assign the PR to them by writing 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 |
@mandarjog Filed #878 |
Merging, in advance of internal testing to allow for proper out-of-the-box Mixer experience. |
Automatic merge from submit-queue. Add release-note collector **Release note**: ```release-note none ``` It's a binary to collect release-note from repos. Example command: ``` Bash $ bazel-bin/toolbox/release_note_collector/release_note_collector --repos istio --previous_release 0.2.2 --current_release 0.2.4 --pr_link ``` And the release-note would be put into a local file, default is in current directory, named "<repo>.releasenote" The example output is: ```Bash $ cat istio.releasenote istio: istio -- 0.2.4 release note Previous release version: 0.2.2 * Provide default Mixer configuration for prometheus metrics and stdio logs. istio/istio#866 * test setup doc update istio/istio#831 * New config model (breaking change). Migration instructions are [here](https://github.com/istio/istio/blob/release-0.2/samples/CONFIG-MIGRATION.md) istio/istio#829 ```
Add the Handler configuration logic. Handler configurer identifies and configures all the handlers that needs to be configure and infer the types to pass them. Former-commit-id: d5caf7b7fd750f103390ca71ea999dd6e30bc50a
* Create default Mixer config YAMLs * Update bookinfo BUILD * Refactor configs to mixer yaml template * delete metrics.yaml Former-commit-id: 70a8218
Add the Handler configuration logic. Handler configurer identifies and configures all the handlers that needs to be configure and infer the types to pass them. Former-commit-id: 52092f162abd315ce406139749097ebfe72b1643
* Create default Mixer config YAMLs * Update bookinfo BUILD * Refactor configs to mixer yaml template * delete metrics.yaml Former-commit-id: 70a8218
* Create default Mixer config YAMLs * Update bookinfo BUILD * Refactor configs to mixer yaml template * delete metrics.yaml Former-commit-id: 70a8218
Automatic merge from submit-queue. Add release-note collector **Release note**: ```release-note none ``` It's a binary to collect release-note from repos. Example command: ``` Bash $ bazel-bin/toolbox/release_note_collector/release_note_collector --repos istio --previous_release 0.2.2 --current_release 0.2.4 --pr_link ``` And the release-note would be put into a local file, default is in current directory, named "<repo>.releasenote" The example output is: ```Bash $ cat istio.releasenote istio: istio -- 0.2.4 release note Previous release version: 0.2.2 * Provide default Mixer configuration for prometheus metrics and stdio logs. istio/istio#866 * test setup doc update istio/istio#831 * New config model (breaking change). Migration instructions are [here](https://github.com/istio/istio/blob/release-0.2/samples/CONFIG-MIGRATION.md) istio/istio#829 ```
This PR moves the "default" configs for mixer from the
samples/app/bookinfo/rules
dir to the maininstall/kubernetes/**
tree.This PR is needed because, without it, the install of mixer will be missing many important configs for basic operation, including:
prometheus
andstdio
adaptersTo make use of the new location for the Mixer configs, the e2e framework code was updated to replace the
istio-config-default
namespace with the namespace of the test. The various, now unnecessary YAML files in thesamples
directory were deleted.cc: @debianmaster, @karmab
Related issue: istio/old_issues_repo#59
Release note: