Installation of cloud2edge in K3S doesn't complete - two services want port 8080 on same external IP?

[mmcc-xx]

I'm trying to install cloud2edge on a new single node K3S deployment.

All pods go to running. All services look ok except c2e-adapter-http whose external IP is stuck in pending. See screenshot below.

Maybe it is stuck because port 8080 on the external IP has already been allocated to another service?

[mmcc-xx]

Work around - after issuing the helm command, get the details of the c2e-adapter-http service: kubectl get svc c2e-adapter-http -ojson -n $NS Copy out the "spec" section into a text file. Replace port 8080 with port 8081. Save as patch.json

Merge patch the service: kubectl patch svc c2e-adapter-http --type=merge --patch-file patch.json -n $NS

The service will get its external IP address and the helm installation will complete.

[calohmn]

When deploying the cloud2edge chart using the Hono 2.4.x chart version, the HTTP adapter service will use the secure port only by default (see #475). Therefore the error above won't happen there, I guess. But nonetheless a port number clash should be prevented if a configuration is used where insecure-ports are enabled.