fenar

---
apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
  name: sno-hugepages-patch
  namespace: openshift-cluster-node-tuning-operator
spec:
  profile:
    - data: |
        [main]

fenar

### Main Guideline
https://docs.openshift.com/container-platform/4.14/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#sno-configure-for-vdu

### Enable SCTP
https://docs.openshift.com/container-platform/4.14/networking/using-sctp.html
For SNO make sure -> machineconfiguration.openshift.io/role: master

### Install Service Mesh
https://docs.openshift.com/container-platform/4.14/service_mesh/v2x/installing-ossm.html

fenar

---
apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
  name: sno-hugepages-patch
  namespace: openshift-cluster-node-tuning-operator
spec:
  profile:
    - data: |
        [main]

fenar

{
  "annotations": {
    "list": [
      {
        "builtIn": 1,
        "datasource": {
          "type": "grafana",
          "uid": "-- Grafana --"
        },
        "enable": true,

fenar

{
  "annotations": {
    "list": [
      {
        "builtIn": 1,
        "datasource": {
          "type": "grafana",
          "uid": "-- Grafana --"
        },
        "enable": true,

fenar

---Incase You Have a Messed-Up Bios---- Start
(A) Clear all pending jobs via iDRAC WebUI: Maintenance -> Job Queue

(B) Revert back to initial BIOS
ssh to iDRAC terminal
% ssh root@
racadm>>racadm recover BIOS.Setup.1-1
---Incase You Have a Messed-Up Bios---- End

Enabling Dell-Intel-E810 on Server Side

fenar

Error: kubelet_node_status "unable to register node with api server" err="nodes is forbidden: user \"system:anonymous\" cannot create resource \"nodes\" in api group \"\" at the cluster scope"
<br>
$ oc get csr
<br>
'''
NAME                                                    AGE    SIGNERNAME                                    REQUESTOR                                                                         REQUESTEDDURATION   CONDITION
csr-7vmxb                                               33m    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper         <none>              Pending
csr-c2hc8                                               8m5s   kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-machine-config-operator:node-bootstrapper         <none>              Pending
csr-nd65q                                               23m    kubernetes.io/kube-apiserver-client-kubelet   system:serviceaccount:openshift-mach

fenar

Here is an example Ansible playbook that can be used to claim a hibernated cluster over Red Hat Advanced Cluster Manager (ACM):
---
---
- name: Claim a hibernated cluster on Red Hat ACM
  hosts: localhost
  gather_facts: no

  vars:
    acm_username: "acm-admin"
    acm_password: "mypassword"

fenar

Here's an example of a liveness probe that checks if Apache is able to handle incoming web traffic on an OpenShift container:
---
apiVersion: v1
kind: Pod
metadata:
  name: my-apache-pod
spec:
  containers:
  - name: apache
    image: httpd:2.4

fenar

#Requirements:
1x RHACM HUB
2x+ Managed Clusters

#Join clusters
Go ahead and make sure that all your ManagedClusters joined the RHACM Hub and are in ready state.

#ManagedClusters must have labels that will be used for app placement together with the LatencyCheck operator. For example, if we plan to use the label `ddosify` as the one used by the operator when creating the PlacementRule, that label should have the following values:

- If using locationMatchingStrategy set to city: NA.US.TX.SA