meshStack Settings
To change Settings for the meshStack go to the "meshStack Settings" section of the Administration area.
Change Logo
Organization admins and organization users can access the meshStack Settings to change the logo on the top left of the panel.
Upload a new Logo
Click the button "Browse" to find a new logo on your system and upload this logo, which will be shown on the top-left of the panel to all users of your company.
Please make sure your image fits the following requirements: Only images with .png extension are allowed. Maximum dimensions allowed are 1000x500 px. The size of the image should not be more than 250 KB.
Reset Logo
After clicking the "Reset Logo" button, the logo will be reset to the default logo, which is usually the meshcloud logo. This change will be visible to all users of your company.
Lightweight Platforms
If you build every platform you offer with building blocks, you can turn on "Lightweight Platforms" in the "Management" tab of the meshStack Settings, under "Platforms".
While the setting is on, platform engineers and admins can only create platforms of a custom platform type. meshStack refuses to create a new platform of a built-in platform type such as AWS, Azure or GCP, in meshPanel and in the meshPlatform API. Platforms you already have keep working as before.
Turning the setting on also deactivates every built-in platform type that no active platform and no building block definition uses. A deactivated platform type no longer appears when you create a platform or choose the supported platforms of a building block definition. Built-in platform types that are in use stay active. Turning the setting off activates the platform types that the setting deactivated. A platform type that an admin deactivated stays deactivated. meshStack writes an event log entry for each platform type it deactivates or activates.
The setting also applies to landing zones of custom platforms: they can no longer get new mandatory or recommended building blocks. meshPanel hides the building blocks section when you create or edit such a landing zone. The meshLandingZone API refuses new building blocks, but you can keep or remove the ones a landing zone already has. Tenants created with the landing zone still get its mandatory building blocks. Landing zones of built-in platform types are not affected.
For custom platforms, meshPanel hides the "Configuration" tab with the metering configuration while the setting is on.
You can choose per building block definition which landing zones it supports, in its supported platforms: tick single
landing zones in the supported platforms tree in meshPanel, or add meshLandingZone entries in the meshObject API.
Use building block definitions for platform team automation only
in compositions: a composition building block definition of the same workspace can add such a building block, but an
application team cannot. In a meshStack with lightweight platforms, the two together replace mandatory and recommended
building blocks on landing zones of custom platforms.
You can turn the setting off again at any time. meshStack writes an event log entry each time an admin turns the setting on or off.