-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArangoDeployment spec.architecture silently ignores additional architectures #1140
Comments
Hello! Arch switch will be possible to do in 1.2.20/1.3.0. PR is already merged on master (#1107). Once applied, you will be able to change Architecture of running Members (but member will be able to have assigned only one Architecture at same time). Will keep you informed. Best Regards, |
Hi Adam, thanks for the reply! Are you referring to switching a currently running cluster ref arangodb/arangodb-docker#53 (comment) ? This issue is about spinning up fresh clusters: specifying multiple arch in ArangoDeployment, e.g.
Currently, specifying multiple arch's (fresh cluster boot) will result in only the first one being respected. |
Hello! About this line For 3.11 we plan to mark this feature as Production together with weights (you can configure that you prefer to run on arm, but in case use also amd). It will be accessible before 3.11 as a alpha feature in Operator. 3.10 is first ARM64 release, especially 3.10.0. We need to ensure everything will be fine with multi-arch clusters and dynamic arch switching inside cluster (especially when you will upload custom analyzers). Best Regards, |
Hi 👋
it would be cool if specifying multiple architectures in an ArangoDeployment
spec.architecture
would result in multiple nodeAffinity entries on the pod specs:in the original implementation there was an error
"Only one architecture type is supported currently"
, but that seems to have disappeared before/during/after merging that PR.only the first architecture specified here is respected, however. the rest is ignored (only one nodeAffinity is added to the pods). maybe the error should not have gone 🤔 ref arangodb/arangodb-docker#110 (comment)
Originally posted by @ddelange in arangodb/docs#1141 (comment)
The text was updated successfully, but these errors were encountered: