This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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.