mirror of https://github.com/k3s-io/k3s
Brian Downs
4 years ago
committed by
GitHub
2 changed files with 46 additions and 1 deletions
@ -0,0 +1,45 @@
|
||||
<!-- HTML Comments can be left in place or removed, dealers choice. They are present simply to guide you on your pull-request journey. --> |
||||
Proposed changes |
||||
====== |
||||
<!-- |
||||
|
||||
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. |
||||
|
||||
--> |
||||
|
||||
Types of changes |
||||
====== |
||||
<!-- |
||||
|
||||
What types of changes does your code introduce to Rancher? |
||||
- Bugfix (non-breaking change which fixes an issue) |
||||
- New feature (non-breaking change which adds functionality) |
||||
- Breaking change (fix or feature that would cause existing functionality to not work as expected) |
||||
|
||||
--> |
||||
|
||||
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 relavent to this pull request. |
||||
|
||||
If you are opening a PR without a corresponding issue please consider creating one first, [here](https://github.com/rancher/k3s/issues). A functional example will greatly help QA with verifying/reproducing a bug or testing new features. |
||||
|
||||
--> |
||||
|
||||
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... |
||||
|
||||
--> |
Loading…
Reference in new issue