runtimeproxy: fix env lost#957
Conversation
Codecov ReportBase: 66.96% // Head: 66.99% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #957 +/- ##
==========================================
+ Coverage 66.96% 66.99% +0.03%
==========================================
Files 243 243
Lines 28240 28240
==========================================
+ Hits 18910 18920 +10
+ Misses 8035 8026 -9
+ Partials 1295 1294 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Signed-off-by: lucming <2876757716@qq.com>
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: lucming <2876757716@qq.com>
Ⅰ. Describe what this PR does
fix bug: env lost when container's env contains = in its value.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
kubectl apply -f nginx.yaml, like this
However, this env is not written in the container
Ⅳ. Special notes for reviews
V. Checklist
make test