-
Notifications
You must be signed in to change notification settings - Fork 463
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
Restore tenant configuration for Loki forwarder. #842
Restore tenant configuration for Loki forwarder. #842
Conversation
a5141ff
to
f62057c
Compare
@@ -148,6 +148,12 @@ The following optional output fields are Loki-specific: | |||
Example: `kubernetes.labels.foo` => `kubernetes_labels_foo`.\ | |||
**Note**: `kubernetes.host` is *always* be included, even if not requested. | |||
It is required to ensure ordered label streams. | |||
- `tenantKey`: (string, default=`"kubernetes.namespaceName"`) \ |
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.
We don't provide a default for in-cluster.
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.
In addition do we really want to define as tenant key a label key or simply leave it as arbitrary data?
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.
A fixed tenant ID limits us to static tenants pre-defined by the log admin based on input filters. This has turned out to be inadequate for other cases (JSON, cloudwatch groups etc.), where the logging system needs to respond to new label values or new namespaces appearing in the cluster without a manual re-config each time. I think the same applies to tenants - you can't implement "namespace as tenant" without it unless you know all your namespaces in advance.
0a533bf
to
63d9314
Compare
7f74862
to
2ada059
Compare
@periklis @jcantrill can I get an LGTM here? This brings the enhancement proposal up to date with the code that merged to the CLO. |
This configuration will not be required for our default Loki instance, but may be required for custom Loki instances.
2ada059
to
e147186
Compare
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcantrill 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 |
This configuration will not be required for our default Loki instance, but may be required for custom Loki instances.
/cc @periklis
/assign @jcantrill