Skip to content

KEDA PR gate test - #1

Open
pvishwa3 wants to merge 1 commit into
mainfrom
keda-pr
Open

pvishwa3 wants to merge 1 commit into
mainfrom
keda-pr

Conversation

@pvishwa3

Copy link
Copy Markdown

Should fail with 13 KEDA findings.

@github-actions

Copy link
Copy Markdown

Deployment risk: HIGH (score 80) — 125 findings

Severity Rule Resource Title
MEDIUM wrs-rs-unset Deployment/no-requests No resource requests set — unpredictable scheduling, BestEffort eviction priority
MEDIUM wrs-spec-no-readiness Deployment/worker No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/no-requests No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/uses-vault-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/bounds-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/fallback-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/dup-triggers-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/to-zero-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/modifiers-app No readiness probe — traffic may hit unready pods
MEDIUM wrs-spec-no-readiness Deployment/schema-app No readiness probe — traffic may hit unready pods
LOW wrs-spec-no-liveness Deployment/worker No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/no-requests No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/uses-vault-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/bounds-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/fallback-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/dup-triggers-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/to-zero-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/modifiers-app No liveness probe — hung pods won't auto-restart
LOW wrs-spec-no-liveness Deployment/schema-app No liveness probe — hung pods won't auto-restart
LOW wrs-rs-nolimit Deployment/worker No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/no-requests No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/uses-vault-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/bounds-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/fallback-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/dup-triggers-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/to-zero-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/modifiers-app No CPU/memory limit — noisy-neighbour risk
LOW wrs-rs-nolimit Deployment/schema-app No CPU/memory limit — noisy-neighbour risk
LOW mrs-runasroot-unspecified Deployment/worker runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/no-requests runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/uses-vault-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/bounds-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/fallback-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/dup-triggers-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/to-zero-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/modifiers-app runAsNonRoot not set — container may run as root
LOW mrs-runasroot-unspecified Deployment/schema-app runAsNonRoot not set — container may run as root
LOW mrs-labels-missing-required Deployment/worker Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/no-requests Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/uses-vault-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/bounds-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/fallback-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/dup-triggers-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/to-zero-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/modifiers-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-labels-missing-required Deployment/schema-app Missing required labels (app.kubernetes.io/name or /version)
LOW mrs-allow-priv-esc-unset Deployment/worker allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/worker readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/worker seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/no-requests allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/no-requests readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/no-requests seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/uses-vault-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/uses-vault-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/uses-vault-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/bounds-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/bounds-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/bounds-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/fallback-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/fallback-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/fallback-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/dup-triggers-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/dup-triggers-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/dup-triggers-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/to-zero-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/to-zero-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/to-zero-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/modifiers-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/modifiers-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/modifiers-app seccompProfile not set — relies on cluster default
LOW mrs-allow-priv-esc-unset Deployment/schema-app allowPrivilegeEscalation not set — defaults can allow privilege escalation
LOW mrs-readonly-rootfs Deployment/schema-app readOnlyRootFilesystem not enabled — writable container root filesystem
LOW mrs-seccomp-unset Deployment/schema-app seccompProfile not set — relies on cluster default
MEDIUM mrs-diff-resource-removed ScaledObject/shop/legacy Resource removed from manifest
MEDIUM mrs-diff-resource-removed TriggerAuthentication/shop/vault-auth Resource removed from manifest
INFO mrs-diff-resource-added Deployment/shop/no-requests Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/uses-vault Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/a-scaledobject-name-that-is-far-too-long-for-a-kubernetes-label-value-x Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/bounds Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/fallback Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/dup-triggers Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/to-zero Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/no-request Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/modifiers Resource added to manifest
INFO mrs-diff-resource-added ScaledObject/shop/schema Resource added to manifest
INFO mrs-diff-resource-added TriggerAuthentication/shop/bad-vault Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/uses-vault-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/a-scaledobject-name-that-is-far-too-long-for-a-kub-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/bounds-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/fallback-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/dup-triggers-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/to-zero-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/modifiers-app Resource added to manifest
INFO mrs-diff-resource-added Deployment/shop/schema-app Resource added to manifest

Add-on findings · KEDA (13)

