fix(KONFLUX-5917): adding tekton example of using secret

Signed-off-by: Kasem Alem <[email protected]>

Author: Kasem Alem

docs/modules/ROOT/pages/how-tos/configuring/creating-secrets.adoc

@@ -47,6 +47,61 @@ Some container builds may use parent images from registries that require authent
 . Enter the password for the registry in **Password**.
 . Click **Add secret**.
 
+== Example of creating a quay.io secret 
+. Login to Konflux console your workspace (https://console.redhat.com/application-pipeline/workspaces/<your workspace>/applications)
+. Click on `Secrets` on the left menu.
+. Click on `Add Secret`
+. Choose `Image pull secret` for `Secret type`
+. Enter `Secret name` , for example `my-quay-secret` 
+. Choose `Image registry credentials` in `Authentication type` field
+. Enter `quay.io` in `Registry server address`
+. Enter your Quay.io username in `Username`
+. Enter your Quay.io API token in `Password` field.
+. Click on `Add secret`
+. Email is optional
+
+Once all is information is valid and adding secret successful you can see it appears in the secrets list, 
+Here is the yaml file of the secret looks like:
+
+
+[source,yaml]
+----
+apiVersion: v1
+data:
+  .dockerconfigjson: <your base64 generated token>
+kind: Secret
+metadata:
+  creationTimestamp: "2025-01-28T17:45:04Z"
+  name: my-quay-secret
+  namespace: <your workspace- tenant>
+  resourceVersion: "3088423929"
+  uid: 4af266b0-c63a-4aed-b808-a29cbd0cadfe
+type: kubernetes.io/dockerconfigjson
+
+----
+
+In below an example how to use the secret within a Tekton task
+
+[source, yaml]
+----
+apiVersion: tekton.dev/v1beta1
+kind: TaskRun
+metadata:
+  name: build-container
+spec:
+  taskRef:
+    name: build-container
+  params:
+    - name: image
+      value: quay.io/my-image:latest
+  workspaces:
+    - name: source
+      subPath: src
+  volumes:
+    - name: registry-credentials
+      secret:
+        secretName: my-quay-secret
+----
 
 [NOTE]
 ====