Hi,
When I use an oc v4.3 client against a v4.3 server, I get:
[zaphod@oc3027208274 tmp]$ oc new-app --name=special-sm
kstephe/security-manager
--> Found image 8031044 (5 days old) in image stream
"kstephe/security-manager" under tag "latest" for "kstephe/security-manager"
* This image will be deployed in deployment config "special-sm"
* The image does not expose any ports - if you want to load balance or
send traffic to this component
you will need to create a service with 'oc expose dc/special-sm
--port=[port]' later
* WARNING: Image "kstephe/security-manager:latest" runs as the 'root'
user which may not be permitted by your cluster administrator
--> Creating resources ...
imagestreamtag.image.openshift.io "special-sm:latest" created
deploymentconfig.apps.openshift.io "special-sm" created
--> Success
Run 'oc status' to view your app.
[zaphod@oc3027208274 tmp]$
......which creates a deployment config, as expected. However, when I use
an oc v4.5 client against the same server, I get:
[zaphod@oc6010654212 ~]$ oc new-app --name=special-sm
kstephe/security-manager
--> Found image 8031044 (6 days old) in image stream
"kstephe/security-manager" under tag "latest" for "kstephe/security-manager"
--> Creating resources ...
imagestreamtag.image.openshift.io "special-sm:latest" created
deployment.apps "special-sm" created
--> Success
Run 'oc status' to view your app.
.....which is creating a deployment. Why this change in behavior? Is there
a shift in policy as of v4.5?
Regards,
Marvin
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
