community
community copied to clipboard
kubernetes
api-conventions.md should explain patchStrategy
The API conventions doc should explain, or point to an explanation of, the patchStrategy stuff that appears in golang. The reader should be told how to understand the existing golang, and how to use patchStrategy when writing new golang. This should include a pointer to the definitions of what each patchStrategy means.
Adding sig-arch as well because they own the doc /sig architecture /kind documentation
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@lavalamp: Reopened this issue.
In response to this:
/reopen /lifecycle frozen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Note that we should also recommend the newer SSA version of these concepts.
I don't know if we can realistically get rid of SMP, or even officially deprecate it, at least not soon -- but it has bugs we don't intend to fix.
Mostly I find myself confused which values are available for which tags, what the semantics of them are, and how they intersect between SMP and SSA
On Wed, Mar 30, 2022 at 9:39 AM Daniel Smith @.***> wrote:
Note that we should also recommend the newer SSA version of these concepts.
I don't know if we can realistically get rid of SMP, or even officially deprecate it, at least not soon -- but it has bugs we don't intend to fix.
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/3752#issuecomment-1083370890, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKWAVCNHYLNI6WIAUPGT7LVCR7STANCNFSM4HR4OURQ . You are receiving this because you commented.Message ID: @.***>