https://github.com/sysdiglabs/setechassessment
https://github.com/sysdiglabs/setechassessment
Last synced: 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/sysdiglabs/setechassessment
- Owner: sysdiglabs
- Created: 2021-06-18T00:23:30.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2024-05-21T01:26:48.000Z (12 months ago)
- Last Synced: 2025-01-23T01:22:08.583Z (4 months ago)
- Size: 19.5 KB
- Stars: 13
- Watchers: 5
- Forks: 10
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# SETechAssessment
Cloud Native infrastructure encompasses many, many things these days. We do not expect anyone to be an expert in everything--that is impossible! Rather, we look for key traits:
**GRIT** - We are a scale-up. It's fun, challenging, and demanding. GRIT is the number one trait we look for when finding someone who we believe will be successful, contributing to a world class organization. Learn more about GRIT: https://angeladuckworth.com/grit-book/
**Creativity** - Successful individuals are those that think outside the box. They are willing to question the norms and speak up about their thoughts and ideas in an effort to make everyone better.
**Coachable** - We want people who want to be better, learn from their peers, and educate them selves. This space evolves fast, we must evolve with it.
**Mentors** - In order to be successful we have to mentor each other. Again, this space is vast, no one person can know it all. We expect everyone to contribute their knowledge back to their peers. Some people will be more knowledgeable in some areas, that's not only great, it's expected. You need to be willing to coach your peers to raise everybody up.
**Cultural Contribution** - We have a lot of fun, everyone supports each other and lifts each other up, and we work hard to help everyone be as successful as they can be. Many of us come from different backgrounds and we're stronger for that. We don't tolerate negative behaviour and we encourage collaboration and team ethic. This isn't just about technical knowledge, but also professional experiences.
# The Project
To get a handle on who you are, what your drive is, and how we can best support your success we have a few asks. **Disclaimer**, we live in the age of Google, and that's OK! It's totally fine to look things up as you go. Get as far as you can, and be honest with yourself about your time. We're happy to give you more if you need it, just communicate with us when you're ready! At a high level, we'd like you to attempt the following:
1. Create Managed Kubernetes cluster in your cloud provider of choice - Do this however you want (AWS/EKS, Azure/AKS, GCP/GKE - Lots of free 'credit' options out there.)
- (Note: A node with 4cpu and 8 gigs of ram should be fine to run the Sysdig agent on with the below voting app)
- If you're building in the cloud, and you're new to the cloud, learn about security and billing alerts!
- Turn off or scale down your cluster when you're not using it, but **don't destroy it!**
3. Request a Sysdig Trial, from your hiring team.
4. Connect your cloud account to Sysdig using the onboarding Wizard.
5. Install the Sysdig Agent(s) to your Kubernetes cluster, once again we suggest using the onboarding Wizard.
6. Install the classic *voting app* into your K8s cluster (https://github.com/dockersamples/example-voting-app)
- Clone the repo to your github
- Expose the app so you can browse to the UI and see it working
7. Get Creative and build some stuff in Sysdig.
- In Sysdig Secure:
- Scan the images being used for the Voting App, what do the results mean? Which one has the most Risk? Why?
- Bonus points if you setup a Github action to build the vote, worker and result containers and scan them with our cli scanner
- Integrate Sysdig IaC with the voting app in your github repo.
- Compliance? Setup a Zone for your App & repo. Configure a benchmark to run. Submit a PR to the voting app repo from Sysdig compliance
- Enable Runtime Policies, generate some events. Be creative with the events you create and then. Show us how you did it and why you think the activity maybe suspicious?
- Activity audit! Why's that valuable?
- In Sysdig Monitor:
- Advisor, what is the usage of your cluster vs the requests and limits? What other interesting information can you find?
- Build a PromQL query using the query builder in the explore section of Sysdig Monitor using metrics from the Voting App (bonus points if you use StatsD metrics in a PromQL query)
- Build a dashboard with your query + static metrics from Sysdig that relate multiple things together
- Add views to the dashboard that might be interesting to a user
8. Don't destroy your cluster! We'd like to look at it with you.
- Hit some buttons and nav around things
- Show off your namespaces
- Pull some logs
9. Feedback?
- How can we get better?
- How did you experience with Sysdig differ from your experience of any other similar solutions?
- What suggestions do you have on this process?
- What tasks could be different or better?
# Additional Resources
By no means are we saying you need to do these things. These are resources you might find helpful to learn about K8s and the Cloud Native world.
**Sysdig - Learn Cloud Native** - https://sysdig.com/learn-cloud-native/
**Sysdig Docs** - https://docs.sysdig.com/
**Kube Academy** - https://kube.academy/
**Intro to Kubernetes** - https://acloudguru.com/course/introduction-to-kubernetes
**Kubernetes Up and Running** - https://www.oreilly.com/library/view/kubernetes-up-and/9781491935668/