Verify the SeekrFlow deployment

Check that SeekrFlow came up healthy before you finish setup. Services can take several minutes to start, and model servers longer, while they download model weights.

Check the deployment

With the sfe CLI
Without the sfe CLI

Check the resources

sfe resources status -p <profile-name>

The command lists every SeekrFlow resource and its phase.

Compare the deployment with your values file

sfe verify -p <profile-name> -r <version>

The command reports any difference between what you configured and what’s running.

Check the pods

kubectl get pods -n seekrflow

Every pod should reach Running, with all its containers ready.

Check the services

kubectl get flowservices -n seekrflow

The list shows the services the operator created and manages.

Create the DNS record

If SeekrFlow creates its own ingress on Amazon Web Services (AWS), create the Domain Name System (DNS) record for your hostname now. The load balancer exists only after install. Create the record before you sign in or set up single sign-on, because both use the hostname. See Create the DNS record.

If pods aren’t running

Check the License service first. Other services wait for it. A missing or invalid license key shows up as many stuck pods rather than one clear failure.

With the sfe CLI
Without the sfe CLI

sfe resources describe <kind>/<name>
sfe resources logs <kind>/<name>

SeekrFlow’s images have no shell. To investigate inside a pod, attach a debug container:

sfe resources debug <kind>/<name>

kubectl describe pod <pod-name> -n seekrflow
kubectl logs <pod-name> -n seekrflow

The Events section at the end of the describe output usually names the problem.

Symptom	Cause
`ImagePullBackOff`	The image pull secret is missing. Check that it exists in both the `seekrflow` and `argo-workflows` namespaces.
`CreateContainerConfigError`	A secret is missing. The pod’s events name it.
Most pods stuck, none obviously failing	The license key. Check the `seekrflow-license` secret first.
The ingress has no address, and its events say `no certificate found for host`	The load balancer has no certificate for your hostname. In AWS Certificate Manager, check that the certificate is issued and covers the `global.ingress.host` value.

For more symptoms, see Troubleshoot a deployment.

SeekrFlow Self-Managed

Plan a SeekrFlow deployment

Provision SeekrFlow dependencies

Prepare to install SeekrFlow

Deploy SeekrFlow

Operate SeekrFlow

Reference

Check the deployment

Create the DNS record

If pods aren’t running

​Check the deployment

​Create the DNS record

​If pods aren’t running

Check the deployment

Create the DNS record

If pods aren’t running