Skip to content

Commit 14f79a4

Browse files
authored
Merge branch 'main' into fix/variables.md
2 parents 72c9c9b + eb7ff74 commit 14f79a4

File tree

13 files changed

+66
-71
lines changed

13 files changed

+66
-71
lines changed

.github/workflows/check-links.yaml

+2-2
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ jobs:
1515

1616
- name: Check unrendered links
1717
id: lychee_unrendered
18-
uses: lycheeverse/lychee-action@f796c8b7d468feb9b8c0a46da3fac0af6874d374 # v2.2.0
18+
uses: lycheeverse/lychee-action@f613c4a64e50d792e0b31ec34bbcbba12263c6a6 # v2.3.0
1919
env:
2020
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
2121
with:
@@ -48,7 +48,7 @@ jobs:
4848

4949
# - name: Check rendered links
5050
# id: lychee_rendered
51-
# uses: lycheeverse/lychee-action@f796c8b7d468feb9b8c0a46da3fac0af6874d374 # v2.2.0
51+
# uses: lycheeverse/lychee-action@f613c4a64e50d792e0b31ec34bbcbba12263c6a6 # v2.3.0
5252
# env:
5353
# GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
5454
# with:

content/en/blog/general/openshift-machinesets/index.md

-1
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,6 @@ metadata:
120120
MachineSet created. This policy fetches the value of the infrastructure name from the
121121
Cluster resource and replaces all instances of TEMPLATE in a MachineSet with that name.
122122
spec:
123-
schemaValidation: false
124123
rules:
125124
- name: replace-template
126125
match:

content/en/docs/monitoring/cleanup-ttl-controller-deleted-objects.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Cleanup Controller Deleted Objects
2+
title: Cleanup TTL Controller Deleted Objects
33
description: This metric can be used to track the number of objects deleted by the cleanup TTL controller.
44
weight: 45
55
---

content/en/docs/monitoring/cleanup-ttl-controller-errors.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Cleanup Controller Errors Count
2+
title: Cleanup TTL Controller Errors Count
33
description: This metric can be used to track the number of errors encountered by the cleanup TTL controller while trying to delete objects.
44
weight: 45
55
---
+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: Kyverno Info
3+
description: This metric can be used to information related to Kyverno such as its version.
4+
weight: 50
5+
---
6+
7+
#### Metric Name(s)
8+
9+
* `kyverno_info`
10+
11+
#### Metric Value
12+
13+
Gauge - A constant value of 1 with labels to include relevant information
14+
15+
#### Metric Labels
16+
17+
| Label | Allowed Values | Description |
18+
|--------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------|
19+
| version | | Current version of Kyvero being used |
20+
21+
#### Use cases
22+
23+
* The cluster admin wants to see information related to Kyverno such as its version
24+
25+
#### Useful Queries
26+
27+
* `kyverno_info`

content/en/docs/monitoring/opentelemetry.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ spec:
9797
name: collector-config
9898
```
9999

100-
This references the collector defined in the `configmap.yaml` above. Here we are using a Deployemtn with just a single replica. Ideally, a DaemonSet is preferred. Check the [OpenTelemetry documentation](https://opentelemetry.io/docs/instrumentation/go/getting-started) for more deployment strategies.
100+
This references the collector defined in the `configmap.yaml` above. Here we are using a Deployement with just a single replica. Ideally, a DaemonSet is preferred. Check the [OpenTelemetry documentation](https://opentelemetry.io/docs/instrumentation/go/getting-started) for more deployment strategies.
101101

102102
### The Collector Service
103103

content/en/docs/writing-policies/jmespath.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2053,7 +2053,7 @@ spec:
20532053
<details><summary>Expand</summary>
20542054
<p>
20552055

2056-
The `sum()` filter takes an array of numbers, durations, or quantities and sums them together. This is a customized version of `sum()` found in the [upstream JMESPath specification](https://jmespath.org/specification.html#sum) but augmented to support inputs common to Kubernetes workloads, specifically durations and quantities. `sum()` is similar to `add()` with the difference that `sum()` accepts an array as an input while `add()` does not. Inputs must be of a homogenous type. For example, the query `echo '{"input":['2Ki','5Gi','8Mi']}' | kyverno jp query "sum(input)"` results in the value `"5251074Ki"`. The query `echo '{"input":['2h','50s','90s']}' | kyverno jp query "sum(input)"` results in the value `"2h2m20s"`. And the query `echo '{"input":[6,3,8]}' | kyverno jp query "sum(input)"` results in the value of `17`.
2056+
The `sum()` filter takes an array of numbers, durations, or quantities and sums them together. This is a customized version of `sum()` found in the [upstream JMESPath specification](https://jmespath.org/specification.html#sum) but augmented to support inputs common to Kubernetes workloads, specifically durations and quantities. `sum()` is similar to `add()` with the difference that `sum()` accepts an array as an input while `add()` does not. This `sum()` function requires at least one element in the array. Inputs must be of a homogenous type. For example, the query `echo '{"input":['2Ki','5Gi','8Mi']}' | kyverno jp query "sum(input)"` results in the value `"5251074Ki"`. The query `echo '{"input":['2h','50s','90s']}' | kyverno jp query "sum(input)"` results in the value `"2h2m20s"`. And the query `echo '{"input":[6,3,8]}' | kyverno jp query "sum(input)"` results in the value of `17`.
20572057

20582058
Arithmetic filters like `sum()` currently accept inputs in the following formats.
20592059

content/en/docs/writing-policies/tips.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ These are some tips and tricks you can use when putting together your Kyverno po
4040
Pattern specifies an overlay-style pattern used to check resources.
4141
```
4242

