FY20-Q4 Security IAVC OKR: Improve GitLab Security resilience and availability by creating independent GitLab Security environments => 50%
Key Results
-
Migrate all existing GitLab Security tooling and infrastructure to the new environments and document in envs list => 50% completed. Environments documented. Separate GCP account created. Migration did not take place yet because of unforeseen blockers with RackSpace (we're working on them to get unblocked)
-
Create Sec-prod
andSec-pre-prod
environments=> 100%, created, but migration to these environments has not started yet because of the issue with RackSpace.
-
Full adoption of a dedicated GitLab instance for tracking of security issues within the new environments => 0%, blocked on the issues above
GOOD
- Enumerated infrastructure and created a solid plan on how to migrate all Security infrastructure over to a new account
- Took time to make sure most infrastructure was stored as code in repos (terraform templates)
BAD
- Unforeseen block by 3rd party (RackSpace). This took us by surprise but stalled the whole effort completely for more than a month, because the 3rd party didn't have processes in place to handle our specific configuration request (single billing, multiple accounts)
- We were unaware of the possibility of circumventing the 3rd party and worth with Google directly
TRY
- ...
Edited by Jan Urbanc