aio helm chart deployment hostPort conflicts with LoadBalencer definition

[drokath]

Steps to reproduce

1. Install the chart

Expected behavior

nextcloud-aio-apache pod should be running

Actual behavior

nextcloud-aio-apache pod is pending with the following message:

node(s) didn't have free ports for the requested pod ports. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..

Host OS

NA

Nextcloud AIO version

Helmchart 7.2.1

Current channel

NA

Other valuable info

[szaimen]

Hi, you can adjust the port via

all-in-one/nextcloud-aio-helm-chart/values.yaml

Line 22 in f8a855f

APACHE_PORT: 443 # Changing this to a different value than 443 will allow you to run it behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else).

[drokath]

Hi Simon,
Unfortunately the APACHE_PORT, is used both as a nodePort in deployment, and in the LoadBalancer which can not work on a single node. Hence the error.

On top of that, apache is exposed twice.

Just removing the nodePort definition would allow to run on a single node while exposing nextcloud-aio-apache only once.

[szaimen]

On top of that, apache is exposed twice.

No, one is tcp and one udp

[szaimen]

Unfortunately the APACHE_PORT, is used both as a nodePort in deployment, and in the LoadBalancer which can not work on a single node. Hence the error.

Are you sure about that? We use kompose to create the chart and it configures this automatically like this. See

all-in-one/nextcloud-aio-helm-chart/update-helm.sh

Line 46 in f8a855f

kompose convert -c -f latest.yml --namespace nextcloud-aio-namespace

[drokath]

Twice meaning as a nodePort for udp/top and LB for tcp/udp both use the exact same port.

[szaimen]

Twice meaning as a nodePort for udp/top and LB for tcp/udp both use the exact same port.

So can we get rid of the Loadbalancer then or how should we fix this in your opinion? The APACHE_PORT must be reachable from outside the cluster, this is why I think we need the loadbalancer?

[drokath]

Yes I am sure: https://github.com/nextcloud/all-in-one/blob/main/nextcloud-aio-helm-chart/templates/nextcloud-aio-apache-deployment.yaml#L79 https://github.com/nextcloud/all-in-one/blob/main/nextcloud-aio-helm-chart/templates/nextcloud-aio-apache-service.yaml#L15-L16 Keeping the LB and removing the container hostPort would be better. As it would ne easier to and an ingress through a reverse proxy from there.

[szaimen]

Will be fixed with #3445

[drokath]

Awesome thank you. Le ven. 29 sept. 2023, 11:32, Simon L. ***@***.***> a écrit :

…

Will be fixed with #3445 <#3445> — Reply to this email directly, view it on GitHub <#3433 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABP3HSOP4S5HBUFZEM45TWLX42IRRANCNFSM6AAAAAA5K4IGN4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[szaimen]

Hi, this is now fixed with v7.4.1. Testing and feedback is welcome!