Pivoting your pipeline from Legacy to Cloud Native

When you begin your Cloud Native journey, you’ll quickly find that your current CI/CD pipeline is not going to make the grade. Kubernetes is finally moving us away from a monolithic approach to software development towards a service-based approach. This means each microservice will have its own life cycle and be independently deployable. This is the game changer. While you can force your current CI/CD pipeline to support microservices, this isn’t an optimal approach. With a cloud native environment comes new complexities. Just as a start, your configuration management shifts from check-in and build where linking is resolved, to a container build and run-time APIs. Join Tracy Ragan, CEO of DeployHub and CDF Board Member for a review of what a K8s pipeline look like, and how your current pipeline is disrupted.  Meet Nathan Martin of Sagecore Technologies who will provide us a real world case study on managing microservice configuration with DeployHub (Ortelius.io open source) and routing with Istio Service Mesh in a modern pipeline.

Takeaways:

• For most organizations, microservices will have their own repository and workflows. CD tools will need to support workflow templates.
• Configuration management will be lost as large monolithic builds are replaced or non-existence. Link decision making is done at runtime – not by a build manager.
• Service Mesh becomes core to deploying and routing microservices.