posit-dev / posit-dev/team-operator
Team Operator should support tagging of cloud resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Currently the Team Operator creates cloud resources through the different providers installed on the cluster; however, these resources are created without tags. We should support setting custom tags at the site level so all the corresponding cloud resources contain these tags. These feature will require modification of the Site configuration and the addition of the tags to the different cloud resources like volumes and load balancers.
For reference:
-
Volumes config: https://github.com/rstudio/ptd/tree/6b3c6719acb6df9f9fcce51733d28255d1a3177c/team-operator/api/product
-
Traefik Load Balancer: https://github.com/rstudio/ptd/blob/6d852d004350f03d70846429c6d895fc317b7ad8/ptd/src/ptd/pulumi_resources/traefik.py#L139
Migrated from rstudio/ptd#1549
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Site configuration in team-operator/api/core/v1beta1/site_types.go, then inspect the volume definitions under team-operator/api/product and the Traefik load balancer entry point in ptd/src/ptd/pulumi_resources/traefik.py. Trace how site settings reach each cloud resource and verify that custom site-level tags appear on volumes and load balancers across the relevant providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, python
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100