[读书笔记] 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

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

My Unsolve Questions

How to reduce the admin work for tester? test Measurement, Management, Communication, Automation.  Agile: Test Might take longer time than development.  How to solve that in Agile? how to make exp test efficient in scurm. does tester be scurm master better sit with developer or tester in scrum should we can Quality advisor Automation test negitive test?
Read more

My interview questions to a company using SAFe.

What is the setup of your QA team?  What is the ratio of Test vs Developer Do you have the system layer test?  Do you have the non function test layer?  How do you divide the train, do you have plat form team, and do they have their own train? Any support work in the team` What is the good part, and what is the bad part How long does the team learn how to do PI planning.  What is the biggest challenge you meet,  Did you have any challenge when you split up the team?  Any suggestion on how to devide the team, and what is the practise in lego.  In the new setup, is it possible different team work on a same product of same feature?  BDD:  In which level do you apply the BDD, how do you use it in integration level? who responsible for design and implemented BDD? Agile: What is your product, do you have technical(platform) team, how do you make them work in the agile framework.  Special list can swap among ...
Read more