Write all to giantswarm tenant #215
Open
+11
−14
Conversation
This file contains 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
QuentinBisson
force-pushed
the
write-all-to-giantswarm-tenant
branch
from
fe77bf7
to
9d7a8c3
Compare
|
Trying this out on grizzly |
|
Oh I did not write anything ... So once we have the multi-tenancy POC running, we will most likely have giantswarm logs under 1 tenant only so the impact is that loki will most likely not like it (need to be scaled) on some installations with lots of traffic but this would allow us to create alerts based on logs on MCs and WCs alike when now it only works on MCs |
QuentinBisson
force-pushed
the
write-all-to-giantswarm-tenant
branch
from
9d7a8c3
to
7eaa4c3
Compare
|
@giantswarm/team-atlas I edited the top description. I forced pushed because the original main branch was too far behind |
Open
2 tasks
QuentinBisson
force-pushed
the
write-all-to-giantswarm-tenant
branch
from
7eaa4c3
to
ade3e56
Compare
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.
Towards giantswarm/roadmap#3726
This PR is the start of the move to multi-tenancy for logs. For the new datasources to work, we need to send all logs to the giant swarm tenant.
This might impact Loki on some installations which we might need to scale up (either the number of buckets or the pod resources)
Once this PR is merged, we can try to work on supporting self-service tenancy on pod logs?