Repository navigation
fix: accept IPv6 addresses in HP_K8S_HOST_ALIASES - #146
Conversation
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
HP_K8S_HOST_ALIASESentries are split at the last:, so an IPv6 address breaks them:nextcloud.example.com:fd00::5becomes the address5and the host namenextcloud.example.com:fd00:. Kubernetes then rejects the whole ExApp Deployment, valid aliases in the same list included (spec.template.spec.hostAliases[0].ip: Invalid value: "5": must be a valid IP address), so every ExApp install on the Kubernetes backend fails with 503.Changes
:, as Docker's--add-hostdoes, and brackets around an IPv6 address are removed.Entries with an IPv4 address are parsed as before.