43-
* Use `kubectl get kyverno -A` to show all the Kyverno Custom Resources present in your cluster. This will return resources such as policies of various types, policy reports, and intermediary resources used internally by Kyverno.
43+
* Use `kubectl get kyverno -A` or `kubectl get crd | grep kyverno` to show all the Kyverno Custom Resources present in your cluster. This will return resources such as policies of various types, policy reports, and intermediary resources used internally by Kyverno.
4444
* When using VS Code, because of the OpenAPIV3 schema Kyverno supports, you can make use of this integration to assist in writing policy by getting field hints and describing elements.
4545
* Make use of the [Kyverno CLI](../kyverno-cli/) to test policies out in advance.
4646
* Organize your policies in a way which is meaningful to you, your organization, and your Kubernetes cluster design keeping in mind how they are processed. Each policy is processed in an idempotent manner while rules within policies are executed serially. When needing to control processing order, put highly-related rules in the same policy and use the `applyRules` field.

content/en/policies/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title = "Policies"
44

55
# Sample Policies
66

7-
The policies here are maintained by the community and are as samples that demontrate the power and flexibility of Kyverno. To use in your environment, make sure you test with the right versions of Kyverno and Kubernetes, and optimize for your use case.
7+
The policies here are maintained by the community and are as samples that demonstrate the power and flexibility of Kyverno. To use in your environment, make sure you test with the right versions of Kyverno and Kubernetes, and optimize for your use case.
88

99
Select the **Policy Type** and **Policy Category** on the left navigation, or use the search, to find the policy you need.
1010

content/en/policies/kasten/kasten-minimum-retention/kasten-minimum-retention.md

-1
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,6 @@ metadata:
2626
policies.kyverno.io/description: >-
2727
Example Kyverno policy to enforce common compliance retention standards by modifying Kasten Policy backup retention settings. Based on regulation/compliance standard requirements, uncomment (1) of the desired GFS retention schedules to mutate existing and future Kasten Policies. Alternatively, this policy can be used to reduce retention lengths to enforce cost optimization. NOTE: This example only applies to Kasten Policies with an '@hourly' frequency. Refer to Kasten documentation for Policy API specification if modifications are necessary: https://docs.kasten.io/latest/api/policies.html#policy-api-type
2828
spec:
29-
schemaValidation: false
3029
rules:
3130
- name: kasten-minimum-retention
3231
match:

content/en/policies/openshift/inject-infrastructurename/inject-infrastructurename.md

-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,6 @@ metadata:
3030
MachineSet created. This policy fetches the value of the infrastructure name from the
3131
Cluster resource and replaces all instances of TEMPLATE in a MachineSet with that name.
3232
spec:
33-
schemaValidation: false
3433
rules:
3534
- name: replace-template
3635
match:

render/go.mod

+7-7
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ module github.com/kyverno/website/render
33
go 1.21.4
44

55
require (
6-
github.com/go-git/go-billy/v5 v5.5.0
7-
github.com/go-git/go-git/v5 v5.11.0
6+
github.com/go-git/go-billy/v5 v5.6.0
7+
github.com/go-git/go-git/v5 v5.13.0
88
github.com/kyverno/kyverno v1.3.6
99
github.com/spf13/cobra v1.8.0
1010
golang.org/x/text v0.21.0
@@ -14,9 +14,9 @@ require (
1414
require (
1515
dario.cat/mergo v1.0.0 // indirect
1616
github.com/Microsoft/go-winio v0.6.1 // indirect
17-
github.com/ProtonMail/go-crypto v0.0.0-20230923063757-afb1ddc0824c // indirect
17+
github.com/ProtonMail/go-crypto v1.1.3 // indirect
1818
github.com/cloudflare/circl v1.3.7 // indirect
19-
github.com/cyphar/filepath-securejoin v0.2.4 // indirect
19+
github.com/cyphar/filepath-securejoin v0.2.5 // indirect
2020
github.com/emirpasic/gods v1.18.1 // indirect
2121
github.com/go-git/gcfg v1.5.1-0.20230307220236-3a3c6141e376 // indirect
2222
github.com/go-logr/logr v1.4.1 // indirect
@@ -30,13 +30,13 @@ require (
3030
github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
3131
github.com/modern-go/reflect2 v1.0.2 // indirect
3232
github.com/pjbgf/sha1cd v0.3.0 // indirect
33-
github.com/sergi/go-diff v1.3.1 // indirect
34-
github.com/skeema/knownhosts v1.2.1 // indirect
33+
github.com/sergi/go-diff v1.3.2-0.20230802210424-5b0b94c5c0d3 // indirect
34+
github.com/skeema/knownhosts v1.3.0 // indirect
3535
github.com/spf13/pflag v1.0.5 // indirect
3636
github.com/xanzy/ssh-agent v0.3.3 // indirect
3737
golang.org/x/crypto v0.31.0 // indirect
3838
golang.org/x/mod v0.17.0 // indirect
39-
golang.org/x/net v0.25.0 // indirect
39+
golang.org/x/net v0.33.0 // indirect
4040
golang.org/x/sync v0.10.0 // indirect
4141
golang.org/x/sys v0.28.0 // indirect
4242
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d // indirect

0 commit comments

Comments
 (0)