Results 13 comments of Ray Chang

Self-test Longhorn can be deployed normally with the modified values.yaml. ![image](https://user-images.githubusercontent.com/17548901/191733727-cc1c2cb8-0216-41b6-885c-cb010518f661.png)

In current version, the default value of `successfulJobsHistoryLimit` in Longhorn will be `1` . So I think we can make the parameter configurable. ![image](https://user-images.githubusercontent.com/17548901/191757044-c0e76ff5-d221-45f4-9a51-6b16ddd01a3b.png)

I can reproduce it in my environment. ![image](https://user-images.githubusercontent.com/17548901/197149806-59327f21-0998-4875-8eb5-a0ffc0631715.png) I think it could have a logic to check the setting value was applied, if so then do not validation the value....

- [x] What is the name of the project you maintain? - The projects under [Longhorn.io](https://github.com/longhorn), like Longhorn-manager and Longhorn-engine - [x] What is the URL to your GitHub repository?...

If I add output log with stdout in manager shutdown function to implement gracefully shutdown, am I right? https://github.com/longhorn/longhorn-share-manager/pkg/server/share_manager.go

I tried deploying with `longhorn.yaml` in the master branch and I can start `share-manger` without restarting. ![image](https://user-images.githubusercontent.com/17548901/189929100-de495f32-3910-4203-ae74-390a4a63e93e.png)

Upon closer inspection, I found that it was because I didn't fix completely in the first time, so I send the [2nd PR](https://github.com/longhorn/longhorn-share-manager/pull/41) to fix, and I think it was...

Self-test `longhornio/longhorn-share-manager:v1_20220914` works in my environment. ![image](https://user-images.githubusercontent.com/17548901/190156624-42fb2d43-7bd4-4ecc-9669-031aaa2d544d.png)

According to the conclusion of the last meeting, since the fs type will continue to be backported in the Linux kernel. So the task will add a check function to...

I think this is one of the things that can happen to users. The delete would fail probably because the snapshot/backup could not be created. However, the reason still needs...