openyurt-bot
commented
2 years ago @JameKeal: GitHub didn't allow me to assign the following users: your_reviewer.
Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to [this](https://github.com/openyurtio/yurt-app-manager/pull/54):
>
>
>
>#### What type of PR is this?
>> /kind bug
>
>
>
>#### What this PR does / why we need it:
>When I deploy yurt-app-manager, and the cluster is also have some uniteddeployment, the yurt-app-manager is not run success, the error is:
>
>
>
>The reason is `ud.Spec.RevisionHistoryLimit` is not exist, but the code use it's pointer to get the value.
>
>#### Which issue(s) this PR fixes:
>
>Fixes #
>
>#### Special notes for your reviewer:
>
>
>
>#### Does this PR introduce a user-facing change?
>
>```release-note
>
>```
>
>#### other Note
>
>
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
rambohe-ch
What type of PR is this?
What this PR does / why we need it:
When I deploy yurt-app-manager, and the cluster is also have some uniteddeployment, the yurt-app-manager is not run success, the error is:
The reason is
ud.Spec.RevisionHistoryLimitis not exist, but the code use it's pointer to get the value.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
other Note