Question: kubectl delete ?

Asked By
janst
Asked At
2017-10-26 07:44:36

Found 15 possible answers.

User Answered At Possible Answer
hoojdev 2017-10-26 07:45:22 @janst kubectl delete configmap name?
janst 2017-10-26 07:46:14 do you have a yaml file?,..
hoojdev 2017-10-26 07:46:27 yes
janst 2017-10-26 07:46:46 or export the yaml file.. and then delete it.. ;0
hoojdev 2017-10-26 07:46:55 one more thing, its been 15 minutes since the status of the pod is ContainerCreating now when I run get, its showing the pod config as well export? should I wait, or something is wrong?
janst 2017-10-26 07:48:00 can you describe the pod?..
hoojdev 2017-10-26 07:48:11 simply followed this https://kubernetes.io/docs/user-guide/configmap/redis/redis-config
deepubn 2017-10-26 07:48:13 yha working for now sure with mentioning nodeport
hoojdev 2017-10-26 07:48:54 but my redis config has the name redis-config.properties so wanted to change it so was wondering if that didnt get the pod up
mattymo 2017-10-26 07:49:23 How can I create a clusterrolebinding to make apiserver ignore discrepancy between cert user name and node name when using cloudprovider?
janst 2017-10-26 07:50:29 how did you create your configamp?
hoojdev 2017-10-26 07:50:56 kubectl create configmap example-redis-config --from-file=$PWD
janst 2017-10-26 07:51:21 then kubectl delete configmap example-redis-config
foxie 2017-10-26 07:51:39 kube hpa wtf
Min replicas:                        2
22h 1s 9 horizontal-pod-autoscaler Normal SuccessfulRescale New size: 15; reason: Current number of replicas above Spec.MaxReplicas 31s 31s 1 horizontal-pod-autoscaler Normal SuccessfulRescale New size: 30; reason: cpu resource utilization (percentage of request) above target 22h 4m 2 horizontal-pod-autoscaler Normal SuccessfulRescale New size: 16; reason: cpu resource utilization (percentage of request) above target 8h 8m 2 horizontal-pod-autoscaler Normal SuccessfulRescale New size: 8; reason: cpu resource utilization (percentage of request) above target 8h 12m 3 horizontal-pod-autoscaler Normal SuccessfulRescale New size: 4; reason: cpu resource utilization (percentage of request) above target ... Max replicas: 15
janst 2017-10-26 07:51:43 should work.

Related Questions