-
Notifications
You must be signed in to change notification settings - Fork 530
Add TLS support to auto-instrumentation #3338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: enhancement | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action) | ||
component: auto-instrumentation | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Add support for specifying exporter TLS certificates in auto-instrumentation. | ||
|
||
# One or more tracking issues related to the change | ||
issues: [3338] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | | ||
Now Instrumentation CR supports specifying TLS certificates for exporter: | ||
```yaml | ||
spec: | ||
exporter: | ||
endpoint: https://otel-collector:4317 | ||
tls: | ||
secretName: otel-tls-certs | ||
configMapName: otel-ca-bundle | ||
# otel-ca-bundle | ||
ca: ca.crt | ||
# present in otel-tls-certs | ||
cert: tls.crt | ||
# present in otel-tls-certs | ||
key: tls.key | ||
``` | ||
|
||
* Propagating secrets across namespaces can be done with https://github.com/EmberStack/kubernetes-reflector or https://github.com/zakkg3/ClusterSecret | ||
* Restarting workloads on certificate renewal can be done with https://github.com/stakater/Reloader or https://github.com/wave-k8s/wave |
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
|
@@ -97,8 +97,37 @@ type Resource struct { | |||||||
// Exporter defines OTLP exporter configuration. | ||||||||
type Exporter struct { | ||||||||
// Endpoint is address of the collector with OTLP endpoint. | ||||||||
// If the endpoint defines https:// scheme TLS has to be specified. | ||||||||
// +optional | ||||||||
Endpoint string `json:"endpoint,omitempty"` | ||||||||
|
||||||||
// TLS defines certificates for TLS. | ||||||||
// TLS needs to be enabled by specifying https:// scheme in the Endpoint. | ||||||||
TLS *TLS `json:"tls,omitempty"` | ||||||||
} | ||||||||
|
||||||||
// TLS defines TLS configuration for exporter. | ||||||||
type TLS struct { | ||||||||
// SecretName defines secret name that will be used to configure TLS on the exporter. | ||||||||
// It is user responsibility to create the secret in the namespace of the workload. | ||||||||
// The secret must contain client certificate (Cert) and private key (Key). | ||||||||
// The CA certificate might be defined in the secret or in the config map. | ||||||||
SecretName string `json:"secretName,omitempty"` | ||||||||
|
||||||||
// ConfigMapName defines configmap name with CA certificate. If it is not defined CA certificate will be | ||||||||
// used from the secret defined in SecretName. | ||||||||
ConfigMapName string `json:"configMapName,omitempty"` | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure about this name because it is something associated to the CA directly. Maybe |
||||||||
|
||||||||
// CA defines the key of certificate (e.g. ca.crt) in the configmap map, secret or absolute path to a certificate. | ||||||||
// The absolute path can be used when certificate is already present on the workload filesystem e.g. | ||||||||
// /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @frzifus what does the We should get rid of it https://book.kubebuilder.io/reference/markers I will submit a follow up PR to remove |
||||||||
CA string `json:"ca,omitempty"` | ||||||||
// Cert defines the key (e.g. tls.crt) of the client certificate in the secret or absolute path to a certificate. | ||||||||
// The absolute path can be used when certificate is already present on the workload filesystem. | ||||||||
Cert string `json:"cert,omitempty"` | ||||||||
// Key defines a key (e.g. tls.key) of the private key in the secret or absolute path to a certificate. | ||||||||
// The absolute path can be used when certificate is already present on the workload filesystem. | ||||||||
Key string `json:"key,omitempty"` | ||||||||
} | ||||||||
|
||||||||
// Sampler defines sampling configuration. | ||||||||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -236,6 +236,14 @@ func (w InstrumentationWebhook) validate(r *Instrumentation) (admission.Warnings | |
default: | ||
return warnings, fmt.Errorf("spec.sampler.type is not valid: %s", r.Spec.Sampler.Type) | ||
} | ||
|
||
if r.Spec.Exporter.TLS != nil { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let's also add a validation that if the scheme for the endpoint contains There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no, this can break already existing installations. Users could configure env vars in the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let's go the reverse and if TLS is set we should block when https is not set. If HTTPS is set, TLS doesn't need to be set. |
||
tls := r.Spec.Exporter.TLS | ||
if tls.Key != "" && tls.Cert == "" || tls.Cert != "" && tls.Key == "" { | ||
warnings = append(warnings, "both exporter.tls.key and exporter.tls.cert mut be set") | ||
} | ||
} | ||
|
||
return warnings, nil | ||
} | ||
|
||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,7 +30,9 @@ rules: | |
- "" | ||
resources: | ||
- namespaces | ||
- secrets | ||
verbs: | ||
- get | ||
- list | ||
- watch | ||
- apiGroups: | ||
|
Uh oh!
There was an error while loading. Please reload this page.