Skip to content
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.

[WIP] GCP Deployment Manager / GKE #2

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

abeagley
Copy link

Wanted to open this PR ahead of completion to possibly get some discussion around it. It looks like an integration is possible with GCP that kind of mimics the behavior of the CloudFormation / Fargate template on AWS.

I've managed to get the cluster portion up and running with a GCP Deployment Manager template, but there are a couple outstanding issues on the GCP side that need to be addressed before it's a solid solution.

Unlike the AWS Fargate template this GCP version does require two steps:

  1. We have to create the cluster first and essentially wrap the Kubernetes API with a custom deployment type in GCP.
  2. After the custom types have been defined and our cluster is ready to accept concepts we can create those concepts and push them into our cluster with a second re-usable GCP Deployment Manager template that has the Kubernetes concept definitions as resource properties.

It looks like Deployment Manager is undergoing some changes / additions so I assume this will become easier in the future, but this at least gives a starting point to working with a re-usable and deployable Prisma on GCP backed by GKE.

I'll be updating this over the next few days with more Kubernetes concepts driven towards the created cluster template. I'd also like to welcome feedback / more experienced GCP engineers to give their two cents.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant