Skip to content

Commit b47bfe8

Browse files
fix(formatting): cleanup
1 parent 50add53 commit b47bfe8

27 files changed

+76
-175
lines changed

_posts/2020-09-12-self-hosted-devops-stack.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ So you're a software engineer or a developer who wants to self-host your own cod
1212

1313
[Watch Video](https://www.youtube.com/watch?v=Xc94HJn1nNo)
1414

15-
16-
1715
## Helpful videos
1816

1917
1 - [Set Up Kubernetes with Rancher](https://www.youtube.com/watch?v=oILc0ywDVTk)
@@ -40,7 +38,6 @@ nginx config for your react application
4038

4139
[https://github.com/techno-tim/techno-react/blob/master/nginx.conf](https://github.com/techno-tim/techno-react/blob/master/nginx.conf)
4240

43-
4441
`pbcopy` for WSL on Windows
4542

4643
[https://www.techtronic.us/pbcopy-pbpaste-for-wsl/](https://www.techtronic.us/pbcopy-pbpaste-for-wsl/)

_posts/2020-10-10-gpu-passthrough-linux.md

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,7 @@ Do you have a lot of virtual machines? Are you running Windows, Linux, and Mac
1313

1414
[Watch Video](https://www.youtube.com/watch?v=9OfoFAljPn4)
1515

16-
17-
18-
```
16+
```na
1917
88 88
2018
88 ""
2119
88
@@ -28,17 +26,14 @@ Do you have a lot of virtual machines? Are you running Windows, Linux, and Mac
2826
"Y8bbdP"
2927
```
3028

31-
32-
3329
If you need to passthrough a GPU, follow [this guide](https://github.com/techno-tim/youtube-videos/tree/master/gpu-passthrough) but install Ubuntu instead.
3430

35-
3631
## Proxmox
32+
3733
Shut down your VM in proxmox, edit your conf file, it should be here (note, change path to your VM's ID)
3834

3935
`/etc/pve/qemu-server/100.conf`
4036

41-
4237
add `cpu: host,hidden=1,flags=+pcid` to that file
4338

4439
start the server.
@@ -65,15 +60,14 @@ Then install `nvtop`
6560
sudo apt-get install nvtop
6661
```
6762

68-
69-
## tensorflow workload
63+
## tensorflow workload
7064

7165
```bash
7266
nvidia-docker run --rm -ti tensorflow/tensorflow:r0.9-devel-gpu
7367
```
7468

75-
7669
## Rancher / Kubernetes
70+
7771
In your Rancher server (or kubernetes host)
7872

7973
```bash
@@ -120,5 +114,4 @@ Then, using `kubectl` on your kubernetes / rancher host
120114

121115
```bash
122116
kubectl create -f https://raw.githubusercontent.com/NVIDIA/k8s-device-plugin/master/nvidia-device-plugin.yml
123-
```
124-
117+
```

_posts/2020-10-17-migrate-database-docker-kubernetes.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ Have you been putting off migrating your database to Docker and Kubernetes like
1212

1313
[Watch Video](https://www.youtube.com/watch?v=jZvnkf_HgcY)
1414

15-
1615
`mysql_backup.sh`
1716

1817
```shell

_posts/2020-10-31-fist-13-things-linux.md

Lines changed: 8 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ After setting up my Linux servers, there are a few things I do before I use them
1212

1313
[Watch Video](https://www.youtube.com/watch?v=ZsjK4VDopiE)
1414

15-
1615
## Update
1716

1817
```bash
@@ -29,23 +28,22 @@ sudo dpkg-reconfigure --priority=low unattended-upgrades
2928

3029
Verify unattended upgrades configuration file in your text editor of choice
3130

32-
```
31+
```bash
3332
/etc/apt/apt.conf.d/20auto-upgrades
3433
```
3534

3635
To disable automatic reboots by the automatic upgrades configuration edit the following file:
3736

38-
```
37+
```bash
3938
/etc/apt/apt.conf.d/50unattended-upgrades
4039
```
4140

4241
and uncomment the following line by removing the leading slashes:
4342

44-
```
43+
```bash
4544
//Unattended-Upgrade::Automatic-Reboot "false";
4645
```
4746

48-
4947
## Account
5048

5149
add user
@@ -63,6 +61,7 @@ sudo usermod -aG sudo someuser
6361
## SSH Server
6462

6563
install
64+
6665
```bash
6766
sudo apt-get install openssh-server
6867
```
@@ -81,12 +80,11 @@ sudo nano /etc/ssh/sshd_config
8180

8281
Add these attributes
8382

84-
```
83+
```bash
8584
PasswordAuthentication no
8685
ChallengeResponseAuthentication no
8786
```
8887

89-
9088
## Networking
9189

9290
static IP
@@ -107,12 +105,8 @@ network:
107105
addresses: [192.168.0.4]
108106
```
109107
110-
111-
112-
113108
## Install `oh-my-zsh`
114109

115-
116110
```bash
117111
sudo apt-get update
118112
sudo apt-get install zsh
@@ -127,7 +121,6 @@ sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/too
127121
sudo lvm
128122
```
129123

130-
131124
```bash
132125
lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
133126
```
@@ -170,13 +163,13 @@ You can also use if you want a menu.
170163
sudo dpkg-reconfigure tzdata
171164
```
172165

173-
## NTP Time
166+
## NTP Time
174167

175168
```bash
176169
sudo nano /etc/systemd/timesyncd.conf
177170
```
178171

179-
```
172+
```conf
180173
NTP=192.168.0.4
181174
```
182175

@@ -188,14 +181,12 @@ sudo timedatectl set-net off
188181
sudo timedatectl set-ntp on
189182
```
190183

191-
192184
## install kvm agent
193185

194186
```bash
195187
sudo apt-get install qemu-guest-agent
196188
```
197189

198-
199190
## firewall
200191

201192
```bash
@@ -228,7 +219,7 @@ sudo cp /etc/fail2ban/jail.{conf,local}
228219
sudo nano /etc/fail2ban/jail.local
229220
```
230221

231-
```
222+
```conf
232223
backend = systemd
233224
```
234225

@@ -238,7 +229,6 @@ check status
238229
sudo fail2ban-client status
239230
```
240231

241-
242232
```bash
243233
sudo fail2ban-client status sshd
244234
```

_posts/2020-11-21-1u-server-upgrade.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,4 @@ tags: homelab hardware
1010

1111
I've been making great use of some older, bigger servers but I decided to try and build, upgrade, and migrate to some 1U servers. Join me as we unbox and build my 2 new virtualization servers!
1212

13-
1413
[Watch Video](https://www.youtube.com/watch?v=CMu5gsWKc9Y)

_posts/2020-12-12-ha-pi-hold-gravity-sync.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ tags: homelab rancher kubernetes docker portainer self-hosted pi-hole gravity-sy
88

99
[![High Availability Pi-Hole? Yes please!](https://img.youtube.com/vi/IFVYe3riDRA/0.jpg)](https://www.youtube.com/watch?v=IFVYe3riDRA "High Availability Pi-Hole? Yes please!")
1010

11-
1211
Dear Pi-Hole,
1312
We love your product. It keeps our network safe from malware and other unwanted domains. While we love what is there so far, please add a feature to your core product to keep multiple servers in sync and provide high availability DNS to our whole entire network. Then, we won't have people asking us "Is the internet down?" every time we reboot our Pi-Hole server.
1413

_posts/2020-12-19-rancher-ha-install.md

Lines changed: 4 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -14,17 +14,15 @@ Join me as we walk through installing Rancher on an existing high availability k
1414

1515
We install Rancher, configure a load balancer, install and configure helm, install cert-manager, configure Rancher, walk through the GUI, scale up our cluster, and set up a health check and liveness check! Join me, it's easy in this straightforward guide.
1616

17-
1817
[Watch Video](https://www.youtube.com/watch?v=APsZJbnluXg)
1918

20-
2119
## install
2220

2321
**Note:**
2422
It's advised you consult the [Rancher Support Matrix](https://rancher.com/support-maintenance-terms/all-supported-versions)
2523
to get the recommended version for all Rancher dependencies.
2624

27-
https://rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-k8s/#1-install-the-required-cli-tools
25+
[https://rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-k8s/#1-install-the-required-cli-tools](https://rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-k8s/#1-install-the-required-cli-tools)
2826

2927
`kubectl`
3028

@@ -40,22 +38,18 @@ add `helm` repo, `stable`
4038
helm repo add rancher-stable https://releases.rancher.com/server-charts/stable
4139
```
4240

43-
4441
create rancher namespace
4542

4643
```bash
4744
kubectl create namespace cattle-system
4845
```
4946

50-
5147
ssl configuration
5248

5349
user rancher generated (default)
5450

55-
5651
install `cert-manager`
5752

58-
5953
```bash
6054
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.2.0/cert-manager.crds.yaml
6155
```
@@ -66,27 +60,24 @@ create name-space for `cert-manager`
6660
kubectl create namespace cert-manager
6761
```
6862

69-
7063
Add the Jetstack Helm repository
7164

7265
```bash
7366
helm repo add jetstack https://charts.jetstack.io
7467
```
7568

76-
7769
update helm repo
7870

7971
```bash
8072
helm repo update
8173
```
8274

83-
8475
install `cert-manager` helm chart
8576

86-
8777
*Note: If you receive an "Error: Kubernetes cluster unreachable" message when installing cert-manager, try copying
8878

8979
the contents of "/etc/rancher/k3s/k3s.yaml" to "~/.kube/config" to resolve the issue.*
80+
9081
```bash
9182
helm install \
9283
cert-manager jetstack/cert-manager \
@@ -96,14 +87,12 @@ helm install \
9687

9788
check rollout of cert-manager
9889

99-
10090
```bash
10191
kubectl get pods --namespace cert-manager
10292
```
10393

10494
Be sure each pod is fully running before proceeding
10595

106-
10796
Install Rancher with Helm
10897

10998
*Note:If you have ".local" for your private TLD then Rancher will NOT finish the setup within the webUI*
@@ -114,19 +103,14 @@ helm install rancher rancher-stable/rancher \
114103
--set hostname=rancher.example.com
115104
```
116105

117-
118-
119106
check rollout
120107

121-
122108
```bash
123109
kubectl -n cattle-system rollout status deploy/rancher
124110
```
125111

126-
127112
you should see
128113

129-
130114
```bash
131115
Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available...
132116
Waiting for deployment "rancher" rollout to finish: 1 of 3 updated replicas are available...
@@ -142,11 +126,10 @@ kubectl -n cattle-system rollout status deploy/rancher
142126

143127
you should see
144128

145-
```bash
129+
```log
146130
deployment "rancher" successfully rolled out
147131
```
148132

149-
150133
## load balancer
151134

152135
If you are using `k3s` you can use the `traefik` ingress controller that ships with `k3s`
@@ -159,26 +142,22 @@ kubectl get svc --all-namespaces -o wide
159142

160143
look for
161144

162-
163-
```
145+
```log
164146
kube-system traefik LoadBalancer 10.43.202.72 192.168.100.10 80:32003/TCP,443:32532/TCP 5d23h app=traefik,release=traefik
165147
```
166148

167149
then create a DNS entry for `rancher.example.com 192.168.100.10`
168150

169151
This can be a host entry on your machine, or a DNS entry in your local DNS system (router, pi hole, etc...)
170152

171-
172153
otherwise you can use `nginx`
173154

174155
nginx lb
175156

176157
[https://rancher.com/docs/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/](https://rancher.com/docs/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/)
177158

178-
179159
## other considerations
180160

181161
Separating Rancher Cluster from your User Cluster
182162

183-
184163
[https://rancher.com/docs/rancher/v2.x/en/overview/architecture-recommendations/#separation-of-rancher-and-user-clusters](https://rancher.com/docs/rancher/v2.x/en/overview/architecture-recommendations/#separation-of-rancher-and-user-clusters)

0 commit comments

Comments
 (0)