v0.24.0

Changed

• Redesigned the “Overview” page in Console administration to show whether the
  platform needs attention. It now shows users online, active users, new orders,
  and user actions on orders, with mini charts and comparisons with yesterday.
  “Needs attention” lists failures before warnings, covering orders, stands,
  integrations, storage, background tasks, settings, and maintenance. Each entry
  shows the service, team, stand, and time, with a link to where the problem can
  be resolved. The full list opens in a side panel. The overview also shows
  platform health, orders and stand operations in progress, the approval queue,
  and recent events. Data refreshes automatically, with the last update time
  beside the page title. If the connection to Console is lost, the page shows
  how long the data has been stale. Online and active user charts start
  collecting data with this version, so they will be short during the first few
  days. Removed the “Sections” block that duplicated the menu and the
  publication counters. Publication counters remain on the “Publications” page.
• Page titles now sit in the same position throughout Console, with status next
  to the title, action buttons on the right, and explanatory text below. Removed
  the “Admin”, “InfoSec”, and “All teams” badges beside titles in the
  administration, information security, and support sections. On the
  “Maintenance” page, status moved from a separate card to beside the title.
  Service cards in the catalog now use the service name as the title, with the
  registry path in smaller text below. Publication and version approval pages
  now show a trail of navigation links instead of a separate back link. On
  publication management pages, this trail starts with “Catalog” instead of
  “Charts”. On the “Variables” page, the warning that variables are not a secret
  store now appears in a separate yellow block.

Fixed

• On administration pages and the “Notifications” page, scrollbars now have
  their own space on the right and no longer cover cards or tables in Firefox or
  Chrome. Content now matches the width of the page heading. On the
  “Configuration” and “Status” pages, spacing between sections has been
  increased to match other administration pages.

v0.23.0

Added

• Platform administrators can now set how long deleted orders and discarded
  drafts are kept. After this period, they and their history are permanently
  deleted. When a retention period is set, each deleted order’s page shows the
  days remaining and the deadline for restoring it. By default, deleted orders
  and discarded drafts are kept indefinitely.
• Service owners can now define a namespace name template so orders deploy to
  the namespace the chart actually creates. The order form previews the name as
  the required fields are filled in.
• Added “Restore order” to the order list and the deleted order’s page. It
  creates a new draft with the order’s parameters without restoring service
  data.
• Added the SHUTDOWN_DRAIN environment variable to help prevent interrupted
  requests during Kubernetes rollouts. During shutdown, the portal first reports
  that it is not ready to accept requests, then continues serving requests
  already heading to it for the configured duration. The default is 0, with no
  delay.
• Added the “Argo CD project” field to stand settings. For stands in
  “Deployment” mode, the stand page checks that the project exists and that the
  portal account can read and sync its applications.

Changed

• Organized the Admin sidebar into groups for monitoring, configuration, and
  maintenance. Shortened the menu labels to “Orders”, “Publications”, and
  “Status”. When the menu is collapsed, separators replace group headings.
• Replaced “Copy to stand” with “Create copy” in the orders list and on the
  order page. You can now create a draft on the same stand with a new service
  name or copy an order to another stand.

Fixed

• The same service ordered on different stands now gets distinct application
  names, preventing conflicts in Argo CD. Application names for existing orders
  remain unchanged. If an application name is already used by an order on
  another stand in the same Argo CD instance, the portal rejects the new order
  and asks you to choose a different service name.
• Removed “Sync with cluster” from the order list row menu and the order page
  actions menu for administrators viewing deleted orders. The portal also
  rejects synchronization requests for deleted orders and drafts, even if sent
  outside the interface.
• The order form no longer blocks submission when required parameters have
  service defaults, including parameters hidden from the form. Default values
  appear as hints, with dropdowns and checkboxes set to their default states.
  Required parameters without defaults still need to be filled in.
• Fixed several issues affecting portals running with multiple instances. “Check
  again” on the “Configuration” page now runs checks on every instance so the
  page no longer shows stale results from another instance. After a leader
  switch, administrators no longer receive duplicate configuration alerts, such
  as warnings about an expiring token or a disabled webhook, and receive alerts
  again if a resolved problem returns. Order and user counts in monitoring are
  no longer inflated when summed across instances after a leader switch. During
  shutdown, the leader now finishes its current background order processing
  before handing the role to another instance.

v0.22.0

Added

