#
Applications Catalog
Phoeniqs runs a set of applications and operators cluster-wide on our shared clusters, so you can use them directly from your tenant namespace without installing anything yourself. This page is the authoritative catalog of what is available on the shared clusters, what we manage for you, what is planned, and how to consume each item.
If an application you need is not on this list, you can request it from the platform team or, if you need full flexibility, provision a Hosted Cluster where you manage operators yourself.
#
How consumption works on the shared clusters
Tenant namespaces are isolated and managed by policy. You cannot install operators yourself: OLM installs (OperatorGroup, Subscription, CatalogSource, InstallPlan) are rejected in tenant namespaces, and you cannot create cluster-scoped objects (CRDs, ClusterRoles, ClusterRoleBindings). Instead, you use the operators we run cluster-wide by creating their custom resources in your own namespace. The namespace admin role already has the permissions for them.
#
Available, self-serve in your tenant namespace
The following applications/operators are available on the shared clusters. For each, create the corresponding custom resource in your namespace (see the "How" column). Cluster availability is noted per item.
#
Platform-internal, not for client namespaces
The following components are managed by Phoeniqs for platform operations and are not for use in your tenant namespaces:
MetalLB, ExternalDNS (the multi-tenant instance watches only the multi-tenant namespace), OpenShift GitOps (Argo CD), Kyverno, Zabbix, Node Feature Discovery, ODF/NooBaa (NooBaa StorageClass is blocked by policy), ACM/MCE (HyperShift), MTV, OADP, etcd backup, and Flux.
Clients do GitOps through their tenant repository (Flux), not Argo CD.
Not offered: MinIO
MinIO is not part of the catalog. For object storage use S3 object storage (Ceph RGW) listed above.
#
Planned / in progress
#
Consumption model
- Operator we provide → self-serve: create the custom resources in your namespace.
- Operator we don't provide → ask the platform team. We evaluate a cluster-wide install; CRDs are shared, so there is one version per cluster for everyone.
- Your own or custom operators, a specific operator version, or cluster-admin → Hosted Cluster. See Hosted Cluster.
#
Related Pages
- Hosted Cluster
- OpenShift Architecture Overview
- Namespaces, Quotas and RBAC
- GPU Infrastructure
- Resource Pricing