In an interview, I was asked to explain every detail when you run "curl google.com". How would you explain?

I started off with DNS resolution and went ahead with packet transmission between every layer of TCP/IP. But I was also asked how "curl" binary executes, what's the process etc.

https://redd.it/ss95zq
@r_devops

In an interview, I was asked to explain every detail when you run "curl google.com". How would you explain?

I started off with DNS resolution and went ahead with packet transmission between every layer of TCP/IP. But I was also asked how "curl" binary executes, what's the process etc.

https://redd.it/ss95zq
@r_devops

Learning DevOps in 2022

I see this question asked all the time: "I want to get into DevOps, but what should I learn?"

Great question! And a tricky one, too, because by the nature of DevOps it has a very wide technical responsibility. Take a look here as I provide some guidance I think a personal can focus on for learning modern DevOps.

- Platforms
- Languages
- Tooling
- Cloud

https://trstringer.com/devops-learning-2022/

https://redd.it/ssdn3s
@r_devops

H-index like for the devs

Hello everyone, just a bit idea i wanted share.

I'm not a developer, but I thought that a system similar to the H-index in science for developers would be nice.

Each developer would be given a score based on the number of people who use and cite their work, allowing amateurs like me to get a very vague idea of the person's level.

Have a good day, sorry for my bad english speaking.

https://redd.it/sse5bh
@r_devops

Bitbucket cloud vs azure devops vs gitlab (continuous deployment)

Hello,

I'm a bit new to all of this, but we (a small startup) currently utilize Bitbucket hosted locally on one of our servers. We are looking at options for continuous deployment and want to move as much to the cloud as makes sense.

How do the three (Bitbucket Cloud, Azure DevOps, and GitLab) compare?

We want:

1) To be able to deploy .net applications both to a locally hosted IIS running on a local server and to an Azure App Service

2) Deploy SQL changes if possible

3) Integration with Jira, we had this but we moved to Jira cloud and lost that link

4) Easily be able to migrate our locally hosted Bitbucket to whatever option we choose. We would also prefer to keep any history (branches and what not) we have in our Bitbucket.

5) A stretch, but we deploy changes to a 3rd party hosted website, if we could some how scrape the site and make changes through the page? This sounds a bit far fetched but thought I'd include it.

If anyone knows if any of the three options can do the above, how well they do it, or if there are better places to ask please advise.

Thank you

https://redd.it/sshhbs
@r_devops

Need advice as a new grad in a DevOps role

I recently started a role as a DevOps Engineer, and I didn’t expect to start my career as one. Initially I had planned on working as a SWE, and building on from my previous experience as a SWE intern.

And for some context on how I got the job - I applied to a pretty big IT company, which offered a new grad program for CS students that funnelled them to different roles - SWE, QA, DevOps, etc. And I was lucky enough that my current team took me. Although I have no DevOps experience, the team took me despite knowing that.

And I took this role because, I thought it would put me in a unique position in my career:

1) I understand that the DevOps role is usually for people who have years of experience
2) Having mostly development experience, I also wanted to have experience on the operations side

Where I need advice on is my focus on learning.
I am overwhelmed with the plethora of tools and concepts that are out there. And I understand that the tools we use will always change.

So if we’re speaking of core concepts/knowledge/principles that will carry througout my career (irrespective of tools) what should I know? What should my foundation of knowledge be strong in? Would that be that be OS concepts, networking, sysadmin, etc.?

Many thanks for reading this post

https://redd.it/sshi6n
@r_devops

First time being offered RSUs, help?

I might be starting a new job soon, and while I'm used to negotiating a salary and bonus, one company I'm interviewing with offers restricted stock units (RSUs). What do I need to know about this so I don't sound like an idiot to the recruiter? Are RSUs something I can negotiate like a salary? What percent of compensation do RSUs make up?

Here's some quick facts from their equity PDF:

* Total vesting period is four years
* First 25% of the shares vest after 12 months
* Quarterly thereafter for 12 quarters

https://redd.it/ssium9
@r_devops

Present Packer variable as a list

So this may be pretty straight forward but I have a hard time finding the solution - how do I present the packer variable ami_users to accept a list of account ID's?


I have a variables.pkr.hcl file which I've stated as:


variable "amiusers" {
type = list(string)
}

and on the variables.auto.pkrvars.hcl I've added the list of shared AWS account ID's in the format:


amiusers = "12345", "678910", 11121314"

The issue is that I get the error:


Error: Incorrect attribute value type

​

on mainscript.pkr.hcl line 17:

(source code not available)

​

with var.ami_users as list of string with 3 elements.

​

Inappropriate value for attribute "ami_users": element 0: string required.


Am I meant to declare the variable as another type in this case? All the similar examples on github declare this as a similar type.

https://redd.it/ssgxct
@r_devops

