Aiman Alsari

Bit of a hack/workaround, but the following patch will allow you to use path based routing. I should probably create a pull request, but I think this breaks rewrite functionality...

Thanks Victor, I'll close the issue seeing as it has been fixed and merged.

Hi, I've just bumped into the same issue - `git flow release start ` _always_ starts the release from HEAD of ``. In some cases it would be more suitable...

Sure, pasted below. ```apiVersion: apps/v1 kind: StatefulSet metadata: annotations: labels: prometheus: k8s name: prometheus-k8s ownerReferences: - apiVersion: monitoring.coreos.com/v1 blockOwnerDeletion: true controller: true kind: Prometheus name: k8s uid: 2147842b-f6f0-11e8-a80d-42010a840072 selfLink: /apis/apps/v1/namespaces/foo/statefulsets/prometheus-k8s...

The storage is increased there (to 250Gi), but it doesn't seem to do anything, I think the Peristent Volume Claim needs to be updated separately, the statefulset doesn't seem to...

Right, Thanks @brancz . This might be a bit more complicated than just copying over fields.. The size is immutable unless it's configured to `allowVolumeExpansion`, so will need a bit...

`allowVolumeExpansion` is on the storageClass - which is not managed by prometheus operator as far as I'm aware.

https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims To summarise - if you have `allowVolumeExpansion` set on your storage class, you can increase the requested size on the persistentVolumeClaim object and K8s will handle everything for you,...

I can reproduce this issue with a short lived service token and also with caching enabled. It's not confined to just batch tokens as far as I can tell.

Just a note that this used to work on Connexion 2.x and is holding us up from migrating to Connexion 3