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

Jump to bottom

TELCODOCS-1836 - Adding telco core 4.14.z RDS updates #75675

Merged
merged 1 commit into from May 20, 2024
Merged

TELCODOCS-1836 - Adding telco core 4.14.z RDS updates #75675

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 9 additions & 2 deletions modules/telco-core-ref-application-workloads.adoc
View file
Open in desktop
@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * telco_ref_design_specs/ran/telco-ran-ref-design-spec.adoc
// * telco_ref_design_specs/core/telco-core-rds-use-cases.adoc

:_mod-docs-content-type: REFERENCE
[id="telco-core-ref-application-workloads_{context}"]
Expand All @@ -14,7 +14,7 @@ Pods running network functions that do not require the high throughput and low l

Description of limits::

* CNF applications should conform to the latest version of the _CNF Best Practices_ guide.
* CNF applications should conform to the latest version of link:https://test-network-function.github.io/cnf-best-practices-guide/[Red Hat Best Practices for Kubernetes].
* For a mix of best-effort and burstable QoS pods.
** Guaranteed QoS pods might be used but require correct configuration of reserved and isolated CPUs in the `PerformanceProfile`.
** Guaranteed QoS Pods must include annotations for fully isolating CPUs.
Expand All @@ -23,6 +23,13 @@ Description of limits::
** Do not use exec probes if a CNF is using CPU pinning.
** Other probe implementations, for example `httpGet/tcpSocket`, should be used.

+
[NOTE]
====
Startup probes require minimal resources during steady-state operation.
The limitation on exec probes applies primarily to liveness and readiness probes.
====

Signaling workload::

* Signaling workloads typically use SCTP, REST, gRPC, or similar TCP or UDP protocols.
Expand Down
1 change: 0 additions & 1 deletion modules/telco-ran-du-application-workloads.adoc
View file
Open in desktop
Expand Up @@ -22,7 +22,6 @@ Use other probe implementations, for example, `httpGet` or `tcpSocket`.
** When you need to use exec probes, limit the exec probe frequency and quantity.
The maximum number of exec probes must be kept below 10, and frequency must not be set to less than 10 seconds.

+
[NOTE]
====
Startup probes require minimal resources during steady-state operation.
Expand Down