Scenarios where it's a pain to manage secrets and configuration data (Kubernetes manifests, parameters, variables, etc.)

Hey Everyone,

I'm looking to get some ideas from you on how it's been a pain in the butt for you to manage things like:

\- Secrets

\- Kubernetes manifest params

\- Parameters in your code

\- Variables in your code

\- Terraform variables

And pretty much anything else that you can think of in the configuration metadata/configuration data space.

I'm building some content around a platform called CloudTruth, and I want to provide real-world, project-focused examples.. so any ideas that you can give that you're currently battling with would be greatly appreciated!

https://redd.it/ss9o64
@r_devops

Help to analyze and monitor nodejs api routes

Whats up guys!! so, i am new in devops so i would like to ask help to perform a task.

Basically i have a backend api running node.js, i would like to monitor some attributes from this API, to analyze metrics from this attributes per moth, year, etc..., so thanks for the help :D

​

PS: the attributes would be something like:

​

route alias (something like this -> ""route/:id/update") , totalRequests, latency and failRate

https://redd.it/ssc29n
@r_devops

DevOps Bulletin Newsletter - Issue 38

Hey folks,

DevOps Bulletin - Digest #38 is out, the following topics are covered:

🚀 5 hours tutorial series but totally worth it to learn how to deploy a production-ready Django application into a Kubernetes cluster running on DigitalOcean with Docker and GitHub Actions.
🔒 Great post to master RBAC and its terminologies (Role, ClusterRole, RoleBinding, and ClusterRoleBinding)
💰 How a bug ended up generating 500k time/minute of logs that costs $1000 on Google Cloud Platform.
🗂 PostgreSQL stores a lot of files on disk such as transaction commit data, sub-transaction status data, write ahead logs (WAL) ... In this post, you'll get into the implementation level details on how PostgreSQL row storage really works.
💻 2021 was a seriously good year for web security research. This post scratches the surface and list the most significant web hacking techniques of last year.
❤️ 100% free Kubernetes tutorials and courses for getting hands-on knowledge and know-how to be a pro Kubernetes developer. Unlock the next level of growth in your cloud native career.

Complete issue: https://www.devopsbulletin.com/issues/1000-wasted-because-of-an-infinite-loop

Feedback is welcome :)

https://redd.it/ss8ge7
@r_devops

Automation ideas

Hi guys cool automation ideas you would like to suggest? My manager is asking me to do some automation but i am out of ideas now.

https://redd.it/ssruvl
@r_devops

Reasonable SLA for API's which serve millions of request per day?

Building API which handles potentially 10 mil calls a day. Whats a reasonable SLA to guarantee? Do to networking issues we may see the backend occasionally get disconnected resulting in some 5xx issues. Is it possible to get to 5 9's or more or is 4 9's or 3 9's more realistic?

https://redd.it/sq4ctw
@r_devops

DevOps Advisory Services | DevOps Consulting Services



Ksolves **DevOps Consulting Services** and Solutions is an end-to-end solution designed to overcome the hurdles presented by the constant market upgrades. The service will allow you to remain on your toes and continuously integrate, deploy, and deliver business processes. We are a DevOps as a service company consolidating application modernization and revitalizing enterprise agility. Get hold of a varied list of services and solutions to automate deployment, analytics, and boost continuous delivery!

https://redd.it/ssuagn
@r_devops

Should you store all configuration in Vault?

I’m trying to fix our configuration management at work - part of the solution I proposed was to put all of our secret values in Vault, and use environment variables for the remaining non-sensitive values.

A coworker said it would be simpler to put all configuration in Vault, but I think it’s bad to unnecessarily store things in Vault - what should I do?

https://redd.it/sssssb
@r_devops

Landed my first real DevOps job after teaching myself! | Motivational

I just wanted to give a big thank you to the DevOps learning community for all the inspiration over the years. I have been a long-time lurker here and I can't believe I finally landed a real gig after all these hours of tutorials and research. It's very surreal to have an actual office where I get paid to code all day.

