kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3537 from lbragstad/fix-broken-link 

Update links in api conventions document
This commit is contained in:
Kubernetes Prow Robot 2019-03-29 14:24:47 -07:00 committed by GitHub
parent 143d277e0c 702d10d7a4
commit 20c1e33a74
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
contributors/devel/sig-architecture/api-conventions.md
View File

@ -379,7 +379,7 @@ Some resources in the v1 API contain fields called **`phase`**, and associated
`message`, `reason`, and other status fields. The pattern of using `phase` is `message`, `reason`, and other status fields. The pattern of using `phase` is
deprecated. Newer API types should use conditions instead. Phase was deprecated. Newer API types should use conditions instead. Phase was
essentially a state-machine enumeration field, that contradicted [system-design essentially a state-machine enumeration field, that contradicted [system-design
principles](../design-proposals/architecture/principles.md#control-logic) and principles](../../design-proposals/architecture/principles.md#control-logic) and
hampered evolution, since [adding new enum values breaks backward hampered evolution, since [adding new enum values breaks backward
compatibility](api_changes.md). Rather than encouraging clients to infer compatibility](api_changes.md). Rather than encouraging clients to infer
implicit properties from phases, we prefer to explicitly expose the individual implicit properties from phases, we prefer to explicitly expose the individual
@ -404,7 +404,7 @@ only provided with reasonable effort, and is not guaranteed to not be lost.
Status information that may be large (especially proportional in size to Status information that may be large (especially proportional in size to
collections of other resources, such as lists of references to other objects -- collections of other resources, such as lists of references to other objects --
see below) and/or rapidly changing, such as see below) and/or rapidly changing, such as
[resource usage](../design-proposals/scheduling/resources.md#usage-data), should be put into separate [resource usage](../../design-proposals/scheduling/resources.md#usage-data), should be put into separate
objects, with possibly a reference from the original object. This helps to objects, with possibly a reference from the original object. This helps to
ensure that GETs and watch remain reasonably efficient for the majority of ensure that GETs and watch remain reasonably efficient for the majority of
clients, which may not need that data. clients, which may not need that data.