member badge
Jelle den Burger
meshStack's
Location
concept is being deprecated. Locations were introduced as a way to group platforms by geography or organizational unit. However, they have proven to create unnecessary complexity.
What is changing
For existing meshStacks, nothing changes at the moment. However, for new meshStack (or if opted-in for existing ones) you can use the newly introduced
autoSelectGlobalLocation
configuration. If enabled:
  • New platform instances
    will automatically be placed in the built-in
    global location
    . You no longer need to create or manage custom locations.
  • Location creation
    via the meshStack panel and meshObject API will be disabled. Existing locations remain readable and operational during the migration window.
  • API integrations
    using
    meshLocation
    as a meshObject (e.g.
    POST /api/meshobjects
    with
    kind: meshLocation
    ) will need to be updated to reference the global location identifier or remove the location reference entirely.
Timeline
  • Now
    : The
    autoSelectGlobalLocation
    config flag is available. New meshStack instances already have locations fully disabled. For existing instances, your platform engineering team can opt in by enabling this flag (ask your Customer Success team)
  • Upcoming
    : meshcloud will enable this flag by default for all new meshStack instances.
  • End-state
    : Locations will be fully removed from meshStack. An exact removal date will be communicated with at least 3 months' notice.
What you need to do
At the moment you don't have to do anything. We will communicate again when there are next steps in the deprecation of meshStack locations for existing meshStacks.
Questions or concerns?
Please reach out to your customer success manager or contact us at support@meshcloud.io. We are happy to help assess the impact on your specific setup.