Deepak Jain
Deepak Jain
Yes, i already did that but it was giving 404. again this is an enterprise runner group that can be used by multiple organisations at the same time
https://docs.github.com/en/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups GitHub DocsManaging access to self-hosted runners using groups - GitHub DocsYou can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.
I am facing the same problem Raised the below PR for the same https://github.com/pusher/k8s-spot-rescheduler/pull/60/files
How can we stop this pod discovery? as this causing lots of errors in iam-controller pods ``` Failed to get credentials for role authenticator-token-zrxnp: AccessDenied: User: arn:aws:sts::xxxx:assumed-role/nodes.xxxx/xxxx is not authorized...
@coderanger i think you are right the last single is part of error display.(i have updated the error msg) But I have checked the JSON of ohai properties displayed in...
I have using many node['ec2'] ohai attributes in my recipe which is causing the test to fail. and to mock those ec2 attributes I am fetching them from dev server....
I am using latest commit from develop branch.
it seems api have changed to `/go/api/feed/pipelines.xml`