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

velaux 1.9.1 not supported multiple gateway traits on a component #859

Open
Louse-luo opened this issue Jul 19, 2023 · 3 comments
Open

velaux 1.9.1 not supported multiple gateway traits on a component #859

Louse-luo opened this issue Jul 19, 2023 · 3 comments
Labels
feature help wanted Extra attention is needed

Comments

@Louse-luo
Copy link

Describe the bug

velaux 1.9.1 not supported multiple gateway traits on a component
To Reproduce

Configuring the second gateway trait through velaux, reporting an error
image

Expected behavior

Screenshots

KubeVela Version
velaux 1.9.1
CLI Version: 1.9.4
Core Version: 1.9.4
GitRevision: git-b9f1cc97
GolangVersion: go1.19.10

Additional context
@Louse-luo Louse-luo added the kind/bug Something isn't working label Jul 19, 2023
@chivalryq
Copy link
Member

dup #829

@chivalryq chivalryq added feature and removed kind/bug Something isn't working labels Jul 20, 2023
@lxkaka
Copy link

lxkaka commented Jul 21, 2023

@Louse-luo if you need multi domains for ingress, you can customize gateway

@wonderflow
Copy link
Contributor

wonderflow commented Jul 24, 2023 •
edited
Loading

Yes, this is an issue of veluax as kubevela already supported this feature. We should relax the constraints in the velaux frontend.

@wonderflow wonderflow added the help wanted Extra attention is needed label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wonderflow @lxkaka @Louse-luo @chivalryq