template: Add a section for OKE #1883
Conversation
* guidelines/enhancement_template.md: Add a section on OpenShift Kubernetes Engine.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
@Miciah: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
| behaviors also be exposed to MicroShift admins through the | ||
| configuration file for MicroShift? | ||
|
|
||
| #### OpenShift Kubernetes Engine |
There was a problem hiding this comment.
Is there an easy way to work out what is in OKE that isn't in OCP?
There was a problem hiding this comment.
Good point—to some extent, you (the EP author or reviewer) just need to know, same as for HCP and MicroShift. However, at a high level, this documentation might be useful: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/overview/oke-about#about_oke_similarities_and_differences
|
Inactive enhancement proposals go stale after 28d of inactivity. See https://github.com/openshift/enhancements#life-cycle for details. Mark the proposal as fresh by commenting If this proposal is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
4 participants
Add a section on OpenShift Kubernetes Engine (OKE) to the enhancement-proposal template.
OpenShift Kubernetes Engine is a product offering that offers a subset of the features that are included in OpenShift Container Platform (OCP). It is important to consider whether an enhancement depends on a feature that is part of OCP but not part of OKE.