Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SRE challenge improvements: clarify HA requirements, remove outdated scaffold #93

Merged
merged 3 commits into from
Jan 3, 2024
Merged

SRE challenge improvements: clarify HA requirements, remove outdated scaffold #93

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7ff208f
Add HA component to SRE challenge
sclevine Dec 21, 2023
0e8cf6e
Delete challenges/sre/sre-server directory
sclevine Dec 21, 2023
842d124
Update challenge.md
sclevine Dec 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 5 additions & 9 deletions challenges/sre/challenge.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,6 @@ The requirements vary depending on the level you are applying to. This
challenge covers 5 engineering levels at Teleport. Level 6 is only for internal
promotions. Check [Site Reliability Engineering (SRE) Levels](../../levels/sre.pdf) for more details.

An incomplete implementation of a Go server is located at
[sre-server/main.go](./sre-server/main.go).

Start by creating a new GitHub repository. Then let the interview panel know the
repository's location by pasting a link in your interview Slack channel. Invite
interview panel participants as contributors to the new repository if you prefer
Expand Down Expand Up @@ -154,6 +151,7 @@ but, at a minimum, please include the following:
### Deployment

* Create a helm chart for the service that includes at least: a Deployment, ServiceAccount and Service
* Upgrading the helm chart should not result in unavailability of the service.

## Level 4

Expand All @@ -177,6 +175,7 @@ but, at a minimum, please include the following:
### Deployment

* Create a helm chart for the service that includes at least: a Deployment, ServiceAccount and Service
* Upgrading the helm chart should not result in unavailability of the service.

## Level 5

Expand All @@ -203,6 +202,7 @@ but, at a minimum, please include the following:

* Create a helm chart for the service
* Include production-level packaging for this service, including but not limited to: Deployment, Role, RoleBinding, ServiceAccount, Service
* Upgrading the helm chart should not result in unavailability of the HTTP API portion of the service.

# Guidance

Expand Down Expand Up @@ -293,12 +293,8 @@ provide a clear path to a solution.
Consider making other reasonable trade-offs. Make sure you communicate them to
the interview team.

Here are some other trade-offs that will help you to spend less time on the task:

* Do not implement a system that scales or is highly performing. Describe which
performance improvements you would add in the future.
* It is OK if the system is not highly available. Write down how you would make
the system highly-available and why your system is not.
Do not implement a system that scales outside of the scope of this challenge.
For example, it is not necessary to deploy a shared cached or support deployment to multiple regions or AZs.

## Pitfalls and Gotchas

Expand Down
64 changes: 0 additions & 64 deletions challenges/sre/sre-server/main.go
View file
Open in desktop

This file was deleted.

Loading