Thanks to visit codestin.com
Credit goes to github.com

Skip to content

kubectl cycle pods #56

@cbluth

Description

@cbluth

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): cycle, refresh


Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE

This is a VERY common occurrence:

  1. update configmap values (using envFrom)
  2. desire this new environment variable to be "pushed out" to all the currently running pods.
  3. at this point i manually delete pods in order for it to take effect, or i have also discovered that adding an extra/non-needed environment variable to the deployment will have a similar effect.
    I would prefer a feature that allows me to cycle or refresh all the pods of a given selector, so that they grab the new config.
  4. Am I doing this wrong, is there a "better" way to do it?

Kubernetes version (use kubectl version):

Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.2", GitCommit:"477efc3cbe6a7effca06bd1452fa356e2201e1ee", GitTreeState:"clean", BuildDate:"2017-04-19T20:22:08Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Environment:

  • Cloud provider or hardware configuration: AWS
  • OS (e.g. from /etc/os-release):
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1465.6.0
VERSION_ID=1465.6.0
BUILD_ID=2017-08-16-0012
PRETTY_NAME="Container Linux by CoreOS 1465.6.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
core@ip-10-20-25-116 ~ $```

- **Kernel** (e.g. `uname -a`):
```core@ip-10-20-25-116 ~ $ uname -a
Linux ip-10-20-25-116.ec2.internal 4.12.7-coreos #1 SMP Tue Aug 15 23:54:56 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz GenuineIntel GNU/Linux
core@ip-10-20-25-116 ~ $```
- **Install tools**: kops
- **Others**:


**What happened**:


**What you expected to happen**:


**How to reproduce it** (as minimally and precisely as possible):


**Anything else we need to know**:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions