-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SAPBTPCFS-3288] CUSTOM TEMPLATES FOR SECRETS #408
Conversation
README.md
Outdated
@@ -286,31 +286,34 @@ SAP BTP service operator search for the credentials in the following order: | |||
|
|||
#### Service Binding | |||
|
|||
1. To get access credentials to your service instance and make it available in the cluster so that your applications can use it, create a `ServiceBinding` custom resource, and set the `serviceInstanceName` field to the name of the `ServiceInstance` resource you created. | |||
To allow applications to access a service instance in your cluster, create a `ServiceBinding` custom resource. Set the `serviceInstanceName` field within the `ServiceBinding` to match the name of the `ServiceInstance` resource you previously created. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not access the service instance, but access/consume/communicate with the service (not instance).
the terminology of the previous version was better. it is actually 'get access credentials' to consume the service.
actually mentioning the term 'credentials' here is very important, as all the service binding chapter deals with credentials.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But is it a service in the cluster? Or an instance?
The rest was changed.
README.md
Outdated
|
||
The credentials are stored in a secret created in your cluster. | ||
This `ServiceBinding` is then exposed to users through a generated output: a `Secret` resource that contains securely-stored access credentials needed to connect to the `ServiceInstance`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the service binding is not exposed to users, but the credentials are exposed.
e.g., These access credentials are then available to consuming applications through a secret resource which is generated in your cluster.....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@avilupu this was the official Kubernetes terminology. But I'll change.
README.md
Outdated
name: sample-binding | ||
spec: | ||
serviceInstanceName: sample-instance | ||
secretRootKey: your-secretRootKey-value |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use 'myBindingData'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this be myCredentialsAndInstanceData if already?? @avilupu
README.md
Outdated
spec: | ||
serviceInstanceName: sample-instance | ||
secretTemplate: your-Go-template | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is "your-Go-template"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@avilupu the applied Go template?
The used Go template?
README.md
Outdated
password: {{ .credentials.client_secret }} | ||
``` | ||
The sample-binding map on which your-Go-template operates is in the JSON format: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure I understand...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 issues still open.
README.md
Outdated
@@ -286,31 +286,34 @@ SAP BTP service operator search for the credentials in the following order: | |||
|
|||
#### Service Binding | |||
|
|||
1. To get access credentials to your service instance and make it available in the cluster so that your applications can use it, create a `ServiceBinding` custom resource, and set the `serviceInstanceName` field to the name of the `ServiceInstance` resource you created. | |||
To allow applications to access a service instance in your cluster, create a `ServiceBinding` custom resource. Set the `serviceInstanceName` field within the `ServiceBinding` to match the name of the `ServiceInstance` resource you previously created. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But is it a service in the cluster? Or an instance?
The rest was changed.
README.md
Outdated
|
||
The credentials are stored in a secret created in your cluster. | ||
This `ServiceBinding` is then exposed to users through a generated output: a `Secret` resource that contains securely-stored access credentials needed to connect to the `ServiceInstance`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@avilupu this was the official Kubernetes terminology. But I'll change.
No description provided.