Skip to content

Commit db0d856

Browse files
Merge branch 'main' into feat/security-config
2 parents e517f53 + e510521 commit db0d856

8 files changed

Lines changed: 454 additions & 392 deletions

File tree

Cargo.lock

Lines changed: 111 additions & 98 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.nix

Lines changed: 305 additions & 260 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,14 @@ edition = "2024"
1010
repository = "https://github.com/stackabletech/opensearch-operator"
1111

1212
[workspace.dependencies]
13-
stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.105.0", features = ["telemetry", "versioned", "webhook"] }
13+
stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.106.1", features = ["telemetry", "versioned", "webhook"] }
1414

1515
built = { version = "0.8.0", features = ["chrono", "git2"] }
1616
clap = "4.5"
1717
futures = { version = "0.3", features = ["compat"] }
1818
pretty_assertions = "1.4"
1919
regex = "1.11"
2020
rstest = "0.26"
21-
schemars = { version = "1.0.0", features = ["url2"] } # same as in operator-rs
2221
serde = { version = "1.0", features = ["derive"] }
2322
serde_json = "1.0"
2423
snafu = "0.8"
@@ -27,5 +26,5 @@ tokio = { version = "1.47", features = ["full"] }
2726
tracing = "0.1"
2827
uuid = "1.18"
2928

30-
#[patch."https://github.com/stackabletech/operator-rs"]
29+
[patch."https://github.com/stackabletech/operator-rs"]
3130
# stackable-operator = { git = "https://github.com/stackabletech//operator-rs.git", branch = "main" }

crate-hashes.json

Lines changed: 14 additions & 14 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

extra/crds.yaml

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1346,11 +1346,12 @@ spec:
13461346
- ERROR
13471347
- FATAL
13481348
- NONE
1349+
- null
13491350
nullable: true
13501351
type: string
13511352
type: object
13521353
custom:
1353-
description: Log configuration provided in a ConfigMap
1354+
description: Custom log configuration provided in a ConfigMap
13541355
properties:
13551356
configMap:
13561357
description: ConfigMap containing the log configuration files
@@ -1373,6 +1374,7 @@ spec:
13731374
- ERROR
13741375
- FATAL
13751376
- NONE
1377+
- null
13761378
nullable: true
13771379
type: string
13781380
type: object
@@ -1392,6 +1394,7 @@ spec:
13921394
- ERROR
13931395
- FATAL
13941396
- NONE
1397+
- null
13951398
nullable: true
13961399
type: string
13971400
type: object
@@ -1459,15 +1462,15 @@ spec:
14591462
Cores are specified either as a decimal point number or as milli units.
14601463
For example:`1.5` will be 1.5 cores, also written as `1500m`.
14611464
nullable: true
1462-
type: string
1465+
x-kubernetes-int-or-string: true
14631466
min:
14641467
description: |-
14651468
The minimal amount of CPU cores that Pods need to run.
14661469
Equivalent to the `request` for Pod resource configuration.
14671470
Cores are specified either as a decimal point number or as milli units.
14681471
For example:`1.5` will be 1.5 cores, also written as `1500m`.
14691472
nullable: true
1470-
type: string
1473+
x-kubernetes-int-or-string: true
14711474
type: object
14721475
memory:
14731476
properties:
@@ -1480,7 +1483,7 @@ spec:
14801483
For example, the following represent roughly the same value:
14811484
`128974848, 129e6, 129M, 128974848000m, 123Mi`
14821485
nullable: true
1483-
type: string
1486+
x-kubernetes-int-or-string: true
14841487
runtimeLimits:
14851488
description: Additional options that can be specified.
14861489
type: object
@@ -1494,7 +1497,7 @@ spec:
14941497
capacity:
14951498
description: "Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.\n\nThe serialization format is:\n\n``` <quantity> ::= <signedNumber><suffix>\n\n\t(Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)\n\n<digit> ::= 0 | 1 | ... | 9 <digits> ::= <digit> | <digit><digits> <number> ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign> ::= \"+\" | \"-\" <signedNumber> ::= <number> | <sign><number> <suffix> ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI> ::= Ki | Mi | Gi | Ti | Pi | Ei\n\n\t(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)\n\n<decimalSI> ::= m | \"\" | k | M | G | T | P | E\n\n\t(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)\n\n<decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```\n\nNo matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.\n\nWhen a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.\n\nBefore serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:\n\n- No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.\n\nThe sign will be omitted unless the number is negative.\n\nExamples:\n\n- 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"\n\nNote that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.\n\nNon-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)\n\nThis format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation."
14961499
nullable: true
1497-
type: string
1500+
x-kubernetes-int-or-string: true
14981501
selectors:
14991502
description: A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
15001503
nullable: true
@@ -1712,11 +1715,12 @@ spec:
17121715
- ERROR
17131716
- FATAL
17141717
- NONE
1718+
- null
17151719
nullable: true
17161720
type: string
17171721
type: object
17181722
custom:
1719-
description: Log configuration provided in a ConfigMap
1723+
description: Custom log configuration provided in a ConfigMap
17201724
properties:
17211725
configMap:
17221726
description: ConfigMap containing the log configuration files
@@ -1739,6 +1743,7 @@ spec:
17391743
- ERROR
17401744
- FATAL
17411745
- NONE
1746+
- null
17421747
nullable: true
17431748
type: string
17441749
type: object
@@ -1758,6 +1763,7 @@ spec:
17581763
- ERROR
17591764
- FATAL
17601765
- NONE
1766+
- null
17611767
nullable: true
17621768
type: string
17631769
type: object
@@ -1825,15 +1831,15 @@ spec:
18251831
Cores are specified either as a decimal point number or as milli units.
18261832
For example:`1.5` will be 1.5 cores, also written as `1500m`.
18271833
nullable: true
1828-
type: string
1834+
x-kubernetes-int-or-string: true
18291835
min:
18301836
description: |-
18311837
The minimal amount of CPU cores that Pods need to run.
18321838
Equivalent to the `request` for Pod resource configuration.
18331839
Cores are specified either as a decimal point number or as milli units.
18341840
For example:`1.5` will be 1.5 cores, also written as `1500m`.
18351841
nullable: true
1836-
type: string
1842+
x-kubernetes-int-or-string: true
18371843
type: object
18381844
memory:
18391845
properties:
@@ -1846,7 +1852,7 @@ spec:
18461852
For example, the following represent roughly the same value:
18471853
`128974848, 129e6, 129M, 128974848000m, 123Mi`
18481854
nullable: true
1849-
type: string
1855+
x-kubernetes-int-or-string: true
18501856
runtimeLimits:
18511857
description: Additional options that can be specified.
18521858
type: object
@@ -1860,7 +1866,7 @@ spec:
18601866
capacity:
18611867
description: "Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.\n\nThe serialization format is:\n\n``` <quantity> ::= <signedNumber><suffix>\n\n\t(Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)\n\n<digit> ::= 0 | 1 | ... | 9 <digits> ::= <digit> | <digit><digits> <number> ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign> ::= \"+\" | \"-\" <signedNumber> ::= <number> | <sign><number> <suffix> ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI> ::= Ki | Mi | Gi | Ti | Pi | Ei\n\n\t(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)\n\n<decimalSI> ::= m | \"\" | k | M | G | T | P | E\n\n\t(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)\n\n<decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```\n\nNo matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.\n\nWhen a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.\n\nBefore serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:\n\n- No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.\n\nThe sign will be omitted unless the number is negative.\n\nExamples:\n\n- 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"\n\nNote that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.\n\nNon-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)\n\nThis format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation."
18621868
nullable: true
1863-
type: string
1869+
x-kubernetes-int-or-string: true
18641870
selectors:
18651871
description: A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
18661872
nullable: true

rust/operator-binary/Cargo.toml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,6 @@ stackable-operator.workspace = true
1515
clap.workspace = true
1616
futures.workspace = true
1717
regex.workspace = true
18-
schemars.workspace = true
1918
serde.workspace = true
2019
serde_json.workspace = true
2120
snafu.workspace = true

0 commit comments

Comments
 (0)