Hybrid CI/CD with Kubernetes and Codefresh
2 likes361 views
Even though the public cloud has changed the way companies deploy and run applications, there are several cases (finance/healthcare) where all services of an organization are running in secure on-premise datacenters behind strict firewalls, in remote storefronts, or even in mobile locations with low connectivity. In this webinar, we will see how you can include these secure and remote services in your CI/CD pipelines, without compromising security and without opening firewall ports. We will use Codefresh and the new Codefresh Runner that can run wherever your clusters live.
More Related Content
What's hot (20)
Similar to Hybrid CI/CD with Kubernetes and Codefresh (20)
More from DevOps.com (20)
Recently uploaded (20)
Hybrid CI/CD with Kubernetes and Codefresh
- 1. Hybrid CI/CD with Kubernetes and Codefresh KOSTIS KAPELONIS
- 6. CI/CD Auth Integrations Pipelines UI Secrets Workers Databases Config CI/CD has lots of components and isn’t portable
- 8. The Basic Software Lifecycle
- 9. In Codefresh every step is a docker image ● Natively runs and scales on Kubernetes ● Support for Kubernetes/Helm deployments ● Complete code to cloud traceability
- 10. Codefresh SAAS ● Intuitive UI ● Web API and CLI ● Integrated Docker registry and Helm repo
- 11. “Our developers can commit and deploy within 10 minutes. Individuals can come up with a feature, add it, test it and ship it quickly” GIPHY
- 12. Codefresh installation options ➔ Managed by Codefresh ➔ Access to public services ➔ Everything runs on Codefresh cloud ➔ Automatic product updates ➔ Managed by Codefresh/Customer ➔ Access to secure services ➔ Pipelines run on private cloud ➔ Automatic product updates ➔ Managed by Customer ➔ Access to secure services ➔ Everything runs on private cloud ➔ Scheduled product updates
- 13. Customers with security constraints ● Financial/Health sector ● Secure services ● Strict firewall rules ● On-premise resources ● Not on public clouds by design
- 14. On premise source code ● Often considered the most sensitive asset ● On premise Github ● On premise Gitlab ● On premise Bitbucket server ●Other providers (.e.g. Perforce)
- 15. On premise Docker images ● Private images with dev tools ● Private images for secure deployments ● Promotion between registries ● Often mixture of public and private registries
- 16. On premise Kubernetes clusters ● K8s for on-premise datacenters ● Often clusters are for internal use only ● Clusters with intermittent network access
- 17. Customers that choose Hybrid CI/CD Scale Use Kubernetes native scaling Secure Access to internal services behind firewall Manage No need to to maintain the whole platform
- 20. Codefresh Hybrid Runner characteristics ● Runs on Kubernetes ● Open-source installer ● Uni-directional communication ● Runner polls Codefresh ● No open ports needed
- 21. Codefresh Hybrid Runner lifecycle ● Fully independent ● Deploys engine automatically ● Manages pipeline volumes ● Standard Kubernetes ● Easy monitoring ● Easy upgrades ● Easy scaling ● Multiple runtimes
- 23. Hybrid CI/CD with Codefresh
- 24. ● Multiple Hybrid runners ● Customer can select any cluster ● Assign runtime to each pipeline ● Custom cloud environments ● On-premise environments ● Mix and match Runtime environments
- 25. Full control on pipeline environment location Codefresh SAAS Google Cloud K8s AWS cloud On-premise Datacenter
- 26. Full control on pipeline environment arch Codefresh SAAS (Linux) Cloud K8s (Linux) Custom cluster (ARM) On-premise Datacenter (Windows)
- 27. Hybrid Demo: Runtime = my laptop
- 28. Run pipelines on Docker for desktop
- 29. Demo 1: Basic build in Hybrid
- 30. Demo 2: Access to resources
- 31. Demo 3: Mixing Hybrid/Cloud pipelines
- 32. Summary ● SAAS, Hybrid, On prem ● Hybrid can be installed on any cluster ● Secure access, no open firewall ports ● Multiple runtime environments ● Consistent experience for CI/CD
- 33. Get 120 FREE builds/month! Signup & schedule a 1:1 at: Codefresh.io Build Fast, Deploy Faster Questions?