Tag : kpack
![Deploy Cloud Foundry to Google Kubernetes in 10 minutes](../../../wp-content/uploads/deploy-cf-for-k8s-to-google-in-10-minutes-300x123.jpg)
Is Cloud Foundry dead? I ask on your behalf because Pivotal – chief cheerleader and contributor to Cloud Foundry – was sold to VMWare in 2019, and all Pivotal-cum-VMWare staff chant “Tanzu” as the answer to all problems. During 2017, ’18, and ’19 the vendor ecosystem around “cloud” and “devops” seemed to pine for all
![Kpack, oh kpack, wherefore art thou build logs?](../../../wp-content/uploads/kpack-viewing-build-logs-300x149.jpg.png)
Any CI/CD is just like a serverless platform or PaaS: you run other people’s code. The difference? With a platform you expect the code to work. With CI/CD you’re waiting for things to fail. So you can fix them. Until they work. Hopefully. And to fix them you need logs. kpack is a new open
![Investigating kpack – Continuously Updating Docker Images with Cloud Native Buildpacks](../../../wp-content/uploads/investigating-kpack-automatically-updating-kubernetes-pods-with-buildpacks-300x198.jpg.png)
Docker images don’t grow on trees, but you shouldn’t buy them from Etsy either. What I mean is, you don’t want your company running on bespoke artisan Docker images based on source code and upstream dependencies that you can’t reproduce 50 times a day, and can’t keep continually updated and secure for the next 10