What risks are associated with merging this PR? What is required to fully test this PR?
No risks, PR can be tested by setting custom labels in the settings UI and observing that custom labels have carried over to the allocations page
How was this PR tested?
Put a custom image of this PR on qa-eks3 controller namespace, changed custom labels in settings UI, observed new custom label was working properly in the allocations UI. Also checked the apiconfig.json file in the aggregator pod, which contained all the expected custom label configurations.
Have you made an update to documentation? If so, please provide the corresponding PR.
What does this PR change?
Nginx config for get and set api config endpoints in aggregator
Does this PR rely on any other PRs?
https://github.com/kubecost/kubecost-cost-model/pull/2575
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Fix a bug that broke custom labels
Links to Issues or tickets this PR addresses or fixes
https://kubecost.atlassian.net/browse/ENG-2392
What risks are associated with merging this PR? What is required to fully test this PR?
No risks, PR can be tested by setting custom labels in the settings UI and observing that custom labels have carried over to the allocations page
How was this PR tested?
Put a custom image of this PR on qa-eks3 controller namespace, changed custom labels in settings UI, observed new custom label was working properly in the allocations UI. Also checked the apiconfig.json file in the aggregator pod, which contained all the expected custom label configurations.
Have you made an update to documentation? If so, please provide the corresponding PR.
No docs needed