[INFO] PACKER_CONFIG env var set; attempting to open config file: /root/.packerconfig
2023/02/01 22:59:11 packer-provisioner-file plugin: [WARN] Config file doesn't exist: /root/.packerconfig
2023/02/01 22:59:11 packer-provisioner-file plugin: [INFO] Setting cache directory: /root/.cache/packer
2023/02/01 22:59:11 packer-provisioner-file plugin: args: []string{"packer-provisioner-file"}
2023/02/01 22:59:11 Received unix RPC address for /usr/bin/packer: addr is /tmp/packer-plugin1710102504
2023/02/01 22:59:11 packer-provisioner-file plugin: Plugin address: unix /tmp/packer-plugin1710102504
2023/02/01 22:59:11 packer-provisioner-file plugin: Waiting for connection...
2023/02/01 22:59:11 packer-provisioner-file plugin: Serving a plugin connection...
2023/02/01 22:59:11 [TRACE] Starting internal plugin packer-provisioner-shell
2023/02/01 22:59:11 Starting plugin: /usr/bin/packer []string{"/usr/bin/packer", "plugin", "packer-provisioner-shell"}
2023/02/01 22:59:11 Waiting for RPC address for: /usr/bin/packer
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] Packer version: 1.8.5 [go1.18.9 linux amd64]
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /root/.packerconfig
2023/02/01 22:59:11 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] Setting cache directory: /root/.cache/packer
2023/02/01 22:59:11 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
2023/02/01 22:59:11 Received unix RPC address for /usr/bin/packer: addr is /tmp/packer-plugin2959182279
2023/02/01 22:59:11 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin2959182279
2023/02/01 22:59:11 packer-provisioner-shell plugin: Waiting for connection...
2023/02/01 22:59:11 packer-provisioner-shell plugin: Serving a plugin connection...
2023/02/01 22:59:11 [TRACE] Starting internal plugin packer-provisioner-shell
2023/02/01 22:59:11 Starting plugin: /usr/bin/packer []string{"/usr/bin/packer", "plugin", "packer-provisioner-shell"}
2023/02/01 22:59:11 Waiting for RPC address for: /usr/bin/packer
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] Packer version: 1.8.5 [go1.18.9 linux amd64]
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /root/.packerconfig
2023/02/01 22:59:11 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
2023/02/01 22:59:11 packer-provisioner-shell plugin: [INFO] Setting cache directory: /root/.cache/packer
2023/02/01 22:59:11 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
2023/02/01 22:59:11 Received unix RPC address for /usr/bin/packer: addr is /tmp/packer-plugin1234524249
2023/02/01 22:59:11 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin1234524249
2023/02/01 22:59:11 packer-provisioner-shell plugin: Waiting for connection...
2023/02/01 22:59:11 packer-provisioner-shell plugin: Serving a plugin connection...
2023/02/01 22:59:11 [TRACE] Starting internal plugin packer-post-processor-shell-local
2023/02/01 22:59:11 Starting plugin: /usr/bin/packer []string{"/usr/bin/packer", "plugin", "packer-post-processor-shell-local"}
2023/02/01 22:59:11 Waiting for RPC address for: /usr/bin/packer
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: [INFO] Packer version: 1.8.5 [go1.18.9 linux amd64]
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2023/02/01 22:59:11

packer-post-processor-shell-local plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /root/.packerconfig
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: [WARN] Config file doesn't exist: /root/.packerconfig
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: [INFO] Setting cache directory: /root/.cache/packer
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: args: []string{"packer-post-processor-shell-local"}
2023/02/01 22:59:11 Received unix RPC address for /usr/bin/packer: addr is /tmp/packer-plugin1063530221
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: Plugin address: unix /tmp/packer-plugin1063530221
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: Waiting for connection...
2023/02/01 22:59:11 packer-post-processor-shell-local plugin: Serving a plugin connection...
2023/02/01 22:59:11 Build debug mode: false
cloudimg.deps.null.dependencies: output will be in this color.
2023/02/01 22:59:11 Force build: false
cloudimg.image.qemu.cloudimg: output will be in this color.

