Stephen Levine

If you're considering Zero Trust security, you may look into IAP as a modern replacement for traditional VPN-based remote access. Teleport can provide it for you. @janakiramm explains for @TheNewStack ▶ bit.ly/3wc7LbX #Cybersecurity #OSS

Humbled to be a part of the @buildpacks_io #TOC alongside a group of such exceptional individuals! Thanks to the community for your resounding vote of confidence. I will be at #KubeConEU next week, so come drop by the #Buildpacks booth to learn more about what's coming!

@CTOPope @RuurdKeizer Cartographer is a tool for building an app platform using tools like Tekton, Flux, ArgoCD, CNCF Buildpacks, etc. It's not trying to compete with those tools -- just make it easier to connect them together and scale them out without sprawl. More examples of this coming soon

So. @carthographer immediately appealed to me but I couldn't quite figure out why. It took me a whole day to realize it's really the k8s native, extensible lovechild of CF push and concourse CI. This plan is coming together.

@jtronson @kelseyhightower (Worth noting: unlike Docker v1 image layers, OCI / Docker v2 image layers are content-addressed and not linked together. buildpacks.io takes advantage of that to provide the functionality you're asking about)

@jtronson @kelseyhightower And VMware has K8s CRDs+controllers for it here: github.com/pivotal/kpack

@nikhilm_in @buildpacks_io This is a feature, not a bug. Many of the next-gen container builders (buildpacks, jib, ko) use fixed, not-quite-zero timestamp values to guarantee image reproducibility

@buildpacks_io 's docker image and another app image built using it says they were created 40 years ago.

@nicolas_frankel Image tags are used in mutable contexts (perhaps analogous to git branches) as well as immutable contexts (analogous to git tags). Paketo also provides immutable tags: docker pull paketobuildpacks/builder:0.0.443-base-platform-api-0.3 You could also pull by digest

@stephen_levine In non-Cloud native software, versions *are* immutable. And the versioning makes it clear whether it's a bugfix, etc. It's up to the consumer to make the decision to upgrade - or not. With the current approach, my image doesn't build anymore because of a Go bug, and I'm helpless

"Downloaded newer image for gcr.io/paketo-buildpa…" Aren't images supposed to be immutable? 🤔 #buildpack #CNB

@nicolas_frankel That said, I haven't found great immutable versioning schemes for images. If you tag an image ":v1.2.3" because it matches v1.2.3 of the project, and you rebuild the image to patch OS packages (say with LTS versions), how do you make sure users of v1.2.3 get those updates?

@nicolas_frankel The "*-platform-api-*" tags provide the latest images that conform to particular upstream CNB Platform API versions. In this case, "0.3" reflects a contract, not a version of the image. See: #platform-api-version" target="_blank" rel="nofollow noopener">github.com/buildpacks/spe…

@rberrelleza @garethr @jbeda @derekcollison @rseroter @Paketo_io @buildpacks_io @tilt_dev @dbentley Please reach out on slack! slack.buildpacks.io Happy to help make this a reality :)

@garethr @jbeda @derekcollison @rseroter @Paketo_io @buildpacks_io @tilt_dev @dbentley We don't support buildpacks yet, but it's something we are looking into actively. A source to deployment experience, without having to worry about Dockerfiles or even k8s manifests would make for a great dev experience.

@derekcollison @rseroter @jbeda @Paketo_io @buildpacks_io kpack (github.com/pivotal/kpack) can provide that UX on K8s if you hook it up to CD. And CF4K8s (github.com/cloudfoundry/c…) integrates kpack to provide a `cf push` experience on K8s that's much faster than CF4BOSH, due to CNB (buildpacks.io)'s aggressive layer reuse

@rseroter @jbeda @Paketo_io @buildpacks_io It wasn't before. That was a big criteria for me. Of course if you are building a huge hairy java app then only so much you can do.

@jbeda @KarlKFI @krisnova @Paketo_io @buildpacks_io Also, modular buildpacks (like Paketo) can totally be composed to build CI base images and keep them up-to-date. We just don't do much to advertise that yet. This is great feedback that we should :)

@jbeda @KarlKFI @krisnova @Paketo_io @buildpacks_io You don't actually need a CI base image to run buildpack builds (the pack CLI is really just a Docker client for platforms that don't natively support containers). Check out the Tekton integration, which uses the underlying lifecycle directly: github.com/tektoncd/catal…

@MOSFETmisfit @ibuildthecloud This was perhaps true of the last-gen Heroku and Cloud Foundry buildpacks, but CNB is a clean break from those with a modular/composable API

So.... Cloud Native Buildpacks.... Does anybody really care about them?

@ahmetb @steren @buildpacks_io Verbosity - Run with `pack build -v` Modularity - Try the ultra-modular Cloud Foundry buildpacks (and check out buildpackages in the next release) Speed - Run with `pack build —publish` (storing the image on the Docker daemon is often very inefficient)

@steren @buildpacks_io > Seems like @buildpacks_io is not yet ready for prime time ^ my thoughts for the past few months. every time I use it, I feel like it needs more verbosity and modularity (also speed lol)

Seems like @buildpacks_io is not yet ready for prime time: ``` $ npx express-generator $ pack build my-image $ docker run -p 8080:8080 -e PORT=8080 my-image ERROR: failed to launch: determine start command: process type web was not found ```

Verifying myself: I am sclevine on Keybase.io. 8dXVhERIYyOZ0Dpi7O-wF7DSjFE7xnZ8tHZU / keybase.io/sclevine/sigs/…