anchor.diff:  
   === Automatic service binding
   
  -The `quarkus-kubernetes-service-binding` extension can automatically generate the `ServiceBinding` resource after detecting that an application requires access to external services provided by available bindable Operators.
  -
  -NOTE: Automatic service binding can be generated for a limited number of service types, or as this chapter addresses with the respect to Kubernetes dictionary, kinds.
  +The `quarkus-kubernetes-service-binding` extension can generate the `ServiceBinding` resource automatically after detecting that an application requires access to the external services that are provided by available bindable Operators.
  +
  +NOTE: Automatic service binding can be generated for a limited number of service types. To be consistent with established terminology for Kubernetes and Quarkus services, this chapter refers to these service types as kinds.
   
   .Operators that support the service auto-binding
   [%autowidth,%noheader,stripes=even]
  
positive.code: quarkus.datasource.db-kind=postgresql
  ----
  
  The above configuration, combined with the presence of `quarkus-datasource`, `quarkus-jdbc-postgresql`, `quarkus-kubernetes`, and `quarkus-kubernetes-service-binding` properties in the application results in the generation of  the `ServiceBinding` resource for the the `postgresql` database type.
  
  By using the `apiVersion` and `kind` properties of the Operator resource, which matches the used `postgresql` Operator, the generated `ServiceBinding` resource binds the service/resource to the application.
  
  The `db-kind` is used by default when the configured datasource remains unnamed.
  
  [source,yaml]
  ----
  
negative.code: 
  The `service key` is usually the name of the service, for example the name of the datasource, or the name of the `mongo` client. When this value is not available, the datasource type, such as `postgresql`, `mysql`, `mongo`, is used instead.
  
  To avoid naming conflicts between different types of services, prefix the `service key` with a specific datasource type, such as `postgresql-__<person>__`.
  
  The following example shows how to customize the `apiVersion` property of the `PostgresCluster` resource:
  
  [source,properties]
  ----
  