mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-05-20 08:04:27 +00:00
6.4 KiB
6.4 KiB
CI/CD
- Introduction
- CI/CD Continuous Integration and Continuous Delivery
- Deployment Strategies
- CI/CD with Kubernetes
- Reports on the Enterprise CI/CD Market
- Awesome Lists
Introduction
- opensource.com: What is CI/CD?
- Wikipedia.org: DevOps
- Wikipedia.org: Continuous Integration
- Wikipedia.org: Continuous Delivery
CI/CD Continuous Integration and Continuous Delivery
- DZone: Continuous Integration: Servers and Tools Learning to Utilize DevOps with Servers and Tools
- sdtimes.com: CI/CD pipelines are expanding 🌟 The “basic” CI/CD pipeline includes five processes, which are: merge, build, test, package and deploy. All of these are individually defined so readers have a common reference point. The basic pipeline includes sub-pipelines associated with each step, such as moving artifacts from a build into a repository.
- devopsonline.co.uk: ChatOps, DevOps, ScrumOps and 5 Other Ops religions
- opensource.com: A beginner's guide to building DevOps pipelines with open source tools If you're new to DevOps, check out this five-step process for building your first pipeline.
- acloud.guru: How youtr org predicts your CI/CD pipeline
- dev.to: CI/CD Continuous Integration & Delivery Explained 🌟🌟
- mindtheproduct.com: The Product Managers’ Guide to Continuous Delivery and DevOps 🌟🌟
- tech.buzzfeed.com: Continuous Deployments at BuzzFeed
- Dzone refcard: Continuous Delivery - Patterns and Anti-Patterns in the Software Lifecycle 🌟
- infoworld.com: What is CI/CD? Continuous integration and continuous delivery explained The CI/CD pipeline is one of the best practices for devops teams to implement, for delivering code changes more frequently and reliably
- devops.com: How to Implement an Effective CI/CD Pipeline
- ammeon.com: 5 Tips For Building A CI/CD Pipeline
- medium: What is CI/CD Pipeline in DevOps? 🌟🌟 Understanding the Importance of CI/CD Pipeline.
- aws.amazon.com: Automating safe, hands-off deployments 🌟🌟
Deployment Strategies
- blog.container-solutions.com: Deployment Strategies 🌟
- It really depends on the needs and budget. When releasing to development/staging environments, a recreate or ramped deployment is usually a good choice. When it comes to production, a ramped or blue/green deployment is usually a good fit, but proper testing of the new platform is necessary.
- Blue/green and shadow strategies have more impact on the budget as it requires double resource capacity. If the application lacks in tests or if there is little confidence about the impact/stability of the software, then a canary, a/b testing or shadow release can be used. If your business requires testing of a new feature amongst a specific pool of users that can be filtered depending on some parameters like geolocation, language, operating system or browser features, then you may want to use the a/b testing technique.
- Last but not least, a shadow release is complex and requires extra work to mock egress traffic which is mandatory when calling external dependencies with mutable actions (email, bank, etc.). However, this technique can be useful when migrating to a new database technology and use shadow traffic to monitor system performance under load.
CI/CD with Kubernetes
- blog.sonatype.com: Achieving CI and CD With Kubernetes 🌟
- thenewstack.io: 7 features that make kubernetes ideal for CI/CD
- thenewstack.io: CI/CD with kubernetes 🌟
Reports on the Enterprise CI/CD Market
- GigaOm's Radar for Enterprise CI/CD 🌟 is a must-see report for any DevOps enthusiast. The goal of an end-to-end Continuous Integration/Continuous Delivery (CI/CD) pipeline is to deliver software-based innovation and business value at both speed and scale. CI/CD plays a very important role in the company's DevOps journey. Keeping several factors in mind, Gigaom has come up with it'sown research and presented who leads and who lags in the CI/CD market.
