Octopus Kubernetes Operator for GitOps Pull Workflow
We're currently using Octopus to manage our Kubernetes clusters, but we're interested in transitioning to a GitOps Pull Model (rather than the current Push based approach where the Octopus Server is executing kubectl commands against our clusters) in which (in a similar fashion to the polling tentacles Octopus already offers), a service would run within our clusters and periodically
poll both git repositiories and docker registries/helm feeds for changes and sync the cluster state accordingly.
What a great idea! The security benefits of the pull model can't be ignored and this would allow us to continue to use octopus while abiding by best practices!