86
Reddit DevOps. #devops Thanks @reddit2telegram and @r_channels
We all are DevOps but what's your hobby?
What do you like to do in your spare time?
I fullfill myself with music, back then played a lot of guitar but 5 years ago I switch to alto saxophone and and I try to make some electronic experiments as well - https://www.instagram.com/klimat.wav
Aparat from that, together with my gf we plan to go to carpentry course this fall - serious one it lasts 3 semestrs (1.5 years on weekends).
Yep, no kids :))
Hopefully this thread is fine with the rules!
https://redd.it/1cm6vcr
@r_devops
Public repositories or examples of internal technical documentation?
Hi guys!
Is there any library or collection of internal documentation from large companies? e.g. any public repository?
https://redd.it/1cm3uz3
@r_devops
for a website in China , should i go AWS China or alibabacloud?
any recommendations are appreciated
https://redd.it/1clwf41
@r_devops
Does anyone have examples on how to set up a postgres_exporter.yml file for monitoring with Prometheus?
I'm using Docker Compose to run Prometheus, Grafana, and Postgres Exporter in containers. I have a `postgres_exporter.yml` file but having issues configuring it due to not having any idea how to fill it out.
I'm trying to piece different sources I've found online to piece it together but nothing is making sense.
Here is the GitHub for the Postgres Exporter: [https://github.com/prometheus-community/postgres\_exporter](https://github.com/prometheus-community/postgres_exporter) but it doesn't, at least to me, really explain how to set up a `postgres_exporter.yml` file.
I found this [article](https://www.ongres.com/blog/create-prometheus-integrated-postgres-custom-metrics/) that explains how to set it up but just putting in their example errors out the container.
Maybe I am not understanding the `README` file in the GitHub repo but I don't know how to set up the `yml` file.
https://redd.it/1cluhth
@r_devops
Better way to set and talk about goals
So every year my company creates "objectives" for us usually along the very vague lines of:
* Support the dev and data team
* Meet Outage SLAs
* Make revenues go up
etc. etc.
They also rate how well we achieved that objective on a five point scale 1 being under-performing and 5 being going above and beyond! Most people end up getting a 3 or 4 for their objectives.
To me these objectives are the equivalent of me saying: I want to lose weight this year. If I set that goal for myself more than likely I won't lose a single pound because I wasn't specific enough. How much weight do I want to lose? How do I measure whether I am making progress or not? Should the measurements be monthly or should there be another metric I base it off of?
I try and clarify these goals with my manager similar to my example with the weight but I always get hesitation from my manager about setting quantifiable goals. I know this is for a variety of reasons whether they be political, unwilling, or just covering their own ass. These conversations always go back to "I know when you've achieved it and how well when I see it."
I understand this sentiment but it never sat well with me because my manager only has insight to what I am doing when we meet during our one on ones and maybe through communications with other team members. Whether they have enough knowledge on whether I deserve a 4 or a 5 I feel is just based upon feeling and what other managers do.
I guess what I am ultimately asking is if anyone here mastered the art of making objectives that are meaningful and actionable at their work whether you are a manager or an associate?
https://redd.it/1closng
@r_devops
Did anyone go to APIDays New York? Worth it or no?
Hey devs, did any of y'all go to API Days New York last week?
We did and we had a couple good takeaways: https://www.getambassador.io/blog/navigating-security-ai-apidays-new-york, but it felt pretty vendor-heavy for our dev team who attended. What did y'all think? Any conferences that would be better to send our devs too from a educational stand point so they get the most out of it next time?
https://redd.it/1clndl1
@r_devops
Getting weird TLS errors from Kubelet, EKS
Hi everyone, I need some help, hoping to find it here.
My kubelet is sending a lot of errors, including:
1. Can't find container
2. Can't get status
3. TLS error
We use Fluentbit to traffic the logs from Kubernetes to Coralogix.
I'm using EKS version 1.29 with these addons:
1. VPC CNI
2. kube-proxy
3. coredns
4. amazon ebs csi driver
All are at the latest version.
Did anyone encounter this kind of issue?
What could cause it?
Any idea how to debug?
Any idea would be great.
https://redd.it/1clkul6
@r_devops
[HELM] is this the correct way to pass values ?
values.yaml
mongodb:
replicaCount: 1
image:
repository: mongo
tag: 4.4.6
command:
- "numactl"
- "--interleave=all"
- "mongod"
- "--wiredTigerCacheSizeGB"
- "0.1"
- "--bind_ip"
- "0.0.0.0"
command:
{{- range $command := .Values.mongodb.command }}
- {{ $command}}
{{- end }}
https://redd.it/1clgr55
@r_devops
Any platforms using AI for Hiring?
In today's digital landscape, innovation and efficiency are the order of the day, with many companies looking for ways to streamline important necessities like hiring. With the global talent pool and the barriers that come with using traditional hiring methods, companies are unable to tap into the pool of talent and identify the right talents amidst a sea of applicants. Although some companies have built models to help improve hiring practices and identify special talents, I can't help but think that the infusion of AI in hiring practices can help revolutionize the recruitment process.
The use of AI can help companies cut across a vast number of applicants across a promising and talent-filled global pool, especially in tech hiring such as front-end, back-end, and full-stack, to mention a few. Infusing AI with machine learning can refine algorithms that help analyze this vast application process of sifting through resumes and candidate profiles, which will in turn help shortlist the most suitable matches for the required position.
Unlike the traditional hiring process plagued with human bias, nepotism, and favouritism, AI plays an advantage in curbing such vices during hiring. The use of AI can help eliminate conscious and unconscious human biases from hiring processes. This ensures that shortlisted candidates are evaluated based on their qualifications and how they fit the hiring needs, thus improving diversity and inclusivity, one important direction that companies across the world have recently embraced.
In recent times, with the rise of so many startups and businesses needing tech hiring on short notice, the use of AI in hiring processes can help expedite such needs. Infusing AI would help fast-track the screening and shortlisting processes, thus saving time and resources for businesses that need urgent hiring. As mentioned above, AI can help cut through a vast number of applications and select only the top candidates, ultimately speeding up the hiring process.
On a personal note and from personal experience, I would like to believe that the use of AI in hiring processes can aid individuals with non-tech skills in hiring developers. Having suffered from hiring wrongly due to my inability to test the skills of applicants vying for a developer role, I believe infusing AI in hiring processes can solve this problem by offering advanced assessment tools to test a candidate's skill sets, which could help people like me make informed decisions, and in general reduce the risk of mismatch and poor hiring, all of which would harm a business.
https://redd.it/1ccnjqv
@r_devops
$MAIN_BRANCH_DESKTOP_ACCESSIBILITY_SCORE)"
exit 1
else
echo "Current branch scores (mobile accessibility: $CURRENT_BRANCH_MOBILE_ACCESSIBILITY_SCORE, desktop accessibility: $CURRENT_BRANCH_DESKTOP_ACCESSIBILITY_SCORE) are higher than or equal to main branch scores (mobile accessibility: $MAIN_BRANCH_MOBILE_ACCESSIBILITY_SCORE, desktop accessibility: $MAIN_BRANCH_DESKTOP_ACCESSIBILITY_SCORE)"
fi
# Add a comment to the merge request
curl --location --request POST "https://gitlab.com/api/v4/projects/$CI_PROJECT_ID/merge_requests/$CI_MERGE_REQUEST_IID/notes" --header "PRIVATE-TOKEN: $PAT" --header "Content-Type: application/json" --data-raw "{ \"body\": \"🎉Lighthouse scores comparison:\n\nMain branch mobile accessibility score: ${MAIN_BRANCH_MOBILE_ACCESSIBILITY_SCORE}\nCurrent branch mobile accessibility score: ${CURRENT_BRANCH_MOBILE_ACCESSIBILITY_SCORE}\n\nMain branch desktop accessibility score: ${MAIN_BRANCH_DESKTOP_ACCESSIBILITY_SCORE}\nCurrent branch desktop accessibility score: ${CURRENT_BRANCH_DESKTOP_ACCESSIBILITY_SCORE}\" }"
only:
refs:
- merge_requests
variables:
- $CI_MERGE_REQUEST_TARGET_BRANCH_NAME == "main"
except:
- main
https://redd.it/1cch4fd
@r_devops
Calyptia and FluentBit
Seeking engineers with either #FluentBit or #Calyptia experience to participate in a virtual fireside chat 🔥 👋 Comment below if interested 🎉 #CloudNative #OSS #Otel #Datadog
https://redd.it/1ccgno7
@r_devops
Oncall rotation
My work decided today that our principle engineer isn’t going to be apart of our rotation anymore. We are going from being oncall once every 5 weeks to once every 4.
How has your work handled things similar situations?
https://redd.it/1cca5qe
@r_devops
“DevOps isn’t an entry level role” from an entry level DevOps
As one of the few people who actually did start out as an entry level DevOps Engineer for their first full time IT role out of college, I wanted to give my input on this.
I mostly agree that DevOps is not an entry level role. I wouldn’t recommend what I went through to anyone who could avoid it. Getting to even a minimum level of competence to be productive was filled with horrible growing pains that I didn’t see the entry level Devs come anywhere close to experiencing. Particularly the networking, infrastructure, and some of the containerization concepts were extremely hard to understand with no background. And I have a hard time believing that anyone “entry level” would know Linux to the level required, besides Linux just being boring to study. There was also tons of proprietary knowledge and business process stuff that I just didn’t know how to navigate the way someone with professional experience would have. Everything I mentioned so far is hard to practice or learn on your own compared to other roles, unlike making a simple portfolio website for example.
The other main problem with starting as a DevOps Engineer is that there’s not really a natural progression of tasks you can do as your knowledge increases, unlike developer and other IT roles, and the consequences for mistakes is typically an outage or some other critical.
Another Redditor u/MammothCache pointed out that there’s a very logical progression for how you grow as a SWE. You first start with bug fixes, then features of increasing scope, then to an entire application, API, or data model, ending at a more architect role. A developer can kind’ve just know a programming language decently and how to use google or ChatGPT to be given small tasks.
This doesn’t exist in DevOps. You can’t really just know a tool without understanding other IT concepts & tools with it. Even if you did know just Terraform or just Kubernetes or any DevOps tool really well in a vacuum somehow, you wouldn’t be able to do anything with it by just knowing the syntax and documentation. To make a CI/CD pipeline or troubleshoot an outage is basically already architect level knowledge. You need to know the software, admin/ops, and your DevOps tools to a decent level to be helpful. I would sometimes get jealous of the developers for having such an organic, painless progression compared to me.
I used to hear people say it takes about a year for most entry level/new grad developers to become useful to the business and feel somewhat confident in their skills. I think this is the case for most IT roles. Maybe it’s shorter now with ChatGPT and others massively increasing what Juniors can do, but it would still be completely unfair to give the same timeline to a truly entry level DevOps Engineer that you would an entry level data engineer, web dev, sysadmin, etc.
But it’s an over exaggeration to say that a smart person couldn’t provide more value than their salary after a slightly longer ramp up in the right scenario. I think this may be an ego thing of people trying to make their job sound harder than it is.
The SRE aspects are much easier to progress on from an entry level, so that’s how I started. A lot of monitoring, alerts, & logging. I was also allowed to do some cool Python coding for internal uses. That, plus writing tons of documentation and good ol’ trial by fire until eventually the dots started to connect around 9 or 10 months in. I didn’t study outside of work at all but I did put in long hours often. Through a path like this, entry level DevOps is possible.
Furthermore, a huge reason my ramp up was so rough is that I was at a toxic startup that didn’t train me, had no mentorship, had no documentation, no enforced standards or best practices, you name it. I was told that the Jr. DevOps I was brought on to replace was nearly useless in that same time frame. I pretty much only survived because I have more grit and talent than average.
Where I’m at now takes training juniors and documentation much more seriously,
How to prepare for certifications?
Hi guys!
I'm planning to appear for AWS certifications: Cloud Practitioner and SysOps Administrator.
Last year, I tried to pass Azure:104 but I failed by short margin(670), and because of that I lost some confidence. I, although, have a good experience with cloud fundamentals, but whenever I see the questions I very nervous, and get caught off guarded, despite prep.
So, I want your help and advices.....
Thanks!!
https://redd.it/1cc2vv2
@r_devops
Udemy or KodeKloud
Hi, I am looking into starting my learning path into being a Cloud Engineer. I am considering two options: subscribe with KodeKloud and stick with its path, or buying individual separated courses on Udemy. Which choice is better?
https://redd.it/1cc0vge
@r_devops
Which of these resources is the best for learning Docker and becoming job-ready?
Read the sub and came to the conclusion that these were the most recommended resources. But which one actually gives you enough knowledge to use at work? Not just an introductory guide, but comprehensive enough to know what you're doing on the job.
1. Helsinki's MOOC course "DevOps with Docker"
1. Bret Fisher's Udemy course "Docker Mastery"
1. Adrian Cantrill's course "Docker Fundamentals"
1. Nigel Poulton's book "Docker Deep Dive"
Can anyone who tried out any of these resources share their opinion please? Thanks
https://redd.it/1cm61iz
@r_devops
Lost track of our cronjobs and webservices - looking for ideas
Hey there!
I'm looking for a tool to manage various cronjob scripts and microservices on our on-prem servers.
Currently, I have 5 servers, on each of them a few cronjobs and webservices listening on random ports, - and I've lost track and would like to regain control.
By management I mean: a WebUI/tool that enforces a standardized approach to the storage location of these bash scripts, their auto-start, and their log files. These scripts a rarely updated, so it doesn't even have to integrate with a CI/CD pipeline, manual deployment would be fine.
The only problem: I can't find anything that matches my requirements, even though it is a real pain to deal with:
Dokku/Caprover/Portainer - won't help as they require to convert everything into a Dockerfile
Redhat Cockpit - just displays overall server processes and health
Windmill.dev / Appsmith - overkill and also requires converting everything to Dockerfiles
Ansible: would solve the standardized deployment part but not so much the management part
I mean there must be some wrapper tool for cronjob/systemd with a WebUI for easier setup/management, right? I just can't find any.
https://redd.it/1cm2rnx
@r_devops
Official Salary Sharing thread for devops :: may 2024
It's been awhile since I posted one of the salary threads. Let's do this again!
Crediting this thread from /r/cscareerquestions that gets posted quarterly [December Salary Sharing Thread for Experienced Devs](https://old.reddit.com/r/cscareerquestions/comments/kfh0fd/officialsalarysharingthreadforexperienced/)
I like to keep up to date with the current state of salaries/compensation across the world. Feel free to share your information below.
This thread is aimed at anyone from entry > Sr level DevOps/SRE/Infra engineers.
Please only post an offer if you're including hard numbers, but feel free to use a throwaway account if you're concerned about anonymity. You can also generalize some of your answers (e.g. "Biotech company" or "Hideously Overvalued Unicorn"), or add fields if you feel something is particularly relevant.
Salary should be in USD (pre-tax), unless otherwise stated (i.e. CAD, GBP for your home country)
Tech Stack:
Education:
Prior Experience:
$Internship
$RealJob
Company/Industry:
Title:
Tenure length:
Location:
Salary:
Relocation/Signing Bonus:
Stock and/or recurring bonuses:
Total comp:
Note that you only really need to include the relocation/signing bonus into the total comp if it was a recent thing. Also, while the primary purpose of these threads is obviously to share compensation info, discussion is also encouraged.
The format here is slightly unusual, so please make sure to post under the appropriate top-level thread, which are: US High/Medium/Low CoL, Western Europe, Eastern Europe, Latin America, Aus/NZ, Canada, Asia, or Other.
If you don't work in the US, you can ignore the rest of this post. To determine cost of living buckets, I used this site: http://www.bestplaces.net/
If the principal city of your metro is not in the reference list below, go to bestplaces, type in the name of the principal city (or city where you work in if there's no such thing), and then click "Cost of Living" in the left sidebar. The buckets are based on the Overall number: Low: < 100, Medium: >= 100, < 150, High: >= 150. (last updated Dec. 2019)
High CoL: NYC, LA, DC, SF Bay Area, Seattle, Boston, San Diego
Medium CoL: Orlando, Tampa, Philadelphia, Dallas, Phoenix, Chicago, Miami, Atlanta, Riverside, Minneapolis, Denver, Portland, Sacramento, Las Vegas, Austin, Raleigh
Low CoL: Houston, Detroit, St. Louis, Baltimore, Charlotte, San Antonio, Pittsburgh, Cincinnati, Kansas City
https://redd.it/1clvbk4
@r_devops
Internal Documentation
How much is too much? Is writing down the deployment process for each project we manage to much when all the deployment processes are the same? We have 2 Devops guys, myself being one and the other one who know the deployment process and its rather simple. Is there a need to document every single thing?
Trying to find the balance of just enough documentation without over documenting things when i know it may not be really referenced.
What is your take on internal documentation for your team - at least when it comes to reference things. Do you also have documentation which is used to help developers whenever they get stuck an issue?
https://redd.it/1cloclx
@r_devops
Need suggestions to resume
Increasing my experience on my resume to 3 or 3+ years, when I have 2.1 years of actual experience as a DevOps engineer, to meet the requirement for a job that asks for 3+ years of experience could pose an issue?.
https://redd.it/1clotee
@r_devops
The guide to kubectl I never had.
It took me a while to figure out how to fully get the most out of kubectl (mainly combining it with useful plugins and complimentary k8s tooling) Since none of this was intuitive when I started learning to interface with k8s clusters through kubectl I wrote up a summary of what I have learned so far. Hopefully it might be useful to others.
jake.page91/the-guide-to-kubectl-i-never-had-3874cc6074ff" rel="nofollow">https://medium.com/@jake.page91/the-guide-to-kubectl-i-never-had-3874cc6074ff
https://redd.it/1clhxrn
@r_devops
Monday morning funny
Good morning! Here's a joke for you fellow Monday warriors:
Why did the developer stare intently at the application monitoring dashboard all weekend? ...Because if they looked away, it might actually go green! 😂 ☕
https://redd.it/1clirq7
@r_devops
SEEKING REFERRALS DevOps Engineer for 100% Remote Web3 Roles
Hey Fellas,
I'm a DevOps engg with 4+ years of experience, specializing in Web3 space for the past 3 years. Seeking 100% remote roles. If you know of any openings or can refer me, I'd be grateful.
Check out my LinkedIn and let's connect!
Peace Out
https://redd.it/1clgdjv
@r_devops
Using the open-source version of Prometheus to monitor a service on Google Cloud Run?
Hello, I'm wanting to learn how to use monitoring tools. Prometheus sounds like a good OSS to use for monitoring my cloud environment. However, I can't seem to find anything regarding monitoring a Cloud Run service.
I looked through the docs and only found a configuration for Compute Engine?
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#gce\_sd\_config
I've also seen that there is a managed service for Prometheus offered by Google Cloud, but I'd rather use a local version on my computer than use a managed service for this. Is this possible?
Also, is Prometheus mainly meant for virtual machines? That seems to be the case in that configuration doc from Prometheus.
I'd appreciate any help.
https://redd.it/1cc98pj
@r_devops
Why GitLab pipeline stays in "Checking pipeline status"?
Hi Folks! I create a GitLab Pipeline in order to check the **Lighthouse** between two branches.
*This should be the rules:*
* *Doesn't run if you push something into* ***main*** *branch*
* ***Only works*** *when you perform a* ***merge request***
* ***Only should work IF*** *you are doing a* ***merge request to main branch,*** so, *it should't work if you try to merge dev-2 into dev*
**The problems happends when** i try to do a merge request from *dev-2 into dev...*
If you go to this merge request: [https://gitlab.com/RicardoRien/lighthouse\_pipeline/-/merge\_requests/9](https://gitlab.com/RicardoRien/lighthouse_pipeline/-/merge_requests/9)
you can see, that **stays in a infinite load spinner with this message "Checking pipeline status."**
Do you know why? Thanks in advance!
**.gitlab-ci.yml**:
image: cypress/browsers:node14.15.0-chrome86-ff82
stages:
- compare
compare:
stage: compare
script:
- |
# install required dependencies
npm install -g http-server puppeteer lighthouse@6.5.0
# check the current branch scores
http-server . &
sleep 5
lighthouse http://localhost:8080 --output=json --output-path=./current-branch-mobile-score.json --chrome-flags="--headless --no-sandbox" || exit 1
lighthouse http://localhost:8080 --output=json --output-path=./current-branch-desktop-score.json --emulated-form-factor=desktop --throttling-method=provided --chrome-flags="--headless --no-sandbox" || exit 1
CURRENT_BRANCH_MOBILE_ACCESSIBILITY_SCORE=$(node -e "const data = require('./current-branch-mobile-score.json'); console.log(Math.round(data.categories.accessibility.score * 100));") || exit 1
CURRENT_BRANCH_DESKTOP_ACCESSIBILITY_SCORE=$(node -e "const data = require('./current-branch-desktop-score.json'); console.log(Math.round(data.categories.accessibility.score * 100));") || exit 1
# Check the main branch scores
# Be aware it's pointing to "main"
git remote set-branches --add origin main
git fetch
git checkout main
http-server . &
sleep 5
lighthouse http://localhost:8080 --output=json --output-path=./main-branch-mobile-score.json --chrome-flags="--headless --no-sandbox" || exit 1
lighthouse http://localhost:8080 --output=json --output-path=./main-branch-desktop-score.json --emulated-form-factor=desktop --throttling-method=provided --chrome-flags="--headless --no-sandbox" || exit 1
MAIN_BRANCH_MOBILE_ACCESSIBILITY_SCORE=$(node -e "const data = require('./main-branch-mobile-score.json'); console.log(Math.round(data.categories.accessibility.score * 100));") || exit 1
MAIN_BRANCH_DESKTOP_ACCESSIBILITY_SCORE=$(node -e "const data = require('./main-branch-desktop-score.json'); console.log(Math.round(data.categories.accessibility.score * 100));") || exit 1
# logging out the scores and compare them
# exit 1 Pipeline fails
echo "Main branch mobile accessibility score: $MAIN_BRANCH_MOBILE_ACCESSIBILITY_SCORE"
echo "Current branch mobile accessibility score: $CURRENT_BRANCH_MOBILE_ACCESSIBILITY_SCORE"
echo "Main branch desktop accessibility score: $MAIN_BRANCH_DESKTOP_ACCESSIBILITY_SCORE"
echo "Current branch desktop accessibility score: $CURRENT_BRANCH_DESKTOP_ACCESSIBILITY_SCORE"
if [ "$CURRENT_BRANCH_MOBILE_ACCESSIBILITY_SCORE" -lt "$MAIN_BRANCH_MOBILE_ACCESSIBILITY_SCORE" ] || [ "$CURRENT_BRANCH_DESKTOP_ACCESSIBILITY_SCORE" -lt "$MAIN_BRANCH_DESKTOP_ACCESSIBILITY_SCORE" ]; then
echo "Current branch scores (mobile accessibility: $CURRENT_BRANCH_MOBILE_ACCESSIBILITY_SCORE, desktop accessibility: $CURRENT_BRANCH_DESKTOP_ACCESSIBILITY_SCORE) are lower than main branch scores (mobile accessibility: $MAIN_BRANCH_MOBILE_ACCESSIBILITY_SCORE, desktop accessibility:
Terraform & Kubernetes
I am new to Terraform, and am currently in the process of re-writing my architecture.
With Kubernetes and terraform, you guys no longer write deployment or service YAMLs? Just double checking before I start using this Terraform Kubernetes provider!
https://redd.it/1ccfi9a
@r_devops
and I’m really feeling the benefits. I could an entry level engineer having a much smoother time somewhere like here. But, even though it counters my own point, gone are the days when companies will truly train employees and people entering the workforce need to adapt. That’s perhaps the greatest lesson I’ve learned. In my new role, I was basically autonomous from the beginning and that didn’t seem unexpected. I’m effectively treated like a mid-level. That’s just the nature of DevOps in my opinion. You’re either able to do stuff without much hand holding or you’re not able to do anything at all.
I’ll end with a comment. There are some small advantages to starting out as DevOps. I agree that the DevOps ”philosophy” seems to be much rarer and less ingrained in people who switch later. Also, it was very humbling and made me emphasize working well with others, persistence, and doing good research. And we will see more of the business inefficiencies/bottlenecks with our fresher eyes, since new DevOps Engineers at your company will suffer the most from these. There’s more but nothing major. A good employee is a good employee.
Since people may ask, I graduated in 2022 as an Electrical Engineering major with two IT internships then worked as a DevOps engineer for a little under 1.5 years before being laid off in November 2023. The job hunt wasn’t bad for me. I put in ~125 job apps. I had 8 phone screenings, 4 interviews, and got 2 Jr. DevOps Engineer job offers (one remote, one hybrid, both contract-to-hire) at the end of February, plus a third offer for an Electrical Engineering position surprisingly. 5 of the phone screenings came from recruiters, so yeah my numbers from cold applying are a lot worse. I’m not a unicorn in any way(no prestigious university or big tech on my resume) but I do interview pretty well.
TL;DR: I agree that there’s no such thing as entry level DevOps, but it’s 100% possible to start out in DevOps and become useful in a similar timeframe to other IT roles if a company is willing to invest even a moderate amount into training you and by being smart about the task progression they’re given.
https://redd.it/1cc9qi6
@r_devops
HashiCorp joins IBM to accelerate multi-cloud automation
Today we announced that HashiCorp has signed an agreement to be acquired by IBM to accelerate the multi-cloud automation journey we started almost 12 years ago. I’m hugely excited by this announcement and believe this is an opportunity to further the HashiCorp mission and to expand to a much broader audience with the support of IBM.
https://www.hashicorp.com/blog/hashicorp-joins-ibm
https://redd.it/1cc99j9
@r_devops
Tips for dealing with alert fatigue?
Trying to put together some general advice for the team on the dreaded alert fatigue. I'm curious:
* How do you measure it?
* Best first steps?
* Are you using fancy tooling to get alerts under control, or just changing alert thresholds?
https://redd.it/1cbvf5w
@r_devops
A Pastebin for Terminals
Runme Gist brings securely shareable GitHub Gists to your day-to-day DevOps workflows and documentation.
Learn more here: https://runme.dev/blog/runme-gist.
https://redd.it/1cc13h5
@r_devops