Giter Club home page Giter Club logo

Comments (7)

ddelange avatar ddelange commented on June 6, 2024 1

awesome thanks so much for the quick action and the clear explanation!

from docs.

Simran-B avatar Simran-B commented on June 6, 2024 1

#1187 is not merged yet, and we typically re-publish the docs for a release (v3.9.5 is imminent).

from docs.

ddelange avatar ddelange commented on June 6, 2024

fwiw 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)

from docs.

ddelange avatar ddelange commented on June 6, 2024

fwiw, <group>.id is also missing from docs ref arangodb/kube-arangodb#1141 (comment)

from docs.

ddelange avatar ddelange commented on June 6, 2024

@nerpaula @Simran-B I think this should be re-opened:

as far as I can see, the linked PR documents the arango operator's spec.architectures field, not the ArangoDeployment resource's spec.architecture field.

the operator supports multiple architectures passed as list[str], whereas the ArangoDeployment field is list[str] but only supports one architecture in that list, see previous comments above.

from docs.

Simran-B avatar Simran-B commented on June 6, 2024

@ddelange Thanks for pointing out that something isn't right with the new content. I clarified with @jwierzbo that the deployment specification uses spec.architecture (singular) for defining an architecture, and it should normally be a list with a single item only. However, for the purpose of migrating to a different architecture, you can specify two architectures, and the first one defines the architecture you want to migrate to. After the migration, the old architecture should be removed from the list. It's being discussed internally whether a secondary architecture should be supported as a fallback, i.e. having two architectures in the deployment specification permanently.

Clarifications PR: #1187

from docs.

ddelange avatar ddelange commented on June 6, 2024

@Simran-B spec.architecture seems still missing in the ArangoDeployment resource docs, is this part not auto-generated? also related to arangodb/docs-hugo#215

from docs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.