Porter Operator v1.0.0 is here!
Porter Operator v1.0.0 is finally here! 🎉
The Porter Operator gives you a native, integrated experience for managing your bundles from Kubernetes. It is the recommended way to automate your bundle pipeline with support for GitOps.
🚨 Outputs is currently WIP, we will be following up shortly with the ability for outputs to work after an installation upgrade.
Our biggest feature by far is the Outputs API. Being able to share outputs between bundles,
services, and allow users to retrieve outputs from bundles is a must have. By creating the
installation.outputs CRD we are now able to expose those outputs. We leverage the work done
in Porter to turn a gRPC server which enables for these outputs to be shared for a variety of
There were a myriad of issues we were running into when trying to delete resources. One of these issues being that a finalizer would block the deletion of a namespace. By updating one of our reconcilers to check that a deletion timestamp was set, the deletion of namespaces which have operator resources is now able to occur.
TTLSecondsAfterFinished agent configuration option is out, which allows users to set the time limit of a job that has finished its execution. This defaults to 600 seconds, but in the long term should allow for easier debugging.
If you’d like to take the Operator for a spin please go through out Quickstart here. However, if you’re looking for something with more fun tools included, Brian DeGeeter has this amazing porter-argo-demo.
None of this would have been possible without the following: