krzwiatrzyk

Up. This is an issue. I can't use the same image for dev and production as for dev I must have `sh` available in container. My solution is to have...

@pchico83 I use Go to develop my app. I found other solution, I use multi-stage build and my base image called builder is based on golang:1.18 image, which has sh...

Another case when this issue occur: All of my apps (Application CR) are using remote values (via URL) to supply it to helm. Any change in those values won't occur...

@Kurisutian please check exported XML. I had the same issue with self-hosted JIRA. Downloading result from browser results with empty XML, you have to use curl for that.

I am struggling with the same issue.

> While I recognize not wanting to introduce latency, we need to have the option. Surely sane defaults address the latency concern, don't they? It's configurable in nginx, caddy, apace,...

I've got the same, Kubernetes version v1.25, Fission v1.18.0, all CRDs installed: `Waiting for CRDs to be installed`

It seems that the issue is related to `defaultNamespaces` parameter. I have deployed fission into `fission` namespace and set `defaultNamespace` to fission... changing it back to `default` helped.

Same here, crashing without any error

Solved it out, increase memory, default value is too low