2023/02/01 22:59:11 On error:
2023/02/01 22:59:11 Waiting on builds to complete...
2023/02/01 22:59:11 Starting build run: cloudimg.image.qemu.cloudimg
2023/02/01 22:59:11 Running builder:
2023/02/01 22:59:11 [INFO] (telemetry) Starting builder qemu.cloudimg
2023/02/01 22:59:11 Starting build run: cloudimg.deps.null.dependencies
2023/02/01 22:59:11 Running builder:
2023/02/01 22:59:11 [INFO] (telemetry) Starting builder null.dependencies
2023/02/01 22:59:11 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:11 Qemu path: /usr/bin/qemu-system-x86_64, Qemu Image path: /usr/bin/qemu-img
2023/02/01 22:59:11 packer-builder-null plugin: [INFO] communicator disabled, will not connect
2023/02/01 22:59:11 packer-builder-null plugin: Unable to load communicator config from state to populate provisionHookData
2023/02/01 22:59:11 packer-builder-null plugin: Running the provision hook
==> cloudimg.image.qemu.cloudimg: Retrieving ISO
2023/02/01 22:59:11 [INFO] (telemetry) Starting provisioner shell-local
==> cloudimg.image.qemu.cloudimg: Trying https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img
2023/02/01 22:59:11 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:11 Acquiring lock for: https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img?checksum=sha256%3A71657529fc067dbda2537762730904a68905ae1202a30ec00a645828506939df (/root/.cache/packer/4ac13ea39617f95e49eb6b13917c0e6ff190f0d5.iso.lock)
==> cloudimg.image.qemu.cloudimg: Trying https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img?checksum=sha256%3A71657529fc067dbda2537762730904a68905ae1202a30ec00a645828506939df
2023/02/01 22:59:11 packer-provisioner-shell-local plugin: [INFO] (shell-local): Prepending inline script with #!/bin/bash -e
==> cloudimg.deps.null.dependencies: Running local shell script: /tmp/packer-shell2978727124
2023/02/01 22:59:11 packer-provisioner-shell-local plugin: [INFO] (shell-local): starting local command: /bin/sh -c PACKER_BUILDER_TYPE='null' PACKER_BUILD_NAME='dependencies' /tmp/packer-shell2978727124
2023/02/01 22:59:11 packer-provisioner-shell-local plugin: [INFO] (shell-local communicator): Executing local shell command [/bin/sh -c PACKER_BUILDER_TYPE='null' PACKER_BUILD_NAME='dependencies' /tmp/packer-shell2978727124]
==> cloudimg.deps.null.dependencies: /tmp/packer-shell2978727124: line 3: cloud-localds: command not found
2023/02/01 22:59:11 [INFO] (telemetry) ending shell-local
2023/02/01 22:59:11 packer-builder-null plugin: Unable to load communicator config from state to populate provisionHookData
==> cloudimg.deps.null.dependencies: Provisioning step had errors: Running the cleanup provisioner, if present...
2023/02/01 22:59:11 [INFO] (telemetry) ending null.dependencies
Build 'cloudimg.deps.null.dependencies' errored after 21

milliseconds 779 microseconds: Script exited with non-zero exit status: 127. Allowed exit codes are: [0]
==> cloudimg.image.qemu.cloudimg: https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img?checksum=sha256%3A71657529fc067dbda2537762730904a68905ae1202a30ec00a645828506939df => /root/.cache/packer/4ac13ea39617f95e49eb6b13917c0e6ff190f0d5.iso
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Leaving retrieve loop for ISO
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 No floppy files specified. Floppy disk will not be made.
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 No CD files specified. CD disk will not be made.
==> cloudimg.image.qemu.cloudimg: Creating required virtual machine disks
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 [INFO] Creating disk with Path: output-cloudimg/packer-cloudimg and Size: 4G
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Executing qemu-img: []string{"create", "-f", "qcow2", "-b", "/root/.cache/packer/4ac13ea39617f95e49eb6b13917c0e6ff190f0d5.iso", "-F", "qcow2", "-F", "qcow2", "output-cloudimg/packer-cloudimg", "4G"}
==> cloudimg.image.qemu.cloudimg: Resizing hard drive...
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 stdout: Formatting 'output-cloudimg/packer-cloudimg', fmt=qcow2 size=4294967296 backing_file=/root/.cache/packer/4ac13ea39617f95e49eb6b13917c0e6ff190f0d5.iso backing_fmt=qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 stderr:
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Executing qemu-img: []string{"resize", "-f", "qcow2", "output-cloudimg/packer-cloudimg", "4G"}
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 stdout: Image resized.
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 stderr:
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Found available port: 8063 on IP: 0.0.0.0
==> cloudimg.image.qemu.cloudimg: Starting HTTP server on port 8063
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Looking for available communicator (SSH, WinRM, etc) port between 2222 and 4444
==> cloudimg.image.qemu.cloudimg: Found port for communicator (SSH, WinRM, etc): 3695.
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Found available port: 3695 on IP: 127.0.0.1
==> cloudimg.image.qemu.cloudimg: Looking for available port between 5900 and 6000 on 127.0.0.1
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Looking for available port between 5900 and 6000 on 127.0.0.1
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Found available port: 5945 on IP: 127.0.0.1
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Found available VNC port: 5945 on IP: 127.0.0.1
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Qemu --version output: QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.24)
==> cloudimg.image.qemu.cloudimg: Starting VM, booting disk image
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Qemu version: 4.2.1
cloudimg.image.qemu.cloudimg: view the screen of the VM, connect via VNC without a password to
cloudimg.image.qemu.cloudimg: vnc://127.0.0.1:5945
cloudimg.image.qemu.cloudimg: The VM will

