-
Notifications
You must be signed in to change notification settings - Fork 829
Proposal for integration with PromOp CRDs #6985
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Bogdan Stancu <[email protected]>
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 general I feel Cortex should be environment agnostic similar to Prometheus. It should work in any environment like Kubernetes, VMs, etc.
I am not sure if we want first class Prometheus Operator CRD integration in Cortex. I see it to be an ecosystem project that syncs Prometheus Operator CRDs and updates in Cortex accordingly
Currently, Cortex Alertmanager configuration can be managed through: | ||
1. Direct HTTP API calls to set/update configurations and rules (when enabled) | ||
2. Command-line tool for configuration management (cortextool) | ||
3. Manual change of the persisent storage |
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.
3. Manual change of the persisent storage | |
3. Manual change of the persistent storage |
I have to say, though. There is a crossplane integration for this https://github.com/swisscom/provider-cortex ping @janwillies @mleahu |
1. Direct HTTP API calls to set/update configurations and rules (when enabled) | ||
2. Command-line tool for configuration management (cortextool) | ||
3. Manual change of the persisent storage | ||
4. I might be missing somehting? |
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.
4. I might be missing somehting? | |
4. I might be missing something? |
Hello all, opening this for the discussion.
I am not sure how "needed" this feature is but would love to hear your feedback and suggestions. I have not thought about it thoroughly, not sure about implementation details, just wanted to hear opinions on this. I think it does make a lot of sense for deployments with many users across different clusters/regions.