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

reporting deployment when it should be deploymentConfig #251

Closed
dustymabe opened this issue Oct 27, 2016 · 0 comments
Closed

reporting deployment when it should be deploymentConfig #251

dustymabe opened this issue Oct 27, 2016 · 0 comments

Comments

@dustymabe
Copy link
Contributor

In the below scenario we are creating DeploymentConfigs and not Deployments. It's a bit misleading to report that we are creating deployments so we should fix that.

$ kompose --provider openshift up 
We are going to create OpenShift DeploymentConfigs, Services and PersistentVolumeClaims for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 

INFO[0005] Successfully created service: mlbparks       
INFO[0005] Successfully created service: mongodb        
INFO[0005] Successfully created deployment: mlbparks    
INFO[0005] Successfully created ImageStream: mlbparks   
INFO[0005] Successfully created deployment: mongodb     
INFO[0005] Successfully created ImageStream: mongodb    
INFO[0005] Successfully created persistentVolumeClaim: mongodb-claim0

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is,pvc' for details.
$ oc get dc
NAME       REVISION   REPLICAS   TRIGGERED BY
mlbparks   1          1          config,image(mlbparks:latest)
mongodb    1          1          config,image(mongodb:latest)
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

1 participant