Skip to content

Commit b842ef2

Browse files
committed
Review the instructions to use Tekton and Tekton dashboard
Signed-off-by: cmoulliard <cmoulliard@redhat.com>
1 parent 56a3beb commit b842ef2

1 file changed

Lines changed: 21 additions & 3 deletions

File tree

resources/examples/platform-ingress-tekton-dashboard.yml

Lines changed: 21 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,25 @@
11
#
2-
# mkcert tekton.localtest.me localtest.me localhost 127.0.0.1 ::1
3-
# kubectl delete secret -n tekton-pipelines self-signed
4-
# kubectl create secret tls self-signed --cert tekton.localtest.me+4.pem --key tekton.localtest.me+4-key.pem -n tekton-pipelines
2+
# To access the Tekton UI using ingress from your browser and instead of using the Kubernetes Fake self-signed certificate,
3+
# a better approach is to use the following tool able to generate a CA root certificate and to trust it locally
4+
#
5+
# - Install mkcert. See instructions on: https://github.com/FiloSottile/mkcert
6+
#
7+
# - Install the root CA on Firefox, Java keystore and Mac Keychain tool, chrome, etc using the command:
8+
#
9+
# mkcert -install
10+
#
11+
# You can read the certificate generated using the command:
12+
#
13+
# cat "$(mkcert -CAROOT)"/rootCA.pem | openssl x509 -noout -text
14+
#
15+
# - Create a pem and key files for: localtest.me domain and tekton host
16+
#
17+
# mkcert tekton.localtest.me localtest.me localhost 127.0.0.1 ::1
18+
#
19+
# - Create next a secret on the cluster
20+
#
21+
# kubectl delete secret -n tekton-pipelines self-signed
22+
# kubectl create secret tls self-signed --cert tekton.localtest.me+4.pem --key tekton.localtest.me+4-key.pem -n tekton-pipelines
523
#
624
apiVersion: halkyon.io/v1alpha1
725
kind: Platform

0 commit comments

Comments
 (0)