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
[DRAFT] W-14847538 PCE 4.0 Documentation #327
base: v3.2
Are you sure you want to change the base?
Conversation
You define new alerts using a gravity resource called `alert`, as shown in the following example: | ||
== Alerting Rules | ||
|
||
By default prometheus provides a set of alerts which can be found https://github.com/kubernetes-monitoring/kubernetes-mixin/blob/master/runbook.md[here^] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default prometheus provides a set of alerts which can be found https://github.com/kubernetes-monitoring/kubernetes-mixin/blob/master/runbook.md[here^] | |
By default, Prometheus provides a set of alerts which can be found https://github.com/kubernetes-monitoring/kubernetes-mixin/blob/master/runbook.md[here^] |
|
||
== Configure Alerting Rules | ||
|
||
You define new rules using a prometheus resource called `PrometheusRule`, as shown in the following example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You define new rules using a prometheus resource called `PrometheusRule`, as shown in the following example: | |
Define new rules using the `PrometheusRule` resource, as shown in the following example: |
---- | ||
|
||
. Configure the FROM email address by replacing the <SMTP_FROM> value: | ||
. Update Alertmanager configuration with the new file: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. Update Alertmanager configuration with the new file: | |
. Update the Alertmanager configuration with the new file: |
* Load Balancer: Any source that is outside the cluster. | ||
* localhost: The port that is used only within the host where the request started. | ||
|
||
You must ensure that all of the following ports are configured correctly on all nodes. | ||
You must ensure that all the following ports are configured correctly on all nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You must ensure that all the following ports are configured correctly on all nodes. | |
Ensure that all the following ports are configured correctly on all nodes. |
|
||
Ensure that no processes on your system overrides any of these flags. To set a parameter, use `sysctl -w`, as shown in the following example: | ||
|
||
---- | ||
root$ sysctl -w net.ipv4.ip_forward=1 | ||
---- | ||
|
||
To make the changes permanent for the next reboot, write the changes to a file under `/etc/sysctl.d`. Replace the setting in the following example with the setting you are configuring. | ||
To make the changes permanent for the next reboot, write the changes to a file under `/etc/sysctl.d/50-k8s.conf`. Replace the setting in the following example with the setting you are configuring and reload systemd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make the changes permanent for the next reboot, write the changes to a file under `/etc/sysctl.d/50-k8s.conf`. Replace the setting in the following example with the setting you are configuring and reload systemd | |
To make the changes permanent for the next reboot, write the changes to a file under `/etc/sysctl.d/50-k8s.conf`. Replace the setting in the following example with the setting you are configuring and reload systemd. |
Writer's Quality Checklist
Before merging your PR, did you: