Proposal: Configuration #1007
Closed
Proposal: Configuration #1007
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think this generally captures the things we want, but I think that having a number of real-world examples of things like the generator, would go a long way to making some of the concrete concepts more tangible. |
|
|
||
| ## Decomposing the configuration process | ||
|
|
||
| Where possible, the Docker image should be used to configuration of Docker and the Linux environment known at build time, such as exposed ports, expected volumes, the entry point, capabilities required for correct operation of the application, and so on. This document will focus on configuration of objects managed by Kubernetes and its ecosystem. |
There was a problem hiding this comment.
the Docker image should be used to configuration of Docker and the Linux environment
to configure?
|
|
||
| Furthermore, with Kubernetes, we’re trying to encourage an open ecosystem of composable systems and layered APIs. Kubernetes will also support plug-ins for a variety of functionality. If you find your use case requires complex configuration transformations, that suggests a missing ecosystem component or plug-in. We encourage you to help the community build that missing mechanism as opposed to proliferating the use of fragile configuration generation logic. | ||
|
|
||
| For example, a common need is to specify instance-specific behavior. Rather than attempting to statically configure such behavior, one could build a runtime task-assignment service, which would be resilient to pod and host failures. |
There was a problem hiding this comment.
Filed #1064 to remind us to try this pattern.
smarterclayton
changed the title
|
I found editing the huge .md file to be unwieldy. I'm going to break this proposal into smaller issues. I already filed #1178, which generated lots more feedback than this PR. |
This was referenced Sep 18, 2014
This was referenced Oct 1, 2014
This was referenced Oct 9, 2014
Merged
This was referenced Mar 11, 2015
4 tasks
b3atlesfan
pushed a commit
to b3atlesfan/kubernetes
that referenced
this pull request
Feb 5, 2021
edit Flannel license info so that GitHub recognizes it
mfojtik
pushed a commit
to mfojtik/kubernetes
that referenced
this pull request
Oct 8, 2021
…ated_pods_openshift Bug 2011513: kubelet: do not arbitrarily create a podSyncStatus for finished pods
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@smarterclayton
Starting point for discussion. Feedback welcome. Also let me know where you'd like more detail.