Limiting scaling of a pod

Is there a way to set OpenShift/Kubernetes maximum scaling limit of a Pod in the yml/json file for either manual scaling or autoscaling? - Luis ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listin

Re: containters with host volumes from controllers

The node is running as a user, but every pod / rc has to be created in a namespace (or project, which is the same thing but with some additional controls). When you create an RC from your credentials, you are either creating it in the "default" namespace (in which case you need to grant system:ser

Re: containters with host volumes from controllers

I now reproduced the issue with OpenShift 3.2 on RHEL 7, as apposed to my few week old origin on CentOS. Unfortunately, my magic command isn't working. Here is my procedure: 1) Create node certs with `oadm create-node-config` 2) Use these certs from said node to create a replication set for a conta

Re: containters with host volumes from controllers

I think I'm making progress: oadm policy add-scc-to-user hostmount-anyuid system:serviceaccount:openshift-infra:default Now when I submit the replica set I get a different mount error that I think I understand. Note, the context I'm submitting the request in is using the node host certs under /open

Re: containters with host volumes from controllers

On May 18, 2016, at 5:26 PM, Alan Jones wrote: > oadm policy ... -z default In the version of openshift origin I'm using the oadm command doesn't take '-z'. Can you fill in the dot, dot, dot for me? I'm trying to grant permission for host volume access for a pod created by the replication control

Re: containters with host volumes from controllers

> oadm policy ... -z default In the version of openshift origin I'm using the oadm command doesn't take '-z'. Can you fill in the dot, dot, dot for me? I'm trying to grant permission for host volume access for a pod created by the replication controller which was submitted with node credentials to

Re: Seems privileged mode cannot be set in a template

Yep, by enabling 'default' to run privileged as you described worked! Thanks Clayton, - Luis - Original Message - From: "Luis Pabón" To: "Clayton Coleman" Cc: "users" , "Erin Boyd" , "Humble Chirammal" Sent: Wednesday, May 18, 2016 3:38:18 PM Subject: Re: Seems privileged mode cannot

Re: Seems privileged mode cannot be set in a template

I think I am getting it now. So when I run: $ oc get serviceaccounts NAME SECRETS AGE builder2 4h default2 4h deployer 2 4h These accounts are the ones used for the replica deployment as shown in https://docs.openshift.com/enterprise/3.0/dev_guide/servic

Re: Seems privileged mode cannot be set in a template

A service account is not a user. A service account is its own concept. A service account already exists in each namespace - in this case, if you run "oc get service accounts" you'll see three (default, builder, and deployer). The pods that are created have a spec.serviceAccountName field which d

Re: Seems privileged mode cannot be set in a template

Thanks Clayton, but that did not work. These are the steps I took: 1. Create a user called test-admin: oadm policy add-cluster-role-to-user cluster-admin test-admin \ --config=openshift.local.config/master/admin.kubeconfig 2. Add privileged settings: oc edit scc privileged 3. Add test-

Re: Seems privileged mode cannot be set in a template

You have to grant access to privileged to the service account in the namespace - if you're running as cluster-admin, you can create privileged pods, but a regular service account unless you add it: oadm policy add-scc-to-user privileged -z default where "default" is the service account that i

Re: Seems privileged mode cannot be set in a template

Hi all, I am able to easily deploy a POD with privileged mode enabled in my openshift cluster. I am also able to deploy a non-privileged application from a service/deploymentConfig template. But, I am unable to create a template which deploys a POD with privileged mode enabled. Is this po

Re: dns failures from build pods

After further investigation (My search skills clearly failed me last night): https://github.com/openshift/origin/issues/4303 So it's sti that's doing the magic to make dns work inside the build container. Non-sti builds don't. -James Ben Parees May 18, 2016 at 10

Re: Error updating deployment [deploy] status to Pending

I have this in the logs (with loglevel=4): https://gist.github.com/gravis/7454a743cb988f6d192bf5a5c9890a82 So, nothing fancy :( Thanks ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: dns failures from build pods

On Wed, May 18, 2016 at 10:14 AM, James Falkner wrote: > Is there any reason (other than bugs :) ) that pods instantiated to > execute builds of Docker-based apps wouldn't be able to resolve > *.svc.cluster.local names? I have two apps in a project, one built using a > Docker strategy, and one us

dns failures from build pods

Is there any reason (other than bugs :) ) that pods instantiated to execute builds of Docker-based apps wouldn't be able to resolve *.svc.cluster.local names? I have two apps in a project, one built using a Docker strategy, and one using s2i.. the s2i one is able (at buildtime) to contact other

Re: Error updating deployment [deploy] status to Pending

This seems like the node is "stuck" in that it didn't see the updated pod, or didn't think it accepted it. What log level are you at on your node? At level 4, when you get "stuck" what shows up at the node log? On Tue, May 17, 2016 at 8:22 PM, Philippe Lafoucrière wrote: > Hello, > > I can't de

Re: access restrictions to private apps

Hi Sebastian. Now there is a official doc ;-) https://github.com/openshift/openshift-docs/blob/master/install_config/install/deploy_router.adoc Cheers Aleks From: Sebastian Wieseler Sent: Monday, May 16, 2016 07:21 To: Aleksandar Lazic Cc: users Subject: R

OpenShift Online v3

Is there any time-frame for upgrading OpenShift Online to v3? I've been holding off a project because of the wait. ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users