20 lines
799 B
Markdown
20 lines
799 B
Markdown
|
---
|
||
|
title: Upstream (disambiguation)
|
||
|
id: upstream
|
||
|
date: 2018-04-12
|
||
|
full_link:
|
||
|
short_description: >
|
||
|
May refer to: core Kubernetes or the source repo from which a repo was forked.
|
||
|
|
||
|
aka:
|
||
|
tags:
|
||
|
- community
|
||
|
---
|
||
|
May refer to: core Kubernetes or the source repo from which a repo was forked.
|
||
|
|
||
|
<!--more-->
|
||
|
|
||
|
* In the **Kubernetes Community**: Conversations often use *upstream* to mean the core Kubernetes codebase, which the general ecosystem, other code, or third-party tools relies upon. For example, [community members](#term-member) may suggest that a feature is moved upstream so that it is in the core codebase instead of in a plugin or third-party tool.
|
||
|
* In **GitHub** or **git**: The convention is to refer to a source repo as *upstream*, whereas the forked repo is considered *downstream*.
|
||
|
|