args:["", ""] to args: - - - fail, and ununderstood behaviour.
Hello,
Question 1
Running this pod from the official doc works (https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/)
apiVersion: v1
kind: Pod
metadata:
name: memory-demo
namespace: default
spec:
containers:
- name: memory-demo-ctr
image: polinux/stress
resources:
limits:
memory: "200Mi"
requests:
memory: "100Mi"
command: ["stress"]
args: ["--vm", "1", "--vm-bytes", "150M", "--vm-hang", "1"]
But as soon as i try to write the "args" without the [] the build fail ..?? (i do not copy-paste)
apiVersion: v1
kind: Pod
metadata:
name: memory-demo
namespace: default
spec:
containers:
- name: memory-demo-ctr
image: polinux/stress
resources:
limits:
memory: "200Mi"
requests:
memory: "100Mi"
command: ["stress"]
args:
- -vm
- "1"
- -vm-bytes
- "150M"
- -vm-hang
- "1"
However, the same try using the course yaml sample works.
.............
memory: "200Mi"
args: ["--cpus", "2", "--mem-total", "350Mi", "--mem-alloc-size", "100Mi", "--mem-alloc-sleep", "1s"]
#- -cpus
#- "2" # set 1 cpu to the container
#- -mem-total
#- "350Mi"
#- -mem-alloc-size
#- "100Mi"
#- -mem-alloc-sleep
#- "1s"
terminationMessagePath: /dev/termination-log
.....................
Any idea ? kind of weird...
note that if i add some cpus configurations , to pod crash again. Strange again, or maybe on some image the cpus can not be configurate ?
apiVersion: v1
kind: Pod
metadata:
name: memory-demo
namespace: default
spec:
containers:
- name: memory-demo-ctr
image: polinux/stress
resources:
limits:
cpu: "2"
memory: "200Mi"
requests:
cpu: "1"
memory: "100Mi"
command: ["stress"]
args: ["--cpus", "1", "--vm", "1", "--vm-bytes", "150M", "--vm-hang", "1"]
Question 2
i run another pod from the official doc (https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/), i add the memory config from the course. That works (what ever the way i write the args), and the top command monitor the memory consumption, fine.
apiVersion: v1
kind: Pod
metadata:
name: cpu-demo
namespace: default
spec:
containers:
- name: cpu-demo-ctr
image: vish/stress
resources:
limits:
cpu: "2"
requests:
cpu: "0.5"
args: ["--cpus", "1", "--mem-total", "350Mi", "--mem-alloc-size", "100Mi", "--mem-alloc-sleep", "1s"]
#- -cpus
#- "2"
#- -mem-total
#- "350Mi"
#- -mem-alloc-size
#- "100Mi"
#- -mem-alloc-sleep
#- "1s"
Now i attempt to allocate some memory as they explain in the Official doc (like in the previous test), but surprisly i the pod can not build, it return an error status... why ?
apiVersion: v1
kind: Pod
metadata:
name: cpu-demo
namespace: default
spec:
containers:
- name: cpu-demo-ctr
image: vish/stress
resources:
limits:
cpu: "2"
requests:
cpu: "0.5"
args: ["--cpus", "1", "--vm", "1", "--vm-bytes", "350M", "--vm-hang", "1"]
Sorry, it s like many questions. I am trying to understand, but all of that doesn't sound really logic.
Thank you.
Comments
-
Hi @djedje,
They seem to be two separate applications, each accepting distinct sets of arguments. Attempting to mix in unexpected arguments may cause your containers to crash. In order to understand the differences in behavior, and how arguments should be used in their respective config manifests, I would recommend researching the documentation on each container image.
Regards,
-Chris0
Categories
- All Categories
- 177 LFX Mentorship
- 177 LFX Mentorship: Linux Kernel
- 754 Linux Foundation IT Professional Programs
- 374 Cloud Engineer IT Professional Program
- 170 Advanced Cloud Engineer IT Professional Program
- 74 DevOps IT Professional Program - Discontinued
- 5 DevOps & GitOps IT Professional Program
- 100 Cloud Native Developer IT Professional Program
- 7.6K Training Courses & Learning Paths
- 2 AI & ML Training
- 1 Blockchain & Decentralized Identity Training
- 5 Cloud & Containers Training
- 1 Cybersecurity Training
- 2 DevOps & Site-Reliability Training
- 1 Linux Kernel Development Training
- 1 Networking Training
- 2 Open Source Best Practice Training
- 2 System Administration Training
- 1 System Engineering Training
- 1 Web & Application Development Training
- 794 Hardware
- 202 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 173 Networking
- 91 Printers & Scanners
- 89 Storage
- 769 Linux Distributions
- 81 Debian
- 68 Fedora
- 22 Linux Mint
- 13 Mageia
- 24 openSUSE
- 150 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 465 Linux System Administration
- 31 Cloud Computing
- 73 Command Line/Scripting
- Github systems admin projects
- 98 Linux Security
- 78 Network Management
- 101 System Management
- 46 Web Management
- 112 Mobile Computing
- 20 Android
- 77 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 393 Off Topic
- 121 Introductions
- 182 Small Talk
- 29 Study Material
- 977 Programming and Development
- 310 Kernel Development
- 649 Software Development
- 990 Software
- 382 Applications
- 182 Command Line
- 5 Compiling/Installing
- 68 Games
- 317 Installation
- Archived
- 2 LFD140 Class Forum
- 1.4K LFS258 Class Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)