search

servicebinding / spec

Specification for binding services to k8s workloads
https://servicebinding.io
Apache License 2.0
92 stars 35 forks source link

Bump `service.binding/v1alpha2` to `servicebinding.io/v1alpha3` #185

Closed scothis closed 2 years ago

scothis commented 3 years ago

We have a number of significant breaking changes since RC2 that should be reflected in a new version number for resources. Implementations may choose to implement both v1alpha2 and v1alpha3.

Updated the api group from service.binding to servicebinding.io.

Resolves #113

Signed-off-by: Scott Andrews andrewssc@vmware.com

pedjak commented 2 years ago

I find placing binding in front of servicebinding.io redundant. Could we go simply with servicebinding.io instead? Tekton uses tekton.dev as the group name for example. If we really want a prefix, how about then something like core, to emphasize what is core API, and what are extensions?

scothis commented 2 years ago

The original request to use binding.servicebinding.io came from @baijum. With the intent that we can also define mappings.servicebinding.io or other groups as siblings rather than as sub groups.

I'm fine with either binding.servicebinding.io or servicebinding.io, but would like to avoid core.servicebinding.io.

nebhale commented 2 years ago

2 September WG: