Skip to content

GoogleCloudPlatform/looker-hosting-reference-implementations

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

27 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Looker Infrastructure as Code Reference Implementations

Introduction

Looker Hosting Reference Implementations (codename "OpsBae") is a set of Infrastructure-as-Code (IaC) tools and Kubernetes manifests to help jump-start Looker customers who choose to self-host on GCP. We have designed it to be highly modular - we want to offer some opinionated solutions and best practices while making it easy to adapt the solution for a client's particular needs. These modules should be taken as a starting point and an accelerator, not as a production-ready solution out of the box.

Status and Support

These reference implementations are not an official Google product. We will respond to any opened issues on a best-effort basis. Our official documentation for setting up a self-hosted Looker instance can be found here and further help center articles can be found here.

Hosting Decision

For the significant majority of customers, Looker's hosted option is the correct choice for how to deploy Looker. If you are working through your hosting decision please reach out to your GCP account team for help. Self-hosting Looker should not be entered into lightly.

How To Use This Repo

This repo is intended to be used as a reference for your own implementation and as such we designed many elements to be as generic as possible. You will almost certainly need to modify elements to fit your organization's specific requirements. We strongly recommend you fork this repo so you can have full control over your unique setup. While you will find end-to-end tools to help spin up a fully functional sandbox environment we've found that most users opt to pick and choose samples of the code to solve specific problems.

Hey! Where's the Kubernetes Directory??

In the 1.0 version of this tooling the Kubernetes components were stored in a separate kubernetes directory. For the 2.0 release we've streamlined the process significantly by leveraging Helm. Please refer to the 2.0 release notes for more details.

Requirements

  • Terraform >= 1.3.0
  • Kubernetes/Kubectl >= 1.21
  • Helm >= 3.0

You will also require Project Creator permissions for your GCP Organization.

Getting Started

We have provided some tutorials to help get you started - they can be found in the docs directory.