-
Notifications
You must be signed in to change notification settings - Fork 456
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
Propose: add the KubeVela project as a integration #1131
Conversation
|
Welcome @barnettZQG! |
Hi @barnettZQG. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hey @barnettZQG, thanks for the PR! Trying to understand how this integration works, could it be used with any Gateway API implementation or is it really just tied to Traefik? So far the integrations we have listed can be used with any implementation of the API. |
@robscott thanks for your reply, we provide the user's APIs (the trait in OAM, including |
Hey @barnettZQG, I brought this up in today's community meeting, some notes:
I'm going to work on a PR to resolve the first item. It sounds like you're going to add support for additional Gateway API implementations soon, maybe we can just leave this PR open until KubeVela is able to support more than Traefik? |
@robscott OK, we will do it. |
Signed-off-by: barnettZQG <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: barnettZQG The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@robscott Hi, I am sorry to update it after a long time. Currently, we make an addon based on the Gateway API and provide two implementation addons. Traefik and Istio Gateway. Based on the same user-side experience, we could integrate more implementations. |
@barnettZQG: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
||
[KubeVela][kubevela] is a modern software delivery platform that makes deploying and operating applications across today's hybrid, multi-cloud environments easier, faster and more reliable. | ||
|
||
KubeVela using the Gateway API provides the standard management ability regarding the application access rules. It currently publishes a [gateway-traits][addon] to provide the user API. There are two implementation addon, [Traefik][traefik] and [Istio gateway][istio]. You can refer to the [installation document][document] to install the KubeVela and enable the gateway-traits addon. |
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.
A small typo.
KubeVela using the Gateway API provides the standard management ability regarding the application access rules. It currently publishes a [gateway-traits][addon] to provide the user API. There are two implementation addon, [Traefik][traefik] and [Istio gateway][istio]. You can refer to the [installation document][document] to install the KubeVela and enable the gateway-traits addon. | |
KubeVela using the Gateway API provides the standard management ability regarding the application access rules. It currently publishes a [gateway-traits][addon] to provide the user API. There are two implementation addons, [Traefik][traefik] and [Istio gateway][istio]. You can refer to the [installation document][document] to install the KubeVela and enable the gateway-traits addon. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/lgtm Need to resolve some conflicts and a rebase. |
@barnettZQG: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/hold after kubevela/catalog#598 gets finished. |
I see we're waiting on kubevela/catalog#598 before this PR can move forward. Looking at that issue it appears there is a significant amount of work that needs to be completed. Any thoughts on maybe closing this PR for the moment, so it doesn't have to linger, and then opening a PR when this is ready? |
@shaneutt OK. I will open a new PR after kubevela/catalog#598 is complete. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
The KubeVela community focuses on the practice of application specification, and we agree with the Gateway API in terms of the application gateway rules, so we integrate the specification.
Does this PR introduce a user-facing change?:
NONE