[读书笔记] The 16-point checklist for GitOps success


  •  We have adopted Kubernetes for container and infrastructure management:  -- Done 
  • We have documented a clear workflow between Application Development teams and the Platform team:  -- Not ready
  • We have trained teams on the new workflows and tooling:  -- Not ready
  • We have identified which changes can be automatically deployed to production, and which require a manual pull request:  -- Not ready
  • We have declared everything in Git (this includes applications, infrastructure, networking, and configuration):   --  Part Ready
  • We have decided on an initial structure for our Git repositories  --  Part Ready
  • We have selected the appropriate tooling that makes up our GitOps pipeline (Flux, Helm, Flagger, etc):  -- Done 
  • We have connected GitOps toolings like Flux, Helm, and Kustomize to our Git repositories:  --  Part Ready
  • We have configured Git webhook for build triggers:   --  Part Ready
  • We have completely automated GitOps Pipelines so that clusters are “always kept reconciled” with changes made in Git repositories:   --  Part Ready
  • We have automated a majority of testing:  -- Not ready
  • We have made test runs to automatically deploy changes to different environments using the new GitOps pipeline:   -- Not ready
  • We have decided where we would host our Kubernetes clusters (AWS EKS, Azure Arc, OpenShift, Bare Metal etc):  -- Done
  • We have set up policies to run security, resilience, and coding standards checks end-to-end from Git to pipeline tooling to Kubernetes clusters. (For example, leveraging a policy engine in Weave GitOps):   -- Not ready
  • We use dedicated secrets management service to manage sensitive data:    --  Part Ready
  • We have ensured that only Platform Engineers have direct access to production Kubernetes clusters (not developers):   -- Not ready


Comments

Post a Comment

Popular posts from this blog

Small summery of ElasticSearch meetup

https://www.elastic.co/guide/en/elasticsearch/reference/current/_basic_concepts.html https://en.wikipedia.org/wiki/Document-oriented_database Configuration (a.k.a Design) matters a lot. Big performance impact to user. Design the configure based on the query pattern of users. Dual scoring model :  Bool query && ?? Shingles , 类似有pairwise，把一个句子里面的单词(token)没连续两个分组，比如 Hello the beautiful world -> [Hello the], [the beautiful], [beautiful world] Kopf:  https://github.com/lmenezes/elasticsearch-kopf, web admin page for elesticsearch
Read more

Such a cold summer

I almost did not wear the t-shirt alone this summer, always have a jacket on when I went outside. Most of time the temperature is lower than 20 c-degree. Totally did not get the feeling of summer. What a pity.
Read more

读书笔记 - 7 Ways Managers Can Help Their Team Focus

 https://hbr.org/2023/01/7-ways-managers-can-help-their-team-focus Inventory tasks and projects. This is a discipline where common sense is not common practice. If your people don’t have a complete list of their commitments and projects, they can’t realistically prioritize. As a leader, hold people accountable for keeping current to-do lists and give them time each week to do a full weekly review of these commitments so they can stay in control. Clarify and curate communication channels. Most of our distraction is the result of a plethora of internal communication channels people must navigate in a typical workplace setting — and that’s not to mention actually processing the content in each channel. Clarify what each channel should be used for and the expectations around response times. Normalize saying no. Leaders need to create psychological safety around airing overwhelm and burnout. One brilliant example comes from Rich Sheridan, CEO of Menlo Innovations, a custom software deve...
Read more