rfcs
rfcs copied to clipboard
concourse
RFC: Concourse Kubernetes Operator
One blocker for this is that the core team has no desire to build or maintain an operator right now. I don't see the team trying to support anything k8s-related besides the chart right now.
This talk also got me wondering if writing an operator is even a good idea for Concourse: https://www.youtube.com/watch?v=CwVCfl4qpdg
- Secret generation is really rough on k8s right now. I think this is a problem the platform needs to solve. The operator solution here feels like a stopgap until the platform catches up
- The motivation for k8s Operators seems to be for stateful applications. Concourse itself is a pretty good example of a classic 12-factor app. All state is in the db which users are probably not using the postgres chart for.
Postponing for now, we'll see how the k8s landscape changes in the future.
The k8s runtime for Concourse feels like a natural fit. If a team correctly sizes (resource.limits) a given step or task then k8s does scheduling and scaling.
Sad to see this delayed.
Postponing for now, we'll see how the k8s landscape changes in the future.
Agree. I don't see a need for concourse operator right now, There are other proposals that should be prioritized.
One other way to go about this issue is to use Carvel.dev and its secret-gen-controller. This is the approach that has been taken by the [reusable concourse templates used by the bosh community][https://github.com/cloudfoundry/bosh-community-stemcell-ci-infra/].
any news ? a K8S runtimes would be great to deal a better granularity/scalbility on K8S cluster. atm it's not very intuitive or easy to set those thing.. we have too much options K8S side and Concourse side.
