armangurkan

> > assume otherwise auth-url wouldn't work. > > The 500 error you are getting is because OAuth2 Proxy is returning an invalid code when Nginx is attempting to request...

 We have deployed the code in the branch this is the error message we get

> >  We have deployed the code in the branch this is the error message we get > > This error means that the previous update has not been...

> > What we had experience was, statefulset replicas got down to 0 constantly, we observed a constant cycle of shutdown and re-instantiation of pods, so at first we thought...

>  We have deployed the code in the branch this is the error message we get @tpiperatgod , somehow the issue is back, the functions can not scale (so...

@tpiperatgod The weird thing is as a result of colliding deployments the autoscaling worked for some reason and I tried every combination that can be possible and can not get...

Quick update we deployed the function-mesh without argocd, we still observed the issue and observed the following set of log in the operator logs: > ` > DEBUG controller-runtime.webhook.webhooks received...

> can you please paste the Function configuration? ```yaml apiVersion: compute.functionmesh.io/v1alpha1 kind: FunctionMesh metadata: name: fm-{{ .Release.Namespace }} spec: sinks: - name: {{ "sink1" | lower }} image: "registry.company.com/project/sink1:{{ (...

> > This issue only occurs in cases when Function has HPA enabled, right? > > If so I think `spec.minReplicas` will make sense, and a preliminary idea would be...

Hello there, Thank you for taking action on the issue first of all. Is there a way that we can get a road map about the issue? We are looking...