be run headless, without a GUI. If you want to
cloudimg.image.qemu.cloudimg: view the screen of the VM, connect via VNC without a password to
cloudimg.image.qemu.cloudimg: vnc://127.0.0.1:5945
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Qemu Builder has no floppy files, not attaching a floppy.
==> cloudimg.image.qemu.cloudimg: Overriding default Qemu arguments with qemuargs template option...
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Executing /usr/bin/qemu-system-x86_64: []string{"-cpu", "host", "-device", "virtio-gpu-pci", "-device", "virtio-net,netdev=user.0", "-drive", "if=pflash,format=raw,id=ovmf_code,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd", "-drive", "if=pflash,format=raw,id=ovmf_vars,file=OVMF_VARS.fd", "-drive", "file=output-cloudimg/packer-cloudimg,format=qcow2", "-drive", "file=seeds-cloudimg.iso,format=raw", "-boot", "c", "-vnc", "127.0.0.1:45", "-machine", "ubuntu,accel=kvm", "-name", "packer-cloudimg", "-netdev", "user,id=user.0,hostfwd=tcp::3695-:22", "-m", "2048M", "-smp", "2"}
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Started Qemu. Pid: 31645
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 Qemu stderr: qemu-system-x86_64: -drive file=seeds-cloudimg.iso,format=raw: Could not open 'seeds-cloudimg.iso': No such file or directory
==> cloudimg.image.qemu.cloudimg: Error launching VM: Qemu failed to start. Please run with PACKER_LOG=1 to get more info.
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 failed to unlock port lockfile: close tcp 127.0.0.1:5945: use of closed network connection
2023/02/01 22:59:15 packer-plugin-qemu_v1.0.9_x5.0_linux_amd64 plugin: 2023/02/01 22:59:15 failed to unlock port lockfile: close tcp 127.0.0.1:3695: use of closed network connection
==> cloudimg.image.qemu.cloudimg: Deleting output directory...
Build 'cloudimg.image.qemu.cloudimg' errored after 3 seconds 340 milliseconds: Build was halted.

==> Wait completed after 3 seconds 340 milliseconds

==> Some builds didn't complete successfully and had errors:
--> cloudimg.deps.null.dependencies: Script exited with non-zero exit status: 127. Allowed exit codes are: [0]
--> cloudimg.image.qemu.cloudimg: Build was halted.

==> Builds finished but no artifacts were created.
2023/02/01 22:59:15 [INFO] (telemetry) ending qemu.cloudimg
==> Wait completed after 3 seconds 340 milliseconds
2023/02/01 22:59:15 machine readable: error-count []string{"2"}
==> Some builds didn't complete successfully and had errors:
2023/02/01 22:59:15 machine readable: cloudimg.deps.null.dependencies,error []string{"Script exited with non-zero exit status: 127. Allowed exit codes are: [0]"}
2023/02/01 22:59:15 machine readable: cloudimg.image.qemu.cloudimg,error []string{"Build was halted."}
==> Builds finished but no artifacts were created.
2023/02/01 22:59:15 [INFO] (telemetry) Finalizing.
2023/02/01 22:59:15 waiting for all plugin processes to complete...
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /root/.config/packer/plugins/github.com/hashicorp/qemu/packer-plugin-qemu_v1.0.9_x5.0_linux_amd64: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
2023/02/01 22:59:15 /usr/bin/packer: plugin process exited
make: *** [Makefile:24: custom-cloudimg.tar.gz] Error 1
serveradmin@maas:/packer-maas/ubuntu$ echo $PATH

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
serveradmin@maas:/packer-maas/ubuntu$ ls
Makefile packages ubuntu-lvm.pkr.hcl
OVMF_VARS.fd scripts user-data-cloudimg
README.md ubuntu-cloudimg.pkr.hcl user-data-flat
http ubuntu-cloudimg.variables.pkr.hcl user-data-lvm
meta-data ubuntu-flat.pkr.hcl variables.pkr.hcl

