Added swift example, moved PVC to bottom

[hector-vido]

Swift

Despite the s3api on swift, is not very obvious how we should set the endpoint, I think this example can help not only people that are trying to deploy Prow inside Openstack but also any other "s3like" person searching for some examples.

I the variables with OPENSTACK_EC2_CREDENTIALS_ to give clue about the credentials command:

openstack ec2 credentials create --user prow --project openshift

PersistentVolumeClaim

I also moved the PersistentVolumeClaims to the bottom, this way we can kubectl replace -f manifest.yaml, and let the PVC fail as the last command, when we don't want to create other files for each object.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: hector-vido / name: Hector Vido (6621a09)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hector-vido
Once this PR has been reviewed and has the lgtm label, please assign cjwagner for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• config/prow/cluster/OWNERS

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

[k8s-ci-robot]

Hi @hector-vido. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[BenTheElder]

I think we should actually be moving this folder to sigs.k8s.io/prow?

https://github.com/kubernetes-sigs/prow

The maintainers of that repo would be best equipped to make decisions about changes to docs for getting started with it, and that repo is a more appropriate place to host them, this is left over from when prow was contained within this repo instead of it's own repo, IMHO.