Mario Manno

Yes, we should :) We briefly discussed smarter scripts in kubecf (they might be able to know if the database needs a migration) and we discussed making qjobs (optionally) run...

We discussed the issue and updated the story in trackers. Can you check if k8s can handle this automatically: https://github.com/kubernetes/kubernetes/issues/35941#issuecomment-509265125 Some storage classes do support this: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims

Looking at the code I can see the quarks statefulset reconciler cannot update the `spec.resources.requests` fields directly. > Forbidden: updates to statefulset spec for fields other than ‘replicas’, ‘template’, and...

I guess k8s doesn't automatically resize, because the storageclass is missing the `allowVolumeExpansion`. We resized an underlying volume manually in the past, then shelled (k9s, ...) into the container and...

@andrew-edgar we've been discussing this. If we allow to override the server, clients won't be able to resolve domains that are configured in bosh-dns anymore, won't that break things? Unless...

https://github.com/cloudfoundry-incubator/quarks-operator/pull/1229

This should be fixed by https://www.pivotaltracker.com/story/show/174661471

Looks like this was never fixed. I added https://www.pivotaltracker.com/story/show/177062682 However Kubecf uses log-cache as a singleton.

I don't think we have any explicit tests for installing multiple operators in a single cluster. The e2e tests on the flintstone Concourse could have catched this, but they are...

If we want to allow multipe operators per namespace, we could use 'monitoredID' to prefix all cluster resources. We'd also have to prefix all the release namespace resources, right now...