• Added the “Maintenance” admin page. Platform admins can start maintenance now
  or schedule it, set an optional end time and user message, pause the portal’s
  background operations in GitLab, Argo CD and the chart registry, and enable
  automatic finishing at the planned end. They can also extend or finish
  maintenance and view its history. Before maintenance, everyone sees a banner
  with the schedule and receives a notification and a reminder 15 minutes before
  the start. During maintenance, only platform admins retain access and see a
  banner linking to the admin page. Other users see the admin’s message and
  planned end time, then automatically return to the same page when maintenance
  ends. Unfinished order forms are saved in the browser when access is blocked
  and offer to restore the saved data afterward. Admins are notified if
  maintenance runs past its planned end without automatic finishing. Server
  administrators can also enable maintenance with MAINTENANCE_FORCE.

Fixed

• Order lists on the “Order list” page, the “All teams’ orders” page in the
  support section, and product pages now update immediately when a stand is
  selected in the filter.

v0.21.0

Added

• Added “All teams’ orders” to the administrator menu, with the same order list
  and filters as in the support section. Administrators can now view orders
  across all teams without switching to the support section.
• Added a banner at the top of every open page when a new portal version is
  available. It reminds you to finish and save your work in forms before
  reloading, provides a reload button and a “What’s new” link to the release
  notes on the “About” page. You can dismiss the banner. If a screen cannot open
  because the page is still using an older portal version, the page
  automatically reloads once and opens that screen.

Changed

• Extended the "Order form constructor" documentation with an explanation of why
  hiding a field filled through initial does not replace defaults. The new
  section explains how hidden fields can still be changed, why changes to
  initial do not update existing field values in orders, and when to use
  defaults to enforce a value on every save.
• Reworked the administrator “Stands” page. The table shows each stand’s order
  processing mode, default cluster, GitLab path and a new “State” column:
  connected, not connected, not checked, ready for orders or no path. Adding and
  editing a stand now use the same side panel with “Basic settings”, “Order
  storage” and “Argo CD settings” sections and a save button. Editing values
  directly in table rows is no longer available. “Make default” and “Delete”
  moved to the row’s “...” menu. Simplified the page text and added guidance for
  each field on what to enter and what happens when it is empty. Throughout the
  portal and its documentation, “Mode” is now “Order processing”, with
  “Deployment” (formerly “Deploy”), “GitLab only” (formerly “Git only”) and
  “Portal only” (formerly “Console only”). “Git layout” is now “GitLab storage”,
  with “Separate repositories” (formerly “Group”) and “Shared repository”
  (formerly “Repository”). These name changes do not affect order processing or
  storage behavior.

Fixed

• Opening an order from the all-team orders list or a stand page in the
  administrator or support section no longer switches the sidebar to “Platform”.
  The sidebar stays in the original section and highlights the orders list item.
• The order form builder now reports an error when validating a view document if
  a tab points to a list of strings, numbers, or booleans. Display these lists
  as regular list fields in a form, since tabs require lists of objects.

v0.20.1

Fixed

• Creating or copying orders to another stand no longer triggers a false
  duplicate-name error when the order name, namespace and cluster name match.
  Duplicate names in the same namespace and cluster are still refused within one
  stand. Importing orders from Git no longer skips an order because the same
  application name exists on another stand.

v0.20.0

Added

• Added optional Git URL and Argo CD namespace settings for each stand. When
  left empty, they use the portal's GitLab URL and the namespace from the
  platform settings. The values are applied to order application.yaml files
  and Argo CD connection manifests on the stand page. Existing orders receive
  the new values when next modified. Changing the Git URL preserves the
  repository path, so a mirror must use the same path.

v0.19.0

Added

• You can now route service orders to named stands such as dev, stage, or prod,
  managed by administrators on the “Stands” page. Choose a stand in the order
  form to fill in its default cluster, and see the stand in the orders list and
  on each order’s page. Existing orders are assigned to the default stand
  without affecting their deployments.
• Administrators can set a shared value for each variable and, when needed, a
  separate value for each stand. When an order is saved, the portal uses the
  value for the selected stand or the shared value if no stand value is set. An
  empty shared value now prevents an order from being saved on a stand without
  its own value. Previously, the portal used an empty string.
• You can now copy an order to another stand from the orders list or the order
  page. This creates a draft of the same service and version in the same team.
  Values from variables are filled in again for the new stand, while other
  values are preserved. Review the draft, make any changes you need, and submit
  it as a regular order.
