# Roadmap review --- ## :pencil: Agenda - Review of the Quarter's Goals and Objectives - Progress update on each Initiative - Risks/Dependencies/Blockers - Recap and follow-up --- ## :dart: Review of the Quarter's Goals and Objectives :point_right: [Miro Board](https://miro.com/app/board/uXjVPDaoP8Q=/) 1. [CircleCI + Kubegen](https://commercetools.atlassian.net/browse/SD-5) 2. [Atlas <> Okta](https://commercetools.atlassian.net/browse/SD-1) 3. [Create new envs easier and faster / maintenance](https://commercetools.atlassian.net/browse/SD-7) 4. [Kubegen Improvements](https://commercetools.atlassian.net/browse/SD-6) 5. JIRA Migration 6. China Support --- ### :diamonds: Progress update on each Initiative #### :one: [CircleCI + Kubegen](https://commercetools.atlassian.net/browse/SD-5) :train2::ok_hand: - [reference_service](https://github.com/commercetools/reference_service) is now integrated with kubegen and is deployed to all envs. - [commercetools-exporter](https://github.com/commercetools/commercetools-exporter/) is also deployed with kubegen on `ctp-staging`. - [`ctp-mongo-sharding-test`](https://github.com/commercetools/ops-terraform/pull/3767) is in progress. --- #### :trophy: Key takeaways and next steps - Our documentation is getting more and more consumed, and suporting our end goal of self-service onboarding to kubegen. - RBAC on k8s clusters is ==_not_== a pleasant experience, especially for new services. Yann has shared his experience of onboarding a new service [here](https://commercetools.atlassian.net/l/cp/bu1ynVbV) - We have better understanding of our ownership in vault config which is anything related to `kubegen` and `atlas` _only_. - TeamQL, Pangolin and BMU would continue to integrate with vault/kubegen. - We have an [issue template](https://github.com/commercetools/special-delivery/issues/968) to onboard teams to vault/kubegen. --- #### :two: [Atlas <> Okta](https://commercetools.atlassian.net/browse/SD-1) :train2::ok_hand: - Okta groups are created by Internal IT. Oncall groups (SRE/Dev) are pending. - Okta IdP is enabled on `dev-commercetools` org. - Automation Development team is aligned with us regarding the impact on 4eyes bot. AD to use OKTA API to manage elevated access instead of Atlas API. --- #### :trophy: key takeaways and next steps - Please join [tmp-mongo-4eye-okta](https://commercetools.slack.com/archives/C052JREBGSH) group, if not done already. - Internal IT should own the Okta groups. Users should request permissions for Atlas via Internal IT with their supervisors' approval. - We should be able to continue with next steps e.g. creating Atlas role mappings programatically. --- #### :three: [Create new envs easier and faster / maintenance](https://commercetools.atlassian.net/browse/SD-7) :construction: :seedling: - Sergey did a [walkthru](https://hackmd.io/@ct-zonorti/H1n1p4Jen) for the team to understand the problem statement and how the env creation happens currently. - This is a research topic and the expectation is to have a plan at the end of the quarter which describes the problem areas with the current process and potential candidates that can be picked for implementation in Q3, we should prefer something that can be actionable by SD. --- #### :trophy: key takeaways and next steps - We had a discussion with Aron to get him onboarded, Marina was also part of the discussion. - This entire topic needs revisit. We might need to scope it down to SD related topics. --- #### :four: [Kubegen Improvements](https://commercetools.atlassian.net/browse/SD-6) :train2::ok_hand: - We started working to integrate `ctp-mongo-sharding-test` with `kubegen`. - Continued improving our user documentation. - Support for `VAULT_ADDR` in `kubeconfig` --- #### :trophy: key takeaways and next steps - [#kubegen-connect](https://commercetools.slack.com/archives/C0549JXCBJQ) to collect topics/queries about `kubegen` related topics. - We need to incorporate changes to the [documentation](https://github.com/commercetools/special-delivery/issues/899#issuecomment-1514644737) about shared vault-context so that teams can themselves do the change in their pipelines. - UX improvements : kubegen without flags should prompt about usage. --- #### :five: JIRA Migration - Epics are created on our Project board. - Issues/Updates are continuously updated on the Epics. We as a team should practice this more. - Tempate proposal for external support requests. We should promote users to create external requests on JIRA in line with this new template?? --- #### :six: China Support :arrows_counterclockwise::computer: - Image Webhook was rolled out successfully to China. :trophy: - There has been continous involvement of Michael/Sergey regarding networking and project management topics. --- #### :trophy: key takeaways and next steps - Clean-up and improvements to monitoring. --- #### :seven: Ad-Hoc Requests :arrows_counterclockwise::computer: - [Puppet decommission](https://github.com/commercetools/special-delivery/issues/970) - [atlas-logs-k8s refactoring to push logs to Cloud buckets](https://github.com/commercetools/special-delivery/issues/971) --- ## :exclamation: Risks/Dependencies - We are ==_low_== at capacity. Only 2 full time engineers for next 2 months. There should be some planned vacations as well. - We also need to account for unplanned work, on-calls, sick-offs etc. - We have dependencies on cloud-tools and cumulus for env creation/maintenance topic. We also rely on Internal IT and AD team for Atlas <> Okta integration. Though this seems to be going fine atm. --- ## 💬 Feedback and Input Please feel free to share your thoughts and inputs. --- :pray: Thank You :pray: ---