Aleksandr Tarasov

I don't know how builder will look in pipeline, but I think that notation like: ``` jiraIssueUpdate( jqlSearch: jql, workflowActionName: action, comment: "Some comment" ) ``` is really easier for...

Add new pipeline steps. One for updating issue field and one for strict workflow process, cause issue updater set build only Unstable, but not Failure.

@meteatamel Hi! Do you deep dive into the problem? I faced the same behavior and thought it could be a VPA issue.

@meteatamel I think that it could be related to the Vertical Pod Autoscaler because Autopilot changes CPU and Memory requests and limits according to its policies, and it could blow...

Hi, could you provide real stacktraces on client side and server side?

@hawkw, the approach can solve one part of the issue (about dependencies). However, it leads to breaking changes or introducing one more field with a similar name that could confuse...

As I know, it is not a bug, it is a feature. So, at the moment you should explicitly define the different versions for each chart 🤷‍♂️

However, I think that for Linkerd and its main extensions is better to have a consistency in versions

Hi Forden, hope you are well. Do you find the reason for your issue? Do you test it on another python version or another aio_pika

@olix0r looking at the errors like this: ``` web time="2022-08-10T13:37:25Z" level=error msg="Post \"http://metrics-api.linkerd-viz.svc.cluster.local:8085/api/v1/StatSummary\": context canceled" ``` I bet that the issue is that the Prometheus backend cannot process requests before...