-
Notifications
You must be signed in to change notification settings - Fork 365
chore: log when kubernetes cluster version does not meet minimum requirement #2693
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
Conversation
Signed-off-by: Ashing Zheng <axingfly@gmail.com>
Signed-off-by: Ashing Zheng <axingfly@gmail.com>
Signed-off-by: Ashing Zheng <axingfly@gmail.com>
internal/manager/run.go
Outdated
| } | ||
|
|
||
| func checkK8sVersion(mgr ctrl.Manager, logger logr.Logger) { | ||
| const minVersion = "1.26.0" |
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.
Maybe we can pass parameters during code compilation. What do you think? Similar to version.
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.
updated.
|
Test cases that cause errors are not within the scope of local modifications. |
Type of change:
What this PR does / why we need it:
Optimize the ingress documentation and clearly inform the reasons for relying on the 1.26+ cluster version
When ingress starts and detects that the cluster version does not meet the requirements, it prints a warning log to alert the user
Pre-submission checklist: