You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against any resource listed will be allowed. '*' represents all resources. Empty string represents v1 api resources.
19
+
APIGroups []string`json:"apiGroups"`
20
+
21
+
// Resources is a list of resources this rule applies to. '*' represents all resources.
22
+
Resources []string`json:"resources"`
23
+
24
+
// Operations which can be executed on the selected resources.
Copy file name to clipboardexpand all lines: charts/capsule-proxy/README.md
+28
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,25 @@ The Capsule-proxy Chart can be used to instantly deploy the Capsule-proxy on you
40
40
41
41
$ helm uninstall capsule-proxy -n capsule-system
42
42
43
+
## Upgrading the Chart
44
+
45
+
Intsructions to upgrade the chart the versions, which may remove features or introduce breaking changes.
46
+
47
+
### 0.7.x
48
+
49
+
Introduces a new methode to manage all capsule-proxy CRDs and their lifecycle. We are no longer relying on the [native CRD hook with the Helm Chart](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations). The hook only allows to manage CRDs on install and uninstall but we can't deliver updates to the CRDs.
50
+
When you newly install the chart we recommend to set `crds.install` to `true`. This will manage the CRDs with the Helm Chart.
51
+
52
+
If you are upgrading to this release, you can choose to set `global.crds.install` to `true` (by default `false`). However you need to add metadata to the existing CRDs so they can be correctly managed with the new flow. Run the following commands:
| crds.install | bool |`false`| Install the CustomResourceDefinitions (This also manages the lifecycle of the CRDs for update operations) |
83
+
| crds.keep | bool |`true`| Keep the CustomResourceDefinitions (when the chart is deleted) |
84
+
59
85
### General Parameters
60
86
61
87
| Key | Type | Default | Description |
@@ -70,6 +96,8 @@ If you only need to make minor customizations, you can specify them on the comma
70
96
| certManager.generateCertificates | bool |`false`| Set if the cert manager will generate SSL certificates (self-signed or CA-signed) |
71
97
| certManager.issuer.kind | string |`"Issuer"`| Set if the cert manager will generate either self-signed or CA signed SSL certificates. Its value will be either Issuer or ClusterIssuer |
72
98
| certManager.issuer.name | string |`""`| Set the name of the ClusterIssuer if issuer kind is ClusterIssuer and if cert manager will generate CA signed SSL certificates |
99
+
| crds.install | bool |`false`| Install the CustomResourceDefinitions (This also manages the lifecycle of the CRDs for update operations) |
100
+
| crds.keep | bool |`true`| Keep the CustomResourceDefinitions (when the chart is deleted) |
73
101
| daemonset.hostNetwork | bool |`false`| Use the host network namespace for capsule-proxy pod. |
74
102
| daemonset.hostPort | bool |`false`| Binding the capsule-proxy listening port to the host port. |
75
103
| hostNetwork | bool |`false`| When deployed as DaemonSet use |
Copy file name to clipboardexpand all lines: charts/capsule-proxy/README.md.gotmpl
+30
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,25 @@ The Capsule-proxy Chart can be used to instantly deploy the Capsule-proxy on you
40
40
41
41
$ helm uninstall capsule-proxy -n capsule-system
42
42
43
+
## Upgrading the Chart
44
+
45
+
Intsructions to upgrade the chart the versions, which may remove features or introduce breaking changes.
46
+
47
+
### 0.7.x
48
+
49
+
Introduces a new methode to manage all capsule-proxy CRDs and their lifecycle. We are no longer relying on the [native CRD hook with the Helm Chart](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations). The hook only allows to manage CRDs on install and uninstall but we can't deliver updates to the CRDs.
50
+
When you newly install the chart we recommend to set `crds.install` to `true`. This will manage the CRDs with the Helm Chart.
51
+
52
+
If you are upgrading to this release, you can choose to set `global.crds.install` to `true` (by default `false`). However you need to add metadata to the existing CRDs so they can be correctly managed with the new flow. Run the following commands:
0 commit comments