Skip to content
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.

Sign up for GitHub

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

Update from component template #202

Merged
merged 2 commits into from
Jun 6, 2024
Merged

Update from component template #202

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b6353b9
Update from template
simu Jun 6, 2024
32774eb
Update golden test outputs
simu Jun 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .cruft.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"template": "https://github.com/projectsyn/commodore-component-template.git",
"commit": "e0fcaa457a78109244747e0879a87e0adaabbd10",
"commit": "073a838986e0d4a0af14095c5983d06faa9cd8fc",
"checkout": "main",
"context": {
"cookiecutter": {
Expand All @@ -13,6 +13,8 @@
"add_golden": "y",
"add_matrix": "y",
"add_go_unit": "n",
"automerge_patch": "y",
"automerge_patch_v0": "n",
"copyright_holder": "VSHN AG <info@vshn.ch>",
"copyright_year": "2021",
"github_owner": "appuio",
Expand Down
14 changes: 13 additions & 1 deletion renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,5 +18,17 @@
"labels": [
"dependency"
],
"separateMinorPatch": true
"separateMinorPatch": true,
"packageRules": [
{
"matchUpdateTypes": ["patch"],
"matchCurrentVersion": "!/^v?0\\./",
"automerge": true,
"platformAutomerge": false,
"labels": [
"dependency",
"automerge"
]
}
]
}
16 changes: 6 additions & 10 deletions ...alerts-with-node-labels/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -392,17 +392,13 @@ spec:
syn_component: openshift4-monitoring
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
16 changes: 6 additions & 10 deletions .../golden/capacity-alerts/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -392,17 +392,13 @@ spec:
syn_component: openshift4-monitoring
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
16 changes: 6 additions & 10 deletions ...s/golden/ovn-kubernetes/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -526,17 +526,13 @@ spec:
syn_component: openshift4-monitoring
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
16 changes: 6 additions & 10 deletions tests/golden/release-4.14/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -392,17 +392,13 @@ spec:
syn_component: openshift4-monitoring
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
16 changes: 6 additions & 10 deletions tests/golden/remote-write/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -392,17 +392,13 @@ spec:
syn_component: openshift4-monitoring
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
16 changes: 6 additions & 10 deletions tests/golden/team-routing/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -413,17 +413,13 @@ spec:
syn_team: clumsy-donkeys
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
16 changes: 6 additions & 10 deletions ...ser-workload-monitoring/openshift4-monitoring/openshift4-monitoring/prometheus_rules.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -392,17 +392,13 @@ spec:
syn_component: openshift4-monitoring
- alert: SYN_HighOverallControlPlaneCPU
annotations:
description: Given three control plane nodes, the overall CPU utilization
may only be about 2/3 of all available capacity. This is because if
a single control plane node fails, the remaining two must handle the
load of the cluster in order to be HA. If the cluster is using more
than 2/3 of all capacity, if one control plane node fails, the remaining
two are likely to fail when they take the load. To fix this, increase
the CPU and memory on your control plane nodes.
description: |-
On a multi-node cluster with three control plane nodes, the overall CPU utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the remaining two must handle the load of the cluster in order to be HA. If the cluster is using more than 2/3 of all capacity, if one control plane node fails, the remaining two are likely to fail when they take the load. To fix this, increase the CPU and memory on your control plane nodes.
On a single node OpenShift (SNO) cluster, this alert will also fire if the 2/3 of the CPU cores of the node are in use by any workload. This level of CPU utlization of an SNO cluster is probably not a problem under most circumstances, but high levels of utilization may result in degraded performance. To manage this alert or silence it in case of false positives see the following link: https://docs.openshift.com/container-platform/latest/monitoring/managing-alerts.html
runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-kube-apiserver-operator/ExtremelyHighIndividualControlPlaneCPU.md
summary: CPU utilization across all three control plane nodes is higher
than two control plane nodes can sustain; a single control plane node
outage may cause a cascading failure; increase available CPU.
summary: CPU utilization across all control plane nodes is more than 60%
of the total available CPU. Control plane node outage may cause a cascading
failure; increase available CPU.
syn_component: openshift4-monitoring
expr: |
sum(
Expand Down
Loading
Loading