-
Notifications
You must be signed in to change notification settings - Fork 417
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
option to use nginx cache #3590
base: develop
Are you sure you want to change the base?
Conversation
|
||
# aggregatorFailoverSvc is experimental and only supported with Kubecost Enterprise | ||
# location of the aggregator service to use as a failover | ||
# aggregatorFailoverSvc: kubecost2-aggregator.kubecost2.svc.cluster.local:9004 |
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.
Should this be uncommented and just add a section for "aggregatorFailover.enabled"?
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.
I'd probably have both an enabled
field as well as a service address field.
What does this PR change?
Does this PR rely on any other PRs?
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Links to Issues or tickets this PR addresses or fixes
What risks are associated with merging this PR? What is required to fully test this PR?
How was this PR tested?
Have you made an update to documentation? If so, please provide the corresponding PR.