Software Support Matrix
Product Lifecycle Matrix
This table shows the support lifecycle for different products, which are made up of several components. It provides an overview of the product's support across various operating systems and software versions.
| Product | Version | Operating Systems | Software | Supported From | Supported Until |
|---|---|---|---|---|---|
| asi bundle - core 0.2 - management-service 2.2 - authenticator 2.2 - dashboards 0.2 | 3.2 | Redhat/Fedora 8.x, 9.x | Java 11, Java 17 | 2025-01-31 | 2027-01-31 |
Deployment Options for the Product
The asi bundle can be deployed in two different ways:
-
Distributed Microservices Deployment
This method involves deploying each of the individual components (Core, Management-service, Authenticator, Dashboards, etc.) as independent microservices. Each component can be deployed on separate servers or containers, enabling a distributed architecture. This approach provides:- Scalability: Each component can scale independently, adapting to varying demand.
- Flexibility: Components can be deployed across different environments, such as cloud, on-premises, or hybrid configurations.
- Resilience: If one component fails, the others can continue to operate without affecting the entire system.
In a distributed setup, the components communicate with each other via APIs or service meshes, allowing for a decoupled architecture where each service has a specific responsibility.
-
Bundled Deployment
Alternatively, users can choose to deploy the asi bundle as an all-in-one installation. This approach installs all the components (Core, Management-service, Authenticator, Dashboards, etc.) together on a single server or container. This option is ideal for:- Simplified Setup: Users can install the entire product on a single machine, making it easier to configure and maintain.
- Faster Deployment: The product is ready to run out of the box without the need for complex orchestration.
- All-in-One Environment: Best suited for smaller deployments or situations where high scalability and distributed architecture are not required.
This method is generally used in smaller or less complex environments where the overhead of microservices and their communication mechanisms is not necessary.
Component Lifecycle Matrix
The table below shows the lifecycle for each component of the product, detailing the version, supported operating systems, and the software required.
| Component | Version | Operating Systems | Software | Supported From | Supported Until |
|---|---|---|---|---|---|
| core | 0.2 | Redhat/Fedora 8.x, 9.x | Java 11, Java 17 | 2024-11-25 | 2026-11-25 |
| management-service | 2.2 | Redhat/Fedora 8.x, 9.x | Java 17 | 2023-01-01 | 2026-12-31 |
| authenticator | 2.2 | Redhat/Fedora 8.x, 9.x | Java 17 | 2023-01-01 | 2026-12-31 |
| dashboards | 0.2 | Redhat/Fedora 8.x, 9.x | Java 17 | 2023-01-01 | 2026-12-31 |
| events | 1.1 | Redhat/Fedora 8.x, 9.x | Java 17 | 2023-01-01 | 2026-12-31 |
| PostgreSQL | 15+ | Platform Agnostic | N/A | check | check |
Notes on Deployment
- Distributed Microservices: For this deployment strategy, you can use container orchestration tools such as Kubernetes to manage and scale each microservice independently. This approach is most suitable for cloud-native environments where flexibility and scalability are required.
- Bundled Installation: In this scenario, the installation process bundles all the components into a single package, which can be installed on a physical or virtual machine. This is ideal for users who prefer simplicity or need to deploy on a limited infrastructure.
Notes
- Dates are subject to change based on lifecycle policies and major releases.
- Support for newer OS versions will be added based on testing outcomes.
For any updates or clarifications, please contact the support team.