Closed smg247 closed 1 week ago
Name | Link |
---|---|
Latest commit | 2a618c8f17e6c6e640d95799df80a861eac05c59 |
Latest deploy log | https://app.netlify.com/sites/k8s-prow/deploys/672a7217619cba000820ec39 |
Deploy Preview | https://deploy-preview-317--k8s-prow.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/cc @petr-muller
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: petr-muller, smg247
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/hold
Can we remove the --allow-insecure
from the tests again? Or at least from one, to integeration-test both paths?
Can we remove the
--allow-insecure
from the tests again? Or at least from one, to integeration-test both paths?
Since the other PR was reverted, this has required no changes to the integration tests at all. It is not present in the deck_tenant_deployment
now.
/hold cancel
Since the other PR was reverted, this has required no changes to the integration tests at all. It is not present in the deck_tenant_deployment now.
Ugh, I forgot that because we reverted the test manifests are now in the state I wanted. Code reviews on Friday :grimacing:
This is a follow up to the failed attempt from https://github.com/kubernetes-sigs/prow/pull/308. It makes it more clear that the CSRF logic wraps the server, and starts the readiness endpoint immediately before starting the server.