refactor from sphinx to mkdocs for added functionality and ease of use
This commit is contained in:
rskntroot
20
compose.yml
20
compose.yml
@@ -1,12 +1,4 @@
|
||||
services:
|
||||
sphinx-docs:
|
||||
image: rskio/sphinx-docs
|
||||
build: .
|
||||
volumes:
|
||||
- ./docs/:/opt/sphinx/
|
||||
- ./bin/entrypoint.sh:/opt/entrypoint.sh
|
||||
entrypoint: /opt/entrypoint.sh
|
||||
|
||||
traefik:
|
||||
image: traefik:latest
|
||||
command:
|
||||
@@ -21,8 +13,8 @@ services:
|
||||
- ./traefik/log:/var/log/traefik
|
||||
- ./traefik/tls:/letsencrypt
|
||||
|
||||
nginx:
|
||||
image: nginx:latest
|
||||
mkdocs:
|
||||
image: squidfunk/mkdocs-material
|
||||
labels:
|
||||
- traefik.enable=true
|
||||
- traefik.http.routers.rskio.entrypoints=websecure
|
||||
@@ -30,11 +22,7 @@ services:
|
||||
- traefik.http.routers.rskio.tls=true
|
||||
- traefik.http.routers.rskio.tls.certresolver=rskio_certresolver
|
||||
- traefik.http.routers.rskio.service=rskio@docker
|
||||
- traefik.http.services.rskio.loadbalancer.server.port=80
|
||||
- traefik.http.services.rskio.loadbalancer.server.port=8000
|
||||
volumes:
|
||||
- ./docs/build/html:/opt/sphinx/html/:ro
|
||||
- ./nginx/etc/conf.d/:/etc/nginx/conf.d/:ro
|
||||
depends_on:
|
||||
sphinx-docs:
|
||||
condition: service_completed_successfully
|
||||
- ./mkdocs:/docs
|
||||
|
||||
|
||||
@@ -1,20 +0,0 @@
|
||||
# Minimal makefile for Sphinx documentation
|
||||
#
|
||||
|
||||
# You can set these variables from the command line, and also
|
||||
# from the environment for the first two.
|
||||
SPHINXOPTS ?=
|
||||
SPHINXBUILD ?= sphinx-build
|
||||
SOURCEDIR = source
|
||||
BUILDDIR = build
|
||||
|
||||
# Put it first so that "make" without argument is like "make help".
|
||||
help:
|
||||
@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
|
||||
|
||||
.PHONY: help Makefile
|
||||
|
||||
# Catch-all target: route all unknown targets to Sphinx using the new
|
||||
# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS).
|
||||
%: Makefile
|
||||
@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
|
||||
@@ -1,28 +0,0 @@
|
||||
# Configuration file for the Sphinx documentation builder.
|
||||
#
|
||||
# For the full list of built-in configuration values, see the documentation:
|
||||
# https://www.sphinx-doc.org/en/master/usage/configuration.html
|
||||
|
||||
# -- Project information -----------------------------------------------------
|
||||
# https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
|
||||
|
||||
project = 'Rskio'
|
||||
copyright = '2024, rskntroot'
|
||||
author = 'rskntroot'
|
||||
release = '1.0.1'
|
||||
|
||||
# -- General configuration ---------------------------------------------------
|
||||
# https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration
|
||||
|
||||
# Markdown Support - https://www.sphinx-doc.org/en/master/usage/markdown.html
|
||||
extensions = ['myst_parser']
|
||||
|
||||
templates_path = ['_templates']
|
||||
exclude_patterns = []
|
||||
|
||||
# -- Options for HTML output -------------------------------------------------
|
||||
# https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output
|
||||
|
||||
# PyData Theme - https://pydata-sphinx-theme.readthedocs.io/en/stable/index.html (0.15.3)
|
||||
html_theme = "furo"
|
||||
html_static_path = ['_static']
|
||||
@@ -1,238 +0,0 @@
|
||||
# K3S Traefik Setup
|
||||
|
||||
## Brief
|
||||
|
||||
Enabling internal access to dashboard and metrics for traefik ingress controller in k3s kubernetes cluster
|
||||
|
||||
- by `rskntroot` on `2024-07-01`
|
||||
|
||||
## Assumptions
|
||||
|
||||
```
|
||||
$ k3s --version
|
||||
k3s version v1.29.5+k3s1 (4e53a323)
|
||||
go version go1.21.9
|
||||
```
|
||||
|
||||
```
|
||||
$ kubectl version
|
||||
Client Version: v1.29.5+k3s1
|
||||
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
|
||||
Server Version: v1.29.5+k3s1
|
||||
```
|
||||
|
||||
## Traefik Dashboards
|
||||
|
||||
*Note: `Traefik Dashboards` refers to both traefik dashboard and prometheus*
|
||||
|
||||
### Preparation
|
||||
|
||||
Enable `internal`+`.your.domain.com` in non-public DNS
|
||||
- (alt) edit the `hosts` file on your admin to point the desired k3s host IP
|
||||
|
||||
On host with `kubectl` access:
|
||||
```
|
||||
export DOMAIN=your.domain.com
|
||||
```
|
||||
|
||||
*Note: This example does not currently include authentication and exposing these dashboards is a security risk.*
|
||||
|
||||
### Update Manifest
|
||||
|
||||
Add the following to `spec.valuesContent` section of `/var/lib/rancher/k3s/server/manifests/traefik.yaml`
|
||||
```
|
||||
dashboard:
|
||||
enabled: true
|
||||
metrics:
|
||||
prometheus: true
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
spec:
|
||||
chart: https://%{KUBERNETES_API}%/static/charts/traefik-25.0.3+up25.0.0.tgz
|
||||
set:
|
||||
global.systemDefaultRegistry: ""
|
||||
valuesContent: |-
|
||||
deployment:
|
||||
podAnnotations:
|
||||
prometheus.io/port: "8082"
|
||||
prometheus.io/scrape: "true"
|
||||
dashboard:
|
||||
enabled: true
|
||||
metrics:
|
||||
prometheus: true
|
||||
```
|
||||
|
||||
### Restart Ingress Controller
|
||||
|
||||
```
|
||||
kubectl -n kube-system scale deployment traefik --replicas=0
|
||||
kubectl -n kube-system get deployment traefik
|
||||
```
|
||||
```
|
||||
kubectl -n kube-system scale deployment traefik --replicas=1
|
||||
```
|
||||
|
||||
Example: (`kubectls`?! see `#shortcuts`)
|
||||
```
|
||||
$ kubectls scale deployment traefik --replicas=0
|
||||
deployment.apps/traefik scaled
|
||||
$ kubectls get deployment traefik
|
||||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
traefik 0/0 0 0 3d1h
|
||||
$ kubectls scale deployment traefik --replicas=1
|
||||
deployment.apps/traefik scaled
|
||||
```
|
||||
|
||||
### Create Resource Definition YAML
|
||||
|
||||
Save the following to `traefik-dashboard.yml` in your workspace.
|
||||
```
|
||||
apiVersion: v1
|
||||
kind: Service
|
||||
metadata:
|
||||
name: traefik-dashboard
|
||||
namespace: kube-system
|
||||
labels:
|
||||
app.kubernetes.io/instance: traefik
|
||||
app.kubernetes.io/name: traefik-dashboard
|
||||
spec:
|
||||
type: ClusterIP
|
||||
ports:
|
||||
- name: traefik
|
||||
port: 9000
|
||||
targetPort: 9000
|
||||
protocol: TCP
|
||||
selector:
|
||||
app.kubernetes.io/instance: traefik-kube-system
|
||||
app.kubernetes.io/name: traefik
|
||||
|
||||
---
|
||||
|
||||
apiVersion: v1
|
||||
kind: Service
|
||||
metadata:
|
||||
name: traefik-metrics
|
||||
namespace: kube-system
|
||||
labels:
|
||||
app.kubernetes.io/instance: traefik
|
||||
app.kubernetes.io/name: traefik-metrics
|
||||
spec:
|
||||
type: ClusterIP
|
||||
ports:
|
||||
- name: traefik
|
||||
port: 9100
|
||||
targetPort: 9100
|
||||
protocol: TCP
|
||||
selector:
|
||||
app.kubernetes.io/instance: traefik-kube-system
|
||||
app.kubernetes.io/name: traefik
|
||||
|
||||
---
|
||||
|
||||
apiVersion: networking.k8s.io/v1
|
||||
kind: Ingress
|
||||
metadata:
|
||||
name: traefik-ingress
|
||||
namespace: kube-system
|
||||
annotations:
|
||||
spec.ingressClassName: traefik
|
||||
spec:
|
||||
rules:
|
||||
- host: internal.${DOMAIN}
|
||||
http:
|
||||
paths:
|
||||
- path: /
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-dashboard
|
||||
port:
|
||||
number: 9000
|
||||
- path: /metrics
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-metrics
|
||||
port:
|
||||
number: 9100
|
||||
```
|
||||
|
||||
If you don't want `traefik-metrics` simply do not include the service definition and remove the `- path: metrics` section from the ingress definition.
|
||||
|
||||
### Create Service & Ingress Resources
|
||||
|
||||
[envsubst](https://www.gnu.org/software/gettext/manual/html_node/envsubst-Invocation.html) - `envsusbst` enables code-reuse by providing environment variable substituion as demonstrated below.
|
||||
|
||||
```
|
||||
envsubst < traefik-dashboard.yml | kubectl apply -f -
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
$ envsubst < traefik-dashboards.yml | kubectl apply -f -
|
||||
service/traefik-dashboard created
|
||||
service/traefik-metrics created
|
||||
ingress.networking.k8s.io/traefik-ingress created
|
||||
$ kubectls get svc | grep traefik-
|
||||
traefik-dashboard ClusterIP 10.43.157.54 <none> 9000/TCP 25s
|
||||
traefik-metrics ClusterIP 10.43.189.128 <none> 9100/TCP 25s
|
||||
```
|
||||
|
||||
### Access Dashboards
|
||||
|
||||
That's it. You should now be able to access the Traefik Ingress Controller Dashboard and metrics remotely.
|
||||
|
||||
Don't forget to include the appropriate uri paths:
|
||||
- `internal.your.domain.com/dashboard/` for `Traefik Dashboard` *(Note: just `/dashboard` will not work.)*
|
||||
- `internal.your.domain.com/metrics` for `Traefik Metrics`
|
||||
|
||||
### Disable Dashboards
|
||||
|
||||
```
|
||||
envsubst < traefik-dashboard.yml | kubectl delete -f -
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
envsubst < traefik-dashboards.yml | kubectl delete -f -
|
||||
service "traefik-dashboard" deleted
|
||||
service "traefik-metrics" deleted
|
||||
ingress.networking.k8s.io "traefik-ingress" deleted
|
||||
```
|
||||
|
||||
## Shortcuts
|
||||
|
||||
### alias kubectls
|
||||
|
||||
*Note: kubectl-completion will not work for `kubectls`*
|
||||
|
||||
```
|
||||
echo 'alias kubectls="kubectl -n kube-system"' >> ~/.bashrc
|
||||
source ~/.bashrc
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
$ echo 'alias kubectls="kubectl -n kube-system"' >> ~/.bashrc
|
||||
$ source ~/.bashrc
|
||||
$ kubectls get deployments
|
||||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
coredns 1/1 1 1 3d2h
|
||||
local-path-provisioner 1/1 1 1 3d2h
|
||||
metrics-server 1/1 1 1 3d2h
|
||||
traefik 1/1 1 1 3d2h
|
||||
```
|
||||
|
||||
(alt) use `skubectl` or `kubesctl` as the alias instead. comparisons:
|
||||
- `skubectl` means you can hit `[up-arrow]` `[ctrl]+[a]` `[s]` `[enter]` when you inevitably forget to include `-n kube-system`
|
||||
- `kubectls` just adds `[alt]+[right-arrow]` to the above
|
||||
- `kubesctl` makes sense because all of these are really kube-system-ctl, but that adds 4x `[right-arrow]`, ewww.
|
||||
|
||||
|
||||
## References
|
||||
|
||||
- [https://docs.k3s.io](https://docs.k3s.io)
|
||||
- [https://k3s.rocks/traefik-dashboard/](https://k3s.rocks/traefik-dashboard/)
|
||||
- [https://doc.traefik.io/traefik/v2.10/](https://doc.traefik.io/traefik/v2.10/)
|
||||
@@ -1,133 +0,0 @@
|
||||
# Network Attached Storage
|
||||
|
||||
## Brief
|
||||
|
||||
Scoping an 80 terabyte onsite Network Attached Storage (NAS) solution for media group usage
|
||||
|
||||
- by `rskntroot` on `2024-06-01`
|
||||
|
||||
## Assumptions
|
||||
|
||||
At a minimum, the storage solution must provide redundant copies of the data. The solution must function in the event of a single drive. Individual storage drives used must be enterprise-grade, warrantied, with the expectation of 1 million hours Mean Time Between Failures (MTBF).
|
||||
|
||||
Given standard network connectivity is at or under 1Gbps speeds, 10Gb/s internal networking is not expected. However, the storage solution should provide future expansion for 10Gb/s networking.
|
||||
|
||||
Concerns regarding redudant power or battery backup for the solution are outside the scope of this document and would be handled by the customer. Recommened best practice for storage solutions is to keep on a battery backup to allow for graceful shutdown.
|
||||
|
||||
## Hardware
|
||||
|
||||
> `$8121 USD | hardware-only estimate*`
|
||||
|
||||
**Not included in estimate: shipping, taxes, build & validation services, installation support*
|
||||
|
||||
### NAS
|
||||
|
||||
#### QNAP TVS-H874T
|
||||
|
||||
8-bay NAS: [qnap product page](https://www.qnap.com/en-us/product/tvs-h874t/specs/hardware)
|
||||
- Thunderbolt 4 support
|
||||
- EZCOPY USB3.2
|
||||
|
||||
Available Upgrades:
|
||||
- 10/25 Gb/s networking (upgrade)
|
||||
|
||||
> `$2899 USD | chassis`
|
||||
|
||||
### Drives
|
||||
|
||||
#### Seagate Exos X24 24TB
|
||||
|
||||
Enterprise 24TB HDD: [seagate product page](https://www.seagate.com/products/enterprise-drives/exos-x/x24/)
|
||||
- 5-year limited warranty
|
||||
- 180MB/s Read (7200RPM)
|
||||
- 2.5M MTBF
|
||||
- Compatibility Check [ [PASS](https://www.qnap.com/en-us/compatibility/?model=758&category=1&filter[type]=1&filter[brand]=Seagate&filter[capacity]=24000) ]
|
||||
|
||||
> `$4792 USD | $599 USD (8 ea)`
|
||||
|
||||
#### Solidgram P44 Pro
|
||||
|
||||
2TB M.2 NVME: [solidigm product page]( https://www.solidigm.com/products/client/pro-series/p44.html#form=M.2%202280&cap=2%20TB)
|
||||
- 5-year limited warranty
|
||||
- 7000 MB/s Read
|
||||
- 1.6M MTBF
|
||||
- Compatibility Check [ [PASS](https://www.qnap.com/en-us/compatibility/?model=758&category=1&filter[type]=1&filter[brand]=Seagate&filter[capacity]=24000) ]
|
||||
|
||||
> `$398 USD | $199 USD (2 ea)`
|
||||
|
||||
### Misc
|
||||
|
||||
#### Ethernet Cables
|
||||
|
||||
CAT8 Ethernet Cables: [vabugo amazon store](https://www.amazon.com/stores/VABOGU/page/20815F77-3E58-4871-A2EB-1772920695D9?ref_=ast_bln)
|
||||
- 1/2.5/10/25 Gb/s support
|
||||
- 10' length (standard)
|
||||
|
||||
> `$32 USD | $16 USD (2 ea)`
|
||||
|
||||
## Deployment Options
|
||||
|
||||
### Hard Drives
|
||||
|
||||
**8-Drives**
|
||||
- This maxes out the hardware with a capacity of `~80TB` with read speeds maxing out around `~1440MB/s`.
|
||||
|
||||
**6-Drives**
|
||||
- Using 6 drives will bring the total capcacity to `~60TB` and access speed maxing out at `~1080MB/s`. This saturates a 10Gbps connection.
|
||||
- Initial Cost down `$1198 USD | ($599 * 8) - ($599 * 4)`
|
||||
|
||||
**4-Drives**
|
||||
- The minimum capacity of 4 drives provides a capacity of `~40TB` and access speed maxing out at `~720MB/s` read. Bringing the cost down
|
||||
- Initial Cost down `$2396 USD | ($599 * 8) - ($599 * 4)`
|
||||
|
||||
**Future Expansion:**
|
||||
- Can we add more drives? Yes, this option is available, but requires additional hardware.
|
||||
- If it is expected to house more than 80TB in the near future, there are other options for hardware available.
|
||||
|
||||
*Notes:*
|
||||
|
||||
*2 Drives is not possible, as the requirements for "fully redundant copies of the data" and "functionality in the event of a single drive failure" mandate the use of RAID10. The minimum drives in a RAID10 deployment is 4 drives.*
|
||||
|
||||
### M.2 NVME Drives
|
||||
|
||||
#### Crucial P3 Plus
|
||||
|
||||
4TB M.2 NVME [crucial product page](https://www.crucial.com/ssd/p3-plus/ct4000p3pssd8?_gl=1*13sw6no*_up*MQ..*_ga*MTMwNzgxNzQwNC4xNzE3Mjk2NjA3*_ga_6H4RYWV7QY*MTcxNzI5NjYwNy4xLjEuMTcxNzI5NjYxNC4wLjAuMjIzMjAyNjQ2&gclid=CjwKCAjwjeuyBhBuEiwAJ3vuoWUcasHvAhPD74JFCo8NZTNCemm5DIvp9fUT5ZnK-EjCZ97iyNceMhoC1d8QAvD_BwE&gclsrc=aw.ds)
|
||||
- 5-year limited warranty
|
||||
- 4,800 MB/s Read
|
||||
- 1.5m MTBF
|
||||
|
||||
> `$718 USD | $359 USD (2 ea)`
|
||||
|
||||
### Chassis
|
||||
|
||||
#### QNAP TVS-H874
|
||||
|
||||
8-bay NAS: [qnap product page](https://www.qnap.com/en-us/product/tvs-h874/specs/hardware)
|
||||
- EZCOPY USB3.2
|
||||
|
||||
Available Upgrades:
|
||||
- 10/25 Gb/s networking card
|
||||
- Thunderbolt 4 card
|
||||
|
||||
> `$2452 USD | chassis`
|
||||
|
||||
#### QNAP TS-873A
|
||||
|
||||
8-bay NAS: [qnap product page](https://www.qnap.com/en-us/product/ts-873a/specs/hardware)
|
||||
- EZCOPY USB3.2
|
||||
|
||||
Available Upgrades:
|
||||
- 10Gb/s networking card
|
||||
- Thunderbolt 3 card
|
||||
|
||||
Requires:
|
||||
- 32GB Kit (2x16GB) DDR4-3200 SODIMM: [crucial product page](https://www.crucial.com/memory/ddr4/ct2k16g4sfra32a?_gl=1*mq22r2*_up*MQ..*_ga*MTYxODEzNzExLjE3MTcyOTgzMTc.*_ga_6H4RYWV7QY*MTcxNzI5ODMxNy4xLjEuMTcxNzI5ODMyNS4wLjAuMTgxMDAzNjg0MQ..&gclid=CjwKCAjwjeuyBhBuEiwAJ3vuoQXDrg49snbi2juKZJSCftPl9NjUEollcaynaS-faIsCAvWBOMN4yxoCBooQAvD_BwE&gclsrc=aw.ds)
|
||||
|
||||
Notes:
|
||||
- Entry-level Option
|
||||
|
||||
> `$1100 USD | chassis`
|
||||
>
|
||||
> `$80 USD | memory`
|
||||
|
||||
@@ -1,16 +0,0 @@
|
||||
.. Rskio documentation master file, created by
|
||||
sphinx-quickstart on Wed May 29 05:30:27 2024.
|
||||
You can adapt this file completely to your liking, but it should at least
|
||||
contain the root `toctree` directive.
|
||||
|
||||
Rskio
|
||||
=====
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:caption: Contents:
|
||||
|
||||
./docs/system_on_chip.md
|
||||
./docs/network_attached_storage.md
|
||||
./docs/k3s_traefik_setup.md
|
||||
|
||||
34
mkdocs/docs/index.md
Normal file
34
mkdocs/docs/index.md
Normal file
@@ -0,0 +1,34 @@
|
||||
# Home
|
||||
|
||||
## Rskio
|
||||
|
||||
This site (a project of mine in and of itself) is meant to catalog my efforts. Through the years, I have "spun my wheels" in order to learn, get something working, or even try something interesting--only for it to be lost to time. You could boil this site down to my notes. However, I fully intend for it to be much more than that. This site exists for me and the possibilty that it might help you too.
|
||||
|
||||
|
||||
## About
|
||||
|
||||
Its been what, now? Around 10 years since I started working in computing proffessionally (right after dropping out of a Computer Science program, oops). Oh and about 14 since I'd learned my first programming language. What?! I'm in my thirties?! Guess I can't go saying I'm just some random kid on the internet anymore.
|
||||
|
||||
Just like everyone else my age, I got into computing because my family didn't know how to get the wifi working when we finally got broadband internet. Somehow that got me into robotics and programming in middle school and it snowballed from there. After a multi-year stint with the challenges of the cyber security field, I found peace by letting other people deal with it. These days I'm a full-time computer engineer that designs and deploys network infrastructure for a Tier-1 cloud provider. In my spare time, I work on projects, or dream of a financial freedom and getting able to work on whatever projects I want full-time, or both.
|
||||
|
||||
## What does Rskio Mean?
|
||||
|
||||
Prounciation:
|
||||
|
||||
=== "English"
|
||||
`R-S-K-I-O`
|
||||
|
||||
=== "IPA"
|
||||
`ɑːr-ɛs-keɪ-aɪ-əʊ`
|
||||
|
||||
Nothing. Just like QUIC and the G in GNU. As a "programmer" from a young age, I too struggle with naming variables and cache invalidation. It's sort of a mix of a nickname I had when I was young and Input/Outout or IO. After trying to think of something clever that pays homage to Nihei's TOHA Heavy Industries, I inevtiably gave up and fought with Route53 until it provided me a 5-letter .com that made sense to me.
|
||||
|
||||
The same goes for "Rskntroot", it's a mix of that same nickname and the classic "root" term.
|
||||
|
||||
## Projects
|
||||
|
||||
Currently, this is an unorganized list of things I have spent many of what corporate America refers to as "cycles" on.
|
||||
|
||||
## Storage
|
||||
|
||||
Also projects, but those dedicated to storage technology.
|
||||
369
mkdocs/docs/projects/k3s_traefik_setup.md
Normal file
369
mkdocs/docs/projects/k3s_traefik_setup.md
Normal file
@@ -0,0 +1,369 @@
|
||||
# K3S Traefik Setup
|
||||
|
||||
## Brief
|
||||
|
||||
Enabling internal access to dashboard and metrics for traefik ingress controller in k3s kubernetes cluster
|
||||
|
||||
- by `rskntroot` on `2024-07-01`
|
||||
|
||||
## Assumptions
|
||||
|
||||
``` bash
|
||||
$ k3s --version
|
||||
k3s version v1.29.5+k3s1 (4e53a323)
|
||||
go version go1.21.9
|
||||
```
|
||||
|
||||
``` bash
|
||||
$ kubectl version
|
||||
Client Version: v1.29.5+k3s1
|
||||
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
|
||||
Server Version: v1.29.5+k3s1
|
||||
```
|
||||
|
||||
## Traefik Dashboards
|
||||
|
||||
`Traefik Dashboards` refers to both traefik dashboard and prometheus metrics for traefik which are readily available, however, disabled by default in K3S.
|
||||
|
||||
### Preparation
|
||||
|
||||
Enable `internal`+`.your.domain.com` in non-public DNS
|
||||
|
||||
- (alt) edit the `hosts` file on your admin to point the desired k3s host IP
|
||||
|
||||
On host with `kubectl` access:
|
||||
``` bash
|
||||
export DOMAIN=your.domain.com
|
||||
```
|
||||
|
||||
!!! warning "This example does not include authentication. Exposing these dashboards is a security risk."
|
||||
|
||||
### Update Manifest
|
||||
|
||||
Add the following to `spec.valuesContent` in:
|
||||
|
||||
``` bash
|
||||
vim /var/lib/rancher/k3s/server/manifests/traefik.yaml
|
||||
```
|
||||
|
||||
=== "Yaml"
|
||||
|
||||
``` yaml
|
||||
dashboard:
|
||||
enabled: true
|
||||
metrics:
|
||||
prometheus: true
|
||||
```
|
||||
|
||||
=== "Example"
|
||||
|
||||
``` yaml
|
||||
spec:
|
||||
chart: https://%{KUBERNETES_API}%/static/charts/traefik-25.0.3+up25.0.0.tgz
|
||||
set:
|
||||
global.systemDefaultRegistry: ""
|
||||
valuesContent: |-
|
||||
deployment:
|
||||
podAnnotations:
|
||||
prometheus.io/port: "8082"
|
||||
prometheus.io/scrape: "true"
|
||||
dashboard:
|
||||
enabled: true
|
||||
metrics:
|
||||
prometheus: true
|
||||
```
|
||||
|
||||
### Restart Ingress Controller
|
||||
|
||||
=== "Bash"
|
||||
|
||||
``` bash
|
||||
kubectl -n kube-system scale deployment traefik --replicas=0
|
||||
# wait a few seconds
|
||||
kubectl -n kube-system get deployment traefik
|
||||
kubectl -n kube-system scale deployment traefik --replicas=1
|
||||
```
|
||||
|
||||
=== "Example"
|
||||
|
||||
``` bash
|
||||
$ kubectls scale deployment traefik --replicas=0
|
||||
deployment.apps/traefik scaled
|
||||
$ kubectls get deployment traefik
|
||||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
traefik 0/0 0 0 3d1h
|
||||
$ kubectls scale deployment traefik --replicas=1
|
||||
deployment.apps/traefik scaled
|
||||
```
|
||||
|
||||
### Create Resource Definition YAML
|
||||
|
||||
Save the following to `traefik-dashboard.yml` in your workspace.
|
||||
|
||||
=== "Traefik Dashboard"
|
||||
|
||||
``` yaml
|
||||
apiVersion: v1
|
||||
kind: Service
|
||||
metadata:
|
||||
name: traefik-dashboard
|
||||
namespace: kube-system
|
||||
labels:
|
||||
app.kubernetes.io/instance: traefik
|
||||
app.kubernetes.io/name: traefik-dashboard
|
||||
spec:
|
||||
type: ClusterIP
|
||||
ports:
|
||||
- name: traefik
|
||||
port: 9000
|
||||
targetPort: 9000
|
||||
protocol: TCP
|
||||
selector:
|
||||
app.kubernetes.io/instance: traefik-kube-system
|
||||
app.kubernetes.io/name: traefik
|
||||
|
||||
---
|
||||
|
||||
apiVersion: networking.k8s.io/v1
|
||||
kind: Ingress
|
||||
metadata:
|
||||
name: traefik-ingress
|
||||
namespace: kube-system
|
||||
annotations:
|
||||
spec.ingressClassName: traefik
|
||||
spec:
|
||||
rules:
|
||||
- host: internal.${DOMAIN}
|
||||
http:
|
||||
paths:
|
||||
- path: /
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-dashboard
|
||||
port:
|
||||
number: 9000
|
||||
```
|
||||
|
||||
=== "Promethus Only"
|
||||
|
||||
``` yaml
|
||||
apiVersion: v1
|
||||
kind: Service
|
||||
metadata:
|
||||
name: traefik-metrics
|
||||
namespace: kube-system
|
||||
labels:
|
||||
app.kubernetes.io/instance: traefik
|
||||
app.kubernetes.io/name: traefik-metrics
|
||||
spec:
|
||||
type: ClusterIP
|
||||
ports:
|
||||
- name: traefik
|
||||
port: 9100
|
||||
targetPort: 9100
|
||||
protocol: TCP
|
||||
selector:
|
||||
app.kubernetes.io/instance: traefik-kube-system
|
||||
app.kubernetes.io/name: traefik
|
||||
|
||||
---
|
||||
|
||||
apiVersion: networking.k8s.io/v1
|
||||
kind: Ingress
|
||||
metadata:
|
||||
name: traefik-ingress
|
||||
namespace: kube-system
|
||||
annotations:
|
||||
spec.ingressClassName: traefik
|
||||
spec:
|
||||
rules:
|
||||
- host: internal.${DOMAIN}
|
||||
http:
|
||||
paths:
|
||||
- path: /
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-dashboard
|
||||
port:
|
||||
number: 9000
|
||||
- path: /metrics
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-metrics
|
||||
port:
|
||||
number: 9100
|
||||
```
|
||||
|
||||
=== "Both"
|
||||
|
||||
``` yaml
|
||||
apiVersion: v1
|
||||
kind: Service
|
||||
metadata:
|
||||
name: traefik-dashboard
|
||||
namespace: kube-system
|
||||
labels:
|
||||
app.kubernetes.io/instance: traefik
|
||||
app.kubernetes.io/name: traefik-dashboard
|
||||
spec:
|
||||
type: ClusterIP
|
||||
ports:
|
||||
- name: traefik
|
||||
port: 9000
|
||||
targetPort: 9000
|
||||
protocol: TCP
|
||||
selector:
|
||||
app.kubernetes.io/instance: traefik-kube-system
|
||||
app.kubernetes.io/name: traefik
|
||||
|
||||
---
|
||||
|
||||
apiVersion: v1
|
||||
kind: Service
|
||||
metadata:
|
||||
name: traefik-metrics
|
||||
namespace: kube-system
|
||||
labels:
|
||||
app.kubernetes.io/instance: traefik
|
||||
app.kubernetes.io/name: traefik-metrics
|
||||
spec:
|
||||
type: ClusterIP
|
||||
ports:
|
||||
- name: traefik
|
||||
port: 9100
|
||||
targetPort: 9100
|
||||
protocol: TCP
|
||||
selector:
|
||||
app.kubernetes.io/instance: traefik-kube-system
|
||||
app.kubernetes.io/name: traefik
|
||||
|
||||
---
|
||||
|
||||
apiVersion: networking.k8s.io/v1
|
||||
kind: Ingress
|
||||
metadata:
|
||||
name: traefik-ingress
|
||||
namespace: kube-system
|
||||
annotations:
|
||||
spec.ingressClassName: traefik
|
||||
spec:
|
||||
rules:
|
||||
- host: internal.${DOMAIN}
|
||||
http:
|
||||
paths:
|
||||
- path: /
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-dashboard
|
||||
port:
|
||||
number: 9000
|
||||
- path: /metrics
|
||||
pathType: Prefix
|
||||
backend:
|
||||
service:
|
||||
name: traefik-metrics
|
||||
port:
|
||||
number: 9100
|
||||
```
|
||||
|
||||
### Create Service & Ingress Resources
|
||||
|
||||
[envsubst](https://www.gnu.org/software/gettext/manual/html_node/envsubst-Invocation.html) - enables code-reuse by providing environment variable substituion as demonstrated below.
|
||||
|
||||
=== "Bash"
|
||||
|
||||
``` bash
|
||||
envsubst < traefik-dashboard.yml | kubectl apply -f -
|
||||
```
|
||||
|
||||
=== "Example"
|
||||
|
||||
``` bash
|
||||
$ envsubst < traefik-dashboards.yml | kubectl apply -f -
|
||||
service/traefik-dashboard created
|
||||
service/traefik-metrics created
|
||||
ingress.networking.k8s.io/traefik-ingress created
|
||||
$ kubectls get svc | grep traefik-
|
||||
traefik-dashboard ClusterIP 10.43.157.54 <none> 9000/TCP 25s
|
||||
traefik-metrics ClusterIP 10.43.189.128 <none> 9100/TCP 25s
|
||||
```
|
||||
|
||||
### Access Dashboards
|
||||
|
||||
That's it. You should now be able to access the Traefik Ingress Controller Dashboard and metrics remotely.
|
||||
|
||||
Don't forget to include the appropriate uri paths:
|
||||
|
||||
=== "Traefik Dashboard"
|
||||
|
||||
```
|
||||
https://internal.your.domain.com/dashboard/
|
||||
```
|
||||
|
||||
!!! tip "When navigating to the traefik dashboard the `/` at the end is necessary. `/dashboard` will not work. "
|
||||
|
||||
=== "Promethus Metrics"
|
||||
|
||||
```
|
||||
https://internal.your.domain.com/metrics
|
||||
```
|
||||
|
||||
### Disable Dashboards
|
||||
|
||||
=== "Bash"
|
||||
|
||||
``` bash
|
||||
envsubst < traefik-dashboard.yml | kubectl delete -f -
|
||||
```
|
||||
|
||||
=== "Example"
|
||||
|
||||
``` bash
|
||||
$ envsubst < traefik-dashboards.yml | kubectl delete -f -
|
||||
service "traefik-dashboard" deleted
|
||||
service "traefik-metrics" deleted
|
||||
ingress.networking.k8s.io "traefik-ingress" deleted
|
||||
```
|
||||
|
||||
## Shortcuts
|
||||
|
||||
### alias kubectls
|
||||
|
||||
!!! tip "When using an `alias` to substitute `kubectl` command completion will not work."
|
||||
|
||||
=== "Bash"
|
||||
|
||||
``` bash
|
||||
echo 'alias kubectls="kubectl -n kube-system"' >> ~/.bashrc
|
||||
source ~/.bashrc
|
||||
```
|
||||
|
||||
=== "Example"
|
||||
|
||||
``` bash
|
||||
$ echo 'alias kubectls="kubectl -n kube-system"' >> ~/.bashrc
|
||||
$ source ~/.bashrc
|
||||
$ kubectls get deployments
|
||||
NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
coredns 1/1 1 1 3d2h
|
||||
local-path-provisioner 1/1 1 1 3d2h
|
||||
metrics-server 1/1 1 1 3d2h
|
||||
traefik 1/1 1 1 3d2h
|
||||
```
|
||||
|
||||
#### Alternatives
|
||||
|
||||
- `skubectl` means you can hit `[up-arrow]` `[ctrl]+[a]` `[s]` `[enter]` when you inevitably forget to include `-n kube-system`
|
||||
- `kubectls` just adds `[alt]+[right-arrow]` into the above before `[s]`
|
||||
- `kubesctl` makes sense because all of these are really kube-system-ctl, but that adds 4x `[right-arrow]`, ewww.
|
||||
|
||||
|
||||
## References
|
||||
|
||||
- [https://docs.k3s.io](https://docs.k3s.io)
|
||||
- [https://k3s.rocks/traefik-dashboard/](https://k3s.rocks/traefik-dashboard/)
|
||||
- [https://doc.traefik.io/traefik/v2.10/](https://doc.traefik.io/traefik/v2.10/)
|
||||
@@ -50,10 +50,11 @@ Or even just use that 4000-series Nvidia GPU for something other than filling up
|
||||
Using Power over Ethernet (PoE) to run your SoCs is just awesome! You only need 1 cable?! Be sure to get yourself some good cables and a solid PoE switch.
|
||||
|
||||
I have personnally been using these:
|
||||
|
||||
- [CAT8 Ethernet cables](https://www.amazon.com/Ethernet-Internet-Network-Professional-Shielded/dp/B08PL1P53C/ref=sr_1_4?crid=1ELCUKBT7V3YB&dib=eyJ2IjoiMSJ9.W2iSbQd5bQGYHCf-9Vt3AovS1xEhC0zzsheMJG1QFnYut2JmmRCQzZmwq60K1uSUoGiTU8RUzjOTwybWF9lFZrGDx4abFxPwgCaCQTvL9Fvqa6UQ4Qu6o6JWEZRkWwNUWK34Izz1HPf1r54hVQ2NrN6f1r6PDUk2NDEab2zld8MVx2zRT4-s-8-jgwi8ng6wccQVAiJu-kTGeN_fkNohbUcpUMkmE-ARnhBrV05qIZg.OigmTuqYLiyRtsbLu-nXFx2nluGZo0e0IwjWTcXuHgg&dib_tag=se&keywords=cat8%2Bethernet%2Bcable&qid=1717047302&sprefix=cat8%2Caps%2C134&sr=8-4&th=1) by [VABOGU](https://www.amazon.com/stores/VABOGU/page/20815F77-3E58-4871-A2EB-1772920695D9?ref_=ast_bln)
|
||||
- Ive used countless Ethernet Cables and fashioning hundreds of my own, I can confirm these are premium.
|
||||
- Ive used countless Ethernet Cables and fashioning hundreds of my own, I can confirm these are premium.
|
||||
- [1G PoE+ 8-port Switch](https://www.amazon.com/dp/B08FCQ8BRC?ref=nb_sb_ss_w_as-reorder_k1_1_9&=&crid=1OZ5HYTQCXGAQ&=&sprefix=poe+switc) by [AMCREST](https://www.amazon.com/stores/Amcrest/page/2404E471-79FC-4D18-B767-8777D048264F?ref_=ast_bln)
|
||||
- Unmanaged switch that I can recommend. Works like a charm.
|
||||
- Unmanaged switch that I can recommend. Works like a charm.
|
||||
|
||||
### CAT8 Real?
|
||||
|
||||
144
mkdocs/docs/storage/network_attached_storage.md
Normal file
144
mkdocs/docs/storage/network_attached_storage.md
Normal file
@@ -0,0 +1,144 @@
|
||||
# Network Attached Storage
|
||||
|
||||
## Brief
|
||||
|
||||
Scoping an 80 terabyte onsite Network Attached Storage (NAS) solution for media group usage
|
||||
|
||||
- by `rskntroot` on `2024-06-01`
|
||||
|
||||
## Assumptions
|
||||
|
||||
At a minimum, the storage solution must provide redundant copies of the data. The solution must function in the event of a single drive. Individual storage drives used must be enterprise-grade, warrantied, with the expectation of 1 million hours MTBF.
|
||||
|
||||
Given standard network connectivity is at or under 1Gbps speeds, 10Gb/s internal networking is not expected. However, the storage solution should provide future expansion for 10Gb/s networking.
|
||||
|
||||
Concerns regarding redudant power or battery backup for the solution are outside the scope of this document and would be handled by the customer. Recommened best practice for storage solutions is to keep on a battery backup to allow for graceful shutdown.
|
||||
|
||||
## Hardware
|
||||
|
||||
> `$8121 USD | hardware-only estimate*`
|
||||
|
||||
!!! warning "* Not included: shipping, taxes, build & validation services, installation support"
|
||||
|
||||
### Chassis
|
||||
|
||||
=== "QNAP TVS-H874T"
|
||||
|
||||
8-bay NAS: [qnap product page](https://www.qnap.com/en-us/product/tvs-h874t/specs/hardware)
|
||||
|
||||
- Thunderbolt 4 support
|
||||
- EZCOPY USB3.2
|
||||
|
||||
Available Upgrades:
|
||||
|
||||
- 10/25 Gb/s networking (upgrade)
|
||||
|
||||
> `$2899 USD | chassis`
|
||||
|
||||
### Drives
|
||||
|
||||
=== "Seagate Exos X24 24TB"
|
||||
|
||||
Enterprise 24TB HDD: [seagate product page](https://www.seagate.com/products/enterprise-drives/exos-x/x24/)
|
||||
|
||||
- 5-year limited warranty
|
||||
- 180MB/s Read (7200RPM)
|
||||
- 2.5M MTBF
|
||||
- Compatibility Check [ [PASS](https://www.qnap.com/en-us/compatibility/?model=758&category=1&filter[type]=1&filter[brand]=Seagate&filter[capacity]=24000) ]
|
||||
|
||||
> `$4792 USD | $599 USD (8 ea)`
|
||||
|
||||
=== "Solidgram P44 Pro"
|
||||
|
||||
2TB M.2 NVME: [solidigm product page]( https://www.solidigm.com/products/client/pro-series/p44.html#form=M.2%202280&cap=2%20TB)
|
||||
|
||||
- 5-year limited warranty
|
||||
- 7000 MB/s Read
|
||||
- 1.6M MTBF
|
||||
- Compatibility Check [ [PASS](https://www.qnap.com/en-us/compatibility/?model=758&category=1&filter[type]=1&filter[brand]=Seagate&filter[capacity]=24000) ]
|
||||
|
||||
> `$398 USD | $199 USD (2 ea)`
|
||||
|
||||
### Misc
|
||||
|
||||
=== "Ethernet Cables"
|
||||
|
||||
CAT8 Ethernet Cables: [vabugo amazon store](https://www.amazon.com/stores/VABOGU/page/20815F77-3E58-4871-A2EB-1772920695D9?ref_=ast_bln)
|
||||
|
||||
- 1/2.5/10/25 Gb/s support
|
||||
- 10' length (standard)
|
||||
|
||||
> `$32 USD | $16 USD (2 ea)`
|
||||
|
||||
## Deployment Options
|
||||
|
||||
### Hard Drives
|
||||
|
||||
=== "8 Drives"
|
||||
|
||||
This maxes out the hardware with a capacity of `~80TB` with read speeds maxing out around `~1440MB/s`.
|
||||
|
||||
=== "6 Drives"
|
||||
|
||||
Using 6 drives will bring the total capcacity to `~60TB` and access speed maxing out at `~1080MB/s`. This saturates a 10Gbps connection.
|
||||
|
||||
Initial Cost down `$1198 USD | ($599 * 8) - ($599 * 4)`
|
||||
|
||||
=== "4 Drives"
|
||||
|
||||
The minimum capacity of 4 drives provides a capacity of `~40TB` and access speed maxing out at `~720MB/s` read. Bringing the cost down
|
||||
|
||||
Initial Cost down `$2396 USD | ($599 * 8) - ($599 * 4)`
|
||||
|
||||
=== "Future Expansion"
|
||||
|
||||
Can we add more drives? Yes, this option is available, but requires additional hardware.
|
||||
|
||||
If it is expected to house more than 80TB in the near future, there are other options for hardware available.
|
||||
|
||||
!!! note "*2 Drives is not possible, as the requirements for 'fully redundant copies of the data' and 'functionality in the event of a single drive failure' mandate the use of RAID10. Where the minimum drives in a RAID10 deployment is 4 drives.*"
|
||||
|
||||
### M.2 NVME Drives
|
||||
|
||||
=== "Crucial P3 Plus"
|
||||
|
||||
4TB M.2 NVME [crucial product page](https://www.crucial.com/ssd/p3-plus/ct4000p3pssd8?_gl=1*13sw6no*_up*MQ..*_ga*MTMwNzgxNzQwNC4xNzE3Mjk2NjA3*_ga_6H4RYWV7QY*MTcxNzI5NjYwNy4xLjEuMTcxNzI5NjYxNC4wLjAuMjIzMjAyNjQ2&gclid=CjwKCAjwjeuyBhBuEiwAJ3vuoWUcasHvAhPD74JFCo8NZTNCemm5DIvp9fUT5ZnK-EjCZ97iyNceMhoC1d8QAvD_BwE&gclsrc=aw.ds)
|
||||
|
||||
- 5-year limited warranty
|
||||
- 4,800 MB/s Read
|
||||
- 1.5m MTBF
|
||||
|
||||
> `$718 USD | $359 USD (2 ea)`
|
||||
|
||||
### Chassis
|
||||
|
||||
=== "QNAP TVS-H874"
|
||||
|
||||
8-bay NAS: [qnap product page](https://www.qnap.com/en-us/product/tvs-h874/specs/hardware)
|
||||
|
||||
- EZCOPY USB3.2
|
||||
|
||||
Available Upgrades:
|
||||
|
||||
- 10/25 Gb/s networking card
|
||||
- Thunderbolt 4 card
|
||||
|
||||
> `$2452 USD | chassis`
|
||||
|
||||
=== "QNAP TS-873A"
|
||||
|
||||
8-bay NAS: [qnap product page](https://www.qnap.com/en-us/product/ts-873a/specs/hardware)
|
||||
|
||||
- EZCOPY USB3.2
|
||||
|
||||
Requires:
|
||||
|
||||
- 32GB Kit (2x16GB) DDR4-3200 SODIMM: [crucial product page](https://www.crucial.com/memory/ddr4/ct2k16g4sfra32a?_gl=1*mq22r2*_up*MQ..*_ga*MTYxODEzNzExLjE3MTcyOTgzMTc.*_ga_6H4RYWV7QY*MTcxNzI5ODMxNy4xLjEuMTcxNzI5ODMyNS4wLjAuMTgxMDAzNjg0MQ..&gclid=CjwKCAjwjeuyBhBuEiwAJ3vuoQXDrg49snbi2juKZJSCftPl9NjUEollcaynaS-faIsCAvWBOMN4yxoCBooQAvD_BwE&gclsrc=aw.ds)
|
||||
|
||||
Available Upgrades:
|
||||
|
||||
- 10Gb/s networking card
|
||||
- Thunderbolt 3 card
|
||||
|
||||
> `$1180 USD | chassis + memory`
|
||||
|
||||
1
mkdocs/includes/abbreviates.md
Normal file
1
mkdocs/includes/abbreviates.md
Normal file
@@ -0,0 +1 @@
|
||||
*[MTBF]: Mean Time Between Failures
|
||||
59
mkdocs/mkdocs.yml
Normal file
59
mkdocs/mkdocs.yml
Normal file
@@ -0,0 +1,59 @@
|
||||
site_name: Rskio
|
||||
site_url: https://rskio.com/
|
||||
repo_name: rskntroot/rskio
|
||||
repo_url: https://github.com/rskntroot/rskio
|
||||
theme:
|
||||
name: material
|
||||
features:
|
||||
- navigation.instant
|
||||
icon:
|
||||
admonition:
|
||||
note: fontawesome/solid/note-sticky
|
||||
abstract: fontawesome/solid/book
|
||||
info: fontawesome/solid/circle-info
|
||||
success: fontawesome/solid/check
|
||||
question: fontawesome/solid/circle-question
|
||||
failure: fontawesome/solid/bomb
|
||||
danger: fontawesome/solid/skull
|
||||
bug: fontawesome/solid/robot
|
||||
example: fontawesome/solid/flask
|
||||
quote: fontawesome/solid/quote-left
|
||||
repo: fontawesome/brands/github
|
||||
palette:
|
||||
# Palette toggle for dark mode
|
||||
- scheme: slate
|
||||
primary: black
|
||||
toggle:
|
||||
icon: material/weather-sunny
|
||||
name: Switch to light mode
|
||||
# Palette toggle for light mode
|
||||
- scheme: default
|
||||
toggle:
|
||||
icon: material/weather-night
|
||||
name: Switch to dark mode
|
||||
markdown_extensions:
|
||||
- admonition
|
||||
- abbr
|
||||
- pymdownx.snippets:
|
||||
auto_append:
|
||||
- includes/abbreviations.md
|
||||
- pymdownx.details
|
||||
- pymdownx.superfences
|
||||
- pymdownx.highlight:
|
||||
anchor_linenums: true
|
||||
line_spans: __span
|
||||
pygments_lang_class: true
|
||||
- pymdownx.inlinehilite
|
||||
- pymdownx.snippets
|
||||
- pymdownx.tabbed:
|
||||
alternate_style: true
|
||||
watch:
|
||||
- includes
|
||||
extra:
|
||||
consent:
|
||||
title: Cookie consent
|
||||
description: >-
|
||||
We use cookies to recognize your repeated visits and preferences, as well
|
||||
as to measure the effectiveness of our documentation and whether users
|
||||
find what they're searching for. With your consent, you're helping us to
|
||||
make our documentation better.
|
||||
@@ -1,22 +0,0 @@
|
||||
server {
|
||||
listen 80;
|
||||
listen [::]:80;
|
||||
server_name localhost rskio.com;
|
||||
|
||||
# rskio logging is handled via traefik
|
||||
#access_log /var/log/nginx/host.access.log main;
|
||||
|
||||
location / {
|
||||
root /opt/sphinx/html;
|
||||
index index.html index.htm;
|
||||
}
|
||||
|
||||
# rskio auth is handled via traefik
|
||||
#error_page 404 /404.html;
|
||||
|
||||
error_page 500 502 503 504 /50x.html;
|
||||
location = /50x.html {
|
||||
root /usr/share/nginx/html;
|
||||
}
|
||||
}
|
||||
|
||||
5
traefik/tls/required.md
Normal file
5
traefik/tls/required.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Required
|
||||
|
||||
this dir is required to enable traefik to start as it is bound
|
||||
|
||||
this enables traefik log persistence
|
||||
Reference in New Issue
Block a user