Mention monitoring-development cluster in onboarding instructions.
1 unresolved thread
1 unresolved thread
Compare changes
Conflict: This file was modified in both the source and target branches.
Ask someone with write access to resolve it.
@@ -44,6 +44,6 @@ Welcome [name] to the Monitor group! We're very excited to have you. This onboar
* [ ] New team member: When taking on a metrics dashboard-related ticket, [create an access request](https://gitlab.com/gitlab-com/access-requests/issues/548) for the "Kubernetes Engine Admin" role in Google Cloud Platform. This will allow you to test your changes in a [review app](https://docs.google.com/document/d/1SZD7hQ1F2A5Qaja1lLy1a-1fN89tXY8ZkkxAlaYcb7E/edit?ts=5c7fd1ad).
* [ ] New team member: When taking on a metrics dashboard-related ticket, [create an access request](https://gitlab.com/gitlab-com/access-requests/issues/548) for the "Kubernetes Engine Admin" role in Google Cloud Platform. Make sure to request access to both the general namespace (`gitlab-internal`) and the team specific one (`monitoring-development`). This will allow you to test your changes in a [review app](https://docs.google.com/document/d/1SZD7hQ1F2A5Qaja1lLy1a-1fN89tXY8ZkkxAlaYcb7E/edit?ts=5c7fd1ad).
\ No newline at end of file
Arguably new team members don't need access to
gitlab-internal. We could remove this from the instructions?monitoring-developmentkubernetes namespace through the google group. Could you just add as an item to first week?