You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ability to provision a cluster and install Flux using a single Infrastructure as Code (IaC) tool is incredibly beneficial. Therefore, expanding the options available with this plugin would be a welcome enhancement.
In my professional environment, we've made a conscious choice to leverage manifests with OCI. We've found that OCI works well as a Flux source due to its lightweight nature, ease of distribution, and version management. The simplicity of an OCI setup has been particularly noteworthy, in its potential to ease the transition of deployments across various environments. This process is more complex with Git, where development practices like trunk-based development competes with some of the best practices for managing GitOps in Git. For example repo per environment vs. main + feature branches flux docs.
Considering our specific needs, I would like to propose that the pulumi-flux plugin incorporate support for OCI. This enhancement would enable us a maintable way to install Flux on our clusters, while still supporting our use case.
The text was updated successfully, but these errors were encountered:
The ability to provision a cluster and install Flux using a single Infrastructure as Code (IaC) tool is incredibly beneficial. Therefore, expanding the options available with this plugin would be a welcome enhancement.
In my professional environment, we've made a conscious choice to leverage manifests with OCI. We've found that OCI works well as a Flux source due to its lightweight nature, ease of distribution, and version management. The simplicity of an OCI setup has been particularly noteworthy, in its potential to ease the transition of deployments across various environments. This process is more complex with Git, where development practices like trunk-based development competes with some of the best practices for managing GitOps in Git. For example repo per environment vs. main + feature branches flux docs.
Considering our specific needs, I would like to propose that the pulumi-flux plugin incorporate support for OCI. This enhancement would enable us a maintable way to install Flux on our clusters, while still supporting our use case.
The text was updated successfully, but these errors were encountered: