No completed application-specific software result is published

Firefox

Ptyxis

Bazaar

Podman Desktop

VS Code / Codium

Bazzite Shell

Flatcar

behave tests/developer/features/ptyxis.feature

View on GitHub

Architectures

License

Flatpak SDK Runtime

Sandbox Permissions

file-access:downloads

flatpak install flathub

Fallback

GitOps Applications

Updated Aug 19, 2026, 19:41 UTCSource: live ArgoCD control-plane APISnapshot: fallbackRaw dataset ↗
Managed Applications
6
6 synced · 0 out of sync
Application Health
6 Healthy
6 Healthy · 0 degraded/other
Policy Pass Rate
79.8%
155 git manifests checked
Managed Resources
9 Pods
0.83 cores · 2.85 GiB RAM

Visualized analytics

Resource Consumption

Memory Allocations vs Requests

Active workload memory allocations mapped relative to configured requests.

Policy Scorecard

Compliance Check Pass Rates

Registry allowlist and storage rules validated across namespaces.

GitOps workload deployment status

arc-runners

argo
Active Pods
0
CPU cores
0.01 / unlimited
Memory RAM
45 MiB
SyncedHealthy
Revision: main
Namespace: argo

arc-systems

argo
Active Pods
2
CPU cores
0.15 / 0.3
Memory RAM
128 MiB
SyncedHealthy
Revision: main
Namespace: argo

argo-workflows

argo
Active Pods
3
CPU cores
0.22 / 0.44
Memory RAM
350 MiB
SyncedHealthy
Revision: main
Namespace: argo

flatcar-update

argo
Active Pods
0
CPU cores
0 / unlimited
Memory RAM
0 MiB
SyncedHealthy
Revision: main
Namespace: argo

testing-lab

argo
Active Pods
0
CPU cores
0 / unlimited
Memory RAM
0 MiB
SyncedHealthy
Revision: main
Namespace: argo

testing-lab-infra

manifests
Active Pods
4
CPU cores
0.45 / 0.9
Memory RAM
2400 MiB
SyncedHealthy
Revision: main
Namespace: argo

Rollout History (Recent Syncs)

No sync rollout history recorded.

Policy Scorecard & Violations

Git Manifest Registry Allowlist

Violation

All container images in git-tracked manifests must reside on allowed registries.

Passed: 153 / 160 checked
[manifests/k3s-upgrade-plans.yaml]: Banned registry for image 'rancher/k3s-upgrade'
[manifests/k3s-upgrade-plans.yaml]: Banned registry for image 'rancher/k3s-upgrade'
[manifests/k3s-upgrade-plans.yaml]: Banned registry for image 'rancher/k3s-upgrade'
[manifests/system-upgrade-controller.yaml]: Banned registry for image 'rancher/system-upgrade-controller:v0.19.2'
+ 3 more violations

Live Cluster Registry Allowlist

Compliant

All running container images in the cluster must reside on allowed registries.

Passed: 0 / 0 checked

No Root Disk Storage Allocations

Violation

No hard hostPath volume mounts on root disks (must use PVCs or approved storage).

Passed: 8 / 32 checked
[manifests/amdgpu-device-plugin.yaml]: Potentially unauthorized hostPath allocation on root disk: '/var/lib/kubelet/device-plugins'
[manifests/amdgpu-device-plugin.yaml]: Potentially unauthorized hostPath allocation on root disk: '/dev'
[manifests/amdgpu-device-plugin.yaml]: Potentially unauthorized hostPath allocation on root disk: '/sys'
[manifests/registry-mirror-config.yaml]: Potentially unauthorized hostPath allocation on root disk: '/var/lib/rancher/k3s/agent/etc/containerd/certs.d'
+ 20 more violations

No Hard Node Selectors in Git

Violation

Workloads must not use hard nodeName or hostname nodeSelectors to bypass scheduler placement.

Passed: 9 / 21 checked
[manifests/pr-image-gc.yaml]: Hard node hostname selector pin found: 'kubernetes.io/hostname: ghost'
[manifests/orphan-vm-cleanup.yaml]: Hard node hostname selector pin found: 'kubernetes.io/hostname: ghost'
[manifests/golden-disk-gc.yaml]: Hard node hostname selector pin found: 'kubernetes.io/hostname: ghost'
[manifests/orphan-pod-gc.yaml]: Hard node hostname selector pin found: 'kubernetes.io/hostname: ghost'
+ 8 more violations

No Hard Node Selectors in Cluster

Compliant

No active pods with hard node selector pinning (excluding approved infrastructure controllers).

Passed: 0 / 0 checked

Data Insights & Raw Telemetry

Direct links to the structured JSON contracts powering this GitOps Applications dashboard for active auditing and inspection.