Skip to content

[fedUC] K8s clusters management

Users with system administrator and operator roles should be able to add, edit, view and delete information about multiple underlying k8s clusters on which user applications can be deployed.

A cluster data should contain the following fields:

  • name (text with length limit, e.g. 256)
  • codename (text with constraint length and characters set, e.g. 16 chars)
  • description (plain text)
  • operator contact information (plain text)
  • date added
  • date last modified
  • cluster configuration file (option to upload raw file or paste content)

To be defined:

  • does the k8s configuration file need to be stored in the filesystem or in the sql database?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information