Michael Bridgen
Michael Bridgen
The correct way to deploy the operator to work in several namespaces is one deployment in each namespace, with permissions just for that namespace. This PR updates the deployment programs...
The programs under deploy/ all mention a specific version of the operator. At present these get edited by hand when there's a release, but they could be automated, e.g., by...
Addresses #299. - [x] Add a test case that verifies the "stale state" problem described in #299. - [x] (Remove focus from that test case, so others will run!) -...
The operator should be tested against different versions of Kubernetes, from the least recent to the (implicitly supported?) latest. I think starting with the trailing and leading versions would be...
Usually a Kubernetes operator will be packaged as a Helm chart or similar, with the circumstances of its deployment left to the user. The Pulumi operator is in a rare...
PR #662 creates plan-only Terraform objects to represent PRs. It uses annotations (or perhaps labels) to track which objects relate to which PR. However, it doesn't track which Terraform object...
There are a number of places in the tests where `Eventually` is used like this: ``` var tf infrav1.Terraform g.Eventually(func() error { return k8sClient.Get(ctx, key, &tf) }).Should(Succeed()) ``` Some of...
With reference to https://pulumi-community.slack.com/archives/C01F5GS6G3X/p1671178540494389: there's no way to run when _either_ there's a new commit, or the Stack object changed -- which you might expect to be the default mode...
For git cloning using SSH, the operator uses strict host key checking (by not changing the default). This is great, because it means it won't establish connections to hosts for...
The logging is inconsistent (which makes it difficult to eyeball, and to use for any automation); and, not always very purposeful. Ongoing wishlist: - [ ] There are duplicate labels,...