Severity Rule Resource Title
HIGH wrs-addon-keda-so-name-too-long ScaledObject/shop/a-scaledobject-name-that-is-far-too-long-for-a-kubernetes-label-value-x KEDA ScaledObject name is longer than 63 characters
HIGH wrs-addon-keda-hpa-name-too-long ScaledObject/shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx KEDA would derive an HPA name longer than 63 characters
HIGH wrs-addon-keda-replica-bounds-invalid ScaledObject/shop/bounds KEDA ScaledObject replica bounds are inconsistent
HIGH wrs-addon-keda-fallback-invalid ScaledObject/shop/fallback KEDA ScaledObject fallback cannot be used as written
HIGH wrs-addon-keda-triggers-invalid ScaledObject/shop/dup-triggers KEDA triggers are refused
HIGH wrs-addon-keda-cpu-memory-only-scale-to-zero ScaledObject/shop/to-zero KEDA cannot scale a cpu/memory-only ScaledObject to zero
HIGH wrs-addon-keda-cpu-memory-request-missing ScaledObject/shop/no-request KEDA cpu/memory trigger on a container without that request
HIGH wrs-addon-keda-scaling-modifiers-invalid ScaledObject/shop/modifiers KEDA scalingModifiers are refused
HIGH wrs-addon-keda-crd-schema-violation ScaledObject/shop/schema Object breaks the KEDA CRD schema
HIGH wrs-addon-keda-trigger-auth-invalid TriggerAuthentication/shop/bad-vault KEDA TriggerAuthentication is refused or cannot be used
MEDIUM wrs-addon-keda-scaledobject-removed ScaledObject/shop/legacy KEDA ScaledObject removed
MEDIUM wrs-addon-keda-paused ScaledObject/shop/worker KEDA autoscaling paused
HIGH wrs-addon-keda-deleted-auth-still-referenced TriggerAuthentication/shop/vault-auth KEDA authentication deleted while scalers still use it
What changed and how to fix it
  • wrs-rs-unset · Deployment/no-requests — Set CPU and memory requests on all containers to enable proper scheduling and QoS.
  • wrs-spec-no-readiness · Deployment/worker — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/no-requests — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/uses-vault-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/bounds-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/fallback-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/dup-triggers-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/to-zero-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/modifiers-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-readiness · Deployment/schema-app — Add a readinessProbe to ensure traffic is only sent to pods that are ready to serve requests.
  • wrs-spec-no-liveness · Deployment/worker — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/no-requests — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/uses-vault-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/bounds-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/fallback-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/dup-triggers-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/to-zero-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/modifiers-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-spec-no-liveness · Deployment/schema-app — Add a livenessProbe so Kubernetes can detect and restart stuck or deadlocked pods.
  • wrs-rs-nolimit · Deployment/worker — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/no-requests — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/uses-vault-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/bounds-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/fallback-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/dup-triggers-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/to-zero-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/modifiers-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • wrs-rs-nolimit · Deployment/schema-app — Set resource limits to prevent this workload from consuming excessive node resources.
  • mrs-runasroot-unspecified · Deployment/worker — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/no-requests — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/uses-vault-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/bounds-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/fallback-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/dup-triggers-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/to-zero-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/modifiers-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-runasroot-unspecified · Deployment/schema-app — No securityContext.runAsNonRoot:true is set; the container may run as root depending on the image. Set runAsNonRoot:true (and a non-zero runAsUser) to guarantee non-root.
  • mrs-labels-missing-required · Deployment/worker — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/no-requests — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/uses-vault-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/bounds-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/fallback-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/dup-triggers-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/to-zero-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/modifiers-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-labels-missing-required · Deployment/schema-app — Add app.kubernetes.io/name and app.kubernetes.io/version labels to the workload metadata. These labels are required for workload tracking and are used by observability, cost-allocation, and upgrade-intelligence tools.
  • mrs-allow-priv-esc-unset · Deployment/worker — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/worker — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/worker — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/no-requests — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/no-requests — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/no-requests — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/uses-vault-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/uses-vault-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/uses-vault-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/bounds-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/bounds-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/bounds-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/fallback-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/fallback-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/fallback-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/dup-triggers-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/dup-triggers-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/dup-triggers-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/to-zero-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/to-zero-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/to-zero-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/modifiers-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/modifiers-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/modifiers-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-allow-priv-esc-unset · Deployment/schema-app — Explicitly set securityContext.allowPrivilegeEscalation: false. When unset, the effective value can permit privilege escalation depending on other settings.
  • mrs-readonly-rootfs · Deployment/schema-app — Set securityContext.readOnlyRootFilesystem: true and mount writable paths as explicit emptyDir/volumes. A read-only root limits tampering and persistence after a compromise.
  • mrs-seccomp-unset · Deployment/schema-app — Set seccompProfile.type: RuntimeDefault at pod or container level so syscall filtering is explicit and not dependent on cluster defaults.
  • mrs-diff-resource-removed · ScaledObject/shop/legacy — ScaledObject shop/legacy was removed from the manifest. Verify this deletion is intentional.
    Fix: A resource present in the base manifest is absent in the head. Verify this deletion is intentional and that no other workloads depend on it.
  • mrs-diff-resource-removed · TriggerAuthentication/shop/vault-auth — TriggerAuthentication shop/vault-auth was removed from the manifest. Verify this deletion is intentional.
    Fix: A resource present in the base manifest is absent in the head. Verify this deletion is intentional and that no other workloads depend on it.
  • mrs-diff-resource-added · Deployment/shop/no-requests — Deployment shop/no-requests was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/uses-vault — ScaledObject shop/uses-vault was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/a-scaledobject-name-that-is-far-too-long-for-a-kubernetes-label-value-x — ScaledObject shop/a-scaledobject-name-that-is-far-too-long-for-a-kubernetes-label-value-x was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx — ScaledObject shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/bounds — ScaledObject shop/bounds was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/fallback — ScaledObject shop/fallback was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/dup-triggers — ScaledObject shop/dup-triggers was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/to-zero — ScaledObject shop/to-zero was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/no-request — ScaledObject shop/no-request was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/modifiers — ScaledObject shop/modifiers was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · ScaledObject/shop/schema — ScaledObject shop/schema was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · TriggerAuthentication/shop/bad-vault — TriggerAuthentication shop/bad-vault was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/uses-vault-app — Deployment shop/uses-vault-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/a-scaledobject-name-that-is-far-too-long-for-a-kub-app — Deployment shop/a-scaledobject-name-that-is-far-too-long-for-a-kub-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app — Deployment shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/bounds-app — Deployment shop/bounds-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/fallback-app — Deployment shop/fallback-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/dup-triggers-app — Deployment shop/dup-triggers-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/to-zero-app — Deployment shop/to-zero-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/modifiers-app — Deployment shop/modifiers-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • mrs-diff-resource-added · Deployment/shop/schema-app — Deployment shop/schema-app was added to the manifest.
    Fix: A new resource is present in the head manifest that was not in the base. Informational: verify the addition is intentional.
  • wrs-addon-keda-so-name-too-long · ScaledObject/shop/a-scaledobject-name-that-is-far-too-long-for-a-kubernetes-label-value-x — ScaledObject shop/a-scaledobject-name-that-is-far-too-long-for-a-kubernetes-label-value-x: the name is 71 characters; KEDA writes it as the scaledobject.keda.sh/name label value, which allows 63. KEDA added this check in 2.20; the installed KEDA version could not be read, so it is reported as if the cluster runs 2.20+.
    Fix: Shorten the ScaledObject name to 63 characters or fewer: KEDA writes it as the scaledobject.keda.sh/name label value. KEDA's admission webhook refuses the apply; with the webhook switched off it applies and the ScaledObject goes Ready=False, so the workload does not autoscale either way.
  • wrs-addon-keda-hpa-name-too-long · ScaledObject/shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx — ScaledObject shop/hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: the HPA name KEDA derives, keda-hpa-hpa-name-check-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, is 66 characters (63 allowed) and spec.advanced.horizontalPodAutoscalerConfig.name is not set. KEDA added this check in 2.20; the installed KEDA version could not be read, so it is reported as if the cluster runs 2.20+.
    Fix: Set spec.advanced.horizontalPodAutoscalerConfig.name to a name of 63 characters or fewer, or shorten the ScaledObject name (keda-hpa- plus the name must fit in 63). KEDA's admission webhook refuses the apply; with the webhook switched off it applies and no HPA can be created.
  • wrs-addon-keda-replica-bounds-invalid · ScaledObject/shop/bounds — ScaledObject shop/bounds: minReplicaCount (5) is above maxReplicaCount (2).
    Fix: Make minReplicaCount at most maxReplicaCount (an unset max is 100; a min of 0 counts as 1 here) and idleReplicaCount lower than minReplicaCount. KEDA's admission webhook refuses the apply; with the webhook switched off the HPA is never created and the workload does not autoscale.
  • wrs-addon-keda-fallback-invalid · ScaledObject/shop/fallback — ScaledObject shop/fallback: a fallback is set but every trigger is cpu or memory; KEDA needs at least one other trigger (or scalingModifiers) to fall back from.
    Fix: Keep fallback.failureThreshold and fallback.replicas at 0 or above, and give the ScaledObject at least one trigger that is not cpu or memory (or use scalingModifiers): KEDA has no fallback metric for cpu/memory. KEDA's admission webhook refuses the apply; with the webhook switched off the fallback never engages.
  • wrs-addon-keda-triggers-invalid · ScaledObject/shop/dup-triggers — ScaledObject shop/dup-triggers: trigger name "same" is used more than once; it must be unique.
    Fix: Declare at least one trigger, drop useCachedMetrics from cpu, memory and cron triggers, and give every named trigger a unique name. KEDA's admission webhook refuses the apply; with the webhook switched off the object goes Ready=False.
  • wrs-addon-keda-cpu-memory-only-scale-to-zero · ScaledObject/shop/to-zero — ScaledObject shop/to-zero: every trigger is cpu or memory and minReplicaCount is unset (KEDA reads it as 0); a resource metric cannot wake a workload with no pods.
    Fix: Set minReplicaCount to 1 or more (an unset minReplicaCount counts as 0 here), or add a trigger that is not cpu or memory: a resource metric cannot wake a workload that has no pods. KEDA's admission webhook refuses the apply; with the webhook switched off it applies, but a cpu/memory scaler is always active, so the workload never scales to zero and minReplicaCount 0 does nothing.
  • wrs-addon-keda-cpu-memory-request-missing · ScaledObject/shop/no-request — ScaledObject shop/no-request: the cpu trigger reads Deployment no-requests, whose container app set no cpu request (and no LimitRange default could be checked from here).
    Fix: Set resources.requests for the resource on the container the trigger reads (every container unless the trigger names containerName), or a pod-level request, or a LimitRange default in the namespace. KEDA's admission webhook refuses the apply (but skips this check on kubectl apply --dry-run=server, so a server dry-run passes); with the webhook switched off the HPA cannot compute utilization and never scales.
  • wrs-addon-keda-scaling-modifiers-invalid · ScaledObject/shop/modifiers — ScaledObject shop/modifiers: scalingModifiers is set but its formula is empty.
    Fix: Give scalingModifiers a formula whenever it has a target or the fallback uses behavior scalingModifiers, make the target a positive number, and use metricType AverageValue or Value (never Utilization). KEDA's admission webhook refuses the apply; with the webhook switched off the ScaledObject goes Ready=False.
  • wrs-addon-keda-crd-schema-violation · ScaledObject/shop/schema — ScaledObject shop/schema: the KEDA 2.20+ CRD refuses pollingInterval 0 (minimum 1). KEDA added this check in 2.20; the installed KEDA version could not be read, so it is reported as if the cluster runs 2.20+.
    Fix: Bring the field inside the bound or enum the KEDA 2.20+ CRD declares (maxReplicaCount and pollingInterval at least 1, the other counts at least 0, a non-empty trigger type and target name, the listed enum values). The API server refuses the apply whether or not KEDA's webhook runs; Kubernetes 1.30+ tolerates an unchanged invalid field on update, so the refusal hits a re-create or an edit of that field.
  • wrs-addon-keda-trigger-auth-invalid · TriggerAuthentication/shop/bad-vault — TriggerAuthentication shop/bad-vault: hashiCorpVault.authentication "aws" is not supported (token or kubernetes). It applies, but every scaler that uses it fails to build and its object goes Ready=False.
    Fix: Fix the field the finding names. Admission refusals (podIdentity identity fields, oauth2, azureServicePrincipal) stop the apply when KEDA's webhook runs; build-time errors (filePath, boundServiceAccountToken without serviceAccountName, an unsupported Vault method or AWS Secrets Manager identity) let it apply and fail every scaler that uses it.
  • wrs-addon-keda-scaledobject-removed · ScaledObject/shop/legacy — ScaledObject shop/legacy: Deployment worker stops autoscaling: KEDA deletes its HPA and the workload stays at the replica count it has at that moment.
    Fix: Confirm the workload should stop autoscaling: without its ScaledObject KEDA deletes the HPA and the workload stays at its current replica count (or the pre-KEDA count when advanced.restoreToOriginalReplicaCount is true) until someone scales it.
  • wrs-addon-keda-paused · ScaledObject/shop/worker — ScaledObject shop/worker: autoscaling.keda.sh/paused: "true" freezes the replica count.
    Fix: Confirm the pause is intended and temporary: autoscaling.keda.sh/paused freezes the replica count where it is (paused-replicas pins it to a number, paused-scale-in / paused-scale-out freeze one direction). Remove the annotation to resume.
  • wrs-addon-keda-deleted-auth-still-referenced · TriggerAuthentication/shop/vault-auth — TriggerAuthentication shop/vault-auth: deleted, but 1 object(s) still use it: ScaledObject shop/uses-vault.
    Fix: Keep the TriggerAuthentication / ClusterTriggerAuthentication until no ScaledObject or ScaledJob references it, or repoint those triggers in the same change. Without it KEDA builds every scaler that references it without its authentication parameters, so a scaler that needs credentials or a host from it fails.

Cluster-aware checks: off — not connected to runtimez. Set runtimez-url, api-key, org-id and cluster-id to add capacity fit, add-on and telemetry checks against the target cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant