Adjust diagrams; fix binding creation description

kyma-project · Dec 11, 2024 · bf17b16 · bf17b16
1 parent ed206ca
commit bf17b16
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/assets/bindings-create-flow.drawio.svg b/docs/assets/bindings-create-flow.drawio.svg
diff --git a/docs/assets/bindings-delete-flow.drawio.svg b/docs/assets/bindings-delete-flow.drawio.svg
diff --git a/docs/assets/bindings-get-flow.drawio.svg b/docs/assets/bindings-get-flow.drawio.svg
diff --git a/docs/user/05-60-kyma-bindings.md b/docs/user/05-60-kyma-bindings.md
@@ -56,7 +56,7 @@ If the limit is not exceeded and the binding does not exist in the database, KEB
 In the binding creation phase, KEB creates a service binding object and generates a kubeconfig file with a JWT token. The kubeconfig file is valid for a specified period, defaulted or set in the request body. 
 
 > [!NOTE]
->  Expired bindings do not count towards the bindings limit. However, they prevent creating new bindings until they exist in the database. Only after they are removed by the cleanup job or manually can the binding be recreated again.
+>  Expired bindings do not count towards the bindings limit. However, they prevent creating new bindings with the same ID until they exist in the database. Only after they are removed by the cleanup job or manually can the binding be recreated again.
 
 After the insert has been done, KEB creates ServiceAccount, ClusterRole (administrator privileges), and ClusterRoleBinding, all named `kyma-binding-{{binding_id}}`. You can use the ClusterRole to modify permissions granted to the kubeconfig.