Che Operator gets stuck updating endpoint URLs when "legacy" hostname is used #22774
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
kind/bug
Outline of a bug - must adhere to the bug report template.
severity/P1
Has a major impact to usage or development of the system.
Describe the bug
When the Che Operator has to fallback to the legacy format for endpoint hostnames (as added by eclipse-che/che-operator#1702), it can get stuck in a loop updating endpoint hostnames. This occurs because in Golang, map iteration order is random, resulting in a random
order
number being used for each endpoint (see here.Che version
7.80@latest
Steps to reproduce
code-redirect-x
endpoints is longer than 63 characters (format is<username>-<workspacename>-<endpointname>
)<workspaceID>-<number>
)Expected behavior
We should be using deterministic names for endpoints.
Runtime
Kubernetes (vanilla)
Screenshots
No response
Installation method
other (please specify in additional context)
Environment
other (please specify in additional context)
Eclipse Che Logs
No response
Additional context
Originally reported: #22667
DevWorkspace's workaround for this issue: link
The text was updated successfully, but these errors were encountered: