Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workspace are deleted and recreated on every iteration for remote repositories #275

Closed
arththebird opened this issue Jun 27, 2024 · 3 comments · Fixed by #276
Closed

Workspace are deleted and recreated on every iteration for remote repositories #275

arththebird opened this issue Jun 27, 2024 · 3 comments · Fixed by #276
Labels
bug Something isn't working needs:triage

Comments

@arththebird
Copy link
Contributor

arththebird commented Jun 27, 2024

What happened?

The provider currently deletes and recreates the Workspace directory for remote repositories as detailed here. My understanding is that this was added as a workaround for an issue in the go-getter library where it would fail to pull a repository in an existing directory. This has the effect of requiring Terraform to download the providers every time when the plugin cache is disabled (required when using max-reconcile-rate > 0), increasing NAT cost and reducing performance as explained here.

The go-getter bug seems to be fixed in the latest v1 release (v1.7.5), so this code could probably be removed if we upgrade to the latest v1 release.

How can we reproduce it?

  • Check the creation time of all workspace directories in the provider pod and notice they are all recent.
  • Wait an hour
  • Check the creation time and again and see the repositories were recreated.

What environment did it happen in?

  • Crossplane Version: v1.16.0
  • Provider Version: v0.16.0
  • Kubernetes Version: v1.29.4
  • Kubernetes Distribution: EKS
@arththebird arththebird added bug Something isn't working needs:triage labels Jun 27, 2024
@bobh66
Copy link
Collaborator

bobh66 commented Jun 27, 2024

This is likely related to #230 - I would expect renovate to upgrade the go-getter dependency as soon as it can. Definitely would be nice to fix this.

@arththebird
Copy link
Contributor Author

arththebird commented Jun 27, 2024

This is likely related to #230 - I would expect renovate to upgrade the go-getter dependency as soon as it can. Definitely would be nice to fix this.

I think the renovate PR is already up for review here

@bobh66
Copy link
Collaborator

bobh66 commented Jun 27, 2024

Oops - right - I have been trying to get the last CI job to run before I merge it and I didn't make the connection. I don't know why the job isn't being picked up by a runner, but I'll kick it one more time and if it doesn't run I'll just merge the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants