Skip to content

Conversation

cilasbeltrame
Copy link
Collaborator

@cilasbeltrame cilasbeltrame commented Sep 6, 2025

What type of PR is this? (check all applicable)

  • πŸ• Feature
  • πŸ› Bug Fix
  • πŸ“ Documentation
  • πŸ§‘β€πŸ’» Refactor
  • βœ… Test
  • πŸ€– Build or CI
  • ❓ Other (please specify)

Related Issue

Create argocd app and overwrites for drone tm stage and prod environments

Describe this PR

Towards k8s migration, a helm chart has been created at hotosm/drone-tm#591 and this PR setups up argocd applications and overwrites for stage/prod. Still need to created the sealed secrets though

@spwoodcock spwoodcock self-assigned this Sep 10, 2025
Copy link
Member

@spwoodcock spwoodcock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This setup looks good! A namespace for prod & a namespace for stage per app works fine πŸ‘

ingress:
enabled: true
hosts:
- host: api.drone-tm-staging.hotosm.org
Copy link
Member

@spwoodcock spwoodcock Oct 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you advise this flatter URL structure like:

  • drone-tm-staging.hotosm.org
  • drone-tm-dev.hotosm.org
  • drone-tm.hotosm.org

Or a subdomain approach I have used elsewhere:

  • stage.drone-tm.hotosm.org
  • dev.drone-tm.hotosm.org
  • drone-tm.hotosm.org

Or perhaps it makes no difference / no preference?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants