Skip to content

Commit 2be6e17

Browse files
committed
Update manifests
1 parent 899960d commit 2be6e17

File tree

2 files changed

+11
-117
lines changed

2 files changed

+11
-117
lines changed

bundle/manifests/limitador-operator.clusterserviceversion.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ metadata:
3737
capabilities: Basic Install
3838
categories: Integration & Delivery
3939
containerImage: quay.io/kuadrant/limitador-operator:latest
40-
createdAt: "2023-11-08T14:12:13Z"
40+
createdAt: "2023-11-15T10:55:48Z"
4141
operators.operatorframework.io/builder: operator-sdk-v1.28.1
4242
operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
4343
repository: https://github.com/Kuadrant/limitador-operator

bundle/manifests/limitador.kuadrant.io_limitadors.yaml

+10-116
Original file line numberDiff line numberDiff line change
@@ -1027,133 +1027,27 @@ spec:
10271027
redis:
10281028
properties:
10291029
configSecretRef:
1030-
description: "ObjectReference contains enough information
1031-
to let you inspect or modify the referred object. --- New
1032-
uses of this type are discouraged because of difficulty
1033-
describing its usage when embedded in APIs. 1. Ignored fields.
1034-
\ It includes many fields which are not generally honored.
1035-
\ For instance, ResourceVersion and FieldPath are both very
1036-
rarely valid in actual usage. 2. Invalid usage help. It
1037-
is impossible to add specific help for individual usage.
1038-
\ In most embedded usages, there are particular restrictions
1039-
like, \"must refer only to types A and B\" or \"UID not
1040-
honored\" or \"name must be restricted\". Those cannot be
1041-
well described when embedded. 3. Inconsistent validation.
1042-
\ Because the usages are different, the validation rules
1043-
are different by usage, which makes it hard for users to
1044-
predict what will happen. 4. The fields are both imprecise
1045-
and overly precise. Kind is not a precise mapping to a
1046-
URL. This can produce ambiguity during interpretation and
1047-
require a REST mapping. In most cases, the dependency is
1048-
on the group,resource tuple and the version of the actual
1049-
struct is irrelevant. 5. We cannot easily change it. Because
1050-
this type is embedded in many locations, updates to this
1051-
type will affect numerous schemas. Don't make new APIs
1052-
embed an underspecified API type they do not control. \n
1053-
Instead of using this type, create a locally provided and
1054-
used type that is well-focused on your reference. For example,
1055-
ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
1056-
."
1030+
description: LocalObjectReference contains enough information
1031+
to let you locate the referenced object inside the same
1032+
namespace.
10571033
properties:
1058-
apiVersion:
1059-
description: API version of the referent.
1060-
type: string
1061-
fieldPath:
1062-
description: 'If referring to a piece of an object instead
1063-
of an entire object, this string should contain a valid
1064-
JSON/Go field access statement, such as desiredState.manifest.containers[2].
1065-
For example, if the object reference is to a container
1066-
within a pod, this would take on a value like: "spec.containers{name}"
1067-
(where "name" refers to the name of the container that
1068-
triggered the event) or if no container name is specified
1069-
"spec.containers[2]" (container with index 2 in this
1070-
pod). This syntax is chosen only to have some well-defined
1071-
way of referencing a part of an object. TODO: this design
1072-
is not final and this field is subject to change in
1073-
the future.'
1074-
type: string
1075-
kind:
1076-
description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
1077-
type: string
10781034
name:
1079-
description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
1080-
type: string
1081-
namespace:
1082-
description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
1083-
type: string
1084-
resourceVersion:
1085-
description: 'Specific resourceVersion to which this reference
1086-
is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
1087-
type: string
1088-
uid:
1089-
description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
1035+
description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
1036+
TODO: Add other useful fields. apiVersion, kind, uid?'
10901037
type: string
10911038
type: object
10921039
x-kubernetes-map-type: atomic
10931040
type: object
10941041
redis-cached:
10951042
properties:
10961043
configSecretRef:
1097-
description: "ObjectReference contains enough information
1098-
to let you inspect or modify the referred object. --- New
1099-
uses of this type are discouraged because of difficulty
1100-
describing its usage when embedded in APIs. 1. Ignored fields.
1101-
\ It includes many fields which are not generally honored.
1102-
\ For instance, ResourceVersion and FieldPath are both very
1103-
rarely valid in actual usage. 2. Invalid usage help. It
1104-
is impossible to add specific help for individual usage.
1105-
\ In most embedded usages, there are particular restrictions
1106-
like, \"must refer only to types A and B\" or \"UID not
1107-
honored\" or \"name must be restricted\". Those cannot be
1108-
well described when embedded. 3. Inconsistent validation.
1109-
\ Because the usages are different, the validation rules
1110-
are different by usage, which makes it hard for users to
1111-
predict what will happen. 4. The fields are both imprecise
1112-
and overly precise. Kind is not a precise mapping to a
1113-
URL. This can produce ambiguity during interpretation and
1114-
require a REST mapping. In most cases, the dependency is
1115-
on the group,resource tuple and the version of the actual
1116-
struct is irrelevant. 5. We cannot easily change it. Because
1117-
this type is embedded in many locations, updates to this
1118-
type will affect numerous schemas. Don't make new APIs
1119-
embed an underspecified API type they do not control. \n
1120-
Instead of using this type, create a locally provided and
1121-
used type that is well-focused on your reference. For example,
1122-
ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
1123-
."
1044+
description: LocalObjectReference contains enough information
1045+
to let you locate the referenced object inside the same
1046+
namespace.
11241047
properties:
1125-
apiVersion:
1126-
description: API version of the referent.
1127-
type: string
1128-
fieldPath:
1129-
description: 'If referring to a piece of an object instead
1130-
of an entire object, this string should contain a valid
1131-
JSON/Go field access statement, such as desiredState.manifest.containers[2].
1132-
For example, if the object reference is to a container
1133-
within a pod, this would take on a value like: "spec.containers{name}"
1134-
(where "name" refers to the name of the container that
1135-
triggered the event) or if no container name is specified
1136-
"spec.containers[2]" (container with index 2 in this
1137-
pod). This syntax is chosen only to have some well-defined
1138-
way of referencing a part of an object. TODO: this design
1139-
is not final and this field is subject to change in
1140-
the future.'
1141-
type: string
1142-
kind:
1143-
description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
1144-
type: string
11451048
name:
1146-
description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
1147-
type: string
1148-
namespace:
1149-
description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
1150-
type: string
1151-
resourceVersion:
1152-
description: 'Specific resourceVersion to which this reference
1153-
is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
1154-
type: string
1155-
uid:
1156-
description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
1049+
description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
1050+
TODO: Add other useful fields. apiVersion, kind, uid?'
11571051
type: string
11581052
type: object
11591053
x-kubernetes-map-type: atomic

0 commit comments

Comments
 (0)