Simple Engineer Notes
154 subscribers
147 photos
2 videos
49 links
Engineering insights from a simple perspective - focusing on DevOps, IaC, OS, automation and solutions without the complexity.

https://www.goncharov.xyz
Download Telegram
πŸ“ƒabout:Fediverse - An introduction to the decentralised social network

https://pretalx.devconf.info/devconf-cz-2025/talk/R9P8M3/

- there are social platforms and they belong to somebody with they own rules
- https://en.wikipedia.org/wiki/Fediverse allows to connect different social medias
- protocol is simple. It’s just batch of json
- there are alternatives for the most of social networks
- you have less followers but interactions are better
- there is no doom scrolling

#devconf
πŸ€”1
πŸ“ƒClick-Click and Kubernetes: Kubernetes-in-Kubernetes with Kamaji, KubeVirt, and the Cluster API

https://pretalx.devconf.info/devconf-cz-2025/talk/EYAAUW/

- there is no cloud, it’s just someone else computer
- it’s not that simple to run your own baremetall k8s or k8s above openstack above baremetall
- there is the solution: k8s inside k8s = cozystack
- https://cozystack.io/

#devconf #k8s
πŸ”₯1
I’ve just made speach at #devconf in Brno about using gpt for IaC. The short summary: Just imagine that there is very smart junior in your team. The main problem is lack of the context

https://www.goncharov.xyz/it/gpt4iac-en.html
https://www.youtube.com/watch?v=OMOVEMChr8A

#devconf #ai #iac
πŸ”₯3
🌧When the Cloud Delete Your Stuff

A person had a 10-year AWS account with important data. AWS sent a verification request and the account was deleted without a proper warning. Later the account was partially restored after people pushed the story to Reddit TOP.
Takeaways:
1. Don’t trust a single provider with the only copy. Two copies in two different places is the baseline.
2. Own your backups off the provider when possible. Snapshots inside the same account are not true redundancy.
3. Automate recovery drills. Backups are useless unless you regularly test restoration.
4. Keep billing and contact info tidy.
6. Human action still matters. Tech fails; people can sometimes save you.

Links:
- AWS deleted my 10-year account and all data without warning https://www.seuros.com/blog/aws-deleted-my-10-year-account-without-warning/
- AWS Restored My Account: The Human Who Made the Difference https://www.seuros.com/blog/aws-restored-account-plot-twist/
- 5 steps to lose your AWS account https://www.reddit.com/r/aws/comments/utwndj/5_steps_to_lose_your_aws_account/
- https://t.me/hacker_news_feed/119503
- https://news.ycombinator.com/item?id=44770250
- my photo archive https://t.me/simpleEngineerNotes/20

#aws #fail
πŸ‘2πŸ’©1
🀑 2 Ways to solve the problem or RTFM

The task was quite simple:
1. build a java app via maven
2. during the build run some tests
3. the tests should connect to external service
4. the API key must be passed as an env var

The problem was at the first glance during a build wasn't possible to pass env vars to maven:
- the custom jenkins library was used
- the was no way to modified it
- the library was designed to follow the very specific flow


So, initial solution was:

1. Jenkins Pipeline -> Exposes credential as LLMHUBAPIKEY_text environment variable
2. setLLMHUBAPIKEY.sh script -> Creates .mvn/maven.config
3. Maven reads .mvn/maven.config -> Sets property LLMHUBAPIKEY=gen-xxx
4. Surefire plugin -> Uses property in argLine
5. Test JVM  -> Receives -DLLMHUBAPIKEY=gen-xxx as system property
6. Test code  -> Reads via System.getProperty("LLMHUBAPIKEY")

It worked, but was over engenieried and too complicated. Hopefully, after reading docs for the jenkins library it was spotted that there is ability to pass env vars to during maven build and solution was

1. Jenkins Pipeline -> Exposes credential as LLMHUBAPIKEY_text environment variable
2. Test code  -> Reads LLMHUBAPIKEY_text environment variable

Well, 3 times easier & much more simplier. RTFM

#java #jenkins #fail
πŸ‘2