And I really have to thank Thetips4you (https://www.youtube.com/c/Thetips4you/videos) for his YouTube channel and courses. Total game-changers. I know some people don't like the free YouTube videos, but they worked for me.

I have been grinding away in earnest for about a year and a half and it finally paid off. Keep plugging away y'all, you'll make it.

https://redd.it/ssy5rx
@r_devops

DevOps pragmatism?

What are your thoughts?


Should I be more pragmatic?


I tend to stand firm when I see something is missing transparency and ask people to do the least amount of work to make something easy to understand whenever we get back to code. Especially from a security point of view.

A coworker upgraded an ye olde application which is not documented in any fashion, other than it exists in a git repository. It wasn't added to a CI/CD pipeline in any form, nor is there added any documentation or pushed a package. The upgrade ended up on a production server, since it was time essential to get the application going again.

From my point of view, there should be at least be a CI build and an application package which ends up in a package repository, even if the application is small and cannot be deploy with a CD tool. Me and my coworker discussed it with our team, but the team decided it wasn't worth the effort since the application/code actually belongs to another team.

I feel like I'm nagging about something that should be the minimum effort. But am I just being an inconvenience?


https://redd.it/ssz4ul
@r_devops

The DevOps handbook - summary

# The DevOps handbook - summary

DevOps handbook is one of the most important DevOps books on the market. It combines the most important DevOps ideas, examples from known companies, and best practices. It does not have any code so it is an ideal book for non-technical readers that would like to know what their teams are talking about. Bellow, you find a summary with the ideas that stick with me the most.

## Flow and Feedback

The first thing we want to accomplish in DevOps is to have fast feedback on our work. The first frontier, before the ultimate testing on production, is a set of well-written fast tests. Those tests should be able to run in parallel and they should be run on each commit automatically. Tests that are not run are useless, and the only way to enforce running those tests is using automation. This allows us to have basic confidence in our code and the fast feedback provided by fast pipeline should not break the flow. The testing should be not limited to unit tests but it can (and should) test also security, integration, and other aspects of our application. Important is to run different tests on different occasions (run slow tests less often) to not break the developer`s flow.



> ...a small number of reliable, automated tests are almost always preferable over a large number of manual or unreliable automated tests.



## Get it out!

You will never test everything. In production, someone will always do something you do not expect, try to hack you, or will not use your shiny feature at all. And the only way to test this is to go to production as fast as possible. This is the only way to test (almost) every possible scenario and see the outcomes. Of course, going fast to production have its dangers but we can mitigate them using tools such as shadow releases, canary testing, or blue-green release pattern. With frequent releases, we generally get smaller release sizes which is associated with a higher deployment success rate.



> ...when we increase our deployment batch size, our change success rates go down and our incident counts and MTTR go up—the opposite of the outcomes we want.

## Observer and learn

If we put our code into production we need to have a way to observe the code running. Other than standard metrics such as CPU and Memory usage, percentage of a cache hit, and other technical measures we should also have business metrics available. Does our new feature that is promoted everywhere have poor usage? It might be caused by a technical issue such as poor performance or distorted render on some browsers. The second case can be that we simply build the wrong thing. Both outcomes are valuable for us developers so we should have access to those metrics to be able to learn from them.

> ...business metrics create context for our infrastructure metrics, enabling Development and Operations to better work together toward common goals.

## Involve everyone

One of the most important lessons for me was how important is to make everyone more exposed to other team's problems. In the end, we all work toward a common goal. By being more exposed to problems of developers, testers, or ops we can often find better solutions to problems, fix the problems earlier, cheaper and build empathy for other teams.


> ...how to make Dev work more visible to Operations. To accomplish this, we explored three broad strategies, including creating self-service capabilities to enable developers in service teams to be productive, embedding Ops engineers into the service teams, and assigning Ops liaisons to the service teams when embedding Ops engineers is not possible.



## Conclusion

The DevOps handbook is one of the technical books that will fill your head with ideas. It will not teach you how to create an ideal pipeline, nor it will give you the answers to all problems but it will tickle those parts of your brain that know that our job can be done better.


> Our call to action is this: no matter what role you play in your organization, start finding people around you who want to change

how work is performed. Show this book to others and create a coalition of like-minded thinkers to break out of the downward spiral.

Orignaly published on my substack, if you like the post consider subscribing
https://rejmank.substack.com/p/the-devops-handbook-summary?r=438li

https://redd.it/ssz1y9
@r_devops

You started a new job, what are the first tools you install on your machine?

I'm curious to know what DevOps engineers do to setup their workspace when they are handed with a new laptop. What tools do you use daily to boost your productivity?

For example, oh my zsh, WSL for Windows, VS Code with X extensions, etc etc.

I'm part of a DevOps IT team for R&D (I'm personally IT) and the engineers at my team always have wacky setups that help them to almost never use their mouse, or never completely type anything without some auto-completion. Basically wizards.

Thanks :)

https://redd.it/st22ia
@r_devops

How long did you wait between your final interview and job offer?

I've been interviewing for this tech company in London for the past 3 weeks, the stages went like this:

​

1. Screening call with Founder of company (invitation to 2nd round 1 week later)
2. Technical interview with DevOps engineer (invitation to culture fit interview day after)
3. Culture fit interview with 2 other Devs at the company last Friday - hopefully will hear back this week (it's Tuesday).

The position is a junior DevOps engineer with a focus on AWS, Kubernetes and Python. I'm a certified SAA and after 5 years working as a sys admin this would be my first devops job.

I think I'm just being anxious and their are clearly a lot of other unseen factors involved, but it would be good to know what the rough estimate is between a final interview and job offer in the devops world. Thanks.

https://redd.it/ssz74u
@r_devops