-
Notifications
You must be signed in to change notification settings - Fork 353
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
Take a look at service binding #1445
Comments
Thats hot! |
I can take a look at this |
@johnpoth would be nice to have sort of proposal, like https://github.com/apache/camel-k/blob/master/proposals/monitoring-security.adoc so it can be turned into a documentation soon or later. |
Sounds good! I'll create one once I have more visibility on this. Creating a small MVP at the moment |
Do you have any graph visualization tools you recommend for the camel-k proposals/docs ? |
I've used http://lucidchart.com for the diagrams in the secured monitoring proposal. I recommend it, though you may have to request a corporate license. Other tools can be used, and you can even try tools like https://github.com/ivanceras/svgbob 😄. |
…ow ServiceBinding trait on all profiles (apache#1445)
…ow ServiceBinding trait on all profiles (apache#1445)
…ow ServiceBinding trait on all profiles (apache#1445)
…ow ServiceBinding trait on all profiles (#1445)
Closed with #1952 , thanks ! |
https://application-stacks.github.io/service-binding-specification/
It provides a clean way by which we can connect to services in the same cluster without the users having to provide credentials and all that stuff.
We can e.g.
(did I already write a similar issue in the past?)
And have your Camel K operator resolve the connection details for the database and inject them into the integration pod, e.g. making a JDBC connection available in the registry.
The same for other brokers or Kafka.
The text was updated successfully, but these errors were encountered: