Create Jupyter notebooks for common operations

[sebgoa]

I started writing simple notebooks for interactive use of this client:

https://github.com/skippbox/notebooks

I am creating this issue to track a proposed GSoC project to expand on those notebooks:

https://github.com/cncf/soc

[sebgoa]

@ianubhav yes this project is open. You will need to submit an application starting March 20th.
if you are interested by this, you can start using the python client for k8s and look at the notebooks project in https://github.com/skippbox/notebooks . Then maybe submit a few PRs...

[sebgoa]

Once the noteboooks for common operations are written:

• start pod
• create deployment
• create service
• rolling update

we can start working on:

#66

[djkonro]

@sebgoa, I have submitted a proposal for this project and I am looking forward to a review of my proposal. Thanks.

[stibi]

Hello, maybe I should create a new issue, I can do that later and now I'll ask here: I have some code done using client-python, we are running a WP hosting on Kubernetes and client-python is used to deploy a WP site using AWS Lambda.

I can contribute a notebook for WP deployment on k8s…kind of "hello world" app in the docker world I'd say :) Does it sound helpful, or do you have something more basic to focus on now?

[sebgoa]

@stibi that would be great. The goal is to create a set of notebooks that people can walk through to do basic operations in k8s. The notebooks should not only contain the code, but also a bit of markdown to explain the steps.

In addition to the above, things like:

• create a daemonset, configmap, secret, ingress
• label pods and other resources (equivalent of kubectl label)
• annotate resources (equivalent of kubectl annotate)
• example of querying resources by labels

Then we can start doing things a bit more involved:

• watch and perform actions
• third party resources

[djkonro]

Pull Requests:

• Update create_deployment notebook: Update create_deployment notebook #239 [Merged]

• Add introductory notebook: Add introductory notebook #272 [Merged]

• Remove code execution output from create_pod notebook: Remove code execution output from create_pod notebook #261 [Merged]

• Add notebook on how to create a Service: Add notebook on how to create a Service #250 [Merged]

• Add watch notebook: Add notebook on how to watch changes to an object  #281 [Under Review]

• Add notebook on how to create a Secret: Add notebook on how to create and use a Secret #301 [Under Review]

• Add notebook on how to create a ConfigMap and use its data in Pods: Add notebook on how to create a ConfigMap and use its data in Pods #304 [Under Review]

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.