Skip to content

Conversation

howardjohn
Copy link
Member

TBD:

  • What telemetry do we produce when we retry?
  • Should we retry all conditions? What about timeouts (retrying these
    increases total timeout time!). What about HBONE status codes?
  • How do we pick the new host. Entirely random? Avoid the current host?

TBD:
* What telemetry do we produce when we retry?
* Should we retry all conditions? What about timeouts (retrying these
  increases total timeout time!). What about HBONE status codes?
* How do we pick the new host. Entirely random? Avoid the current host?
@howardjohn howardjohn added the release-notes-none Indicates a PR that does not require release notes. label Feb 27, 2025
@istio-testing
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@istio-testing istio-testing added do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 27, 2025
@istio-testing istio-testing added the needs-rebase Indicates a PR needs to be rebased before being merged label Mar 9, 2025
@istio-testing
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. needs-rebase Indicates a PR needs to be rebased before being merged release-notes-none Indicates a PR that does not require release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants