operator
operator copied to clipboard
getporter
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.
The outputs generated from running an installation should be natively accessible from Kubernetes. So after the installation completes the output values should be copied into a secret. We have a...
Whenever we embed a porter resource inside a CRD, it would help people move between the two (porter cli and the operator) if resource naming conventions were the same between...
This PR implements the ability to allow users to configure plugins they need in agent-config resource. Current workflow: It creates a new agent config controller to manage the lifecycle of...
the current code has not solved how to install multiple porter plugins with one agent job. From my discovery, currently porter currently does not seem to allow installation for multiple...
We need to have a doc page that explains how to configure plugins through agent config. It should also points out where are the default values are set in both...
PR #120 adds support for AgentActions against bundles in a private registry for #68 . The initial solution is limited to one imagePullSecret for all authentication. This requires the user...
Signed-off-by: Steven Gettys
Porter is preping for its v1 release, the operator should follow below steps to prep itself: - update/test the operator with the current latest porter release - update/test the operator...
Additional env vars can be passed along to the agent action job by populating a secret name "porter-env" with the values you'd like to set. Add this behavior to the...
Porter has switched from debug and debug-plugins to [verbosity](https://github.com/getporter/porter/issues/1429). We need to update the version of Porter used by the operator, and fix PorterConfig CRD to use the new fields.