igooch
igooch
> @igooch I appear to be failing on the `submit-e2e-test-cloud-build` step: > > ``` > Step #25 - "submit-e2e-test-cloud-build": gke-autopilot-1.28: BUILD FAILURE: Build step failure: build step 1 "e2e-runner" failed:...
> In the meantime, I do have some questions about some of the codebase as it relates to the batching/queueing system. > > I may be mistaken but it seems...
The main concern is to ensure the change is backward compatible so it doesn't unintentionally break any current users. As long as the existing labeling behavior remains the default when...
@dmorgan-blizz FYI this is one proposal for your issue #3992. Let us know how this performs.
FWIW the idea here is not to bring this feature to stable, it's to leave it as a dev or alpha feature flag (off by default) until, or if, there's...
This works as a simple bin packing fix when used with a significantly lower `allocationBatchWaitTime`. With with tweaks to the `allocationBatchWaitTime` and client-side throttling it can handle many requests (can't...
What does your FleetAutoscaler status look like before / during / after the timeout? Is the webhook updating the number of `desiredReplicas`?
> > it would depend upon the validation module to bubble the deprecation warnings up to helm to display to the user. > > I think this would be a...
Closing PR as it's been open for over a year. If the need has not been addressed, please open or reopen a issue to discuss the rolling update functionality.