Describe the bug
I was trying to upgrade to kcp 0.28.0 and noticed that during my tests, APIBindings are not accepted anymore.
Steps To Reproduce
- Start a kcp on version 0.28.0.
- Apply the
apibinding.yaml from below.
Expected Behaviour
The APIBinding should be accepted and stored internally as v1alpha2.
Instead I receive
The APIBinding "foo" is invalid:
* spec.permissionClaims[0]: Invalid value: "object": either "all" or "resourceSelector" must be set
* spec.permissionClaims[1]: Invalid value: "object": either "all" or "resourceSelector" must be set
* spec.permissionClaims[2]: Invalid value: "object": either "all" or "resourceSelector" must be set
Additional Context
apibinding.yaml:
apiVersion: apis.kcp.io/v1alpha1
kind: APIBinding
metadata:
name: foo
spec:
reference:
export:
path: root
name: cache.kcp.io
permissionClaims:
- group: ""
resource: "namespaces"
all: true
state: Accepted
- group: ""
resource: "secrets"
all: true
state: Accepted
- group: ""
resource: "configmaps"
all: true
state: Accepted
Describe the bug
I was trying to upgrade to kcp 0.28.0 and noticed that during my tests, APIBindings are not accepted anymore.
Steps To Reproduce
apibinding.yamlfrom below.Expected Behaviour
The APIBinding should be accepted and stored internally as v1alpha2.
Instead I receive
Additional Context
apibinding.yaml: