Richard Wall
Richard Wall
While reviewing #6791 I ran `make verify-crds` locally and it failed with a stack trace. But why didn't that failure also show up in our periodic and pull-request CI results?...
```sh $ E2E_EXISTING_CHART=true E2E_CERT_MANAGER_VERSION=1.14.2 make e2e-setup-certmanager /home/richard/projects/cert-manager/cert-manager/_bin/tools/kubectl apply --server-side -f _bin/scratch/gateway-api-v1.0.0.yaml > /dev/null /home/richard/projects/cert-manager/cert-manager/_bin/tools/helm upgrade \ --install \ --create-namespace \ --wait \ --namespace cert-manager \ --repo https://charts.jetstack.io \ --version1.14.2 \...
In https://github.com/jetstack/jetstack-secure/pull/341 @tfadeyi added a metrics server to the agent. In this PR I've made the minimum viable changes to allow that metrics server to be queried by Prometheus, when...
**Preview**: https://deploy-preview-1520--cert-manager.netlify.app/ Not to be merged until cert-manager 1.16.0 is released and when all the cert-manager 1.16 release notes have been merged to the release-next branch. /hold
- The [WatchList feature](https://kubernetes.io/docs/reference/using-api/api-concepts/#streaming-lists) of the kube-apiserver is available since v1.27. - The ClientWatchList feature of client-go is available since [v0.28.0](https://github.com/kubernetes/client-go/blob/v0.28.0/tools/cache/reflector.go#L240-L242) enabled with a non-standard [ENABLE_CLIENT_GO_WATCH_LIST_ALPHA environment variable](https://github.com/kubernetes/kubernetes/pull/118235). - In...
An alternative approach to #7235. Instead of creating a bespoke STS client and STS credential provider, this branch just uses the AWS-SDK LoadDefaultConfig mechanisms which creates an STS client if...
This modified script will create a GKE cluster and set up: venafi-enhanced-issuer, approver-policy-enterprise, and venafi-kubernetes-agent to authenticate to Venafi Control Plane using a Kubernetes ServiceAccount Token. ```console $ ./hack/e2e/test.sh ......
**Unrelated:** I think we should also check the presence of the images after releasing. Just to double check. Do you think this check should be part as the release process...
I downloaded cmctl from https://github.com/cert-manager/cmctl/releases/download/v2.1.1/cmctl_linux_amd64 When I ran `cmctl version` with verbose logging, I noticed the request header: `User-Agent: cmctl/v0.0.0 (linux/amd64) kubernetes/$Format`. Should contain `User-Agent: cmctl/v2.1.1 (linux/amd64)` I think. Not...