{"action":"created","issue":{"url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/1069","repository_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s","labels_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/1069/labels{/name}","comments_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/1069/comments","events_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/1069/events","html_url":"https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/1069","id":391424066,"node_id":"MDU6SXNzdWUzOTE0MjQwNjY=","number":1069,"title":"Creation of GKE production ready k8s clusters","user":{"login":"consideRatio","id":3837114,"node_id":"MDQ6VXNlcjM4MzcxMTQ=","avatar_url":"https://avatars3.githubusercontent.com/u/3837114?v=4","gravatar_id":"","url":"https://api.github.com/users/consideRatio","html_url":"https://github.com/consideRatio","followers_url":"https://api.github.com/users/consideRatio/followers","following_url":"https://api.github.com/users/consideRatio/following{/other_user}","gists_url":"https://api.github.com/users/consideRatio/gists{/gist_id}","starred_url":"https://api.github.com/users/consideRatio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/consideRatio/subscriptions","organizations_url":"https://api.github.com/users/consideRatio/orgs","repos_url":"https://api.github.com/users/consideRatio/repos","events_url":"https://api.github.com/users/consideRatio/events{/privacy}","received_events_url":"https://api.github.com/users/consideRatio/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-16T00:38:42Z","updated_at":"2018-12-16T18:45:26Z","closed_at":null,"author_association":"MEMBER","body":"For to-be production clusters, I would recommend some settings that cannot be changed at a later time during cluster creation. Sadly GKE has not made their CLI mirror their Web UI so well sadly, and some things cannot be done with the CLI afaik.\r\n\r\n1. One can only make a regional GKE cluster as recommended practice (with three master servers) with only one zone in active use (chosen in advanced section). This is not vital, its only nice to avoid downtime of the kubernetes-api during random times when they make updates without notice.\r\n  ![image](https://user-images.githubusercontent.com/3837114/50048596-c8964680-00d0-11e9-939d-69d159a9905f.png)\r\n  **In the advanced section:**\r\n  ![image](https://user-images.githubusercontent.com/3837114/50048589-a7cdf100-00d0-11e9-8d0d-be35d80778b8.png)\r\n\r\n1. Having ip-alias enabled is recommended and has no drawback afaik.\r\n  ![image](https://user-images.githubusercontent.com/3837114/50048612-317dbe80-00d1-11e9-89d2-063dbd8ca787.png)\r\n\r\nAnyhow, I'm struggling with what we should suggest in the docs regarding this. Complicate things for us and z2jh-guide readers, or leave this out and risk the group users, like me, that perhaps care too much these details me ending up disappointed at some later stage?\r\n\r\nI think a reasonable solution is to convey:\r\n- for to-be production clusters, do this in the console\r\n- regional clusteres are good, disable certain zones\r\n- ip-alias is good"},"comment":{"url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/comments/447666209","html_url":"https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/1069#issuecomment-447666209","issue_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/1069","id":447666209,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NzY2NjIwOQ==","user":{"login":"yuvipanda","id":30430,"node_id":"MDQ6VXNlcjMwNDMw","avatar_url":"https://avatars2.githubusercontent.com/u/30430?v=4","gravatar_id":"","url":"https://api.github.com/users/yuvipanda","html_url":"https://github.com/yuvipanda","followers_url":"https://api.github.com/users/yuvipanda/followers","following_url":"https://api.github.com/users/yuvipanda/following{/other_user}","gists_url":"https://api.github.com/users/yuvipanda/gists{/gist_id}","starred_url":"https://api.github.com/users/yuvipanda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yuvipanda/subscriptions","organizations_url":"https://api.github.com/users/yuvipanda/orgs","repos_url":"https://api.github.com/users/yuvipanda/repos","events_url":"https://api.github.com/users/yuvipanda/events{/privacy}","received_events_url":"https://api.github.com/users/yuvipanda/received_events","type":"User","site_admin":false},"created_at":"2018-12-16T18:45:26Z","updated_at":"2018-12-16T18:45:26Z","author_association":"MEMBER","body":"I think we should make a new page with this, and not put this in the default startup. VPC-Native will become the default soon enough, and it doesn't affect most users. I agree regional masters is an easy win.\r\n\r\nHowever, for a 'real' production use case, I'd argue there are more things that you should consider anyway:\r\n\r\n1. Using shared storage (best for most use long term cases, I'd say) vs individual disks as the default\r\n2. Some kinda monitoring\r\n3. Reserve your public IP address so it doesn't change\r\n\r\nThere are probably a bunch more that you might or might not want (like networkpolicy, staging clusters, hubploy, etc). I think we should have a separate page that explains and lists these things instead.\r\n"}}
{"actor":{"display_login":"yuvipanda"}}