Closed Congrool closed 1 year ago
@kadisi PTAL
The reason is that the attribute revisionHistoryLimit
is missing, adding the attribute revisionHistoryLimit
to yurtappdaemon can solve the problem
@Congrool As @gbtyy 's reply, this problem has been solved. and i will close this issue.
by the way, yurtappdaemon has been migrated into yurt-manager
component, and revisionHistoryLimit will be set with a default value if it is nil. the code is here: https://github.com/openyurtio/openyurt/blob/master/pkg/yurtmanager/webhook/yurtappdaemon/v1alpha1/yurtappdaemon_default.go#L38
What happened:
yurt-app-manager is always in
CrashLoopBackOff
, and the error log:What you expected to happen:
yurt-app-manager should be in
Running
status.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
yurt-app-manager version:
And if we deploy yurt-app-manager first, then create the pool-coordinator yurtappdaemon, yurt-app-manager can work.
others
/kind bug