Prowlarr/README.md

@@ -1,8 +0,0 @@
-# Prowlarr
-Prowlarr is an indexer manager/proxy built on the popular *arr .net/reactjs base stack to integrate with your various PVR apps. Prowlarr supports management of both Torrent Trackers and Usenet Indexers. It integrates seamlessly with Lidarr, Mylar3, Radarr, Readarr, and Sonarr offering complete management of your indexers with no per app Indexer setup required (we do it all).<br>
-\- [source](https://github.com/Prowlarr/Prowlarr)
-
-## Using this kubernetes config
-In `ingress.yml`, set the hostname that users will use to connect to the service. This config assumes you have cert-manager installed on your cluster, so if you want to provide HTTPS another way, feel free to comment out the `spec.tls` section (the annotation shouldn't affect anything, but you can comment it out as well if you want)
-
-You can also change the user ID and group ID in `deployment.yml` under which Prowlarr runs if you need to, but it should work just fine as it is.

Prowlarr/deployment.yml

@@ -1,48 +0,0 @@
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: prowlarr
-spec:
-  replicas: 1
-  selector:
-    matchLabels:
-      app: prowlarr
-  template:
-    metadata:
-      labels:
-        app: prowlarr
-    spec:
-      containers:
-        - name: prowlarr
-          image: linuxserver/prowlarr:latest
-          ports:
-            - containerPort: 9696
-          env:
-            - name: PUID
-              value: "1000"
-            - name: PGID
-              value: "1000"
-            - name: TZ
-              value: "UTC"
-          resources:
-            limits:
-              memory: "512Mi"
-              cpu: "500m"
-          volumeMounts:
-            - name: config
-              mountPath: /config
-      volumes:
-        - name: config
-          persistentVolumeClaim:
-            claimName: prowlarr-config-pvc
----
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: prowlarr-config-pvc
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 512Mi

Prowlarr/ingress.yml

@@ -1,22 +0,0 @@
-apiVersion: networking.k8s.io/v1
-kind: Ingress
-metadata:
-  name: prowlarr
-  annotations:
-    cert-manager.io/cluster-issuer: "letsencrypt-production"
-spec:
-  tls:
-    - hosts:
-        - <prowlarr domain name>
-      secretName: prowlarr-tls
-  rules:
-    - host: <prowlarr domain name>
-      http:
-        paths:
-          - path: /
-            pathType: Prefix
-            backend:
-              service:
-                name: prowlarr
-                port:
-                  number: 80

Prowlarr/service.yml

@@ -1,11 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: prowlarr
-spec:
-  selector:
-    app: prowlarr
-  ports:
-    - name: http
-      port: 80
-      targetPort: 9696

README.md

@@ -1,30 +1 @@
-This is a collection of kubernetes configurations for various services that I have modified from my own personal kubernetes repo to be used by anyone. Each service comes with a readme explaining how to configure each service. The documentation is written assuming you have some knowledge of how to apply kubernetes configs. It also works on the assumption that you have cert-manager installed on your cluster for automatic tls certificate generation
-
-## Progress
-- [x] Authentik
-- [ ] Baikal
-- [ ] Cert-Manager
-- [ ] Conduit
-- [ ] Continuwuity
-- [ ] ErgoChat
-- [x] FlareSolverr
-- [ ] Gitea
-- [x] Headscale
-- [ ] Immich
-- [ ] Inspircd
-- [x] Jellyfin
-- [x] Kavita
-- [ ] Lidarr
-- [x] Mealie
-- [ ] Minecraft Servers
-- [ ] MinIO
-- [ ] Navidrome
-- [ ] Outline
-- [ ] PrivoxyVPN
-- [x] Prowlarr
-- [ ] QBitTorrent
-- [x] Radarr
-- [x] Sonarr
-- [ ] Soulseek
-- [ ] Syncthing
-- [ ] Tuwunnel
+This is a collection of kubernetes configurations for various services that I have modified from my own personal kubernetes repo to be used by anyone. Each service comes with a readme explaining how to configure each service. The documentation is written assuming you have some knowledge of how to apply kubernetes configs. It also works on the assumption that you have cert-manager installed on your cluster for automatic tls certificate generation