Keep pipeline job and comment consistent #46
Description
In Kubernetes/OpenStack integration scenario, we should keep pipeline name, job name and trigger comment consistence, that build consist user experience for developer from k8s community, and easy to understand how to trigger the specific jobs when the job failed.
- update all of pipeline name, job name and trigger comment for k8s jobs
- run all of jobs in separate pipeline when PR commit and update, and report to github independently
- branch-v1.10.0 should be just branch-v1.10
- update https://github.com/theopenlab/cicd-howto#kubernetescloud-provider-openstack