[FEAT] adding target allocator configs #123
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several updates to the OpenTelemetry Collector Helm chart, primarily adding new configurations for the Target Allocator and improving the deployment configurations.
Key changes include:
New Configurations for Target Allocator:
serviceMonitorNamespaceSelector
,podMonitorNamespaceSelector
,scrapeconfigs
, andprobes
in theclusterrole-targetallocator.yaml
file. [1] [2]serviceMonitorNamespaceSelector
andpodMonitorNamespaceSelector
in the_helpers.tpl
file.configmap-targetallocator.yaml
to include new configurations forserviceMonitorNamespaceSelector
andpodMonitorNamespaceSelector
.Deployment Enhancements:
affinity
,tolerations
,volumeMounts
,livenessProbe
,readinessProbe
, andminReadySeconds
in thedeployment-targetallocator.yaml
file. [1] [2]PodDisruptionBudget
configuration in thepdb-targetallocator.yaml
file.Service and Monitoring Updates:
appProtocol: http
to theservice-targetallocator.yaml
file.ServiceMonitor
configuration in theservicemonitor-targetallocator.yaml
file.Version and Metadata Updates:
0.98.5
in theChart.yaml
file.0.98.5
in theCHANGELOG.md
file.Schema and Values Updates:
values.schema.json
to include new properties fortolerations
,affinity
,volumeMounts
,volumes
,serviceMonitor
,pdb
,livenessProbe
,readinessProbe
, andminReadySeconds
.values.yaml
file to include default values for the new configurations. [1] [2] [3]