Skip to content

Commit 9ce9795

Browse files
committed
Fix
Signed-off-by: Pavol Loffay <[email protected]>
1 parent dbdae76 commit 9ce9795

File tree

2 files changed

+21
-11
lines changed

2 files changed

+21
-11
lines changed

apis/v1alpha1/instrumentation_types.go

+6-5
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ type Resource struct {
9797
// Exporter defines OTLP exporter configuration.
9898
type Exporter struct {
9999
// Endpoint is address of the collector with OTLP endpoint.
100-
// The TLS is enabled
100+
// If the endpoint defines https:// scheme TLS has to be specified.
101101
// +optional
102102
Endpoint string `json:"endpoint,omitempty"`
103103

@@ -110,21 +110,22 @@ type Exporter struct {
110110
type TLS struct {
111111
// SecretName defines secret name that will be used to configure TLS on the exporter.
112112
// It is user responsibility to create the secret in the namespace of the workload.
113-
// The secret should contain keys ca.crt, tls.key, tls.crt
113+
// The secret must contain client certificate (Cert) and private key (Key).
114+
// The CA certificate might be defined in the secret or in the config map.
114115
SecretName string `json:"secretName,omitempty"`
115116

116117
// ConfigMapName defines configmap name with CA certificate. If it is not defined CA certificate will be
117118
// used from the secret defined in SecretName.
118119
ConfigMapName string `json:"configMapName,omitempty"`
119120

120-
// CA defines the key of certificate in the configmap map, secret or absolute path to a certificate.
121+
// CA defines the key of certificate (e.g. ca.crt) in the configmap map, secret or absolute path to a certificate.
121122
// The absolute path can be used when certificate is already present on the workload filesystem e.g.
122123
// /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt
123124
CA string `json:"ca,omitempty"`
124-
// Cert defines the key of the client certificate in the secret or absolute path to a certificate.
125+
// Cert defines the key (e.g. tls.crt) of the client certificate in the secret or absolute path to a certificate.
125126
// The absolute path can be used when certificate is already present on the workload filesystem.
126127
Cert string `json:"cert,omitempty"`
127-
// Key defines a key of the private key in the secret or absolute path to a certificate.
128+
// Key defines a key (e.g. tls.key) of the private key in the secret or absolute path to a certificate.
128129
// The absolute path can be used when certificate is already present on the workload filesystem.
129130
Key string `json:"key,omitempty"`
130131
}

docs/api.md

+15-6
Original file line numberDiff line numberDiff line change
@@ -1626,7 +1626,7 @@ Exporter defines exporter configuration.
16261626
<td>string</td>
16271627
<td>
16281628
Endpoint is address of the collector with OTLP endpoint.
1629-
The TLS is enabled<br/>
1629+
If the endpoint defines https:// scheme TLS has to be specified.<br/>
16301630
</td>
16311631
<td>false</td>
16321632
</tr><tr>
@@ -1662,7 +1662,7 @@ TLS needs to be enabled by specifying https:// scheme in the Endpoint.
16621662
<td><b>ca</b></td>
16631663
<td>string</td>
16641664
<td>
1665-
CA defines the key of certificate in the secret or absolute path to a certificate.
1665+
CA defines the key of certificate (e.g. ca.crt) in the configmap map, secret or absolute path to a certificate.
16661666
The absolute path can be used when certificate is already present on the workload filesystem e.g.
16671667
/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt<br/>
16681668
</td>
@@ -1671,25 +1671,34 @@ The absolute path can be used when certificate is already present on the workloa
16711671
<td><b>cert</b></td>
16721672
<td>string</td>
16731673
<td>
1674-
Cert defines the key of the client certificate in the secret or absolute path to a certificate.
1674+
Cert defines the key (e.g. tls.crt) of the client certificate in the secret or absolute path to a certificate.
16751675
The absolute path can be used when certificate is already present on the workload filesystem.<br/>
16761676
</td>
16771677
<td>false</td>
1678+
</tr><tr>
1679+
<td><b>configMapName</b></td>
1680+
<td>string</td>
1681+
<td>
1682+
ConfigMapName defines configmap name with CA certificate. If it is not defined CA certificate will be
1683+
used from the secret defined in SecretName.<br/>
1684+
</td>
1685+
<td>false</td>
16781686
</tr><tr>
16791687
<td><b>key</b></td>
16801688
<td>string</td>
16811689
<td>
1682-
Key defines a key of the private key in the secret or absolute path to a certificate.
1690+
Key defines a key (e.g. tls.key) of the private key in the secret or absolute path to a certificate.
16831691
The absolute path can be used when certificate is already present on the workload filesystem.<br/>
16841692
</td>
16851693
<td>false</td>
16861694
</tr><tr>
16871695
<td><b>secretName</b></td>
16881696
<td>string</td>
16891697
<td>
1690-
SecretName defines a secret name that will be used to configure TLS on the exporter.
1698+
SecretName defines secret name that will be used to configure TLS on the exporter.
16911699
It is user responsibility to create the secret in the namespace of the workload.
1692-
The secret should contain keys ca.crt, tls.key, tls.crt<br/>
1700+
The secret must contain client certificate (Cert) and private key (Key).
1701+
The CA certificate might be defined in the secret or in the config map.<br/>
16931702
</td>
16941703
<td>false</td>
16951704
</tr></tbody>

0 commit comments

Comments
 (0)