3
3
4
4
A Helm chart for deploying Sigstore scaffold chart that is opinionated for OpenShift
5
5
6
- ![ Version: 0.1.29 ] ( https://img.shields.io/badge/Version-0.1.29 -informational?style=flat-square ) ![ Type: application] ( https://img.shields.io/badge/Type-application-informational?style=flat-square )
6
+ ![ Version: 0.1.30 ] ( https://img.shields.io/badge/Version-0.1.30 -informational?style=flat-square ) ![ Type: application] ( https://img.shields.io/badge/Type-application-informational?style=flat-square )
7
7
8
8
## Overview
9
9
10
10
This wrapper chart builds on top of the [ Scaffold] ( https://github.com/sigstore/helm-charts/tree/main/charts/scaffold )
11
11
chart from the Sigstore project to both simplify and satisfy the requirements for deployment within an OpenShift
12
12
13
- If you have already read this document and want a quick no-fail path to installing a Sigstore stack with RH SSO,
13
+ Refer to the quick-start to install Sigstore components on OpenShift with the upstream Sigstore OIDC Issuer URL,
14
+ [ quickstart quide] ( docs/quick-start-with-sigstore-issuer.md )
15
+
16
+ For a quick no-fail path to installing a Sigstore stack with RH SSO,
14
17
follow [ quick start] ( ../../docs/quick-start-with-keycloak.md )
15
18
16
19
The chart enhances the scaffold chart by taking care of the following:
@@ -35,15 +38,48 @@ scaffold:
35
38
36
39
### Sample Implementation
37
40
38
- #### Prerequisites
39
-
40
- The following must be satisfied prior to deploying the sample implementation:
41
+ The installer and the quick start with RedHat SSO script include the creation of the necessary secrets:
41
42
42
43
* Fulcio root CA certificate and signing keys
43
44
* More information in [ requirements-keys-certs.md] ( ../../docs/requirements-keys-certs.md )
44
45
* OpenID Token Issuer endpoint
46
+ * The public Sigstore OIDC Issuer URL ` https://oauth2.sigstore.dev/auth ` is configured in the absence of any other OIDC provider.
45
47
* Keycloak/RHSSO requirements can be followed and deployed in OpenShift with [ keycloak-example.md] ( ../../docs/keycloak-example.md )
46
48
49
+ To add configuration options to the TAS installation, either provide a custom ` values.yaml ` or provide available flags to the ` tas-install `
50
+ command.
51
+
52
+ #### Configure the install with the ` tas-install ` command flags.
53
+
54
+ Here are the available options for use with ` tas-install ` . For any other customization, you may provide a ` values.yaml ` with necessary
55
+ information.
56
+
57
+ ```
58
+ $ ./tas-install install -h
59
+ Installs Trusted Artifact Signer (TAS) on a Kubernetes cluster.
60
+
61
+ This command performs a series of actions:
62
+ 1. Initializes the Kubernetes client to interact with your cluster
63
+ 2. Sets up necessary certificates
64
+ 3. Configures secrets
65
+ 4. Deploys TAS to openshift
66
+
67
+ Usage:
68
+ tas-installer install [flags]
69
+
70
+ Flags:
71
+ --chart-location string /local/path/to/chart or oci://registry/repo location of Helm chart (default "./charts/trusted-artifact-signer")
72
+ --chart-version string Version of the Helm chart (default "0.1.29")
73
+ -h, --help help for install
74
+ --oidc-client-id string Specify the OIDC client ID
75
+ --oidc-issuer-url string Specify the OIDC issuer URL e.g for keycloak: https://[keycloak-domain]/auth/realms/[realm-name]
76
+ --oidc-type string Specify the OIDC type
77
+ --values string path to custom values file for chart configuration
78
+
79
+ Global Flags:
80
+ --kubeconfig string Specify the kubeconfig path (default "/Users/somalley/.kube/config")
81
+ ```
82
+
47
83
#### Update the values file
48
84
49
85
Helm values files are available in the examples directory that provides a baseline to work off of.
@@ -55,15 +91,6 @@ to curate the deployment of the chart:
55
91
56
92
2 . Perform any additional customizations as desired
57
93
58
- ### Installing the Chart
59
-
60
- When logged in as an elevated OpenShift user, execute the following to install the chart referencing the
61
- customized values file. The OPENSHIFT_APPS_SUBDOMAIN will be substituted in the values file with ` envsubst ` below:
62
-
63
- ``` shell
64
- OPENSHIFT_APPS_SUBDOMAIN=apps.$( oc get dns cluster -o jsonpath=' { .spec.baseDomain }' ) envsubst < examples/values-sigstore-openshift.yaml | helm upgrade -i trusted-artifact-signer --debug charts/trusted-artifact-signer -n sigstore --create-namespace --values -
65
- ```
66
-
67
94
### Monitor Sigstore Components with Grafana
68
95
69
96
For real-time analytics through Grafana, refer to our [ enable-grafana-monitoring.md] ( ../../docs/enable-grafana-monitoring.md ) guide.
0 commit comments