# Flux Status

Sunrise clusters run [Flux Operator](https://fluxoperator.dev), a GitOps engine that continuously reconciles your workloads from a Git source. The **Flux Status** web UI gives you real-time visibility into what is running, what is failing, and why.

---

## Access

Each cluster has its own Flux Status URL:

| Cluster | URL |
|---|---|
| Basel | [flux.basel.phoeniqs.com](https://flux.basel.phoeniqs.com) |
| AI-3 | [flux.ai-3.phoeniqs.com](https://flux.ai-3.phoeniqs.com) |

Log in with your Sunrise SSO credentials. You will only see namespaces your account has been granted access to.

---

## What you can do

### Check for failures fast

The quickest way to spot a broken deployment is to filter by failed status directly:

`https://flux.basel.phoeniqs.com/resources?status=Failed`

Replace the hostname with the Flux Status URL for your cluster (see table above). For AI-3:

`https://flux.ai-3.phoeniqs.com/resources?status=Failed`

This shows every GitOps resource in your namespace that Flux is unable to reconcile, with the error message attached.

### Browse live events

The events view shows the reconciliation activity stream for your resources in real time:

`https://flux.basel.phoeniqs.com/events`

Useful for watching a deployment roll out or confirming that a Git commit has been picked up.

### Inspect a specific resource

From the main dashboard, you can drill into any Kustomization or HelmRelease to see its current revision, applied values, and condition history. You can also trigger a manual reconcile, or suspend and resume a resource, subject to your RBAC permissions.

---

## Concepts

| Term | What it means in practice |
|---|---|
| **Kustomization** | A set of Kubernetes manifests applied from a Git path |
| **HelmRelease** | A Helm chart managed and kept in sync by Flux |
| **Reconciliation** | The process of comparing Git state with cluster state and applying the diff |
| **Suspended** | A resource paused from reconciliation; changes in Git are ignored until resumed |

---

## Troubleshooting

If a resource shows as **Failed**:

1. Open the resource detail and read the error message under Conditions.
2. Check the Events view for the sequence of attempts.
3. Fix the source in Git (manifests, values, or chart version).
4. Flux will pick up the change automatically on the next reconciliation interval, or you can trigger one manually from the UI.

If you cannot see your namespace in the UI, contact your cluster administrator to verify your RBAC role assignment.

---

## Further reading

Full documentation for the Flux Status web UI is maintained by the upstream project:

- [Web UI overview](https://fluxoperator.dev/web-ui/)
- [User actions (reconcile, suspend, resume)](https://fluxoperator.dev/docs/web-ui/user-actions/)
- [User management and RBAC](https://fluxoperator.dev/docs/web-ui/user-management/)
- [ResourceSet templating (advanced)](https://fluxoperator.dev/docs/crd/resourceset/)

---

## Related pages

- [How Sunrise Cloud Works](./getting-started/how-it-works.md), Resource Groups, Capacity Pools, and Namespaces.
- [Access Your OpenShift](./getting-started/access-your-openshift.md), Log in to OpenShift and manage workloads in your project.
- [System Status](./iaas-status.md), Platform-wide availability and incidents.