Closed mikeywaites closed 3 years ago
Hi there :wave:
It seems you have run into the NodePort being a fixed value. I have just merged a fix to address this so Kubernetes uses an available port. We plan on releasing a new version of the Chart later today or at latest tomorrow.
Let me know if that fixes your problem!
Hey Thanks for getting back to me and for addressing the issue.
I will eagerly await the release so that I can try out the fix. I will let you know either way.
Hey
Been testing out the new onepassword-connect k8s operator. Firstly, what a fantastic ideas - Our team are really keen to get this going.
Our architecture has several isolated namespaces inside a single gke cluster so our plan was to set up 1password connect and operator inside of each namespace.
Trying to install this into a single namespace
dev
initially results in an error.Error: Service "onepassword-connect" is invalid: spec.ports[0].nodePort: Invalid value: 31080: provided port is already allocated
Hope someone can help us resolve this issue. Also, if there's any advice on how best to manage this architecture where there's an instance of 1password connect per namespace, that would be greatly appreciated.