Kubernetes used in the pits encountered

With the development of kubernetes now use more and more wide, in the use of the process encountered problems are not to avoid, some times some pits can be avoided in advance is the best, below I do a small record, the production of our environment encountered in the pit summary, convenient back query at the same time also convenient for you friends to avoid stepping on the pit

1.Configmap size Limit

Usually use Kubernetes when the configuration file is generally through the Configmap map into the container inside, easy to use; The external interface modifies the contents of the file will be updated automatically, but there is a hole in the Configmap file content size can not exceed 1M, Many users who use JSON format as a configuration may appear on-line after

Suddenly a little configuration file could not be updated. This if you can pay attention before the line is the best, the solution is temporarily split the configuration file or the configuration file content compression, the program read the time to extract the read;

In-depth analysis: The ultimate reason for this problem is the ETCD limit on the size of a single value, and the solution is to update the Kubernetes ETCD service to increase the--max-request-bytes size.

2. Pending additions

Kubernetes used in the pits encountered