forked from sigstore/helm-charts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.md.gotmpl
108 lines (86 loc) · 2.57 KB
/
README.md.gotmpl
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
{{ template "chart.header" . }}
<!-- This README.md is generated. Please edit README.md.gotmpl -->
{{ template "chart.deprecationWarning" . }}
{{ template "chart.badgesSection" . }}
{{ template "chart.description" . }}
{{ template "chart.homepageLine" . }}
The following components are also included as either direct components or through chart dependencies:
* [ctlog](https://github.com/sigstore/helm-charts/tree/main/charts/ctlog)
> **Note**: `0.3.0` NOT backwards compatible
>
> In version `0.3.0`, we will be introducing a second ingress in support of the new gRPC endpoint as introduced in `v0.4.0` of Fulcio.
>
> The change in particular is the structure of the ingress values.
>
> **Previously**
>
> ```shell
> server:
> ingress:
> enabled: true
> hosts:
> - host: fulcio.localhost
> path: /
> ```
>
> **Now**
>
> ```shell
> server:
> ingress:
> http:
> enabled: true
> hosts:
> - host: fulcio.localhost
> path: /
> grpc:
> enabled: false
> ```
## Quick Installation
To install the helm chart with default values run following command.
The [Values](#Values) section describes the configuration options for this chart.
```shell
helm dependency update .
helm install [RELEASE_NAME] .
```
## Uninstallation
To uninstall the Helm chart run following command.
```shell
helm uninstall [RELEASE_NAME]
```
{{ template "chart.maintainersSection" . }}
{{ template "chart.sourcesSection" . }}
{{ template "chart.requirementsSection" . }}
{{ template "chart.valuesSection" . }}
----------------------------------------------
## Ingress
To enabled access from external resources, an Ingress resource is created. The configuration necessary for each Ingress resource is primarily dependent on the specific Ingress Controller being used. In most cases, implementation specific configuration is specified as annotations on the Ingress resources. These can be applied using the `server.ingress.annotations` parameter.
> **Warning**: versions prior to `0.3.0` of this chart use different ingresses.
>
> In version `0.3.0` a second ingress is introduced. This ingress exposes the gRPC endpoint as introduced in v0.4.0 of Fulcio.
>
> The change in particular is the structure of the ingress values.
> Prior to `0.3.0`:
>
> ```shell
> server:
> ingress:
> enabled: true
> hosts:
> - host: fulcio.localhost
> path: /
> ```
>
> Since `0.3.0`:
>
> ```shell
> server:
> ingress:
> http:
> enabled: true
> hosts:
> - host: fulcio.localhost
> path: /
> grpc:
> enabled: false
> ```