Kubernetes website and documentation repo:
This report summarizes scanner evidence for kubernetes/website, a HTML project with 5,417 GitHub stars. SynthScan examined 1,517,251 lines of code across 10726 source files, recording 437 pattern matches distributed across 16 syntactic categories. The legacy adjusted pattern signal is 0.8 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 262 finding(s).
Are imports declared and package/API names verified? 81 finding(s).
Are wrappers, guards, and repeated structures necessary? 104 finding(s).
Which changes need focused human review? 437 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 437 distinct pattern matches across 16 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 102 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.runAsNonRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 104 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.readOnlyRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 106 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.allowPrivi | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 108 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.Privileged | CODE |
| CRITICAL | …og/_posts/2024/validating-admission-policy-ga/index.md | 128 | | object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.Privileged) | | CODE |
| CRITICAL | …og/_posts/2024/validating-admission-policy-ga/index.md | 131 | | object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.Privileged) | | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 161 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.runAsNonRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 163 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.readOnlyRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 165 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.allowPrivi | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 167 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.privileged | CODE |
| CRITICAL | …/2023/kubescape-validating-admission-policy-library.md | 174 | - expression: "['Deployment','ReplicaSet','DaemonSet','StatefulSet','Job'].all(kind, object.kind != kind) || object. | CODE |
| CRITICAL | …/2023/kubescape-validating-admission-policy-library.md | 176 | - expression: "object.kind != 'CronJob' || object.spec.jobTemplate.spec.template.spec.containers.all(container, has( | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 70 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.runAsNonRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 72 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.readOnlyRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 74 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.allowPrivi | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 76 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.Privileged | CODE |
| CRITICAL | …og/_posts/2024/validating-admission-policy-ga/index.md | 90 | | object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.Privileged) | | CODE |
| CRITICAL | …og/_posts/2024/validating-admission-policy-ga/index.md | 93 | | object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.Privileged) | | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 116 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.runAsNonRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 118 | - expression: object.spec.template.spec.containers.all(c, has(c.securityContext) && has(c.securityContext.readOnlyRoot | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 120 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.allowPrivi | CODE |
| CRITICAL⚡ | …og/_posts/2024/validating-admission-policy-ga/index.md | 122 | - expression: object.spec.template.spec.containers.all(c, !has(c.securityContext) || !has(c.securityContext.privileged | CODE |
| CRITICAL | …/2023/kubescape-validating-admission-policy-library.md | 101 | - expression: "['Deployment','ReplicaSet','DaemonSet','StatefulSet','Job'].all(kind, object.kind != kind) || object. | CODE |
| CRITICAL | …/2023/kubescape-validating-admission-policy-library.md | 103 | - expression: "object.kind != 'CronJob' || object.spec.jobTemplate.spec.template.spec.containers.all(container, has( | CODE |
| CRITICAL | static/js/jquery-3.6.0.min.js | 2 | !function(e,t){"use strict";"object"==typeof module&&"object"==typeof module.exports?module.exports=e.document?t(e,!0):f | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | simple finite work queue with redis backend this work queue is finite: as long as no more work is added after workers st | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | simple finite work queue with redis backend this work queue is finite: as long as no more work is added after workers st | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | simple finite work queue with redis backend this work queue is finite: as long as no more work is added after workers st | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | simple finite work queue with redis backend this work queue is finite: as long as no more work is added after workers st | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | simple finite work queue with redis backend this work queue is finite: as long as no more work is added after workers st | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | simple finite work queue with redis backend this work queue is finite: as long as no more work is added after workers st | STRING |
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | the default connection parameters are: host='localhost', port=6379, db=0 the work queue is identified by "name". the lib | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | the default connection parameters are: host='localhost', port=6379, db=0 the work queue is identified by "name". the lib | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | the default connection parameters are: host='localhost', port=6379, db=0 the work queue is identified by "name". the lib | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | the default connection parameters are: host='localhost', port=6379, db=0 the work queue is identified by "name". the lib | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | the default connection parameters are: host='localhost', port=6379, db=0 the work queue is identified by "name". the lib | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | the default connection parameters are: host='localhost', port=6379, db=0 the work queue is identified by "name". the lib | STRING |
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | return true if the queue is empty, including work being done, false otherwise. false does not necessarily mean that ther | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | return true if the queue is empty, including work being done, false otherwise. false does not necessarily mean that ther | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | return true if the queue is empty, including work being done, false otherwise. false does not necessarily mean that ther | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | return true if the queue is empty, including work being done, false otherwise. false does not necessarily mean that ther | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | return true if the queue is empty, including work being done, false otherwise. false does not necessarily mean that ther | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | return true if the queue is empty, including work being done, false otherwise. false does not necessarily mean that ther | STRING |
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | return to the work queuereturn true if the queue is empty, false otherwise. | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | return to the work queuereturn true if the queue is empty, false otherwise. | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | return to the work queuereturn true if the queue is empty, false otherwise. | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | return to the work queuereturn true if the queue is empty, false otherwise. | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | return to the work queuereturn true if the queue is empty, false otherwise. | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | return to the work queuereturn true if the queue is empty, false otherwise. | STRING |
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | returns a string that uniquely identifies an item (bytes). | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | returns a string that uniquely identifies an item (bytes). | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | returns a string that uniquely identifies an item (bytes). | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | returns a string that uniquely identifies an item (bytes). | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | returns a string that uniquely identifies an item (bytes). | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | returns a string that uniquely identifies an item (bytes). | STRING |
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | begin working on an item the work queue. lease the item for lease_secs. after that time, other workers may consider this | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | begin working on an item the work queue. lease the item for lease_secs. after that time, other workers may consider this | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | begin working on an item the work queue. lease the item for lease_secs. after that time, other workers may consider this | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | begin working on an item the work queue. lease the item for lease_secs. after that time, other workers may consider this | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | begin working on an item the work queue. lease the item for lease_secs. after that time, other workers may consider this | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | begin working on an item the work queue. lease the item for lease_secs. after that time, other workers may consider this | STRING |
| HIGH | content/ja/examples/application/job/redis/rediswq.py | 0 | complete working on the item with 'value'. if the lease expired, the item may not have completed, and some other worker | STRING |
| HIGH | content/ru/examples/application/job/redis/rediswq.py | 0 | complete working on the item with 'value'. if the lease expired, the item may not have completed, and some other worker | STRING |
| HIGH | content/zh-cn/examples/application/job/redis/rediswq.py | 0 | complete working on the item with 'value'. if the lease expired, the item may not have completed, and some other worker | STRING |
| HIGH | content/bn/examples/application/job/redis/rediswq.py | 0 | complete working on the item with 'value'. if the lease expired, the item may not have completed, and some other worker | STRING |
| HIGH | content/hi/examples/application/job/redis/rediswq.py | 0 | complete working on the item with 'value'. if the lease expired, the item may not have completed, and some other worker | STRING |
| HIGH | content/en/examples/application/job/redis/rediswq.py | 0 | complete working on the item with 'value'. if the lease expired, the item may not have completed, and some other worker | STRING |
| HIGH | i18n/pl/pl.toml | 0 | the linux foundation ®. all rights reserved. the linux foundation has registered trademarks and uses trademarks. for | STRING |
| HIGH | i18n/ja/ja.toml | 0 | the linux foundation ®. all rights reserved. the linux foundation has registered trademarks and uses trademarks. for | STRING |
| HIGH | i18n/de/de.toml | 0 | the linux foundation ®. all rights reserved. the linux foundation has registered trademarks and uses trademarks. for | STRING |
| HIGH | i18n/ko/ko.toml | 0 | the linux foundation ®. all rights reserved. the linux foundation has registered trademarks and uses trademarks. for | STRING |
| HIGH | i18n/fr/fr.toml | 0 | the linux foundation ®. all rights reserved. the linux foundation has registered trademarks and uses trademarks. for | STRING |
| HIGH | i18n/ja/ja.toml | 0 | the kubernetes authors | documentation distributed under <a href="https://git.k8s.io/website/license" class="light-text" | STRING |
| HIGH | i18n/de/de.toml | 0 | the kubernetes authors | documentation distributed under <a href="https://git.k8s.io/website/license" class="light-text" | STRING |
| HIGH | i18n/ko/ko.toml | 0 | the kubernetes authors | documentation distributed under <a href="https://git.k8s.io/website/license" class="light-text" | STRING |
| HIGH | i18n/fr/fr.toml | 0 | the kubernetes authors | documentation distributed under <a href="https://git.k8s.io/website/license" class="light-text" | STRING |
| HIGH | i18n/en/en.toml | 0 | the kubernetes authors | documentation distributed under <a href="https://git.k8s.io/website/license" class="light-text" | STRING |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM⚡ | …nt/ru/docs/concepts/workloads/controllers/cron-jobs.md | 47 | # ┌───────────── минута (0 - 59) | COMMENT |
| MEDIUM⚡ | …nt/ru/docs/concepts/workloads/controllers/cron-jobs.md | 48 | # │ ┌───────────── час (0 - 23) | COMMENT |
| MEDIUM⚡ | …nt/ru/docs/concepts/workloads/controllers/cron-jobs.md | 49 | # │ │ ┌───────────── день месяца (1 - 31) | COMMENT |
| MEDIUM⚡ | …nt/ru/docs/concepts/workloads/controllers/cron-jobs.md | 50 | # │ │ │ ┌───────────── месяц (1 - 12) | COMMENT |
| MEDIUM⚡ | …nt/ru/docs/concepts/workloads/controllers/cron-jobs.md | 51 | # │ │ │ │ ┌───────────── день недели (0 - 6) (воскресенье - суббота) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 108 | # ┌───────────── minute (0 - 59) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 109 | # │ ┌───────────── hour (0 - 23) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 110 | # │ │ ┌───────────── day of the month (1 - 31) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 111 | # │ │ │ ┌───────────── month (1 - 12) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 112 | # │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 120 | # ┌───────────── 分钟 (0 - 59) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 121 | # │ ┌───────────── 小时 (0 - 23) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 122 | # │ │ ┌───────────── 月的某天 (1 - 31) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 123 | # │ │ │ ┌───────────── 月份 (1 - 12) | COMMENT |
| MEDIUM⚡ | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 124 | # │ │ │ │ ┌───────────── 周的某天 (0 - 6)(周日到周六) | COMMENT |
| MEDIUM⚡ | …pt-br/docs/concepts/workloads/controllers/cron-jobs.md | 49 | # ┌───────────── minuto (0 - 59) | COMMENT |
| MEDIUM⚡ | …pt-br/docs/concepts/workloads/controllers/cron-jobs.md | 50 | # │ ┌───────────── hora (0 - 23) | COMMENT |
| MEDIUM⚡ | …pt-br/docs/concepts/workloads/controllers/cron-jobs.md | 51 | # │ │ ┌───────────── dia do mês (1 - 31) | COMMENT |
| MEDIUM⚡ | …pt-br/docs/concepts/workloads/controllers/cron-jobs.md | 52 | # │ │ │ ┌───────────── mês (1 - 12) | COMMENT |
| MEDIUM⚡ | …pt-br/docs/concepts/workloads/controllers/cron-jobs.md | 53 | # │ │ │ │ ┌───────────── dia da semana (0 - 6) (domingo a sábado; | COMMENT |
| MEDIUM⚡ | …nt/ko/docs/concepts/workloads/controllers/cron-jobs.md | 57 | # ┌───────────── 분 (0 - 59) | COMMENT |
| MEDIUM⚡ | …nt/ko/docs/concepts/workloads/controllers/cron-jobs.md | 58 | # │ ┌───────────── 시 (0 - 23) | COMMENT |
| MEDIUM⚡ | …nt/ko/docs/concepts/workloads/controllers/cron-jobs.md | 59 | # │ │ ┌───────────── 일 (1 - 31) | COMMENT |
| MEDIUM⚡ | …nt/ko/docs/concepts/workloads/controllers/cron-jobs.md | 60 | # │ │ │ ┌───────────── 월 (1 - 12) | COMMENT |
| MEDIUM⚡ | …nt/ko/docs/concepts/workloads/controllers/cron-jobs.md | 61 | # │ │ │ │ ┌───────────── 요일 (0 - 6) (일요일부터 토요일까지) | COMMENT |
| MEDIUM⚡ | …nt/en/docs/concepts/workloads/controllers/cron-jobs.md | 57 | # ┌───────────── minute (0 - 59) | COMMENT |
| MEDIUM⚡ | …nt/en/docs/concepts/workloads/controllers/cron-jobs.md | 58 | # │ ┌───────────── hour (0 - 23) | COMMENT |
| MEDIUM⚡ | …nt/en/docs/concepts/workloads/controllers/cron-jobs.md | 59 | # │ │ ┌───────────── day of the month (1 - 31) | COMMENT |
| MEDIUM⚡ | …nt/en/docs/concepts/workloads/controllers/cron-jobs.md | 60 | # │ │ │ ┌───────────── month (1 - 12) | COMMENT |
| MEDIUM⚡ | …nt/en/docs/concepts/workloads/controllers/cron-jobs.md | 61 | # │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …ster-cluster/change-pv-access-mode-readwriteoncepod.md | 245 | # IMPORTANT: Make sure to edit your PVC in cat-pictures-pvc.yaml before applying. You need to: | COMMENT |
| LOW | …tent/zh-cn/docs/tasks/manage-daemon/pods-some-nodes.md | 41 | ### Step 1: Add labels to your nodes | COMMENT |
| LOW | …tent/zh-cn/docs/tasks/manage-daemon/pods-some-nodes.md | 54 | ### Step 2: Create the manifest | COMMENT |
| LOW | …tent/zh-cn/docs/tasks/manage-daemon/pods-some-nodes.md | 72 | ### Step 3: Create the DaemonSet | COMMENT |
| LOW | …/zh-cn/docs/tasks/manage-daemon/rollback-daemon-set.md | 37 | ### Step 1: Find the DaemonSet revision you want to roll back to | COMMENT |
| LOW | …/zh-cn/docs/tasks/manage-daemon/rollback-daemon-set.md | 104 | ### Step 2: Roll back to a specific revision | COMMENT |
| LOW | …/zh-cn/docs/tasks/manage-daemon/rollback-daemon-set.md | 130 | ### Step 3: Watch the progress of the DaemonSet rollback | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 130 | ### Step 1: Configure kubelet for pod scope | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 168 | ### Step 2: Deploy a mixed-allocation pod | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 202 | ### Step 3: Verify and inspect resource partitioning | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 281 | ### Step 4: Examine the invalid pod manifest | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 297 | ### Step 5: Attempt deployment and observe rejection | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 361 | ### Step 6: Configure kubelet for container scope | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 389 | ### Step 7: Deploy a container-scoped mixed workload | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 419 | ### Step 8: Verify the deployment | COMMENT |
| LOW | …ocs/tutorials/kubernetes-basics/expose/expose-intro.md | 187 | ### Step 1: Creating a new Service | COMMENT |
| LOW | …ocs/tutorials/kubernetes-basics/expose/expose-intro.md | 311 | ### Step 2: Using labels | COMMENT |
| LOW | …ocs/tutorials/kubernetes-basics/expose/expose-intro.md | 396 | ### Step 3: Deleting a service | COMMENT |
| LOW | …cn/docs/reference/instrumentation/native-histograms.md | 167 | ### Step 1: Ensure the Kubernetes feature gate is enabled | COMMENT |
| LOW | …cn/docs/reference/instrumentation/native-histograms.md | 202 | ### Step 2: Configure Prometheus | COMMENT |
| LOW⚡ | …/zh-cn/blog/_posts/2018/airflow-kubernetes-operator.md | 243 | ## Step 1: Set your kubeconfig to point to a kubernetes cluster | COMMENT |
| LOW⚡ | …/zh-cn/blog/_posts/2018/airflow-kubernetes-operator.md | 245 | ## Step 2: Clone the Airflow Repo: | COMMENT |
| LOW⚡ | …/zh-cn/blog/_posts/2018/airflow-kubernetes-operator.md | 249 | ## Step 3: Run | COMMENT |
| LOW | …/zh-cn/blog/_posts/2018/airflow-kubernetes-operator.md | 292 | ## Step 4: Log into your webserver | COMMENT |
| LOW | …/zh-cn/blog/_posts/2018/airflow-kubernetes-operator.md | 326 | ## Step 5: Upload a test document | COMMENT |
| LOW | …/zh-cn/blog/_posts/2018/airflow-kubernetes-operator.md | 341 | ## Step 6: Enjoy! | COMMENT |
| LOW | …ster-cluster/change-pv-access-mode-readwriteoncepod.md | 168 | # IMPORTANT: Make sure to edit your PVC in cat-pictures-pvc.yaml before applying. You need to: | COMMENT |
| LOW⚡ | content/en/docs/tasks/manage-daemon/pods-some-nodes.md | 20 | ### Step 1: Add labels to your nodes | COMMENT |
| LOW⚡ | content/en/docs/tasks/manage-daemon/pods-some-nodes.md | 28 | ### Step 2: Create the manifest | COMMENT |
| LOW⚡ | content/en/docs/tasks/manage-daemon/pods-some-nodes.md | 38 | ### Step 3: Create the DaemonSet | COMMENT |
| LOW | …ent/en/docs/tasks/manage-daemon/rollback-daemon-set.md | 26 | ### Step 1: Find the DaemonSet revision you want to roll back to | COMMENT |
| LOW | …ent/en/docs/tasks/manage-daemon/rollback-daemon-set.md | 71 | ### Step 2: Roll back to a specific revision | COMMENT |
| LOW | …ent/en/docs/tasks/manage-daemon/rollback-daemon-set.md | 88 | ### Step 3: Watch the progress of the DaemonSet rollback | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 79 | ### Step 1: Configure kubelet for pod scope | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 102 | ### Step 2: Deploy a mixed-allocation pod | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 121 | ### Step 3: Verify and inspect resource partitioning | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 166 | ### Step 4: Examine the invalid pod manifest | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 175 | ### Step 5: Attempt deployment and observe rejection | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 220 | ### Step 6: Configure kubelet for container scope | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 238 | ### Step 7: Deploy a container-scoped mixed workload | COMMENT |
| LOW | …/cluster-management/use-pod-level-resource-managers.md | 256 | ### Step 8: Verify the deployment | COMMENT |
| LOW | …ocs/tutorials/kubernetes-basics/expose/expose-intro.md | 96 | ### Step 1: Creating a new Service | COMMENT |
| LOW | …ocs/tutorials/kubernetes-basics/expose/expose-intro.md | 174 | ### Step 2: Using labels | COMMENT |
| LOW | …ocs/tutorials/kubernetes-basics/expose/expose-intro.md | 224 | ### Step 3: Deleting a service | COMMENT |
| LOW | …en/docs/reference/instrumentation/native-histograms.md | 88 | ### Step 1: Ensure the Kubernetes feature gate is enabled | COMMENT |
| LOW | …en/docs/reference/instrumentation/native-histograms.md | 109 | ### Step 2: Configure Prometheus | COMMENT |
| LOW | …ts/2026/tracing-kueue-admission-with-headlamp/index.md | 70 | ## Step 1: Open the Workloads view | COMMENT |
| LOW | …ts/2026/tracing-kueue-admission-with-headlamp/index.md | 101 | ## Step 2: Read status, conditions, and events | COMMENT |
| LOW | …ts/2026/tracing-kueue-admission-with-headlamp/index.md | 127 | ## Step 3: Compare the Workload's request with its assignment | COMMENT |
| LOW | …ts/2026/tracing-kueue-admission-with-headlamp/index.md | 149 | ## Step 4: Follow the linked LocalQueue | COMMENT |
| LOW | …ts/2026/tracing-kueue-admission-with-headlamp/index.md | 173 | ## Step 5: Inspect ClusterQueue capacity and usage | COMMENT |
| LOW | …ts/2026/tracing-kueue-admission-with-headlamp/index.md | 202 | ## Step 6: Check ResourceFlavor and Cohort when needed | COMMENT |
| LOW | …sts/2019/kubernetes-setup-using-ansible-and-vagrant.md | 29 | #### Step 1: Creating a Vagrantfile | COMMENT |
| LOW | …sts/2019/kubernetes-setup-using-ansible-and-vagrant.md | 72 | ### Step 2: Create an Ansible playbook for Kubernetes master. | COMMENT |
| LOW | …sts/2019/kubernetes-setup-using-ansible-and-vagrant.md | 230 | #### Step 3: Create the Ansible playbook for Kubernetes node. | COMMENT |
| LOW | …sts/2019/kubernetes-setup-using-ansible-and-vagrant.md | 249 | #### Step 4: Upon completing the Vagrantfile and playbooks follow the below steps. | COMMENT |
| LOW | …/_posts/2021/data-duplication-in-data-heavy-k8s-env.md | 74 | ## Step 1: Identify Disk | COMMENT |
| LOW | …/_posts/2021/data-duplication-in-data-heavy-k8s-env.md | 88 | ## Step 2: Prepare your golden source | COMMENT |
| LOW | …/_posts/2021/data-duplication-in-data-heavy-k8s-env.md | 122 | ## Step 3: Get your Disk Snapshot ID | COMMENT |
| LOW | …/_posts/2021/data-duplication-in-data-heavy-k8s-env.md | 139 | ## Step 4: Create a development environment for each team | COMMENT |
| 12 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | hugo.server.toml | 1 | # Re-enable Hugo alias pages for local preview. | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 81 | # このプロバイダーを呼び出すべきかどうかを判断するために使用されます。 | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 101 | # - *.*.registry.io | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 121 | # これらはホストの環境変数および、client-goがプラグインに引数を渡すために使用する変数と結合されます。 | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 141 | # +required | COMMENT |
| LOW | content/ja/examples/application/job/redis/rediswq.py | 61 | # # Processing list should not be _too_ long since it is approximately as long | COMMENT |
| LOW | content/ja/examples/application/job/redis/rediswq.py | 121 | # since other workers might think work is done and be in the process | COMMENT |
| LOW | content/ja/examples/debug/fluentd-gcp-configmap.yaml | 1 | kind: ConfigMap | COMMENT |
| LOW | content/ja/examples/debug/fluentd-gcp-configmap.yaml | 21 | # and the Kubernetes container name. For example a Docker container's logs | COMMENT |
| LOW | content/ru/examples/application/job/redis/rediswq.py | 61 | # # Processing list should not be _too_ long since it is approximately as long | COMMENT |
| LOW | content/ru/examples/application/job/redis/rediswq.py | 121 | # since other workers might think work is done and be in the process | COMMENT |
| LOW | content/zh-cn/docs/home/_index.md | 21 | 此开源项目由云原生计算基金会(CNCF)托管。 | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 181 | # name is the required name of the credential provider. It must match the name of the | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 201 | # | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 221 | # Arguments to pass to the command when executing it. | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 241 | serviceAccountTokenAudience: "<audience for the token>" | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 261 | # and that are required to be present in the service account. | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 301 | # matchImages 是一个必需的字符串列表,用于匹配镜像以确定是否应调用此提供程序。 | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 321 | # - gcr.io | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 341 | # env 定义了额外的环境变量以暴露给进程。 | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 361 | # 那么插件可以将此设置为 "ServiceAccount"。在这种情况下, | COMMENT |
| LOW | …zh-cn/docs/concepts/security/pod-security-admission.md | 121 | # The per-mode level label indicates which policy level to apply for the mode. | COMMENT |
| LOW | …zh-cn/docs/concepts/workloads/controllers/cron-jobs.md | 101 | COMMENT | |
| LOW | content/zh-cn/docs/reference/instrumentation/zpages.md | 161 | // GoVersion is the version of the Go programming language used to build the binary. | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 721 | # url must be unique across all authenticators. | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 741 | audiences: | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 761 | - expression: 'claims.hd == "example.com"' | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 781 | # An example claim validation rule expression that matches the validation automatically | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 801 | # Mutually exclusive with uid.expression. | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 841 | # discoveryURL(如果指定)将覆盖用于获取发现信息的 URL,而不是使用 “{url}/.well-known/openid-configuration”。 | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 861 | #(发现、JWKS、分布式申领等)。 | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 881 | claimMappings: | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 901 | expression: 'claims.username + ":external-user"' | COMMENT |
| LOW | …cn/docs/reference/access-authn-authz/authentication.md | 921 | extra: | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 401 | # | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 421 | # and the specified authorizedTTL is ignored/has no effect. | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 441 | # The API version of the authorization.k8s.io SubjectAccessReview to | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 461 | connectionInfo: | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 481 | # - If failurePolicy=Deny, then the webhook rejects the request | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 521 | # 用于描述鉴权人的名称 | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 541 | unauthorizedTTL: 30s | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 561 | # 当 Webhook 请求无法完成或返回格式错误的响应或评估 matchConditions 时出现错误时,控制鉴权决定。 | COMMENT |
| LOW | …-cn/docs/reference/access-authn-authz/authorization.md | 581 | # 1. 如果至少一个 matchCondition 计算结果为 FALSE,则跳过 Webhook。 | COMMENT |
| LOW | …access-authn-authz/extensible-admission-controllers.md | 321 | <!-- | COMMENT |
| LOW | …access-authn-authz/extensible-admission-controllers.md | 341 | # A webhook with `url: https://www.example.com`: | COMMENT |
| LOW | …access-authn-authz/extensible-admission-controllers.md | 381 | # user: ... | COMMENT |
| LOW | …/admin/konnectivity/egress-selector-configuration.yaml | 1 | apiVersion: apiserver.k8s.io/v1beta1 | COMMENT |
| LOW | content/zh-cn/examples/application/job/redis/rediswq.py | 61 | # # Processing list should not be _too_ long since it is approximately as long | COMMENT |
| LOW | content/zh-cn/examples/application/job/redis/rediswq.py | 121 | # since other workers might think work is done and be in the process | COMMENT |
| LOW | content/zh-cn/examples/debug/fluentd-gcp-configmap.yaml | 1 | apiVersion: v1 | COMMENT |
| LOW | content/zh-cn/examples/debug/fluentd-gcp-configmap.yaml | 21 | # and the Kubernetes container name. For example a Docker container's logs | COMMENT |
| LOW | …od-container/enforce-standards-admission-controller.md | 41 | # Padrões aplicados quando o label de modo não é especificado. | COMMENT |
| LOW | …asks/administer-cluster/kubelet-credential-provider.md | 61 | # matchImages é uma lista obrigatória de strings usadas para corresponder às imagens para | COMMENT |
| LOW | …access-authn-authz/extensible-admission-controllers.md | 181 | # Para um webhook configurado para se comunicar com um serviço na porta padrão (443), especifique o nome DNS do serviço: | COMMENT |
| LOW | …/admin/konnectivity/egress-selector-configuration.yaml | 1 | apiVersion: apiserver.k8s.io/v1beta1 | COMMENT |
| LOW | content/bn/examples/application/job/redis/rediswq.py | 61 | # # Processing list should not be _too_ long since it is approximately as long | COMMENT |
| LOW | content/bn/examples/application/job/redis/rediswq.py | 121 | # since other workers might think work is done and be in the process | COMMENT |
| LOW | content/bn/examples/debug/fluentd-gcp-configmap.yaml | 1 | apiVersion: v1 | COMMENT |
| LOW | content/bn/examples/debug/fluentd-gcp-configmap.yaml | 21 | # and the Kubernetes container name. For example a Docker container's logs | COMMENT |
| LOW | content/hi/examples/application/job/redis/rediswq.py | 61 | # # Processing list should not be _too_ long since it is approximately as long | COMMENT |
| 48 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 74 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 134 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 141 | 上記の`fake-ca-file`、`fake-cert-file`、`fake-key-file`は、証明書ファイルの実際のパスのプレースホルダーです。環境内にある証明書ファイルの実際のパスに変更してください。 | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 183 | client-key: fake-key-file | CODE |
| LOW | content/zh-cn/docs/test.md | 117 | Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor | CODE |
| LOW | content/zh-cn/docs/test.md | 117 | Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 149 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 225 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 237 | The `fake-ca-file`, `fake-cert-file` and `fake-key-file` above are the placeholders | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 245 | 其中的 `fake-ca-file`、`fake-cert-file` 和 `fake-key-file` 是证书文件路径名的占位符。 | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 311 | client-key: fake-key-file | CODE |
| LOW | …t/zh-cn/docs/contribute/style/hugo-shortcodes/index.md | 707 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW | …t/zh-cn/docs/contribute/style/hugo-shortcodes/index.md | 707 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW | …t/zh-cn/docs/contribute/style/hugo-shortcodes/index.md | 732 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW | …t/zh-cn/docs/contribute/style/hugo-shortcodes/index.md | 732 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 88 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 148 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 160 | O `fake-ca-file`, o `fake-cert-file` e o `fake-key-file` acima são os espaços reservados | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 211 | client-key: fake-key-file | CODE |
| LOW | content/hi/docs/test.md | 55 | Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna ali | CODE |
| LOW | content/hi/docs/test.md | 55 | Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna ali | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 96 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 157 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 169 | 위 `fake-ca-file`, `fake-cert-file`, `fake-key-file`은 인증서 파일들의 실제 경로 이름을 위한 | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 220 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 85 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 146 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 153 | `fake-ca-file`, `fake-cert-file`, dan `fake-key-file` di atas adalah _placeholder_ | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 203 | client-key: fake-key-file | CODE |
| LOW⚡ | content/id/docs/concepts/policy/pod-security-policy.md | 134 | kubectl create serviceaccount -n psp-example fake-user | CODE |
| LOW⚡ | content/id/docs/concepts/policy/pod-security-policy.md | 135 | kubectl create rolebinding -n psp-example fake-editor --clusterrole=edit --serviceaccount=psp-example:fake-user | CODE |
| LOW⚡ | content/id/docs/concepts/policy/pod-security-policy.md | 142 | alias kubectl-user='kubectl --as=system:serviceaccount:psp-example:fake-user -n psp-example' | CODE |
| LOW | content/id/docs/concepts/policy/pod-security-policy.md | 173 | **Apa yang terjadi?** Walaupun PodSecurityPolicy tersebut telah dibuat, ServiceAccount dari Pod tersebut maupun `fake-us | CODE |
| LOW | content/id/docs/concepts/policy/pod-security-policy.md | 180 | Membuat RoleBinding untuk memberikan `fake-user` akses terhadap kata kerja `use` pada kebijakan contoh kita: | CODE |
| LOW⚡ | content/id/docs/concepts/policy/pod-security-policy.md | 193 | kubectl-admin create rolebinding fake-user:psp:unprivileged \ | CODE |
| LOW⚡ | content/id/docs/concepts/policy/pod-security-policy.md | 195 | --serviceaccount=psp-example:fake-user | CODE |
| LOW⚡ | content/id/docs/concepts/policy/pod-security-policy.md | 196 | rolebinding "fake-user:psp:unprivileged" created | CODE |
| LOW | content/id/docs/concepts/policy/pod-security-policy.md | 258 | **Apa yang terjadi?** Kita telah mengikat Role `psp:unprivileged` untuk `fake-user` kita, kenapa kita mendapatkan kesala | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 81 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 143 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 150 | Le `fake-ca-file`, `fake-cert-file` et `fake-key-file` ci-dessus sont les espaces réservés pour les noms de chemin des f | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 195 | client-key: fake-key-file | CODE |
| LOW | content/en/docs/test.md | 58 | Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor | CODE |
| LOW | content/en/docs/test.md | 58 | Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 97 | kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake- | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 158 | client-key: fake-key-file | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 170 | The `fake-ca-file`, `fake-cert-file` and `fake-key-file` above are the placeholders | CODE |
| LOW | …lication-cluster/configure-access-multiple-clusters.md | 221 | client-key: fake-key-file | CODE |
| LOW⚡ | …tent/en/docs/contribute/style/hugo-shortcodes/index.md | 382 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW⚡ | …tent/en/docs/contribute/style/hugo-shortcodes/index.md | 382 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW⚡ | …tent/en/docs/contribute/style/hugo-shortcodes/index.md | 392 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW⚡ | …tent/en/docs/contribute/style/hugo-shortcodes/index.md | 392 | Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, | CODE |
| LOW | layouts/docs/glossary.html | 10 | <div class="tag-description invisible" id="placeholder">.</div> | CODE |
| LOW | layouts/docs/supported-versions.html | 8 | {{ $.Scratch.Set "version-class" (slice "placeholder") }} | CODE |
| LOW | layouts/docs/supported-versions.html | 9 | {{/* "placeholder" is also used later to check whether we opened the <ul> */}} | CODE |
| LOW | layouts/docs/supported-versions.html | 38 | {{ if ne (index ($.Scratch.Get "version-class") 0) "placeholder" }} | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | content/bn/examples/access/endpoints-aggregated.yaml | 16 | name: custom:aggregate-to-edit:endpoints # you can change this if you wish | CODE |
| MEDIUM | content/hi/examples/access/endpoints-aggregated.yaml | 16 | name: custom:aggregate-to-edit:endpoints # you can change this if you wish | CODE |
| MEDIUM | content/fr/examples/access/endpoints-aggregated.yaml | 16 | name: custom:aggregate-to-edit:endpoints # you can change this if you wish | CODE |
| MEDIUM | content/en/examples/access/endpoints-aggregated.yaml | 16 | name: custom:aggregate-to-edit:endpoints # you can change this if you wish | CODE |
| MEDIUM⚡ | …ource/pod-level-resource-managers-pod-scope-mixed.yaml | 24 | # Note: This is a placeholder image for demonstration purposes, not an | COMMENT |
| MEDIUM⚡ | …ource/pod-level-resource-managers-pod-scope-mixed.yaml | 29 | # Note: This is a placeholder image for demonstration purposes, not an | COMMENT |
| MEDIUM⚡ | …ource/pod-level-resource-managers-pod-scope-mixed.yaml | 35 | # Note: This is a placeholder image for demonstration purposes. | COMMENT |
| MEDIUM | …rce/pod-level-resource-managers-empty-shared-pool.yaml | 24 | # Note: This is a placeholder image for demonstration purposes, not an | COMMENT |
| MEDIUM | …rce/pod-level-resource-managers-empty-shared-pool.yaml | 36 | # Note: This is a placeholder image for demonstration purposes, not an | COMMENT |
| MEDIUM | …rce/pod-level-resource-managers-empty-shared-pool.yaml | 42 | # Note: This is a placeholder image for demonstration purposes. | COMMENT |
| MEDIUM | …pod-level-resource-managers-container-scope-mixed.yaml | 25 | # Note: This is a placeholder image for demonstration purposes, not an | COMMENT |
| MEDIUM | …pod-level-resource-managers-container-scope-mixed.yaml | 38 | # Note: This is a placeholder image for demonstration purposes. | COMMENT |
| MEDIUM | …pod-level-resource-managers-container-scope-mixed.yaml | 41 | # Note: This is a placeholder image for demonstration purposes. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | content/ja/docs/concepts/workloads/autoscaling.md | 90 | ### イベント駆動型自動スケーリング {#event-driven-autoscaling} | COMMENT |
| MEDIUM | content/zh-cn/docs/home/_index.md | 18 | # Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of co | COMMENT |
| MEDIUM | content/zh-cn/docs/home/_index.md | 23 | # Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of co | COMMENT |
| MEDIUM | content/zh-cn/docs/concepts/workloads/autoscaling.md | 202 | ### 事件驱动型自动扩缩 {#event-driven-autoscaling} | COMMENT |
| MEDIUM | content/zh-cn/blog/_posts/2026/agent-sandbox.md | 178 | Once installed, you can try out the [Python SDK](https://github.com/kubernetes-sigs/agent-sandbox/tree/main/clients/pyth | CODE |
| MEDIUM | content/zh-cn/blog/_posts/2026/agent-sandbox.md | 181 | [Python SDK](https://github.com/kubernetes-sigs/agent-sandbox/tree/main/clients/python/agentic-sandbox-client), | CODE |
| MEDIUM | …6/scaling-kubernetes-workloads-with-node-swap/index.md | 45 | This conflict is amplified when deploying autonomous AI agents using secure execution environments like the [`agent-sand | CODE |
| MEDIUM | content/ko/blog/_posts/2026/agent-sandbox.md | 72 | 설치를 마치면 AI 에이전트를 위한 [파이썬 SDK](https://github.com/kubernetes-sigs/agent-sandbox/tree/main/clients/python/agentic-sandbox- | CODE |
| MEDIUM | content/en/blog/_posts/2026/agent-sandbox.md | 70 | Once installed, you can try out the [Python SDK](https://github.com/kubernetes-sigs/agent-sandbox/tree/main/clients/pyth | CODE |
| MEDIUM | content/en/blog/_posts/2026/sig-apps-spotlight.md | 25 | Since then, I've stayed deeply involved in both the technical and community sides of Kubernetes. I have led SIG Apps as | CODE |
| MEDIUM | …6/scaling-kubernetes-workloads-with-node-swap/index.md | 23 | This conflict is amplified when deploying autonomous AI agents using secure execution environments like the [`agent-sand | CODE |
| MEDIUM | …ntent/en/blog/_posts/2018/11-ways-not-to-get-hacked.md | 248 | test-microservice: 80 # `test-microservice` is the DNS name of the target service | CODE |
| MEDIUM | …/rktnetes-brings-rkt-container-engine-to-kubernetes.md | 61 | #### Managing microservice lifecycles | COMMENT |
| MEDIUM | scripts/l10n-outdatedness-triage.py | 969 | # --- CLI / orchestration --- | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …n/examples/pods/pod-single-configmap-env-variable.yaml | 11 | # Define the environment variable | COMMENT |
| MEDIUM | content/bn/examples/configmap/configure-pod.yaml | 11 | # Define the environment variable | COMMENT |
| MEDIUM | …i/examples/pods/pod-single-configmap-env-variable.yaml | 11 | # Define the environment variable | COMMENT |
| MEDIUM | content/hi/examples/configmap/configure-pod.yaml | 11 | # Define the environment variable | COMMENT |
| MEDIUM | …n/examples/pods/pod-single-configmap-env-variable.yaml | 11 | # Define the environment variable | COMMENT |
| MEDIUM | content/en/examples/configmap/configure-pod.yaml | 11 | # Define the environment variable | COMMENT |
| MEDIUM | scripts/fetch_kubecon_events.py | 218 | f.write("# This file is auto-generated by scripts/fetch_kubecon_events.py\n") | CODE |
| MEDIUM | data/events/kubecon.yaml | 2 | # This file is auto-generated by scripts/fetch_kubecon_events.py | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | …bn/examples/service/pod-with-graceful-termination.yaml | 27 | # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, | COMMENT |
| HIGH | …hi/examples/service/pod-with-graceful-termination.yaml | 27 | # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, | COMMENT |
| HIGH | …en/examples/service/pod-with-graceful-termination.yaml | 26 | # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | content/zh-cn/case-studies/workiva/index.html | 64 | <!-- Early on, Workiva’s backend had run mostly on <a href="https://cloud.google.com/appengine/">Google App Engine</a> | CODE |
| MEDIUM | content/zh-cn/case-studies/ancestry/index.html | 68 | His team looked at orchestration platforms offered by <a href="https://docs.docker.com/compose/">Docker Compose</a>, < | CODE |
| MEDIUM | content/zh-cn/case-studies/chinaunicom/index.html | 171 | <p>Plus, "companies can use the managed services offered by companies like <a href="https://rancher.com/">Rancher</a>, b | CODE |
| MEDIUM | content/zh-cn/case-studies/haufegroup/index.html | 90 | As word of the two successful test projects spread throughout the company, interest in Kubernetes has grown. "We w | CODE |
| MEDIUM | content/zh-cn/case-studies/amadeus/index.html | 77 | The first project the team tackled was one that they knew had to run outside the data center in Germany. Because of th | CODE |
| MEDIUM | content/zh-cn/case-studies/netease/index.html | 118 | <p>The team first focused on building the container platform to manage resources better, and then turned their attention | CODE |
| MEDIUM | …pt-br/examples/application/mysql/mysql-deployment.yaml | 31 | # Em cenários reais, utilize um Secret | COMMENT |
| MEDIUM | i18n/pt-br/pt-br.toml | 537 | para [versões mais antigas](https://kubernetes.io/docs/home/supported-doc-versions/#versions-older) ou utilize [download | CODE |
| MEDIUM | i18n/pt-br/pt-br.toml | 537 | para [versões mais antigas](https://kubernetes.io/docs/home/supported-doc-versions/#versions-older) ou utilize [download | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …t/ja/examples/application/mysql/mysql-statefulset.yaml | 123 | # Check if we need to complete a clone by starting replication. | COMMENT |
| LOW | …t/ru/examples/application/mysql/mysql-statefulset.yaml | 125 | # Check if we need to complete a clone by starting replication. | COMMENT |
| LOW | …t/bn/examples/application/mysql/mysql-statefulset.yaml | 125 | # Check if we need to complete a clone by starting replication. | COMMENT |
| LOW | …t/hi/examples/application/mysql/mysql-statefulset.yaml | 125 | # Check if we need to complete a clone by starting replication. | COMMENT |
| LOW | …t/en/examples/application/mysql/mysql-statefulset.yaml | 125 | # Check if we need to complete a clone by starting replication. | COMMENT |
| LOW | scripts/test_examples.sh | 10 | # Check if examples folders (all locales) change in this branch | COMMENT |
| LOW | scripts/lsync.sh | 14 | # Check if path exists, and whether it is a directory or a file | COMMENT |
| LOW | i18n/pl/pl.toml | 705 | # Set this to "" if your localization implements the new strings. | COMMENT |
| LOW | i18n/ja/ja.toml | 690 | # Set this to "" if your localization implements the new strings. | COMMENT |
| LOW | i18n/es/es.toml | 672 | # Set this to "" if your localization implements the new strings. | COMMENT |
| LOW | i18n/en/en.toml | 741 | # Set this to "" if your localization implements the new strings. | COMMENT |
| LOW | i18n/fa/fa.toml | 628 | # Set this to "" if your localization implements the new strings. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | update-imported-docs/update-imported-docs.py | 132 | except Exception as ex: | CODE |
| LOW | update-imported-docs/update-imported-docs.py | 152 | except Exception as ex: | CODE |
| LOW | update-imported-docs/update-imported-docs.py | 203 | except Exception as ex: | CODE |
| LOW | scripts/linkchecker.py | 361 | except Exception as ex: | CODE |
| LOW | scripts/linkchecker.py | 402 | except Exception as ex: | CODE |
| LOW | scripts/linkchecker.py | 525 | except Exception as ex: | CODE |
| LOW | scripts/upstream_changes.py | 16 | except Exception as exc: | CODE |
| LOW | scripts/upstream_changes.py | 30 | except Exception as exc: | CODE |
| LOW | scripts/upstream_changes.py | 40 | except Exception as exc: | CODE |
| MEDIUM | scripts/find_pr.py | 82 | print("Error Connecting: %s" % err) | STRING |
| LOW | scripts/fetch_kubecon_events.py | 197 | except Exception as e: | CODE |
| LOW | scripts/fetch_kubecon_events.py | 266 | except Exception as e: | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | content/zh-cn/docs/update-user-guide-links.py | 8 | def find_documents_to_rewrite(): | CODE |
| LOW | content/bn/docs/update-user-guide-links.py | 8 | def find_documents_to_rewrite(): | CODE |
| LOW | content/es/docs/update-user-guide-links.py | 8 | def find_documents_to_rewrite(): | CODE |
| LOW | content/en/docs/update-user-guide-links.py | 8 | def find_documents_to_rewrite(): | CODE |
| LOW | static/js/apiref.js | 6 | function getCurrentlyVisibleSection(scrollPosition) { | CODE |
| LOW | scripts/l10n-outdatedness-triage.py | 358 | def _extract_feature_state_tokens(text: str) -> FrozenSet[str]: | CODE |
| LOW | scripts/l10n-outdatedness-triage.py | 396 | def _count_missing_new_versions( | CODE |
| LOW | scripts/l10n-outdatedness-triage.py | 476 | def _should_ignore_length_gap( | CODE |
| LOW | scripts/l10n-outdatedness-triage.py | 571 | def _is_expected_translated_anchor_loss( | CODE |
| LOW | scripts/l10n-outdatedness-triage.py | 822 | def _build_locale_profile_note(profile: LocaleProfile) -> List[str]: | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | content/ja/examples/application/job/redis/rediswq.py | 58 | # TODO: implement this | COMMENT |
| LOW | content/ru/examples/application/job/redis/rediswq.py | 58 | # TODO: implement this | COMMENT |
| LOW | content/zh-cn/examples/application/job/redis/rediswq.py | 58 | # TODO: implement this | COMMENT |
| LOW | content/bn/examples/application/job/redis/rediswq.py | 58 | # TODO: implement this | COMMENT |
| LOW | content/hi/examples/application/job/redis/rediswq.py | 58 | # TODO: implement this | COMMENT |
| LOW | content/en/examples/application/job/redis/rediswq.py | 58 | # TODO: implement this | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | update-imported-docs/update-imported-docs.py | 107 | CODE | |
| LOW | scripts/linkchecker.py | 394 | CODE | |
| LOW | scripts/find_pr.py | 22 | CODE | |
| LOW | scripts/l10n-outdatedness-triage.py | 735 | CODE | |
| LOW | scripts/l10n-outdatedness-triage.py | 850 | CODE | |
| LOW | scripts/diff_l10n_branches.py | 81 | CODE | |
| LOW | scripts/fetch_kubecon_events.py | 54 | CODE |