---
title: Charmhub | Deploy Indico using Charmhub - The Open Operator Collection
description: Deploy the latest version of Indico as a Kubernetes Operator on any cloud.
url: https://charmhub.io/indico/docs/reference-integrations
---

# Indico

[Canonical IS DevOps](https://charmhub.io/publisher/canonical-is-devops "View all packages from Canonical IS DevOps")

* [Canonical IS DevOps](https://charmhub.io/publisher/canonical-is-devops "View all packages from Canonical IS DevOps")

Platform:

stable 330

```
juju deploy indico
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Contacts

##### Maintainers

+ [Launchpad Team](https://launchpad.net/~canonical-is-devops)

* [Submit a bug](https://github.com/canonical/indico-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

# Integrations

An overview of the different relation endpoints.

### [`db`](https://charmhub.io/indico/docs/reference-integrations#p-23187-db)

*Interface*: pgsql
*Supported charms*: [`postgresql-k8s`](https://charmhub.io/postgresql-k8s), [`postgresql`](https://charmhub.io/postgresql)

Database integration is a required relation for the Indico charm to supply structured data
storage for Indico.

Example `db` integrate command:

```
juju integrate indico postgresql-k8s:db
```

### [`redis`](https://charmhub.io/indico/docs/reference-integrations#p-23187-redis)

*Interface*: redis
*Supported charms*: [redis-k8s](https://charmhub.io/redis-k8s)

Redis integration is a required relation for the Indico charm to supply caching capabilities and
a message broker to interface with Celery. As such, two instances are needed, `redis-cache` and
`redis-broker`.

Example `redis` integrate commands:

```
juju integrate redis-cache indico
juju integrate redis-broker indico
```

### [`ingress`](https://charmhub.io/indico/docs/reference-integrations#p-23187-ingress)

*Interface*: ingress
*Supported charms*: [nginx-ingress-integrator](https://charmhub.io/nginx-ingress-integrator)

Ingress manages external HTTP/HTTPS access to services in a Kubernetes cluster.
Ingress relation through [nginx-ingress-integrator](https://charmhub.io/nginx-ingress-integrator)
charm enables additional `blog_hostname` and `use_nginx_ingress_modesec` configurations. Note that the
Kubernetes cluster must already have an nginx ingress controller already deployed. Documentation to
enable ingress in MicroK8s can be found [here](https://microk8s.io/docs/addon-ingress).

Example `ingress` integrate command:

```
juju integrate indico nginx-ingress-integrator
```

### [`metrics-endpoint`](https://charmhub.io/indico/docs/reference-integrations#p-23187-metrics-endpoint)

*Interface*: [prometheus\_scrape](https://charmhub.io/interfaces/prometheus_scrape)
*Supported charms*: [prometheus-k8s](https://charmhub.io/prometheus-k8s)

Metrics-endpoint relation allows scraping the `/metrics` endpoint provided by apache-exporter sidecar
on port 9117, which provides apache metrics from apache’s `/server-status` route. This internal
apache’s `/server-status` route is not exposed and can only be accessed from within the same
Kubernetes pod. The metrics are exposed in the [open metrics format](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#data-model) and will only be scraped by Prometheus once the relation becomes active. For more
information about the metrics exposed, please refer to the apache-exporter [documentation](https://github.com/Lusitaniae/apache_exporter#collectors).

Example `metrics-endpoint` integrate command:

```
juju integrate indico prometheus-k8s
```

### [`grafana-dashboard`](https://charmhub.io/indico/docs/reference-integrations#p-23187-grafana-dashboard)

*Interface*: grafana-dashboard
*Supported charms*: [grafana-k8s](https://charmhub.io/grafana-k8s)

Grafana-dashboard relation enables quick dashboard access already tailored to fit the needs of
operators to monitor the charm. The template for the Grafana dashboard for indico charm can
be found at `/src/grafana_dashboards/indico.json`. In Grafana UI, it can be found as “Indico
Operator Overview” under the General section of the dashboard browser (`/dashboards`). Modifications
to the dashboard can be made but will not be persisted upon restart/redeployment of the charm.

Example Grafana-Prometheus integrate command:

```
juju integrate grafana-k8s:grafana-source prometheus-k8s:grafana-source
```

Grafana-dashboard integrate command:

```
juju integrate indico grafana-dashboard
```

See more information in [Charm Architecture](https://charmhub.io/indico/docs/explanation-charm-architecture).

---