You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where the items program, sys, usr-host, modules-host has gone? I think it replace d items, instead of add which I wrote as the value of op item in patch.yaml.
I just represented for volumeMounts here, but volumes also works in the same way.
Alternative Method?
I tried to fix container name of kubectl-trace pod and tried strategic patch, with creating new PR, but it breaks some integration test - failing TestKubectlTraceSuite/TestDeploymentTarget. Does anyone can help me how to deal integration tests?
Additional feature request
How about adding --dry-run option on kubectl-trace run, to check which resources are going to be deployed?
The text was updated successfully, but these errors were encountered:
How to patch adding volumes and volumeMounts?
What I tried?
Expected Pod Spec VolumeMounts
Actual Results for Pod Spec VolumeMounts
Where the items
program
,sys
,usr-host
,modules-host
has gone? I think itreplace
d items, instead ofadd
which I wrote as the value ofop
item inpatch.yaml
.I just represented for
volumeMounts
here, butvolumes
also works in the same way.Alternative Method?
I tried to fix container name of kubectl-trace pod and tried strategic patch, with creating new PR, but it breaks some integration test - failing
TestKubectlTraceSuite/TestDeploymentTarget
. Does anyone can help me how to deal integration tests?Additional feature request
How about adding
--dry-run
option onkubectl-trace run
, to check which resources are going to be deployed?The text was updated successfully, but these errors were encountered: