SRE Resources

overview

While our overall product surface is vast, the scope for SRE specific tools is much narrower.

SRE tools

ensure all SREs have access to the following tools by using your G Suite @balena.io email address or your existing GitHub account to sign-up and then requesting organisation access in the t/operations flow using hashtag #access (i.e. #hashtag please grant "foo" access to bar@balena.io|username). Some services may require an invitation first (i.e. VictorOps).

infrastructure

• generate RSA|EC and GPG keys and add it to your GitHub profile.

  • The process is explained here

• request SSH access

- misc1.dev.balena.io
- misc2.dev.balena.io
- balenaCloud utility-console access

• Passpack v7 (⚠️ not on https://app.passpack.com/...) and activate sharing

• We authenticate our AWS access using Google. Follow this guide to setup the SAML authentication tools for AWS CLI.

• ARM architecture builders hosted on Equinix
• Kubernetes (k8s) cluster(s)
• CloudFlare
• Hubot hosted at Heroku
• balena.io blog and website in Netlify

CI/CD

• GitHub (assumes existing account)
• Jenkins hosted at Hetzner (admin access)
• Jenkins master and build agents (SSH)
• balenaCI/concourse-ci
• DockerHub

monitoring

• Prometheus metrics aggregator
• Grafana metrics visualiser
• VictorOps on-call scheduling
• Sentry front-end logging
• Logentries back-end logging
• statuspage.io customer facing status page
• Nodeping TBC/legacy?
• healthchecks.io TBC/legacy?

balena|product

• JellyFish
• personal account (e.g. GitHub linked) balenaCloud team member group membership
• company account (e.g. G Suite linked) balenaCloud support agent permission
• balenaStaging and admin support agent permission