Paul "TBBle" Hampson

Results 386 comments of Paul "TBBle" Hampson

Small progress report. I now have networking functional for the containerd worker under Windows. It's a minor hassle to set up using BuildKit and containerd directly (as you have to...

It occurs to me... I'm only testing with the containerd backend. Is there any interest in the runc executor working (using [runhcs](https://github.com/microsoft/hcsshim))? I feel like there's a movement away from...

The main blocker (my last remaining hack) for bringing this up in CI is refactoring `GenerateSpec` to not add any `Linux` elements to the spec, as that triggers LCOW mode....

A problem for using the vendored containerd for client-side diffing in the runc executor is that the vendored containerd is 1.3, which doesn't support diffing windows-layers, as that code is...

I think this is implemented using the `eks.amazoneaws.com/skip-containers` annotation now?

Looking at [the source](https://github.com/jetstack/cert-manager/blob/master/pkg/issuer/acme/dns/route53/route53.go), it's actually _not_ needed if you are using ambient credentials, e.g. a Service Account with appropriate IAMs Role; it will happily take and ignore an empty...

Looking at https://github.com/jetstack/cert-manager/pull/1917, it appears region's "requiredness" persisted from when the credentials were mandatory. That's probably what the comment meant?

I'm not in a position to put up PRs, but I'll just highlight that although this bug was filed on the website repo, I think it's actually revealed a bug...

https://opencontainers.org/community/overview/#chat links to https://communityinviter.com/apps/opencontainers/join-the-oci-community now, is that a temporary workaround? Or since the DNS entry for chat.opencontainers.org (and others like blog.opencontainers.org) appears to be NXDOMAIN again, should this README (which...

> I get that it is how it works, but shouldn't this requirement to have the same port for service's `port` and `nodePort` be documented somewhere ? There's not a...