Gke deployment

[deep-diver]

No description provided.

[sayakpaul]

Great work @deep-diver. I have just left a few questions I need clarification on.

[sayakpaul]

@deep-diver final question is on MemoryStore.

As per this document, we need to enable VPC Native during the creation of the clusters. Is this incorporated currently or how are we handling it?

[deep-diver]

@deep-diver final question is on MemoryStore.

As per this document, we need to enable VPC Native during the creation of the clusters. Is this incorporated currently or how are we handling it?

It seems like the version of GKE is almost always above 1.18 for these days, so we are ok with it. Another setting is to do something with iptables, however this is unnecessary if we put --enable-ip-alias option when creating GKE cluster with gcloud container clusters.

So I think if we create with --enable-ip-alias option, there is nothing to configure as long as MemoryStore is setup in the same Region.

[sayakpaul]

Yes, that's what I was coming to. So, how are we creating the clusters now? Are we manually executing that for the time being?

[deep-diver]

Yes, that's what I was coming to. So, how are we creating the clusters now? Are we manually executing that for the time being?

That depends on scenarios. In this project, it is assumed that a cluster is already created, then GitHub Action is going to just apply the updated docker image whenever there is any changes to server directory. Note that GitHub Action for GKE deployment is not setup yet

[sayakpaul]

Okay thank you. In the Google Doc (draft) I have shared a starter GitHub Action workflow that might be useful. Let me know.

[sayakpaul]

@deep-diver feel free to merge the PR :)