Make linking the kubeconfig idempotent.#1852
Conversation
|
@joerg84: Adding do-not-merge/release-note-label-needed because the release note process has not been followed. DetailsOne of the following labels is required "release-note", "release-note-action-required", or "release-note-none". 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/test-infra repository. |
|
Hi @joerg84. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/assign @douglas-reid |
Codecov Report
@@ Coverage Diff @@
## master #1852 +/- ##
==========================================
- Coverage 82.56% 82.55% -0.01%
==========================================
Files 202 196 -6
Lines 19849 19047 -802
==========================================
- Hits 16389 15725 -664
+ Misses 3015 2920 -95
+ Partials 445 402 -43
Continue to review full report at Codecov.
|
|
/ok-to-test |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: douglas-reid The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue. |
Automatic merge from submit-queue. Make linking the kubeconfig idempotent. Previously there were situations where we needed to manually unlink the config, e.g., after build errors. ```release-note NONE ```
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
This reverts commit f85f49c.
Previously there were situations where we needed to manually unlink the config, e.g., after build errors.