shapirus

/remove-lifecycle stale time to rerun the performance tests, it's a good reminder.

@clayrisser this is interesting. I'm curious to see if TF can switch between the different authors' providers without recreating all resources, I think I'll give it a try.

@clayrisser I ran into issues when trying to use your fork, so I wanted to open a GitHub issue, but there's no "Issues" tab in the respective repo, and https://github.com/clayrisser/terraform-provider-kops/issues...

glad to see you're back and are hopefully well :)

There's been some activity (see discussion at https://github.com/clayrisser/terraform-provider-kops/issues/2). No clue if there are any results.

Argocd `v2.7.8+92949f6.dirty` here. Doesn't matter if the empty `annotations: {}` is present or not, the app stays out of sync with the following diff: 

One important aspect that I'd like to point out here is that the benchmarks should cover the following cases: - single invocation of kustomize to process a big and complex...

> @shapirus yeah, we should have some benchmarks emulating argo/flux too. Do you think this affects how this PR is structured? @chlunde As far as I can see, it is...

@pkalemba this link points to a signup-protected page. Is there an open version?

See also: https://github.com/distribution/distribution/issues/3266