Skip to content

Conversation

@zstevenson-payments
Copy link
Contributor

Since the controller is now using sidecar init containers, these should be checked for existence when determining if a pod needs to be recreated because the proxy injection failed. In other words, currently we get false positives if the main workload is erroring and the proxy was injected as a sidecar init container, which causes the controller to remove the pod instead of letting it progress.

I ran into some errors running the go_lint step in the Makefile (even before making changes) and ran into a problem during the terraform execution of building the infra for the e2e tests, so I wasn't able to complete them as laid out in the docs. I did however remove the go_lint step, build the controller image and replace it in my cluster and confirmed the desired effect.

  • Tests pass
  • Appropriate changes to README are included in PR

@zstevenson-payments zstevenson-payments requested a review from a team as a code owner March 31, 2025 13:49
@hessjcg hessjcg changed the title Check all containers and init containers for proxy before recreating pod fix: Check all containers and init containers for proxy before recreating pod Apr 22, 2025
@hessjcg hessjcg enabled auto-merge (squash) April 22, 2025 18:41
@hessjcg hessjcg merged commit a28e16a into GoogleCloudPlatform:main Apr 22, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants