Adding a glossary of commonly used terms #15
Conversation
The terms herein will be used in future documents that make progress toward completing kubernetes-retired#14
|
|
||
| **Application developer**: the team of people responsible for developing consumer | ||
| applications. This "team" may be one person. Additionally, it may overlap | ||
| (partially or completely) with the cluster operator team |
There was a problem hiding this comment.
@arschles if I could recommend two tweaks here:
- Change this to "application operators." Those who configure and deploy applications aren't necessarily the application's developers.
- Clarify that users in this role have some access to the k8s cluster-- i.e. at minimum, access to their own application(s) namespace(s), and presumably (except in cases of overlap with the cluster operator role) not much else. The differing levels of access is probably an important detail as we continue to document the use cases.
|
I'm good with this, if @krancour's comment is addressed. |
|
agree with @krancour's comments. |
|
I think more CLAs are needed. |
|
@arschles and I should both be all set CLA-wise. Not sure what's going on here. |
|
@krancour I know Google's CLAbot didn't work on PRs with commits from multiple authors. Perhaps this is also the case with the LF CLAbot. |
| **Resource**: a specific instantiation of an aforementioned resource type, | ||
| often represented as a YAML or JSON file that is submitted or retrieved via the | ||
| standard Kubernetes API (or via `kubectl`) | ||
|
|
There was a problem hiding this comment.
@bgrant0607 when you get a chance, can you comment on whether these are correct and appropriate entries in the terminology?
|
RE @krancour's earlier comment - I am also registered under the deis org's LF CLA, and all of my PRs have failed the CLA bot. I'm guessing it's because the LF account page can't connect my GH account |
|
geez I wish we would just use DCOs :-) |
|
Superseded by #25. Closing |
Get over nil serializer hurdle
…-check Fix go version check
The terms herein will be used in future documents that make progress toward completing #14
This patch partially replaces #13
cc/ @pmorie @bgrant0607 @duglin @judkowitz @slack @MHBauer
TODO:
README.md