Skip to content

Commit 6a1defc

Browse files
committed
Update manifests
1 parent 6948750 commit 6a1defc

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
@@ -36,7 +36,7 @@ metadata:
3636
capabilities: Basic Install
3737
categories: Integration & Delivery
3838
containerImage: quay.io/kuadrant/limitador-operator:latest
39-
createdAt: "2023-09-27T14:09:01Z"
39+
createdAt: "2023-11-15T10:55:48Z"
4040
operators.operatorframework.io/builder: operator-sdk-v1.28.1
4141
operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
4242
repository: https://github.com/Kuadrant/limitador-operator

bundle/manifests/limitador.kuadrant.io_limitadors.yaml

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

0 commit comments

Comments
 (0)