openshift-origin

I am using openshift v3 which uses kubernetes version 1.2. I am exploring more on autoscaling feature. Currently it says only CPU metrics is supported. Is there a way pods in openshift can be scaled based on memory or other metrics data collected from heapster? As you mentioned: OpenShift v3 is using multiple components of Kubernetes. The official documentation of Kubernetes and openshift are talking about autoscaling on CPU. (Kubernetes 1.2 adds alpha support for scaling based on application-specific metrics like QPS). Autoscaling on memory wasn't released in the initial version of horizontal

All of a sudden, I cannot deploy some images which could be deployed before. I got the following pod status: [root@webdev2 origin]# oc get pods NAME READY STATUS RESTARTS AGE arix-3-yjq9w 0/1 ImagePullBackOff 0 10m docker-registry-2-vqstm 1/1 Running 0 2d router-1-kvjxq 1/1 Running 0 2d The application just won't start. The pod is not trying to run the container. From the Event page, I have got Back-off pulling image "172.30.84.25:5000/default/arix@sha256:d326 . I have verified that I can pull the image with the tag with docker pull . I have also checked the log of the last container. It was

I can't figure a namespace-portable way to build an image into an imagestream that can then be used for a job in an OpenShift project namespace without hard-coding the internal registry URL in the job config. Unlike deployment configs, the job configuration does not automatically build a pod config with the image URL correct for the internal registry. The resulting job never runs because the image can't be pulled. Failed to pull image "is-copy-adaptermappings": Error: image library/is-copy-adaptermappings:latest not found Working example generated deployconfig-generated pod ... containers: -