mirror of https://github.com/k3s-io/k3s
Add ga-beacon analytics to gendocs scripts
hack/run-gendocs.sh puts ga-beacon analytics link into all md files, hack/verify-gendocs.sh verifies presence of link.pull/6/head
Jeff Lowdermilk
parent
ab0844840a
commit
553f9f822b
|
|
@ -586,3 +586,6 @@
|
|||
|
||||
## 0.4 (10/14/2014)
|
||||
- Support Persistent Disk volume type
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1 +1,3 @@
|
|||
[Moved to CONTRIBUTING.md](CONTRIBUTING.md)
|
||||
[Moved to CONTRIBUTING.md](CONTRIBUTING.md)
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -27,3 +27,6 @@ Also take a look at the [development guide](docs/devel/development.md) for infor
|
|||
## Adding dependencies
|
||||
|
||||
If your patch depends on new packages, add that package with [`godep`](https://github.com/tools/godep). Follow the [instructions to add a dependency](docs/devel/development.md#godep-and-dependency-management).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -5,3 +5,6 @@ See the [user overview](docs/overview.md) for an introduction to Kubernetes and
|
|||
See the [design overview](docs/design) for an overview of the system design.
|
||||
|
||||
See the [API overview](docs/api.md) and [conventions](docs/api-conventions.md) for an overview of the API design.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -93,3 +93,6 @@ We also have the [google-containers Google Groups mailing list](https://groups.g
|
|||
|
||||
If you are a company and are looking for a more formal engagement with Google around Kubernetes and containers at Google as a whole, please fill out [this form](https://docs.google.com/a/google.com/forms/d/1_RfwC8LZU4CKe4vKq32x5xpEJI5QZ-j0ShGmZVv9cm4/viewform) and we'll be in touch.
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -89,3 +89,6 @@ These are in no particular order
|
|||
* [X] Harmonize with scripts in `hack/`. How much do we support building outside of Docker and these scripts?
|
||||
* [X] Deprecate/replace most of the stuff in the hack/
|
||||
* [ ] Finish support for the Dockerized runtime. Issue (#19)[https://github.com/GoogleCloudPlatform/kubernetes/issues/19]. A key issue here is to make this fast/light enough that we can use it for development workflows.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -7,3 +7,6 @@ See the [getting-started guides](../docs/getting-started-guides) for examples of
|
|||
*cloudprovider*/`config-default.sh` contains a set of tweakable definitions/parameters for the cluster.
|
||||
|
||||
The heavy lifting of configuring the VMs is done by [SaltStack](http://www.saltstack.com/).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
# Heapster
|
||||
|
||||
Heapster enables monitoring of Kubernetes Clusters using [cAdvisor](https://github.com/google/cadvisor). The kubelet will communicate with an instance of cAdvisor running on localhost and proxy container stats to Heapster. Kubelet will attempt to connect to cAdvisor on port 4194 by default but this port can be configured with kubelet's `-cadvisor_port` run flag. Detailed information about heapster can be found [here](https://github.com/GoogleCloudPlatform/heapster).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
# Maintainers
|
||||
|
||||
Tim Hockin <thockin@google.com>
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -72,3 +72,6 @@ SkyDNS to find.
|
|||
Kubernetes installs do not configure the nodes' resolv.conf files to use the
|
||||
cluster DNS by default, because that process is inherently distro-specific.
|
||||
This should probably be implemented eventually.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -23,3 +23,6 @@ example, if this is set to `kubernetes.io`, then a service named "nifty" in the
|
|||
|
||||
'-etcd_mutation_timeout': For how long the application will keep retrying etcd
|
||||
mutation (insertion or removal of a dns entry) before giving up and crashing.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -3,3 +3,6 @@
|
|||
|
||||
This container only exists until skydns itself is reduced in some way. At the
|
||||
time of this writing, it is over 600 MB large.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -5,3 +5,6 @@ and sends them to an instance of [Elasticsearch](http://www.elasticsearch.org/).
|
|||
This image is designed to be used as part of the [Kubernetes](https://github.com/GoogleCloudPlatform/kubernetes)
|
||||
cluster bring up process. The image resides at DockerHub under the name
|
||||
[kubernetes/fluentd-eslasticsearch](https://registry.hub.docker.com/u/kubernetes/fluentd-elasticsearch/).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -6,3 +6,6 @@ This image is designed to be used as part of the [Kubernetes](https://github.com
|
|||
cluster bring up process. The image resides at DockerHub under the name
|
||||
[kubernetes/fluentd-gcp](https://registry.hub.docker.com/u/kubernetes/fluentd-gcp/).
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -49,3 +49,6 @@ Please note: Do not set this to "false" unless you...
|
|||
- ... already configured a route for "0.0.0.0/0" to this NAT instance
|
||||
- ... already configured a route for "YOUR_IP/32" to an AWS internet gateway (for the master instance to reach your
|
||||
client directly during setup)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -5,3 +5,6 @@ This image is used to run nginx on the master.
|
|||
make
|
||||
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -195,3 +195,6 @@ for more details about the Kubernetes concepts and terminology.
|
|||
|
||||
Having a problem? Check the [Kubernetes issues database](https://github.com/GoogleCloudPlatform/kubernetes/issues)
|
||||
for related issues.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -99,3 +99,6 @@ to interact with the environment.
|
|||
- [Kubernetes issue tracker](https://github.com/GoogleCloudPlatform/kubernetes/issues)
|
||||
- [Kubernetes Documenation](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs)
|
||||
- [Kubernetes releases](https://github.com/GoogleCloudPlatform/kubernetes/releases)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -98,3 +98,6 @@ to interact with the environment.
|
|||
- [Kubernetes issue tracker](https://github.com/GoogleCloudPlatform/kubernetes/issues)
|
||||
- [Kubernetes Documenation](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs)
|
||||
- [Kubernetes releases](https://github.com/GoogleCloudPlatform/kubernetes/releases)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -10,4 +10,6 @@ This is a work-in-progress; not all options are documented yet!
|
|||
|
||||
**NUM_MINIONS**
|
||||
|
||||
The number of minion instances to create. Most providers default this to 4.
|
||||
The number of minion instances to create. Most providers default this to 4.
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -15,3 +15,6 @@ See more:
|
|||
* [pillar](pillar/)
|
||||
* [reactor](reactor/)
|
||||
* [salt](salt/)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -17,3 +17,6 @@ this directory, though, because they are written into
|
|||
## Future work
|
||||
|
||||
Document the current pillars across providers
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
[SaltStack reactor](http://docs.saltstack.com/en/latest/topics/reactor/) files, largely defining reactions to new nodes.
|
||||
|
||||
**Ignored for GCE, which runs standalone on each machine**
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -32,3 +32,6 @@ Config | GCE | Vagrant | AWS | Az
|
|||
[static-routes](static-routes/) (vsphere only) | | | |
|
||||
[base](base.sls) | M n | M n | M n | M n
|
||||
[kube-client-tools](kube-client-tools.sls) | M | M | M | M
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -40,3 +40,6 @@ Only etcd:
|
|||
Only flannel:
|
||||
|
||||
$ ansible-playbook -i inventory flannel.yml
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
# Maintainers
|
||||
|
||||
Eric Paris <eparis@redhat.com>
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -2,3 +2,6 @@ serve_hostname
|
|||
==============
|
||||
|
||||
Util app to serve your hostname on TCP and/or UDP. Useful for testing.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -14,3 +14,6 @@ docker run -d GIT_SYNC_REPO=https://github.com/GoogleCloudPlatform/kubernetes GI
|
|||
# run a nginx container to serve sync'ed content
|
||||
docker run -d -p 8080:80 -v /git-data:/usr/share/nginx/html nginx
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -28,3 +28,6 @@ kubectl services create config/pod.html
|
|||
```
|
||||
|
||||
Open the service external ip in your browser
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -7,3 +7,6 @@ title = "about"
|
|||
## A headline
|
||||
|
||||
Some content about the blog.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -7,3 +7,6 @@ title = "first"
|
|||
## first port
|
||||
|
||||
This is the first post.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -10,3 +10,6 @@ docker build -t hugo .
|
|||
# run the hugo container
|
||||
docker run -e HUGO_BASE_URL=example.com -v /path/to/md:/src -v /path/to/html:/dest hugo
|
||||
``
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -32,4 +32,6 @@ Hello, Go examples!
|
|||
- [ ] go get the package if not present in `$GOPATH`
|
||||
- [ ] add push command
|
||||
- [ ] test more complicated package (ex: etcd)
|
||||
- [ ] fix permission inside the tar
|
||||
- [ ] fix permission inside the tar
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -32,3 +32,6 @@ It may seem reasonable to use --option=${OPTION} in the .service file instead of
|
|||
While some command line options to the daemons use the default when passed an empty option some cause the daemon to fail to launch. --allow_privileged= (without a value of true/false) will cause the kube-apiserver and kubelet to refuse to launch.
|
||||
|
||||
It also may seem reasonable to just use $DAEMON_ARGS and string all of these into one line in the environment file. While that makes the .service file simple it makes the admin job more difficult to locate and make appropriate changes to the config. This is a tradeoff between having to update the .service file to add new options or having the config files easy for an admin to work with. I choose: "easy for admin most of the time".
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -23,3 +23,6 @@ You should see the logs show up in the cluster's Kibana log viewer shortly after
|
|||
```
|
||||
kubectl delete -f logging-sidecar-pod.yaml
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -23,3 +23,6 @@ You should see the logs show up in the log viewer of the Google Developer Consol
|
|||
```
|
||||
kubectl delete -f logging-sidecar-pod.yaml
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1,3 +1,6 @@
|
|||
# Maintainers
|
||||
|
||||
Johan Euphrosine <proppy@google.com>
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -27,3 +27,6 @@ $ podex -format json -type container -name nodejs-nginx google/nodejs-hello ngin
|
|||
- [ ] option to merge multiple container manifest into one pod
|
||||
- [ ] docker run flags support
|
||||
- [ ] option to generate service bindings from links
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -69,3 +69,6 @@ at port 9090.
|
|||
- Possibly use postgre or mysql as a promdash database.
|
||||
- push gateway (https://github.com/prometheus/pushgateway) setup.
|
||||
- Setup high availability via NFS
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -3,3 +3,6 @@ Solutions to interesting problems and unique implementations that showcase the e
|
|||
|
||||
- [Automated APIServer load balancing using Hipache and Fleet](docs/apiserver_hipache_registration.md)
|
||||
- [Jenkins-triggered rolling updates on sucessful "builds"](docs/rolling_updates_from_jenkins.md)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -104,3 +104,6 @@ That's it! Fleet will schedule the apiserver on one of your minions and once it'
|
|||
twitter @jeefy
|
||||
|
||||
irc.freenode.net #kubernetes jeefy
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -55,3 +55,6 @@ When using a private docker registry as we are, the Jenkins slaves as well as th
|
|||
twitter @jeefy
|
||||
|
||||
irc.freenode.net #kubernetes jeefy
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -5,3 +5,6 @@
|
|||
${KUBERNETES_ROOT}/build/make-release-notes.sh <pr-number>
|
||||
```
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -14,3 +14,6 @@
|
|||
* An overview of the [Design of Kubernetes](design)
|
||||
|
||||
* There are example files and walkthroughs in the [examples](../examples) folder.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -201,4 +201,7 @@ kube-dns-oh43e 10.244.1.10 etcd
|
|||
monitoring-heapster-controller-fplln 10.244.0.4 heapster kubernetes/heapster:v0.8 kubernetes-minion-2il2.c.kubernetes-user2.internal/130.211.155.16 kubernetes.io/cluster-service=true,name=heapster,uses=monitoring-influxdb Running 5 hours
|
||||
monitoring-influx-grafana-controller-0133o 10.244.3.4 influxdb kubernetes/heapster_influxdb:v0.3 kubernetes-minion-kmin.c.kubernetes-user2.internal/130.211.173.22 kubernetes.io/cluster-service=true,name=influxGrafana Running 5 hours
|
||||
grafana kubernetes/heapster_grafana:v0.4
|
||||
```
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -73,3 +73,6 @@ variety of uses cases:
|
|||
Localhost will no longer be needed, and will not be the default.
|
||||
However, the localhost port may continue to be an option for
|
||||
installations that want to do their own auth proxy.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -22,3 +22,6 @@ Possible information that could be recorded in annotations:
|
|||
* phone/pager number(s) of person(s) responsible, or directory entry where that info could be found, such as a team website
|
||||
|
||||
Yes, this information could be stored in an external database or directory, but that would make it much harder to produce shared client libraries and tools for deployment, management, introspection, etc.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -578,3 +578,6 @@ Events
|
|||
TODO: Document events (refer to another doc for details)
|
||||
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -51,3 +51,6 @@ Some important differences between v1beta1/2 and v1beta3:
|
|||
* Pull policies changed from `PullAlways`, `PullNever`, and `PullIfNotPresent` to `Always`, `Never`, and `IfNotPresent`.
|
||||
* The volume `source` is inlined into `volume` rather than nested.
|
||||
* Host volumes have been changed from `hostDir` to `hostPath` to better reflect that they can be files or directories.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -38,3 +38,6 @@ after the user has been (re)authenticated by a *bedrock* authentication
|
|||
provider external to Kubernetes. We plan to make it easy to develop modules
|
||||
that interface between kubernetes and a bedrock authentication provider (e.g.
|
||||
github.com, google.com, enterprise directory, kerberos, etc.)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -101,3 +101,6 @@ to a remote authorization service. Authorization modules can implement
|
|||
their own caching to reduce the cost of repeated authorization calls with the
|
||||
same or similar arguments. Developers should then consider the interaction between
|
||||
caching and revocation of permissions.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -128,3 +128,6 @@ calls for maximum 100 node clusters at v1.0 and maximum 1000 node clusters in th
|
|||
When you have multiple clusters, you would typically create services with the same config in each cluster and put each of those
|
||||
service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forwarding Rule or HTTP Load Balancer), so that
|
||||
failures of a single cluster are not visible to end users.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -76,3 +76,6 @@ Server-side support:
|
|||
1. Field selection [#1362](https://github.com/GoogleCloudPlatform/kubernetes/issues/1362)
|
||||
1. Field filtering [#1459](https://github.com/GoogleCloudPlatform/kubernetes/issues/1459)
|
||||
1. Operate on uids
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -12,3 +12,6 @@
|
|||
* [PHP](https://github.com/devstub/kubernetes-api-php-client)
|
||||
* [Node.js](https://github.com/tenxcloud/node-kubernetes-client)
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -70,3 +70,6 @@ project.](salt.md).
|
|||
|
||||
* **Authorization** [authorization]( authorization.md)
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -57,3 +57,6 @@ If you want more control over the upgrading process, you may use the following w
|
|||
If you deleted the node's VM instance and created a new one, then a new schedulable node resource will
|
||||
be created automatically when you create a new VM instance (if you're using a cloud provider that supports
|
||||
node discovery; currently this is only GCE, not including CoreOS on GCE using kube-register). See [Node](node.md).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -85,3 +85,6 @@ Hook handlers are the way that hooks are surfaced to containers. Containers ca
|
|||
* HTTP - Executes an HTTP request against a specific endpoint on the container. HTTP error codes (5xx) and non-response/failure to connect are treated as container failures. Parameters are passed to the http endpoint as query args (e.g. http://some.server.com/some/path?reason=HEALTH)
|
||||
|
||||
[1]: http://man7.org/linux/man-pages/man2/gethostname.2.html
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -87,3 +87,6 @@ The relationship between Docker's capabilities and [Linux capabilities](http://m
|
|||
| SETFCAP | CAP_SETFCAP |
|
||||
| WAKE_ALARM | CAP_WAKE_ALARM |
|
||||
| BLOCK_SUSPEND | CAP_BLOCK_SUSPEND |
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -15,3 +15,6 @@ A single Kubernetes cluster is not intended to span multiple availability zones.
|
|||
Finally, Kubernetes aspires to be an extensible, pluggable, building-block OSS platform and toolkit. Therefore, architecturally, we want Kubernetes to be built as a collection of pluggable components and layers, with the ability to use alternative schedulers, controllers, storage systems, and distribution mechanisms, and we're evolving its current code in that direction. Furthermore, we want others to be able to extend Kubernetes functionality, such as with higher-level PaaS functionality or multi-cluster layers, without modification of core Kubernetes source. Therefore, its API isn't just (or even necessarily mainly) targeted at end users, but at tool and extension developers. Its APIs are intended to serve as the foundation for an open ecosystem of tools, automation systems, and higher-level API layers. Consequently, there are no "internal" inter-component APIs. All APIs are visible and available, including the APIs used by the scheduler, the node controller, the replication-controller manager, Kubelet's API, etc. There's no glass to break -- in order to handle more complex use cases, one can just access the lower-level APIs in a fully transparent, composable manner.
|
||||
|
||||
For more about the Kubernetes architecture, see [architecture](architecture.md).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -246,3 +246,6 @@ Initial implementation:
|
|||
Improvements:
|
||||
- API server does logging instead.
|
||||
- Policies to drop logging for high rate trusted API calls, or by users performing audit or other sensitive functions.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -77,3 +77,6 @@ will ensure the following:
|
|||
6. Object is persisted
|
||||
|
||||
If at any step, there is an error, the request is canceled.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -130,3 +130,6 @@ In the current proposal, the **LimitRangeItem** matches purely on **LimitRangeIt
|
|||
It is expected we will want to define limits for particular pods or containers by name/uid and label/field selector.
|
||||
|
||||
To make a **LimitRangeItem** more restrictive, we will intend to add these additional restrictions at a future point in time.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -151,3 +151,6 @@ replicationcontrollers 5 20
|
|||
resourcequotas 1 1
|
||||
services 3 5
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -42,3 +42,6 @@ The scheduler binds unscheduled pods to nodes via the `/binding` API. The schedu
|
|||
All other cluster-level functions are currently performed by the Controller Manager. For instance, `Endpoints` objects are created and updated by the endpoints controller, and nodes are discovered, managed, and monitored by the node controller. These could eventually be split into separate components to make them independently pluggable.
|
||||
|
||||
The [`replicationController`](../replication-controller.md) is a mechanism that is layered on top of the simple [`pod`](../pods.md) API. We eventually plan to port it to a generic plug-in mechanism, once one is implemented.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -58,3 +58,6 @@ This diagram dynamic clustering using the bootstrap API endpoint. That API endp
|
|||
This flow has the admin manually approving the kubelet signing requests. This is the `queue` policy defined above.This manual intervention could be replaced by code that can verify the signing requests via other means.
|
||||
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -23,4 +23,6 @@ If you are using boot2docker and get warnings about clock skew (or if things are
|
|||
|
||||
## Automatically rebuild on file changes
|
||||
|
||||
If you have the fswatch utility installed, you can have it monitor the file system and automatically rebuild when files have changed. Just do a `make watch`.
|
||||
If you have the fswatch utility installed, you can have it monitor the file system and automatically rebuild when files have changed. Just do a `make watch`.
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -141,4 +141,6 @@ functionality. We need to make sure that users are not allowed to execute
|
|||
remote commands or do port forwarding to containers they aren't allowed to
|
||||
access.
|
||||
|
||||
Additional work is required to ensure that multiple command execution or port forwarding connections from different clients are not able to see each other's data. This can most likely be achieved via SELinux labeling and unique process contexts.
|
||||
Additional work is required to ensure that multiple command execution or port forwarding connections from different clients are not able to see each other's data. This can most likely be achieved via SELinux labeling and unique process contexts.
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -76,3 +76,6 @@ This demonstrates what would have been 20 separate entries (indicating schedulin
|
|||
* PR [#4206](https://github.com/GoogleCloudPlatform/kubernetes/issues/4206): Modify Event struct to allow compressing multiple recurring events in to a single event
|
||||
* PR [#4306](https://github.com/GoogleCloudPlatform/kubernetes/issues/4306): Compress recurring events in to a single event to optimize etcd storage
|
||||
* PR [#4444](https://github.com/GoogleCloudPlatform/kubernetes/pull/4444): Switch events history to use LRU cache instead of map
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -88,3 +88,6 @@ objectives.
|
|||
1. Each container is started up with enough metadata to distinguish the pod from whence it came.
|
||||
2. Each attempt to run a container is assigned a UID (a string) that is unique across time.
|
||||
1. This may correspond to Docker's container ID.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -332,4 +332,6 @@ has a deletion timestamp and that its list of finalizers is empty. As a result,
|
|||
content associated from that namespace has been purged. It performs a final DELETE action
|
||||
to remove that Namespace from the storage.
|
||||
|
||||
At this point, all content associated with that Namespace, and the Namespace itself are gone.
|
||||
At this point, all content associated with that Namespace, and the Namespace itself are gone.
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -106,3 +106,6 @@ Another approach could be to create a new host interface alias for each pod, if
|
|||
### IPv6
|
||||
|
||||
IPv6 would be a nice option, also, but we can't depend on it yet. Docker support is in progress: [Docker issue #2974](https://github.com/dotcloud/docker/issues/2974), [Docker issue #6923](https://github.com/dotcloud/docker/issues/6923), [Docker issue #6975](https://github.com/dotcloud/docker/issues/6975). Additionally, direct ipv6 assignment to instances doesn't appear to be supported by major cloud providers (e.g., AWS EC2, GCE) yet. We'd happily take pull requests from people running Kubernetes on bare metal, though. :-)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -212,3 +212,6 @@ cluster/kubectl.sh delete pvc myclaim-1
|
|||
The ```PersistentVolumeClaimBinder``` will reconcile this by removing the claim reference from the PV and change the PVs status to 'Released'.
|
||||
|
||||
Admins can script the recycling of released volumes. Future dynamic provisioners will understand how a volume should be recycled.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -53,3 +53,6 @@ TODO
|
|||
## General principles
|
||||
|
||||
* [Eric Raymond's 17 UNIX rules](https://en.wikipedia.org/wiki/Unix_philosophy#Eric_Raymond.E2.80.99s_17_Unix_Rules)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -558,3 +558,6 @@ source. Both containers will have the following files present on their filesyst
|
|||
|
||||
/etc/secret-volume/username
|
||||
/etc/secret-volume/password
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -115,3 +115,6 @@ Both the Kubelet and Kube Proxy need information related to their specific roles
|
|||
The controller manager for Replication Controllers and other future controllers act on behalf of a user via delegation to perform automated maintenance on Kubernetes resources. Their ability to access or modify resource state should be strictly limited to their intended duties and they should be prevented from accessing information not pertinent to their role. For example, a replication controller needs only to create a copy of a known pod configuration, to determine the running state of an existing pod, or to delete an existing pod that it created - it does not need to know the contents or current state of a pod, nor have access to any data in the pods attached volumes.
|
||||
|
||||
The Kubernetes pod scheduler is responsible for reading data from the pod to fit it onto a minion in the cluster. At a minimum, it needs access to view the ID of a pod (to craft the binding), its current state, any resource information necessary to identify placement, and other data relevant to concerns like anti-affinity, zone or region preference, or custom logic. It does not need the ability to modify pods or see other resources, only to create bindings. It should not need the ability to delete bindings unless the scheduler takes control of relocating components on failed hosts (which could be implemented by a separate component that can delete bindings but not create them). The scheduler may need read access to user or project-container information to determine preferential location (underspecified at this time).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -155,3 +155,6 @@ has defined capabilities or privileged. Contexts that attempt to define a UID o
|
|||
will be denied by default. In the future the admission plugin will base this decision upon
|
||||
configurable policies that reside within the [service account](https://github.com/GoogleCloudPlatform/kubernetes/pull/2297).
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -162,3 +162,6 @@ to services in the same namespace and read-write access to events in that namesp
|
|||
Finally, it may provide an interface to automate creation of new serviceAccounts. In that case, the user may want
|
||||
to GET serviceAccounts to see what has been created.
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -89,3 +89,6 @@ then ```foo-next``` is synthesized using the pattern ```<controller-name>-<hash-
|
|||
* Otherwise, ```foo-next``` and ```foo``` both exist
|
||||
* Set ```desired-replicas``` annotation on ```foo``` to match the annotation on ```foo-next```
|
||||
* Goto Rollout with ```foo``` and ```foo-next``` trading places.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -19,3 +19,6 @@ Docs in this directory relate to developing Kubernetes.
|
|||
and how the version information gets embedded into the built binaries.
|
||||
|
||||
* **Profiling Kubernetes** ([profiling.md](profiling.md)): How to plug in go pprof profiler to Kubernetes.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -332,3 +332,6 @@ the change gets in. If you are unsure, ask. Also make sure that the change gets
|
|||
## Adding new REST objects
|
||||
|
||||
TODO(smarterclayton): write this.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -5,3 +5,6 @@ Coding style advice for contributors
|
|||
- https://github.com/golang/go/wiki/CodeReviewComments
|
||||
- https://gist.github.com/lavalamp/4bd23295a9f32706a48f
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -38,3 +38,6 @@ PRs that are incorrectly judged to be merge-able, may be reverted and subject to
|
|||
## Holds
|
||||
|
||||
Any maintainer or core contributor who wants to review a PR but does not have time immediately may put a hold on a PR simply by saying so on the PR discussion and offering an ETA measured in single-digit days at most. Any PR that has a hold shall not be merged until the person who requested the hold acks the review, withdraws their hold, or is overruled by a preponderance of maintainers.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -333,3 +333,6 @@ export KUBERNETES_MINION_MEMORY=2048
|
|||
|
||||
#### I ran vagrant suspend and nothing works!
|
||||
```vagrant suspend``` seems to mess up the network. It's not supported at this time.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -267,3 +267,6 @@ git remote set-url --push upstream no_push
|
|||
```
|
||||
hack/run-gendocs.sh
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -175,3 +175,6 @@ take the place of common sense and good taste. Use your best judgment, but put
|
|||
a bit of thought into how your work can be made easier to review. If you do
|
||||
these things your PRs will flow much more easily.
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -64,3 +64,6 @@ Eventually you will have sufficient runs for your purposes. At that point you ca
|
|||
If you do a final check for flakes with ```docker ps -a```, ignore tasks that exited -1, since that's what happens when you stop the replication controller.
|
||||
|
||||
Happy flake hunting!
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -17,3 +17,6 @@ Definitions
|
|||
* design - priority/design is for issues that are used to track design discussions
|
||||
* support - priority/support is used for issues tracking user support requests
|
||||
* untriaged - anything without a priority/X label will be considered untriaged
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -24,3 +24,6 @@ The following conventions for the glog levels to use. [glog](http://godoc.org/g
|
|||
* Logging in particularly thorny parts of code where you may want to come back later and check it
|
||||
|
||||
As per the comments, the practical default level is V(2). Developers and QE environments may wish to run at V(3) or V(4). If you wish to change the log level, you can pass in `-v=X` where X is the desired maximum level to log.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -32,3 +32,6 @@ to get 30 sec. CPU profile.
|
|||
## Contention profiling
|
||||
|
||||
To enable contention profiling you need to add line ```rt.SetBlockProfileRate(1)``` in addition to ```m.mux.HandleFunc(...)``` added before (```rt``` stands for ```runtime``` in ```master.go```). This enables 'debug/pprof/block' subpage, which can be used as an input to ```go tool pprof```.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -14,3 +14,6 @@ We want to limit the total number of PRs in flight to:
|
|||
* Maintain a clean project
|
||||
* Remove old PRs that would be difficult to rebase as the underlying code has changed over time
|
||||
* Encourage code velocity
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -163,3 +163,6 @@ After this summary, preamble, all the relevant PRs/issues that got in that
|
|||
version should be listed and linked together with a small summary understandable
|
||||
by plain mortals (in a perfect world PR/issue's title would be enough but often
|
||||
it is just too cryptic/geeky/domain-specific that it isn't).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -97,3 +97,6 @@ These guidelines say *what* to do. See the Rationale section for *why*.
|
|||
if you use another Configuration Management tool -- you just have to do some manual steps
|
||||
during testing and deployment.
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -33,3 +33,6 @@ Guide](cluster-admin-guide.md).
|
|||
## Contributing to the Kubernetes Project
|
||||
|
||||
See this [README](../docs/devel/README.md).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -36,3 +36,6 @@ time.
|
|||
## For more information
|
||||
|
||||
See [the docs for the cluster addon](../cluster/addons/dns/README.md).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -45,3 +45,6 @@ spec:
|
|||
fieldPath: metadata.namespace
|
||||
restartPolicy: Never
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -57,3 +57,6 @@ Definition of columns:
|
|||
- **Community**: Actively supported by community contributions. May not work with more recent releases of kubernetes.
|
||||
- **Inactive**: No active maintainer. Not recommended for first-time K8s users, and may be deleted soon.
|
||||
- **Notes** is relevant information such as version k8s used.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -212,3 +212,6 @@ Visit the public IP address in your browser to view the running pod.
|
|||
```bash
|
||||
kubectl delete pods hello
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -79,3 +79,6 @@ cluster/kube-down.sh
|
|||
## Further reading
|
||||
Please see the [Kubernetes docs](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs) for more details on administering
|
||||
and using a Kubernetes cluster.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -19,3 +19,6 @@ mv kubectl /usr/local/bin/
|
|||
```bash
|
||||
ssh -f -nNT -L 8080:127.0.0.1:8080 core@<master-public-ip>
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -126,3 +126,6 @@ Look in `api/examples/` for more examples
|
|||
```
|
||||
cluster/kube-down.sh
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue