Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container Trait for Resource Allocation on Openshift #3052

Closed
Mohid-A opened this issue Mar 1, 2022 · 1 comment
Closed

Container Trait for Resource Allocation on Openshift #3052

Mohid-A opened this issue Mar 1, 2022 · 1 comment

Comments

@Mohid-A
Copy link

Mohid-A commented Mar 1, 2022

Hello,

While trying to run a sample hello world program on openshift fails due to the resources allocation issues to the container. Openshift is setup to deny scheduling/creating any pods if deployed with no resource requests and limits are set. I have tried to run the integration using the following command but it doesn't work.

VERSION

red-hat-camel-k-operator.v1.6.3
Camel K Client 1.6.1

Command to produce the Issue

kamel.exe run --trait deployer.kind=deployment --trait container.enabled=true --trait container.request-cpu=50m --trait container.request-memory=50Mi --trait container.limit-cpu=100m --trait container.limit-memory=100Mi --trait container.name=camelk hello.groovy

Error Log

Error creating build pod: pods "camel-k-kit-c8es8h3soul29r5ppfeg-1-build" is forbidden: failed quota: compute-resources: must specify limits.cpu,limits.memory,requests.cpu,requests.memory

I am following the documentation https://camel.apache.org/camel-k/1.6.x/traits/container.html to set the resources using container trait, but that doesn't seems to work for me.

Thanks

@oscerd
Copy link
Contributor

oscerd commented Mar 1, 2022

This is the upstream project. You need to ask to Red Hat support.

@oscerd oscerd closed this as completed Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants