fabito / htk8s Goto Github PK

kubernetes-sigs/kustomize#2934

after excute kustomize command I got duplicate port in install.yaml:

        - containerPort: 51413
          name: torrent-tcp
          protocol: TCP
        - containerPort: 51413
          name: torrent-tcp
          protocol: TCP

Was checking this project out for the first time. Forgive me for my k8s/k3s laypersonship.

Ran the x86 install, was unable to access Transmission. Ingress said 502 Bad Gateway. Checking out the logs indicated that the settings.json was malformed. Inspection of the JSON shows:

"rpc-host-whitelist-enabled": false,

Obviously, something has been interpreted weird. So I scaled the replicaset to 0, nuked the file, and scaled back up:

kubectl scale --replicas=0 replicaset/transmission-5bf9655f77
rm /opt/htpc/transmission/settings.json
kubectl scale --replicas=1 replicaset/transmission-5bf9655f77

That restored it back to the application default which has the tragic side-effect of turning whitelisting back on. Back to the drawing board. Lets try a new deployment:

kubectl scale --replicas=0 replicaset/transmission-5bf9655f77
rm /opt/htpc/transmission/settings.json
kubectl rollout restart deployment/transmission

Isolated the issue to the deployment args by manually replacing the JSON being echo'd into the config file:

      - args:                                                                                                                                                                                          
        - echo starting; echo deadbeef > /config/settings.json; echo done;   

Success. The config file literally just says "deadbeef." So there seems to be something wrong with the way the JSON is being spit out into the config file as a deployment argument.

Running on a bare-metal Ubuntu 20.04 server, if that matters.

The volumes are mounted per machine, instead of using PersistantVolumeClaim (PVC).
The issue is that In case more than one node is running, it's possible for example radarr to run on machine 1 and the download to be done on machine 2, meaning that radarr on machine 1 cannot copy the download from machine 2.

I think a starting 20-40gb is good enough.

HI,

This setup looks great. I am thinking of trying it out shortly once I get a new pi 4. Any support for VPN inside the cluster ?

Add init container logic to pre configure bazarr.

• add bazarr to ingress
• create /config/config/config.ini
• configure sonarr
• configure radarr
• configure base_url

[assrt]
token = 

[opensubtitles]
username = 
use_tag_search = False
skip_wrong_fps = False
ssl = False
vip = False
timeout = 15
password = 

[sonarr]
apikey = abc
full_update = Daily
ip = sonarr
only_monitored = False
base_url = /sonarr
ssl = False
port = 8989

[proxy]
username = 
url = 
exclude = localhost,127.0.0.1
password = 
type = None
port = 

[radarr]
apikey = abc
full_update = Daily
ip = radarr
only_monitored = False
base_url = /radarr
ssl = False
port = 7878

[addic7ed]
username = 
password = 
random_agents = True

[legendastv]
username = 
password = 

[auth]
username = 
password = 
type = None

[general]
movie_default_hi = False
movie_default_language = []
ip = 0.0.0.0
use_scenename = True
use_postprocessing = False
enabled_providers = subscene,tvsubtitles
auto_update = True
port = 6767
use_radarr = True
base_url = /bazarr/
page_size = 25
minimum_score_movie = 70
branch = master
single_language = False
use_sonarr = True
serie_default_hi = False
path_mappings_movie = [['/movies', '/movies'], ['', ''], ['', ''], ['', ''], ['', '']]
serie_default_enabled = False
movie_default_enabled = False
serie_default_language = []
path_mappings = [['/tv', '/tv'], ['', ''], ['', ''], ['', ''], ['', '']]
postprocessing_cmd = 
minimum_score = 90
debug = False
use_embedded_subs = True
adaptive_searching = False

log from bazarr pod:
PermissionError: [Errno 13] Permission denied: '/config/bazarr.restart'

Maybe you need to add the chown part to the init container?

Getting a deprecation warning when using a contemporary Kubernetes release. Just a matter of reformatting the spec for the Ingress resources. The deprecation was introduced in 1.14 and will remove it in 1.22+.

I'd be happy to submit a patch for it if you want, its a boring manual change. I am fixing it in my fork but it has a bunch of of other implementation specific changes.

If interested, how would you like this fix delivered? Separate fork or just a PR? Or do you not care (which is totally fair) :D