Topics started by kenneth.vinson
Looker will not be updating this content, nor guarantees that everything is up-to-date. This article is meant to be used in conjunction with the Looker documentation page Setting Up and Testing a Git Connection, which describes how to integrate Looker with Git, including connecting to Git using SSH. This article highlights the steps for setting up version control with an SSH key from Cloud Source Repositories. IMPORTANT: The user who owns the SSH key must be a member of the Cloud Source Repositories repository and must have write access on the repository. To be allowed such access, the user must be the owner of the repository, have explicit write access granted to them, or be a member of a group that has write permissions on the repository.You can follow along with the instructions in the "Connecting to Git Using SSH" section of the Setting Up and Testing a Git Connection documentation page. As you read through and implement the instructions in the SSH section of the documentation page
Looker will not be updating this content, nor guarantees that everything is up-to-date. OverviewDeploying the Looker application usually involves database servers, load balancers, and multiple servers running the Looker application itself, as well as other ancillary software. Looker is packaged as a monolithic application distributed in a JAR file. Each node in a Looker cluster is a running instance of Looker on either a Linux server or a container.Required componentsThe following components are required for a clustered Looker deployment:GKE Google Kubernetes Engine, managed Kubernetes service (it is possible, but not recommended, to run your own clusters) MySQL Relational database system used by Looker as its "internal" database Shared file system Shared POSIX-compliant multi access block device that all Looker cluster nodes store model data on Containerized version of the Looker application JAR files Containers that contain the Looker application and other required components and
If you receive the error Certificates do not conform to algorithm constraints when trying to save changes to a LookML project, this can be due to a bug in OpenJDK 8 that prevents the use of the RSASSA-PSS signature algorithm on SSL certificates. If you receive this error, try installing a different SSH certificate that does not use the RSASSA-PSS signature algorithm.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.