trying to deploy loki and promtail

docs/k3s/k3s-config.yaml

@@ -0,0 +1,19 @@
+# Configuration file for k3s
+
+# Node Configuration
+node-name: "my-k3s-node" # The name of the node
+token: 95e2850a0e0b505b8b677661885509a2
+
+# TLS Configuration
+tls-san: 192.168.5.200
+
+# ETCD configuration
+etcd-snapshot-schedule-cron: "0 */6 * * *" #Schedule ETCD snapshots every 6 hours
+etcd-snapshot-retention: 7 # Retain the last 7 snapshots
+etcd-snapshot-dir: "/var/lib/rancher/k3s/etcd/snapshots" # Directory to store ETCD snapshots
+
+# Security Configuration
+# List of features to disable
+disable:
+  - "traefik"
+  - "servicelb"

docs/k3s/k3s-registry.yaml

@@ -0,0 +1,11 @@
+mirrors:
+  "192.168.7.210:5000":
+    endpoint:
+      - "http://192.168.7.210:5000"
+configs:
+  "192.168.7.210:5000":
+    tls:
+      insecure_skip_verify: true
+  "docker.io":
+    tls:
+      insecure_skip_verify: true

docs/k3s/specs.md

@@ -0,0 +1,51 @@
+# Recommended Specifications for a Production k3s Cluster
+
+## Control Plane Node (Master)
+
+1. **Boot Drive (ETCD Storage)**:
+
+   - **Type**: SSD (NVMe preferred for higher performance and reliability)
+   - **Size**: 100 GB or more (depending on the size and number of resources managed by the cluster)
+
+2. **Storage Drive**:
+
+   - **Type**: SSD (NVMe preferred)
+   - **Size**: 100 GB or more (separate from the boot drive for storing persistent data and logs)
+
+3. **CPU / Cores**:
+
+   - **Cores**: 4 cores (minimum)
+   - **Type**: Multi-core processor (modern Intel or AMD processors with high clock speeds)
+
+4. **Memory**:
+   - **RAM**: 16 GB (minimum)
+
+## Worker Node
+
+1. **Boot Drive**:
+
+   - **Type**: SSD (NVMe preferred)
+   - **Size**: 50 GB or more (sufficient for OS and k3s runtime)
+
+2. **Storage Drive**:
+
+   - **Type**: SSD (NVMe preferred)
+   - **Size**: 100 GB or more (additional storage can be added based on workload requirements)
+
+3. **CPU / Cores**:
+
+   - **Cores**: 2 cores (minimum)
+   - **Type**: Multi-core processor (modern Intel or AMD processors with good performance per core)
+
+4. **Memory**:
+   - **RAM**: 8 GB (minimum)
+
+## Additional Considerations
+
+- **High Availability**: For a highly available control plane, deploy at least three control plane nodes to ensure resilience and fault tolerance.
+- **Network**: Ensure high-speed networking (1 Gbps or higher) between nodes for optimal performance.
+- **Backup and Recovery**: Implement regular backups of ETCD and other critical data to ensure disaster recovery capabilities.
+- **Monitoring and Logging**: Deploy comprehensive monitoring and logging solutions to track the health and performance of the cluster.
+- **Load Balancing**: Consider using a load balancer in front of the control plane nodes to distribute traffic evenly and provide redundancy.
+
+These recommendations aim to provide a robust and reliable k3s production cluster. Adjustments may be necessary based on specific workload requirements and performance benchmarks.

kubernetes/apps/homepage-dashboard/config-map.yaml

@@ -111,6 +111,12 @@ data:
           description: PGAdmin for Postgres
           target: _blank
 
+      - Redis:
+          icon: redis.svg
+          href: http://redis-insight.pnfb.home
+          description: World’s fastest data platform
+          target: _blank
+
       - Grafana:
           icon: grafana.png
           href: http://grafana.pnfb.home
@@ -123,6 +129,12 @@ data:
           description: Open-source monitoring system
           target: _blank
 
+      - Loki:
+          icon: loki.png
+          href: http://loki.pnfb.home
+          description: Fully featured logging stack
+          target: _blank
+
       - Longhorn:
           icon: longhorn.png
           href: http://longhorn.pnfb.home
@@ -135,11 +147,6 @@ data:
           description: Domain and network tunnel
           target: _blank
 
-      - Redis:
-          icon: redis.svg
-          href: http://redis-insight.pnfb.home
-          description: World’s fastest data platform
-          target: _blank
 
 
     - Docker: