Skip to content
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

cost-allocation: Re-factor cost-allocation #1228

Assignees

Comments

@emirgens
Copy link
Contributor

emirgens commented Mar 4, 2024

Re-factor cost allocation to follow the new structure for infrastructure

Order of things

  • ## Create new resources (resources with new name, transfer data when starting to use it)
    • Keep legacy users and databases, install MI on all servers, old and new
    • Create MI and federated credentials for Github and Kubernetes
  • ## Use the new resources
    • Upgrade API to MI
      kubectl patch rr radix-cost-allocation-api -p '{"spec":{"radixConfigFullName":"radixconfig.dev.yaml"}}' --type merge --context weekly-11 kubectl patch rr radix-cost-allocation-api -p '{"spec":{"radixConfigFullName":"radixconfig.dev.yaml"}}' --type merge --context weekly-12 kubectl patch rr radix-cost-allocation-api -p '{"spec":{"radixConfigFullName":"radixconfig.platform.yaml"}}' --type merge --context eu-18 kubectl patch rr radix-cost-allocation-api -p '{"spec":{"radixConfigFullName":"radixconfig.playground.yaml"}}' --type merge --context playground-11 kubectl patch rr radix-cost-allocation-api -p '{"spec":{"radixConfigFullName":"radixconfig.c2.yaml"}}' --type merge --context c2-prod-25 kubectl patch rr radix-cost-allocation-api -p '{"spec":{"radixConfigFullName":"radixconfig.c2.yaml"}}' --type merge --context c2-11
    • Upgrade Flux
    • Upgrade Scanner to MI
    • Release API
    • Release Scanner
  • ## Cleanup

PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment