-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Update gateway usage #4264
Update gateway usage #4264
Conversation
🤖 Generated by lychee actionSummary
Full action output |
Apply Sweep Rules to your PR?
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4264 +/- ##
=======================================
Coverage 65.45% 65.45%
=======================================
Files 8 8
Lines 660 660
=======================================
Hits 432 432
Misses 180 180
Partials 48 48 ☔ View full report in Codecov by Sentry. |
📘 Preview documentation website |
Whoa! Easy there, Partner!This PR is too big. Please break it up into smaller PRs. |
1. Update NGINX ingress annotations. 2. Remove usage references to APISIX. Signed-off-by: zzjin <tczzjin@gmail.com>
Moved from ingress gateway annotation to backend server decide. Signed-off-by: zzjin <tczzjin@gmail.com>
Signed-off-by: zzjin <tczzjin@gmail.com>
Remove static-cdn image. Remove adminer zalando support. Signed-off-by: zzjin <tczzjin@gmail.com>
Signed-off-by: zzjin <tczzjin@gmail.com>
applaunchpad等ingress变了,sealos cloud部署脚本中是不是需要使用higress作为网关? 有影响吗? |
Applaunchpad and other ingress have changed. Is it necessary to use higress as the gateway in the sealos cloud deployment script? Is there any impact? |
不需要改应用代码,安装 higress的时候会改写参数,让 higress 监听所有 class=nginx 的资源,但是需要 run 一下 higress 的集群镜像(todo) |
No, when installing higress, the parameters will be rewritten to allow higress to monitor all resources with class=nginx |
🤖 Generated by Copilot at 523a9f5
Summary
🚫🚀🐛
Removed APISIX support from the
Adminer
andTerminal
controllers and their related resources. Simplified the ingress configuration and code for these controllers and the registry service. Updated the documentation and CRDs accordingly.Walkthrough
createNginxIngress
function incontrollers/db/adminer/controllers/ingress.go
(link, link, link)path
field from/()(.*)
to/
in theingress.yaml
sections indocs/4.0/docs/quick-start/app-deployments/use-terminal.md
anddocs/4.0/i18n/zh-Hans/quick-start/app-deployments/use-terminal.md
to fix a redirection issue with the terminal service (link, link)rewrite-target
annotation from theingress.yaml
files incontrollers/db/adminer/controllers/ingress.go
,controllers/terminal/controllers/ingress.go
, anddeploy/registry/manifests/ingress.yaml
, as it is not needed for the adminer, terminal, and registry services ( link, link)configuration-snippet
andAuthType
constants from theingress.go
files incontrollers/db/adminer/controllers/ingress.go
andcontrollers/terminal/controllers/ingress.go
, as they are not used by the adminer and terminal controllers (link, link, link, link)time
package import from theingress.go
files incontrollers/db/adminer/controllers/ingress.go
andcontrollers/terminal/controllers/ingress.go
, as it is no longer needed (link, link)defaultNginxConfigurationSnippet
to usefmt.Sprintf
instead of string concatenation incontrollers/db/adminer/controllers/ingress.go
for readability and maintainability (link)ingress.go
file incontrollers/db/adminer/controllers/ingress.go
(link)