Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add support in rad app graph for Kubernetes interop service-service communication #7340

Open
1 task done
willdavsmith opened this issue Mar 15, 2024 · 3 comments
Open
1 task done

Add support in rad app graph for Kubernetes interop service-service communication #7340

willdavsmith opened this issue Mar 15, 2024 · 3 comments
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged

Comments

@willdavsmith
Copy link
Contributor

willdavsmith commented Mar 15, 2024 •
edited
Loading

Overview of feature request

Today, for the Kubernetes interop scenario, we have labels that specify the connections between resources. Today, this is limited to recipe resources, so is missing service to service connections (e.g. frontend container and backend container).

https://docs.radapp.io/tutorials/helm/#step-6-add-connection

Acceptance criteria

  • I can specify a connection between services with Kubernetes labels and rad app graph will reflect the correct data.

Additional context

https://docs.radapp.io/tutorials/add-radius/

Would you like to support us?

  • Yes, I would like to support you

AB#11526
@willdavsmith willdavsmith added the feature This issue describes a feature request in Radius label Mar 15, 2024
@radius-triage-bot
Copy link

👋 @willdavsmith Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@willdavsmith willdavsmith changed the title Add application graph support for Kubernetes resources (incremental adoption) Add application graph support for Kubernetes interop resources Mar 15, 2024
@willdavsmith willdavsmith changed the title Add application graph support for Kubernetes interop resources Add support in rad app graph for Kubernetes interop service-service communication Mar 18, 2024
@sylvainsf sylvainsf added the triaged This issue has been reviewed and triaged label Mar 18, 2024
@radius-triage-bot
Copy link

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@sylvainsf sylvainsf removed the triaged This issue has been reviewed and triaged label Mar 18, 2024
@nicolejms nicolejms added the triaged This issue has been reviewed and triaged label Mar 28, 2024
@radius-triage-bot
Copy link

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sylvainsf @willdavsmith @nicolejms