chore: deploy 2023.02 to QA-PRC

[atharvar28]

Link to Jira ticket if there is one:

Environments

Description of changes

[PlanXCyborg]

qa-covid19.planx-pla.net/manifest.json

Deployment changes

• awshelper
  • Add .global.karpenter to manifest if you'd like to use karpenter. (feat(karpenter): Added configuration to use karpenter instead of clus… cloud-automation#2128)
  • To set up the metadata-delete-expired-objects job, run the gen3 kube-setup-metadata-delete-expired-objects-cronjob command. Note that the metadata-delete-expired-objects-job client must be granted access to (resource=/mds_gateway, method=access, service=mds_gateway) and (resource=/programs, method=delete, service=fence) ((PXP-9516): Add metadata-delete-expired-objects job cloud-automation#1941)
  • Currently requires to manually update prisma api key in json format under this path in the adminvm (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • ~/Gen3Secrets/prisma/apikey.json (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • format has to be the following: (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • { (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • "AccessKeyID": "XXXX", (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • "SecretKey": "XXXX" (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • } (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
  • This PR extends kube-setup-hatchery to create a kubernetes secret with for prisma cloud credentials, and extending the hatchery deployment to look for this secret and use it, if it exists. (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
• dashboard
  • This change will add some CSP and CORS related header to the response that returned from the dashboard services. They should not be interruptive, but each team is encouraged to double check their webpages hosted by dashboard to ensure they still works (fix: sec patch gen3-statics#27)
  • Because of these CSP directives being added, starting from this version, if anyone what to load remote scripts in their dashboard-hosted webpages, they will need to update the CSP directives in this dashboard service if the current directives doesn't fit, or to ship the script files with the page (fix: sec patch gen3-statics#27)
• fence
  • Requires a Fence DB migration (PXP-10541 Client credentials rotation fence#1068)
• metadata
  • configuration files will need to be updated (PXP-8825 & BRH 206  metadata-service#65)
• sheepdog
  • Sheepdog does not rely on configuration files in the cloud-automation repository anymore. The Sheepdog configuration files are in the Sheepdog repository. (PXP-6245 PXP-9633 Poetry + Python 3.9 sheepdog#387)

Breaking changes

• arborist
  • The GET /auth/mapping endpoint does not accept username as a query parameter anymore. It only supports parsing the username from the provided JWT. To specify a username, use the POST /auth/mapping endpoint. (PXP-10229 Client auth mapping arborist#153)
• indexd
  • Ensure you are using Fence>=2021.10. Remove deprecated GA4GH access endpoints. these have existed (and been used) from the Fence microservice since last year. See cloud automation change here (Revert "Revert "fix(migrate): improve acl->authz migration, remove de… indexd#338)
• metadata
  • The configuration file is not compatible with the previous release. This is due to the new support for defining a schema, new configuration options, and changes to the adapters. (PXP-8825 & BRH 206  metadata-service#65)