So you want to write a cloud function
0 likes193 views
With Cloud Functions you write simple, functions that doing one unit of execution. Cloud Functions can be written using JavaScript, Python 3, or Go and you simply deploy a function bound to the event you want and you are all done. In our case we will leavrage from Cloud Function to manage our K8s clusters based on work times in order to save budget.
Ad
More Related Content
What's hot (20)
Similar to So you want to write a cloud function (20)
Ad
More from Elad Hirsch (11)
Ad
Recently uploaded (20)
So you want to write a cloud function
- 1. So you want to write a cloud function
- 2. ● Spinning new k8s clusters for E+ ● Unused VM's = $$$ Problem Solution ● A daily job will run at 9pm and stop clusters ● Expose API to manually start cluster ● Implementation based on Cloud Functions
- 5. Serverless ● Simplest way to run your code in the cloud ● Automatically scales, highly available and fault tolerant ● No servers to provision, manage, patch or update ● Pay only while your code runs ● Connects and extends cloud services
- 6. Serverless - Pricing Charge is based on the number of requests to your functions and compute resources consumption, only while your code is running.
- 7. ● Language - JavaScript / Python ● Triggers - HTTP / PubSub ● Service Account - Default / Custom ● Logging ● Scheduling Google Cloud Function
- 8. JavaScript/Node 6 - production ready Language Serverless by the numbers: 2018 report
- 9. HTTP PubSub
- 10. Best Practice Why not HTTP instead of Cloud Pub/Sub ? ● HTTP functions in Cloud Functions have no authentication and are not secure ● HTTP functions are unprotected and will respond to any HTTP request ● HTTP Trigger or Foreground functions that you invoke directly, Background functions don’t invoked directly
- 11. PubSub HTTP
- 12. PubSub
- 13. PubSub
- 14. PubSub API
- 15. HTTP
- 16. HTTP API
- 17. First Try
- 18. ● VM stopped and start again ● We want to free resources without deleting our k8s cluster ● Set node-pool size = 0 ○ Cleanup cluster nodes ○ Unable to cleanup node storage Google Cloud Function
- 19. Let’s explore the API
- 20. Second Try
- 21. ● Unpredictable Timeouts ● "Error: 4 DEADLINE_EXCEEDED - Deadline Exceeded ● Sometime even after function deploy its seems like perv version is still running Is it over now ?
- 25. Cloud Schedule
- 26. ● Wrap code in a serverless project (toolkit for building serverless apps) ● Add Jenkins job : ○ Install + build npm package ○ Research - Integration + E2E tests ○ Deploy - Functions + Triggers Next steps
- 29. ● We didn’t solved the Storage resources ● It requires a complex solution involving doing a storage snapshotting to remote storage … ● Is there any way to export the cluster (config , state , data …) and restore it ? Explore other solutions
- 30. apiVersion: volumesnapshot.external-storage.k8s.io/v1 kind: VolumeSnapshot metadata: name: snapshot-demo spec: persistentVolumeClaimName: gce-pvc Introduce Volume Snapshot - Alpha This feature allows creating/deleting volume snapshots, and the ability to create new volumes from a snapshot natively using the Kubernetes API.
- 32. Ark - Snapshotting cluster state