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
FallbackManaged 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
GitOps workload deployment status
Active Pods0CPU cores0.01 / unlimitedMemory RAM45 MiB SyncedHealthy
Revision: main
Namespace: argo
Active Pods2CPU cores0.15 / 0.3Memory RAM128 MiB SyncedHealthy
Revision: main
Namespace: argo
Active Pods3CPU cores0.22 / 0.44Memory RAM350 MiB SyncedHealthy
Revision: main
Namespace: argo
Active Pods0CPU cores0 / unlimitedMemory RAM0 MiB SyncedHealthy
Revision: main
Namespace: argo
Active Pods0CPU cores0 / unlimitedMemory RAM0 MiB SyncedHealthy
Revision: main
Namespace: argo
testing-lab-infra
manifests
Active Pods4CPU cores0.45 / 0.9Memory RAM2400 MiB SyncedHealthy
Revision: main
Namespace: argo
Rollout History (Recent Syncs)
No sync rollout history recorded.
Policy Scorecard & Violations
Git Manifest Registry Allowlist
ViolationAll 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
CompliantAll running container images in the cluster must reside on allowed registries.
Passed: 0 / 0 checked
No Root Disk Storage Allocations
ViolationNo 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
ViolationWorkloads 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
CompliantNo 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.
Sync Status Data
Resource Metrics Data
Compliance Scorecard Data
Rollout History Data