https://redd.it/10raipa
@r_devops

Designing a company’s CI/CD system, please recommend resources

I’ve built CI/CD systems before but never company wide. I was hoping you lovely smart folks might be able to point me to any useful resources on the topic?

We’re using GHA so I’d also appreciate any specific tips there!

Thank you kindly

https://redd.it/10tpitf
@r_devops

Is there a way to save a docker volume and then apply the docker volume to a container after changing the image and wiping out everything?

I don't think changing the image wipes the volume, but just to be safe, because sometimes I may wipe off something, because the image just won't update. Is there a way to safe the volume into a file and then apply the volume to a docker container?

https://redd.it/10tr0xa
@r_devops

Career advice/resume review

Hello,

I'm looking to transition to an "official" DevOps role. I've been in a small non-profit for a while, so I've worn many hats and though my job title has shifted, I've always been in between the developer, sysadmin and network teams, often leading projects and advising on architecture decisions.

I think I have the necessary skills: I look at https://roadmap.sh, and I have at least basic if not intermediate or advanced knowledge of about 90% of the topics in the DevOps, Backend and ASP.NET Core roadmaps. I don't think that I'm exaggerating; I've had imposter syndrome (confirmed by other co-workers I respect) for a long time and I believe my confidence has finally caught up to my skills.

However, after 6 weeks of a job search (applying on LinkedIn, Indeed and Dice; and directly to at least a couple dozen other companies) and talking to 3 different recruiters, I haven't had one request for an interview. I also tried job searching for about 6 months for about a year and a half ago, and I had to give up because it was the same result.

Is it my resume (https://imgur.com/a/tmayECw, anonymized)? Previous job titles? Lack of certifications? I'm confident that I could do great DevOps/infrastructure engineer work, but I don't know what to how to communicate it. I've only been at one company, where I started at as an entry level support desk tech and grew from there, so I haven't successfully navigated this kind of job search before.

I don't have a ton of free time outside of work because of a family situation that I have. I could maybe squeeze 1 or 2 hours a weekend, but that's it. If you have any recommendations on how I could fix my resume or best use my time, I'd appreciate it.

https://redd.it/10trpi5
@r_devops

Junior DevOps needs advice

I‘m new into devops and I work in eCommerce since 2 years now.

My first company was very modern and used state of the art technologies (worked with terraform and K8 most of time, in an ops only Team) but paycheck was very low with no opportunities and a lot of pressure so i quit work after a year.

Now I‘m the only devops person in a Scrum team of developers. Its a big company with an 90s mindset willing to change, but I‘m far away to do K8 stuff and so on.

I have problems because

* I forget all the modern stuff, instead I‘m doing ops stuff no one else wants to do (write new scripts for monitoring, update servers and so on). Thats hard for me because I’m new into these topics and I’m slow, so during Daily stand up Meetings I feel very uncomfortable.
* I wasn‘t able to develop kind of key technology I‘m really good at - java devs are doing Java, the Front end guy is doing Front end stuff, but what I‘m doing? I have certifications in ITIL and DevOps Master but cant bring it to action in a technical way for two reasons: I‘m still a beginner and my team doesn‘t need to change anything (using monolithic architecture which works fine)
* The team tend to be dissatsfied with me, because I was hired to replace a senior architect (who joined another team), and they need his knowledge I oviously have to rebuild first in a lot of meetings/ pair „programming„ time with him
* There are a lot of dependencies to other teams and confusing architecture.
* There are also external consultants which are responsible for operations (they‘re working with Terraform and K8 for example) so I‘m asking myself why I‘m there.

I‘m learning a lot in my freetime (I‘m reading Pipeline as Code at the moment, even if we have all buildscripts ready and no need to change), but I‘m so unhappy and demotivated. Sometimes I think about to quit, but I dont want to give up.

Did you went through similiar phases in your junior devops years? Have you any advice?
Thank you for listening.

https://redd.it/10r7qwz
@r_devops

How are devops interviews for engineers from other software development backgrounds?

Most devops engineers I have met are career changers who were previously software engineers, data engineers, and database/system admins.




As a data engineer who has worked on devops-related projects at my current company, how would my experience be seen if I applied for devops jobs? I might not have the experience or background to answer a lot of interview questions, but I'm still coming in with plenty of Python, SQL, shell scripting, and AWS experience.

https://redd.it/10tw0tf
@r_devops

On the verge of taking a Devops Engineer bootcamp.

Please tell me all your
pros and cons
about this position.

https://redd.it/10r7n73
@r_devops

Am I shadowbanned?

Testing if I can see this post, my comments seem not to appear on this subreddit.

https://redd.it/10r2ek0
@r_devops

What Package Repository software are you using?

Morning all... Quick question. What is everyone using for package storage and replication? We've got about 10 package servers internally at my company, and I'm wondering what folks are using. Paid package repos are expensive, so I'm wondering what folks are using and if it's a home rolled solution, how are you handling replication and the like.

https://redd.it/10qv8ky
@r_devops

Minimize delivery risk with progressive delivery

A short article about reducing delivery risk with traffic routing and feature flags.


https://dev.to/cosmicflood/reduce-risk-with-progressive-delivery-43p8

https://redd.it/10qosco
@r_devops

How to get into DevOps 2023?

I've been a software engineer almost a year now, and I'd like to pivot into DevOps in years to come.

Experienced ops, how did you get into it(entry level)? What would you advise?

https://redd.it/10qy326
@r_devops

Triggering Lambda from one region to all

I am using Event bridge to trigger a lambda function. Suppose a S3 bucket is created in us-west-2 region(same as lambda function) and another bucket in us-east-1 but lambda triggers for us-west-2 only. How can I solve this for other regions too ?

https://redd.it/10qo5wt
@r_devops

Are the AWS certs still worth it?

I've spent a lot of time on these so I hope so.

https://redd.it/10u6fyy
@r_devops

Cloudfront dist for site maintenance

Hello folks,
I have 100 sites which all are serving through cloudfront distribution and finally with cloudflare dns, now I want to go for site maintenance for certain time, so what I want is-
1. Show custom site maintenance page

2. Stop serving cloudfront


How should I do it

https://redd.it/10u78hj
@r_devops

Career advice for a new Junior DevOps

Hi, I started as DevOps Engineer job 6 months ago with no background, I only really knew Linux/AWS/Python and got myself AWS SAA cert and that's about it.

I got into a junior position in q company which has a product that is:

1) Not containerized - the application is just 1 big monolith mess that is also unoptimized.

