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.

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

Changes to Http2Rpc won't become effective right away #617

Closed
CH3CHO opened this issue Nov 1, 2023 · 1 comment · Fixed by #657
Closed

Changes to Http2Rpc won't become effective right away #617

CH3CHO opened this issue Nov 1, 2023 · 1 comment · Fixed by #657
Assignees

Comments

@CH3CHO
Copy link
Collaborator

CH3CHO commented Nov 1, 2023

Ⅰ. Issue Description

[AddOrUpdateHttp2Rpc](https://github.com/alibaba/higress/blob/main/pkg/ingress/config/ingress_config.go#L992) and [DeleteHttp2Rpc](https://github.com/alibaba/higress/blob/main/pkg/ingress/config/ingress_config.go#L1008C10-L1008C23) functions of IngressConfig won't trigger any MCP push, which causes creating, updating and deleting Http2Rpc resources won't become effective right away.

We should trigger corresponding MCP pushes when any changes are made to Http2Rpc resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants