(update benefit to fedora) |
(change openshift to kubernetes) |
||
Line 23: | Line 23: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= | = Kubernetes modules <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
Create modules for all supported | Create modules for all supported Kubernetes versions. | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. | ||
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". --> | Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". --> | ||
Line 61: | Line 61: | ||
== Detailed Description == | == Detailed Description == | ||
Currently, the | Currently, the Kubernetes upstream project develops and supports multiple versions of Kubernetes, along with component tools like cri-o/cri-tools which have their versions tightly coupled to OpenShift versions. This change will result in creation of module builds which will contain the rpms for Kubernetes / cri-o and other required tools. | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Ability to support/switch between multiple | Ability to support/switch between multiple Kubernetes versions with minimal effort on the user's part would make both users and maintainers happy. | ||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | ||
Line 97: | Line 97: | ||
== Scope == | == Scope == | ||
* Proposal owners: Creation / review / koji builds of | * Proposal owners: Creation / review / koji builds of Kubernetes modules | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
Revision as of 20:07, 24 July 2018
Kubernetes modules
Summary
Create modules for all supported Kubernetes versions.
Owner
- Name: Lokesh Mandvekar
- Email: lsm5@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2018-07-24
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Currently, the Kubernetes upstream project develops and supports multiple versions of Kubernetes, along with component tools like cri-o/cri-tools which have their versions tightly coupled to OpenShift versions. This change will result in creation of module builds which will contain the rpms for Kubernetes / cri-o and other required tools.
Benefit to Fedora
Ability to support/switch between multiple Kubernetes versions with minimal effort on the user's part would make both users and maintainers happy.
Scope
- Proposal owners: Creation / review / koji builds of Kubernetes modules
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
Users will be able to quickly setup OpenShift environments and switch between versions.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)