| Excerpt | ||
|---|---|---|
| ||
If clients opt for self-hosted options, either Customer Managed Tenant or On Premise Tenant, they (potentially with Uniques Advisory at a rate) must equally provide all necessary pieces in order to satisfy the setup and run requirements. You can learn about them in the respective models details linked above. Note that this page gives a high-level overview. For Customer Managed Tenant clients can use the Pre-Installation Checklist to further cross-check their tenant for the arrival of Unique. |
| Inc drawio | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Providing a tenant (1)
It does not matter what deployment model is chosen, a client has to provide a landscape that can provide user accounts (IAM, IDP, potentially Just-In-Time or Privileged Access Management).
...
Hosting Unique / Dedicated resources (2)
Clients must provide means to provision a set of resources needed to run Unique successfully. Depending on the use cases, more or less of these services are needed.
...
Workload configurations and supporting services (3)
Brick | Use Case | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Postgres Server1 |
|
| ||||||||||||
MongoDB1 |
|
| ||||||||||||
Redis Cache(s)1 |
|
| ||||||||||||
LLMs1 (mainly Azure OpenAI) |
|
| ||||||||||||
|
| |||||||||||||
S3 compatible storage1 |
|
| ||||||||||||
|
|
1 These services are recommended to be provisioned outside of the orchestrator, see (2).
Unique workloads (4)
The Unique workloads themselves have no requirements except all the services mentioned above, CPU and memory. Some require some disk space to locally ephemerally cache file or similar content.
...
You can get familiar with those in Releases Release Process.
Some key bullets in that regard are:
...
Tool | Use Case | Examples |
|---|---|---|
Git or another VCS | Store versioned Unique artefacts as code for audits, infrastructure as code, customisation and automation etc. | GitHub (Cloud) GitHub Enterprise Azure DevOps GitLab Enterprise |
(CI/) but especially CD Automation | Automation and Principals that apply code changes published by Unique | GitHub Actions Azure DevOps Agents GitLab CI Bitbucket Pipelines Or more futuristic: FluxCD ArgoCD |
Container Registry | Cache, scan, analyze container images delivered by Unique as part of the Releases Release Process. In order to mirror the images the Automation above can be reused. | Azure Container Registry DockerHub Github Packages |
Helm Chart Gallery | Cache, validate helm charts delivered by Unique as part of the Releases Release Process. In order to mirror the charts the Automation above can be reused. ⚠️ This must also be used to potentially cache public helm charts as Unique does not re-deliver open source components! | Azure Container Registry |
Secrets Management | When deploying and maintaining Unique (incl. via Helm Charts), secrets must be provided to the workloads. The Secrets Management is highly dependent on the Clients eco-system. |
...
Author |
|---|