Skip to content

Commit

Permalink
[opentelemetry-operator] - BUMP operator to 0.60.0 (open-telemetry#385)
Browse files Browse the repository at this point in the history 
Signed-off-by: birca <[email protected]>
  • Loading branch information
@Allex1
Allex1 authored Sep 26, 2022
1 parent df87fa1 commit f43c632
Show file tree
Hide file tree
Showing 4 changed files with 145 additions and 7 deletions.
4 changes: 2 additions & 2 deletions charts/opentelemetry-operator/Chart.yaml
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
apiVersion: v2
name: opentelemetry-operator
version: 0.12.2
version: 0.13.0
description: OpenTelemetry Operator Helm chart for Kubernetes
type: application
home: https://opentelemetry.io/
Expand All @@ -11,4 +11,4 @@ maintainers:
- name: dmitryax
- name: TylerHelmuth
icon: https://raw.githubusercontent.com/cncf/artwork/a718fa97fffec1b9fd14147682e9e3ac0c8817cb/projects/opentelemetry/icon/color/opentelemetry-icon-color.png
appVersion: 0.59.0
appVersion: 0.60.0
138 changes: 138 additions & 0 deletions charts/opentelemetry-operator/crds/crd-opentelemetrycollector.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,130 @@ spec:
description: Args is the set of arguments to pass to the OpenTelemetry
Collector binary
type: object
autoscaler:
description: Autoscaler specifies the pod autoscaling configuration
to use for the OpenTelemetryCollector workload.
properties:
behavior:
description: HorizontalPodAutoscalerBehavior configures the scaling
behavior of the target in both Up and Down directions (scaleUp
and scaleDown fields respectively).
properties:
scaleDown:
description: scaleDown is scaling policy for scaling Down.
If not set, the default value is to allow to scale down
to minReplicas pods, with a 300 second stabilization window
(i.e., the highest recommendation for the last 300sec is
used).
properties:
policies:
description: policies is a list of potential scaling polices
which can be used during scaling. At least one policy
must be specified, otherwise the HPAScalingRules will
be discarded as invalid
items:
description: HPAScalingPolicy is a single policy which
must hold true for a specified past interval.
properties:
periodSeconds:
description: PeriodSeconds specifies the window
of time for which the policy should hold true.
PeriodSeconds must be greater than zero and less
than or equal to 1800 (30 min).
format: int32
type: integer
type:
description: Type is used to specify the scaling
policy.
type: string
value:
description: Value contains the amount of change
which is permitted by the policy. It must be greater
than zero
format: int32
type: integer
required:
- periodSeconds
- type
- value
type: object
type: array
x-kubernetes-list-type: atomic
selectPolicy:
description: selectPolicy is used to specify which policy
should be used. If not set, the default value Max is
used.
type: string
stabilizationWindowSeconds:
description: 'StabilizationWindowSeconds is the number
of seconds for which past recommendations should be
considered while scaling up or scaling down. StabilizationWindowSeconds
must be greater than or equal to zero and less than
or equal to 3600 (one hour). If not set, use the default
values: - For scale up: 0 (i.e. no stabilization is
done). - For scale down: 300 (i.e. the stabilization
window is 300 seconds long).'
format: int32
type: integer
type: object
scaleUp:
description: 'scaleUp is scaling policy for scaling Up. If
not set, the default value is the higher of: * increase
no more than 4 pods per 60 seconds * double the number of
pods per 60 seconds No stabilization is used.'
properties:
policies:
description: policies is a list of potential scaling polices
which can be used during scaling. At least one policy
must be specified, otherwise the HPAScalingRules will
be discarded as invalid
items:
description: HPAScalingPolicy is a single policy which
must hold true for a specified past interval.
properties:
periodSeconds:
description: PeriodSeconds specifies the window
of time for which the policy should hold true.
PeriodSeconds must be greater than zero and less
than or equal to 1800 (30 min).
format: int32
type: integer
type:
description: Type is used to specify the scaling
policy.
type: string
value:
description: Value contains the amount of change
which is permitted by the policy. It must be greater
than zero
format: int32
type: integer
required:
- periodSeconds
- type
- value
type: object
type: array
x-kubernetes-list-type: atomic
selectPolicy:
description: selectPolicy is used to specify which policy
should be used. If not set, the default value Max is
used.
type: string
stabilizationWindowSeconds:
description: 'StabilizationWindowSeconds is the number
of seconds for which past recommendations should be
considered while scaling up or scaling down. StabilizationWindowSeconds
must be greater than or equal to zero and less than
or equal to 3600 (one hour). If not set, use the default
values: - For scale up: 0 (i.e. no stabilization is
done). - For scale down: 300 (i.e. the stabilization
window is 300 seconds long).'
format: int32
type: integer
type: object
type: object
type: object
config:
description: Config is the raw JSON to be used as the collector's
configuration. Refer to the OpenTelemetry Collector documentation
Expand Down Expand Up @@ -681,6 +805,12 @@ spec:
description: TargetAllocator indicates a value which determines whether
to spawn a target allocation resource or not.
properties:
allocationStrategy:
description: AllocationStrategy determines which strategy the
target allocator should use for allocation. The current options
are least-weighted and consistent-hashing. The default option
is least-weighted
type: string
enabled:
description: Enabled indicates whether to use a target allocation
mechanism for Prometheus targets or not.
Expand All @@ -701,6 +831,14 @@ spec:
custom resources as targets or not.
type: boolean
type: object
replicas:
description: Replicas is the number of pod instances for the underlying
TargetAllocator. This should only be set to a value other than
1 if a strategy that allows for high availability is chosen.
Currently, the only allocation strategy that can be run in a
high availability mode is consistent-hashing.
format: int32
type: integer
serviceAccount:
description: ServiceAccount indicates the name of an existing
service account to use with this instance.
Expand Down
8 changes: 4 additions & 4 deletions charts/opentelemetry-operator/values.schema.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -84,13 +84,13 @@
"default": "",
"title": "The tag Schema",
"examples": [
"v0.59.0"
"v0.60.0"
]
}
},
"examples": [{
"repository": "ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator",
"tag": "v0.59.0"
"tag": "v0.60.0"
}]
},
"collectorImage": {
Expand Down Expand Up @@ -444,7 +444,7 @@
"examples": [{
"image": {
"repository": "ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator",
"tag": "v0.59.0"
"tag": "v0.60.0"
},
"collectorImage": {
"repository": "otel/opentelemetry-collector",
Expand Down Expand Up @@ -867,7 +867,7 @@
"manager": {
"image": {
"repository": "ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator",
"tag": "v0.59.0"
"tag": "v0.60.0"
},
"collectorImage": {
"repository": "otel/opentelemetry-collector",
Expand Down
2 changes: 1 addition & 1 deletion charts/opentelemetry-operator/values.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ imagePullSecrets: []
manager:
image:
repository: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
tag: v0.59.0
tag: v0.60.0
collectorImage:
repository: otel/opentelemetry-collector
tag: 0.60.0
Expand Down

0 comments on commit f43c632

Please sign in to comment.