Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Very rarely we see a flake on the CI that looks like this
While it does not mess with any test, it causes CP to restart on which we have assertion after all tests are run.
Here is an example https://github.com/Kong/kong-mesh/actions/runs/11144879402/job/30973956156
We may be starting CP too soon. When we deploy using kumactl we install CRDs and CP deployment at the same time.
Implementation information
The solution is to first install CRD, wait for them using kumactl and only then install the CP.
I did not fix it for HELM because HELM installs CRDs via hook so there is much more time between CP installation and CP start, I don't think we ever saw this problem with HELM.
I checked that it takes about ~3s to wait for all CRDs so it's not a big overhead.
Supporting documentation
No issue, just a flake that we noticed