Filip Swiatczak

Hi @YOU54F, thank you for the pointer. I have double checked with a single consumer having a pact against 3 different providers and it works correctly, with the publishing log...

thanks @awprice, it worked with these two changes: 1. Run EksCtl to create OIDC for the Cluster like: `eksctl utils associate-iam-oidc-provider --cluster --approve --region ` 2. and then modify Trust...

Also @awprice if escalator runs in the same node group that it controls, how can it prevent tainting it's own node and forcing escalator re-deployment? Really can't find an answer...

> Also @awprice if escalator runs in the same node group that it controls, how can it prevent tainting it's own node and forcing escalator re-deployment? Really can't find an...

> We tend to use IAM roles for service accounts on EKS, as this will prevent the need to deal with node instance roles. This documentation from AWS gives a...

It appears when the escalator is deployed in a separate node-group, with custom label escalator:worker at both node and pod level, escalator does't see any cpu or mem utilisation (0)....

When escalator is attempting to scale node-group different to one it's deployed in, it throws: ``` time="2023-10-24T10:46:18Z" level=info msg="Node IP.eu-west-1.compute.internal, aws:///eu-west-1c/ID ready to be deleted" drymode=false nodegroup=bitbucketpipelines-ng-spot time="2023-10-24T10:46:18Z" level=error msg="failed...

> @FilipSwiatczak what about https:// urls? hi @mathpaquette , the bitbucket ssh url is almost identical to the github one with the distinction of having **.git** at the end, therefore...