|
38 | 38 | FeatureFlagConfiguration |
39 | 39 | properties: |
40 | 40 | featureFlagSpec: |
41 | | - description: Foo is an example field of FeatureFlagConfiguration. |
42 | | - Edit featureflagconfiguration_types.go to remove/update |
| 41 | + description: FeatureFlagSpec is the json representation of the feature |
| 42 | + flag |
43 | 43 | type: string |
| 44 | + provider: |
| 45 | + description: 'INSERT ADDITIONAL SPEC FIELDS - desired state of cluster |
| 46 | + Important: Run "make" to regenerate code after modifying this file' |
| 47 | + properties: |
| 48 | + credentials: |
| 49 | + description: 'ObjectReference contains enough information to let |
| 50 | + you inspect or modify the referred object. --- New uses of this |
| 51 | + type are discouraged because of difficulty describing its usage |
| 52 | + when embedded in APIs. 1. Ignored fields. It includes many |
| 53 | + fields which are not generally honored. For instance, ResourceVersion |
| 54 | + and FieldPath are both very rarely valid in actual usage. 2. |
| 55 | + Invalid usage help. It is impossible to add specific help for |
| 56 | + individual usage. In most embedded usages, there are particular |
| 57 | + restrictions like, "must refer only to types A and B" or "UID |
| 58 | + not honored" or "name must be restricted". Those cannot be well |
| 59 | + described when embedded. 3. Inconsistent validation. Because |
| 60 | + the usages are different, the validation rules are different |
| 61 | + by usage, which makes it hard for users to predict what will |
| 62 | + happen. 4. The fields are both imprecise and overly precise. Kind |
| 63 | + is not a precise mapping to a URL. This can produce ambiguity |
| 64 | + during interpretation and require a REST mapping. In most cases, |
| 65 | + the dependency is on the group,resource tuple and the version |
| 66 | + of the actual struct is irrelevant. 5. We cannot easily change |
| 67 | + it. Because this type is embedded in many locations, updates |
| 68 | + to this type will affect numerous schemas. Don''t make new |
| 69 | + APIs embed an underspecified API type they do not control. Instead |
| 70 | + of using this type, create a locally provided and used type |
| 71 | + that is well-focused on your reference. For example, ServiceReferences |
| 72 | + for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 |
| 73 | + .' |
| 74 | + properties: |
| 75 | + apiVersion: |
| 76 | + description: API version of the referent. |
| 77 | + type: string |
| 78 | + fieldPath: |
| 79 | + description: 'If referring to a piece of an object instead |
| 80 | + of an entire object, this string should contain a valid |
| 81 | + JSON/Go field access statement, such as desiredState.manifest.containers[2]. |
| 82 | + For example, if the object reference is to a container within |
| 83 | + a pod, this would take on a value like: "spec.containers{name}" |
| 84 | + (where "name" refers to the name of the container that triggered |
| 85 | + the event) or if no container name is specified "spec.containers[2]" |
| 86 | + (container with index 2 in this pod). This syntax is chosen |
| 87 | + only to have some well-defined way of referencing a part |
| 88 | + of an object. TODO: this design is not final and this field |
| 89 | + is subject to change in the future.' |
| 90 | + type: string |
| 91 | + kind: |
| 92 | + description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds' |
| 93 | + type: string |
| 94 | + name: |
| 95 | + description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names' |
| 96 | + type: string |
| 97 | + namespace: |
| 98 | + description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/' |
| 99 | + type: string |
| 100 | + resourceVersion: |
| 101 | + description: 'Specific resourceVersion to which this reference |
| 102 | + is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency' |
| 103 | + type: string |
| 104 | + uid: |
| 105 | + description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids' |
| 106 | + type: string |
| 107 | + type: object |
| 108 | + name: |
| 109 | + enum: |
| 110 | + - flagD |
| 111 | + type: string |
| 112 | + required: |
| 113 | + - credentials |
| 114 | + - name |
| 115 | + type: object |
44 | 116 | type: object |
45 | 117 | status: |
46 | 118 | description: FeatureFlagConfigurationStatus defines the observed state |
|
0 commit comments