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

k8s: Add views for Deployments and ReplicaSets #1372

Closed
2opremio opened this issue Apr 24, 2016 · 5 comments
Closed

k8s: Add views for Deployments and ReplicaSets #1372

2opremio opened this issue Apr 24, 2016 · 5 comments
Assignees
Labels
k8s Pertains to integration with Kubernetes
Milestone

Comments

@2opremio
Copy link
Contributor

2opremio commented Apr 24, 2016

Kubernetes 1.2 comes with Deployments and ReplicaSets (similar to ReplicationControllers but enable declarative changes/rollouts and use hashing for versioning), we should add views for them.

See http://blog.kubernetes.io/2016/04/using-deployment-objects-with.html for a friendly example.

For Deployments we probably want some sort of log view to see the changes which were made to the deployment (it would require a similar view to #1329 )

@2opremio 2opremio added the k8s Pertains to integration with Kubernetes label Apr 24, 2016
@2opremio 2opremio added this to the 0.15.0 milestone Apr 24, 2016
@rimusz
Copy link

rimusz commented Apr 25, 2016

👍

@errordeveloper
Copy link
Contributor

Can you do a Deployment of a DaemonSet? ...I seem to recall there was a limitation, but not too sure.

@rimusz
Copy link

rimusz commented Apr 28, 2016

Deployment is replication controller replacement and does nothing to DaemonSets

@errordeveloper
Copy link
Contributor

Ok, sorry, I confused, thought this was in the context of scope manifest.

@2opremio
Copy link
Contributor Author

No, this is for adding views in Scope (hence the title :) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s Pertains to integration with Kubernetes
Projects
None yet
Development

No branches or pull requests

4 participants