• You can now choose a Git layout and GitLab path for each stand: a group with
  separate team permissions or a single repository without that separation. The
  layout and path cannot be changed while the stand has orders other than drafts
  or deleted orders. Each stand now has a page with GitLab access checks, Argo
  CD checks, and manifests that you apply manually once per stand. The portal
  creates nothing in Argo CD. Git imports now scan each stand’s path and assign
  discovered orders to that stand.
• Stands now support three modes. "Deploy" keeps the existing workflow: the
  portal saves order files to Git and opens a merge request. After the merge,
  Argo CD deploys the service while the portal tracks its status. "Git only"
  saves the same files to Git and opens a merge request. After the merge, the
  order receives the status "Saved in Git" and no further action runs. "Console
  only" stores the order in the portal without writing to Git and immediately
  sets its status to "Saved in console". Edits and deletion apply immediately
  without a merge request. Each stand can also specify its own chart registry
  for Argo CD. Leave this value empty to use the platform registry.
• Added background stand checks and a Stands section on the platform status page
  with each stand's worst check result, last check time, and a link to its page.
  Orders on stands not yet connected to Argo CD now show a waiting notice with a
  link to connection manifests for administrators. The new Nested paths check
  warns on both stand pages when Argo CD for a stand in "Deploy" mode would also
  deploy files from a nested stand in "Git only" or "Console only" mode.
• Added support for changing a stand's mode when it has orders. Existing orders
  move in the background from "Console only" to "Git only" or "Deploy", and from
  "Git only" to "Console only" or "Deploy". The stand's mode changes immediately
  and applies to new orders. The stand page shows progress and orders that could
  not be moved, with reasons. You can stop the task. Orders already moved keep
  their new mode, and the remaining orders keep their previous mode. While the
  task is running, the stand's mode, layout, and path cannot be changed. If
  automatic merging is disabled, the task waits for manual merging of merge
  requests. Leaving "Deploy" still requires deleting the stand's orders, except
  drafts and deleted orders.
• Administrators can now delete a stand and its orders from the stand list.
  Deletion runs in the background and blocks new orders on the stand. Once all
  orders are deleted, the portal removes the stand, its variable values, and its
  GitLab group or repository if created by the portal. The group specified in
  platform settings and groups created outside the portal are preserved. The
  default stand, the last remaining stand, and stands with an active task cannot
  be deleted. If any order fails to delete or the task is stopped, the stand
  remains. Deleted orders cannot be restored. After successful deletion,
  administrators must manually remove the stand's ApplicationSet and secrets
  from Argo CD.
• Added a support chat button in the bottom-right corner of every portal page.
  It opens the platform support chat in a messenger in a new tab. Occasional
  hints next to the button invite you to ask questions or report problems. You
  can dismiss the hints with the close icon while keeping the button available.
  Administrators set the chat address using the SUPPORT_CHAT_URL environment
  variable. The button is hidden if the variable is not set.

v0.18.1

Changed

• Rewrote the page about the version constructor in the portal's "Documentation"
  section. It now describes every feature of the version document with a
  ready-to-use example. Constructor error messages are grouped into tables by
  topic, with explanations of what to fix.

Fixed

• Opening the order form now immediately shows a page outline instead of a blank
  screen. The "Service parameters" card shows field outlines until the form
  loads and keeps the same height when the fields appear.
• Fixed orders staying in “deploying” without an error reason while Argo CD
  retried after failing to build the service. The order now switches to “failed”
  a few minutes after the error appears, even during retries, and its card shows
  the reason reported by Argo CD. Once the service builds successfully again,
  the order automatically returns to “running”. No action is required.
• Security users can now open the Platform section and work with orders for
  their teams. Users without a team cannot see or place orders. Ask an
  administrator to add you to a team. Security access does not include orders
  from other teams.

v0.18.0

Added

• In the version constructor, you can now follow a $ref reference in the chart
  schema to its definition using Ctrl+click or F12. Hovering over the reference
  shows its destination or indicates that the definition is missing.

Changed

• In the version constructor, field suggestions for a form view now include
  nested fields as paths, such as tls/certificates. You can display an
  individual field without the heading of its parent section.
• The order form, service list tabs and edit dialogs now show field outlines
  instead of a loading indicator while loading. This prevents the layout from
  shifting when the fields appear.

Fixed

• Fixed error messages in the order form when one field controls whether another
  is enabled. The messages now use the field label and explain whether to turn
  the field on or off.

v0.17.1

Fixed

• Fixed an incorrect "Not working" order status during a service upgrade when
  the error belongs to the version being replaced.
• Fixed stalled service upgrades by automatically retrying deployment.
• Fixed missing settings for nested components in the order form and service
  details.