ci: deploy develop to bitween-dev and releases to production

[MusaMisto]

What changes

Develop (releases/r10.0-develop) deploys to the bitween-dev namespace on the same dev cluster instead of playground. Nothing else about it changes: release bitween, app-dev.bitween.io, same values and secrets.

Release (releases/r10.0) now also deploys, to the bitween namespace on the production cluster (S9PROD_KUBECONFIG_V2), at app.bitween.io, as GitHub environment production:

• gateway-parent-namespace: s9-prod-edge. The production gateway is public-gateway in s9-prod-edge. With the default (s9-dev-edge), the onboarding step would create a second public-gateway there instead of failing.
• global.environment=Production, 2 replicas, the same resources as develop, bus providers on. Develop's AWS checksum experiment is not copied.
• Production's own settings come from PROD_* secrets, the same ten settings the develop job passes.
• deploy: ${{ vars.BITWEEN_PROD_DEPLOY == 'true' }}: off until the prerequisites below are done, so a release never installs with empty settings. Publishing and tagging don't depend on it.

Before setting BITWEEN_PROD_DEPLOY=true

1. Add the repo secrets PROD_TOKENKEY, PROD_DBCONNECTION, PROD_RABBITURL, PROD_ACCESSKEYID, PROD_SECRETACCESSKEY, PROD_SERVICEURL, PROD_BUCKETNAME, PROD_RABBITMQMANAGEMENTURL, PROD_RABBITMQMANAGEMENTUSERNAME, PROD_RABBITMQMANAGEMENTPASSWORD.
2. Share the org secret S9PROD_KUBECONFIG_V2 with this repo. It's private today, and GitHub withholds private org secrets from public repos.
3. Point app.bitween.io at the production gateway (164.90.243.23).

After merge (develop cutover)

1. The develop run installs bitween in bitween-dev.
2. helm uninstall bitween -n playground. Gateway API gives app-dev.bitween.io to the oldest HTTPRoute, so the playground route keeps the host until it's removed. Only the release goes; the namespace also hosts other apps.
3. simplify9/bitween-lab: faults.chaos.bitweenNamespace changes to bitween-dev. Its chaos Role lives in that namespace.

Checked

• actionlint passes, and neither helm-set-values block has a comment line.
• I ran the shared workflow's "Resolve deploy parameters" script with the production inputs. It produced parentRefs[0]=s9-prod-edge/public-gateway, release bitween, and onboards only app.bitween.io.
• helm template of charts/default with those values renders a single HTTPRoute (s9-prod-edge/public-gateway, app.bitween.io, /, /api, /swagger), ASPNETCORE_ENVIRONMENT=Production and Bitween__PublicUrl=https://app.bitween.io. Resource names are bitween, and nothing of that name exists in the production bitween namespace, which holds bitweenweb and bitweendocs.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (8)

• ^main$
• ^master$
• ^staging$
• ^development$
• ^gigstaging$
• ^develop$
• ^releases$
• ^releases/r10.0$

---

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: simplify9/coderabbit/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d3f5d28e-ce89-4f30-ae9c-951ec75ea8f9

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}