RFE : Improve secret management doc in OpenShift Pipeline and support Azure KeyVault

[ezYakaEagle442]

Writing your first OpenShift Pipeline/Tekton, you discover that secrets are declared as string in Tasks params and are displayed in clear text in the ARO console.

Request For Enhancement :

1. Improve ARO & OpenShift documentation to describe how to limit secret exposure in the Pipeline
2. Add in the roadmap the integration with Azure KeyVault + the Azure Key Vault Provider for Secrets Store CSI Driver

Note: There is no GitHub Issue page at - https://github.com/openshift/tektoncd-pipeline

See also:

• https://github.com/tektoncd/pipeline/blob/master/docs/tasks.md#using-a-secret-as-an-environment-source
• https://github.com/tektoncd/pipeline/issues/2343
• https://github.com/tektoncd/pipeline/issues/3443
• https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html/pipelines/index
• https://docs.openshift.com/container-platform/4.6/pipelines/understanding-openshift-pipelines.html#about-tasks_understanding-openshift-pipelines

[ezYakaEagle442]

see also :

• https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/363
• https://github.com/Azure/OpenShift/issues/201

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-azure/issues/2344#issuecomment-857458226): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.