2) Not in the Cloud - right now we just run on VM's

3) Undocumented - i feel like i can count on 1 hand the amount of people that are documenting stuff.

4) Understaffed - most of the people that made the product have left

Although as a DevOps I am supposed to support the infrastructure and developers I spend around half the time supporting the application.

Now, what bothers me most about this job is that I am not working with 'meta' tools(K8S, cloud, terraform, ansible etc...)

I am worrying this could be a career suicide nowadays and it would be hard to find a new job(when that day happens) that doesn't require experience on fancy tools.

Now don't get me wrong, we are currently not using the tools right now but it is planned to use the tools in the future the problem is that R&D thinks that moving the application from monolith to microservices/containers will take years so that puts me in a strange position in my career.

Do I stay around and see how it plays out, do I self-learn the tools and try to find a new job after 2 years?

What would you be doing in my position?

https://redd.it/10u8081
@r_devops

Laravel Containerization or serverless

Hello,

Just looking for opinions on which deployment better is more suitable for laravel apps. We currently deploy to EC2 and have recently been looking at modernising our approach.

Discussing with the dev teams there seems to be a real divide between which technology to use. While I can see the pros and cons of each approach I am edging towards a containerized deployment as it provides a more comfortable dev environment and tech like ECS Fargate can remove a lot of the infrastructure maintenance overhead.

Serverless while it maybe quicker to scale seems to have certain limitations in terms of response size. Some of our APIs have pretty huge response bodies (a problem for another day). API Gateway also has some limitations in the timeout which I think when we are under heavy load could cause issues for us.

Does anyone recommend one deployment method over the other? What experiences have you had? Anything to keep an eye out for?

https://redd.it/10qnu8d
@r_devops

What is the best resource (something similar to leetcode, codecademy) to learn the docker and practice it at the same time?

I'm looking for a platform similar to leetcode, codecademy where I can learn lessons and practice exercises while keeping track of my progress. Are there such sites for docker?

I want to get at least beginner level better before I setup VPS and practice on actual server.

https://redd.it/10ublw1
@r_devops