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.

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

Open
wants to merge 11 commits into
base: v3.2
Choose a base branch
from
Open

Conversation

diegostrubolini
Copy link
Contributor

Writer's Quality Checklist

Before merging your PR, did you:

  • Run spell checker
  • Run link checker to check for broken xrefs
  • Check for orphan files
  • Perform a local build and do a final visual check of your content, including checking for:
    • Broken images
    • Dead links
    • Correct rendering of partials if they are used in your content
    • Formatting issues, such as:
      • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
      • Messed up tables
      • Proper indentation
      • Correct header levels
  • Receive final review and signoff from:
    • Technical SME
    • Product Manager
    • Editor or peer reviewer
    • Reporter, if this content is in response to a reported issue (internal or external feedback)
  • If applicable, verify that the software actually got released

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^]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants