Deploy and Host GLPI on Sealos

GLPI is an open-source IT asset management and service desk platform. This template deploys GLPI 11.0.8 with a dedicated KubeBlocks MySQL database, persistent storage, and a public HTTPS endpoint on Sealos Cloud.

About Hosting GLPI

GLPI combines hardware and software inventory, license tracking, service desk workflows, knowledge management, and reporting in one web application. Teams can use it as a central system of record for IT assets and support operations.

The template follows the official two-service container topology: one GLPI application instance connects to a dedicated MySQL database. Sealos provisions both persistent volumes, database credentials, service discovery, TLS, and the public domain. The official image automatically installs or upgrades the GLPI schema after MySQL becomes available.

Common Use Cases

• IT Asset Management: Track computers, monitors, network devices, software, licenses, and their ownership.
• Service Desk: Manage incidents, requests, problems, changes, service-level targets, and technician queues.
• Inventory and Compliance: Maintain an auditable inventory and monitor software license usage.
• Knowledge Management: Publish internal procedures and reusable solutions for users and support teams.
• Operations Reporting: Build dashboards and reports for asset health, ticket flow, and support performance.

Dependencies for GLPI Hosting

The template includes the GLPI 11.0.8 application, a KubeBlocks-managed MySQL 8 cluster, a 1 GiB application volume mounted at /var/glpi, a 1 GiB database volume, and HTTPS ingress.

Deployment Dependencies

• GLPI documentation - Product and administration documentation
• GLPI installation documentation - Requirements and installation behavior
• Official GLPI container images - Container configuration and environment variables
• GLPI community - Community support forum

Implementation Details

Architecture Components:

• GLPI application: A single glpi/glpi:11.0.8 StatefulSet serves the web UI and runs the official bundled cron worker.
• MySQL database: A single-node KubeBlocks MySQL 8 cluster stores GLPI configuration, users, inventory, and service desk data.
• Persistent storage: /var/glpi preserves configuration, uploaded files, logs, sessions, and marketplace data. MySQL uses a separate persistent volume.
• Public endpoint: A Sealos-managed ingress exposes GLPI over HTTPS with an automatically provisioned domain and certificate.

Configuration:

• Database credentials are generated by KubeBlocks and injected from its connection Secret.
• The database and GLPI schema are created automatically during the first startup.
• Before the Pod becomes Ready, the template replaces the seeded glpi password with the deployment input and disables the tech, normal, and post-only accounts.
• The application runs with one replica because the official image includes the cron worker and the /var/glpi volume uses ReadWriteOnce storage.
• Live Sealos validation established 100m CPU and 512Mi memory as the minimum stable GLPI application tier. The adjacent 256Mi tier reached an out-of-memory termination during authenticated dashboard traffic.
• GLPI community storage uses POSIX filesystem semantics, so this template keeps application files on the persistent volume.

License Information:

GLPI is licensed under the GNU General Public License v3.0.

Why Deploy GLPI on Sealos?

Sealos is a Kubernetes-based cloud operating system that manages application resources through a visual Canvas. This GLPI deployment provides:

• One-Click Deployment: Launch the complete GLPI and MySQL topology from one template.
• Managed Database Credentials: KubeBlocks creates MySQL credentials and wires them into GLPI automatically.
• Persistent Data: Dedicated volumes retain both GLPI files and database records across restarts.
• Instant HTTPS Access: Sealos creates a public domain, ingress, and TLS certificate.
• Efficient Resource Use: Validated resource limits and pay-as-you-go pricing keep the starting footprint small.
• Visual Operations: Use the Canvas, AI dialog, and resource cards to inspect or update the deployment.

Deployment Guide

1. Open the GLPI template and click Deploy Now.
2. Enter the initial Super-Admin password. Use a long, unique value; line breaks are rejected. Review the generated application name, domain, and resource plan, then start the deployment.
3. Wait for deployment to complete. The Canvas typically opens in 2-3 minutes; the initial MySQL provisioning and GLPI schema installation may take several additional minutes.
4. Open the URL shown on the GLPI application card. The root path / displays the login page when initialization is complete.

Initial Login and Account Setup

GLPI creates four upstream accounts during automatic installation. The readiness gate secures them before Sealos adds the Pod to the public Service endpoint:

Sign in at the root application URL with username glpi and the password entered during deployment. Migrate from the bootstrap account in this order:

1. Open Administration → Users and create the permanent administrator account.
2. Assign that user the Super-Admin profile for the Root entity, with recursive access when the account must manage child entities.
3. Open a separate private or incognito browser session, sign in as the new administrator, and verify access to Administration → Profiles and Setup.
4. Return to the original session and disable or remove the bootstrap glpi account. Keep the three other seeded accounts disabled or remove them.

Account onboarding remains administrator-managed from the Users page.

Configuration

After deployment, manage GLPI through:

• GLPI administration: Configure entities, profiles, authentication, notifications, inventory, and plugins in the web UI.
• AI dialog: Describe infrastructure changes in the Sealos Canvas and review the proposed update.
• Resource cards: Adjust CPU, memory, storage, environment variables, or network settings from the relevant Canvas card.
• Persistent files: Back up both the MySQL volume and /var/glpi to preserve a complete installation.

Scaling

The default topology intentionally keeps one GLPI replica. A multi-replica design requires ReadWriteMany storage for /var/glpi, GLPI_CRONTAB_ENABLED=0 on web replicas, one dedicated cron worker, and a controlled single-run database upgrade process. Keep these components coordinated when adapting the template for high availability.

Troubleshooting

The login page is still unavailable

Open the Sealos Canvas and verify that both the MySQL cluster and GLPI StatefulSet report Ready. First startup waits for MySQL, creates the glpi database, installs 400+ schema tables, starts Apache, rotates the bootstrap password, and disables the other seeded accounts before readiness succeeds.

GLPI reports database or filesystem problems

Check /status.php and confirm that both db.status and filesystem.status are OK. Review the GLPI and MySQL logs from their Canvas resource cards before changing configuration.

Getting Help

• GLPI documentation
• GLPI GitHub issues
• Sealos Discord

License

This Sealos template is provided under the templates repository license. GLPI is licensed under the GNU General Public License v3.0.