-
Notifications
You must be signed in to change notification settings - Fork 192
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
Support more Deployment operations #47
Comments
silasbw
pushed a commit
that referenced
this issue
May 13, 2017
The current code assumes every root group resources (e.g., /api/v1/nodes) is a BaseObject. This adds support for custom resources (e.g., Pod or Deployment). This is a ground work for: #47
silasbw
pushed a commit
that referenced
this issue
May 14, 2017
The current code assumes every root group resources (e.g., /api/v1/nodes) is a BaseObject. This adds support for custom resources (e.g., Pod or Deployment). This is a ground work for: #47
silasbw
added a commit
that referenced
this issue
May 14, 2017
The current code assumes every root group resources (e.g., /api/v1/nodes) is a BaseObject. This adds support for custom resources (e.g., Pod or Deployment). This is a ground work for: #47
silasbw
pushed a commit
that referenced
this issue
May 14, 2017
… resources Some named resources (e.g., `pod('foo'))` can contain resources (e.g., `pod('foo').log` or `deploy('bar').status`). The ContainerBaseObject makes implementing these resources easier. This is groundwork for #47.
silasbw
pushed a commit
that referenced
this issue
May 14, 2017
… resources Some named resources (e.g., `pod('foo'))` can contain resources (e.g., `pod('foo').log` or `deploy('bar').status`). The ContainerBaseObject makes implementing these resources easier. This is groundwork for #47.
silasbw
pushed a commit
that referenced
this issue
May 22, 2017
silasbw
added a commit
that referenced
this issue
May 23, 2017
kdamedhaar
added a commit
to kdamedhaar/k8-client
that referenced
this issue
Dec 17, 2020
The current code assumes every root group resources (e.g., /api/v1/nodes) is a BaseObject. This adds support for custom resources (e.g., Pod or Deployment). This is a ground work for: godaddy/kubernetes-client#47
kdamedhaar
added a commit
to kdamedhaar/k8-client
that referenced
this issue
Dec 17, 2020
… resources (#102) Some named resources (e.g., `pod('foo'))` can contain resources (e.g., `pod('foo').log` or `deploy('bar').status`). The ContainerBaseObject makes implementing these resources easier. This is groundwork for godaddy/kubernetes-client#47.
kdamedhaar
added a commit
to kdamedhaar/k8-client
that referenced
this issue
Dec 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
E.g., POST /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/rollback
This is a special case of a more general problem we need to handle with other objects (e.g.,
proxy
for Pods and Services).The text was updated successfully, but these errors were encountered: