Updating podinfo volume name to be seldon specific

[SachinVarghese]

Related to istio/istio#22246

[seldondev]

Thu May 21 11:39:39 UTC 2020
The logs for [pr-build] [1] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/1.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=1

[seldondev]

Thu May 21 11:39:39 UTC 2020
The logs for [lint] [2] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/2.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=2

[adriangonz]

/test integration

[seldondev]

Thu May 21 13:07:06 UTC 2020
The logs for [integration] [3] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/3.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=3

[SachinVarghese]

@cliveseldon @adriangonz Was wondering if we should change the volume mount path from /etc/podinfo to /etc/seldon/podinfo (similar to Istio) to avoid clashes as a part of this PR? Do you foresee any issues with that?

[ryandawsonuk]

/lgtm
/approve

[ryandawsonuk]

/hold

[ryandawsonuk]

@SachinVarghese I think the path is fine. Istio does use an istio-specific mount path but I don't think it's necessary. The mount path is only at the container level so there shouldn't be a clash there. The clash on the volume name is because that's at pod level.

[ryandawsonuk]

/lgtm

[seldondev]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ryandawsonuk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ryandawsonuk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[seldondev]

Tue May 26 10:10:25 UTC 2020
The logs for [lint] [5] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/5.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=5

[adriangonz]

/test this

[seldondev]

Wed May 27 10:35:52 UTC 2020
The logs for [pr-build] [6] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/6.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=6

[seldondev]

Wed May 27 10:50:57 UTC 2020
The logs for [lint] [8] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/8.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=8

[seldondev]

Wed May 27 10:51:41 UTC 2020
The logs for [pr-build] [9] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1863/9.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1863 --build=9

[seldondev]

failed to trigger Pull Request pipeline

• failed to create agent
• failed to calculate in repo config
• failed to load trigger config for repository SeldonIO/seldon-core for ref c0c7738
• failed to find any lighthouse configuration files in repo SeldonIO/seldon-core at sha c0c7738
• failed to process repo SeldonIO/seldon-core refref c0c7738
• failed to list files in directory /var/tmp/gitrepo660600678/.lighthouse
• open /var/tmp/gitrepo660600678/.lighthouse
• no such file or directory