chart: adding extraVolumeMounts and extraVolumes fields to be mapped on the pods as volumes#5853
chart: adding extraVolumeMounts and extraVolumes fields to be mapped on the pods as volumes#5853nnicora wants to merge 4 commits intoenvoyproxy:mainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5853 +/- ##
==========================================
+ Coverage 70.60% 70.66% +0.05%
==========================================
Files 220 220
Lines 36829 36829
==========================================
+ Hits 26003 26025 +22
+ Misses 9293 9275 -18
+ Partials 1533 1529 -4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
I think we didn't the extra prefix, WDYT?
cc @envoyproxy/gateway-maintainers
There was a problem hiding this comment.
if we dont do the extra then we will need to expose the internal volumeMount here
|
@envoyproxy/gateway-maintainers Any updates on this PR ? |
|
hey @nnicora is there any prior art for this
|
|
@nnicora can you sign your commit and force push ? |
Done! |
|
can you fix DCO? |
…mapped on the pods for eternal volumes, one of the cases is the unix volume mapping. Signed-off-by: Nicolae Nicora <n.nicora@sap.com>
Signed-off-by: Nicolae Nicora <n.nicora@sap.com>
Signed-off-by: Nicolae Nicora <n.nicora@sap.com>
|
some tests are failing @nnicora, also can you add a test in https://github.com/envoyproxy/gateway/tree/main/test/helm |
|
@nnicora can you address the comments ? |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, when it's ready. Thank you for your contributions! |
|
let's close this for now, feel free to reopen. |
What type of PR is this?
What this PR does / why we need it:
Whenever wants the gateway to communicate with the extensions over the unix socket, the gateway have to be configured with the right existing socket directory path which should be mounted to the deployment.
Release Notes: No