mirror of
https://github.com/k3s-io/k3s.git
synced 2024-06-07 19:41:36 +00:00
32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
<!-- HTML Comments can be left in place or removed. -->
|
|
<!-- Please see our contributing guide at https://github.com/rancher/k3s/blob/master/CONTRIBUTING.md for guidance on opening pull requests -->
|
|
|
|
#### Proposed Changes ####
|
|
|
|
<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. -->
|
|
|
|
#### Types of Changes ####
|
|
|
|
<!-- What types of changes does your code introduce to K3s? Bugfix, New Feature, Breaking Change, etc -->
|
|
|
|
#### Verification ####
|
|
|
|
<!-- How can the changes be verified? Please provide whatever additional information necessary to help verify the proposed changes. -->
|
|
|
|
#### Linked Issues ####
|
|
|
|
<!-- Link any related issues, pull-requests, or commit hashes that are relevant to this pull request. If you are opening a PR without a corresponding issue please consider creating one first, at https://github.com/rancher/k3s/issues . A functional example will greatly help QA with verifying/reproducing a bug or testing new features. -->
|
|
|
|
#### User-Facing Change ####
|
|
<!--
|
|
Does this PR introduce a user-facing change? If no, just write "NONE" in the release-note block below.
|
|
If the PR requires additional action from users switching to the new release, include the string "action required".
|
|
-->
|
|
```release-note
|
|
|
|
```
|
|
|
|
#### Further Comments ####
|
|
|
|
<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
|