Tom Plant

+1, this would be excellent for service-level alerting/troubleshooting. Particularly with vendored or legacy services that can't be instrumented directly. At the moment I've resorted to parsing logs which isn't a...

@lst123 would be great if you can share sources :)

As of last week, buildkit `master` can build basic Windows images. But it might take a while for tests, releases, buildx/actions-toolkit integration, and availability in GitHub hosted runners. Partially tracked...

This is now available via the `remote` driver ```yaml - uses: docker/[email protected] with: driver: remote endpoint: tcp://buildkitd.tplant.com.au:1234 env: BUILDER_NODE_0_AUTH_TLS_CACERT: ${{ secrets.BUILDKIT_ARM_CA }} BUILDER_NODE_0_AUTH_TLS_CERT: ${{ secrets.BUILDKIT_ARM_CERT }} BUILDER_NODE_0_AUTH_TLS_KEY: ${{ secrets.BUILDKIT_ARM_KEY }}...

The workaround is failing for me on TQ3A.230805.001 after many attempts. But the controls aren't disappearing on a different device with the same patch (which had them added years ago)

@jpelgrom it's fixed for me on Android 14 (build UP1A.231005.007)

Possibly related to https://github.com/opencost/opencost/blob/6cb52d08d24adfefa62bbb4316220ff83cb3019b/pkg/cloud/azureprovider.go#L546-L551

@thomasvn I tried just client ID, then added tenant ID and subscription ID. Tenant ID and sub ID should be automatically detected by the MSI though

@thomasvn yes, the error message didn't change. I also received the same error when no azure parameters were provided

@andriktr Thanks! Do you know whether this works with AAD Workload Identities, which [replaced AAD Pod Identity](https://cloudblogs.microsoft.com/opensource/2022/01/18/announcing-azure-active-directory-azure-ad-workload-identity-for-kubernetes/)? I don't think my cluster implements either of them, but it does have...