
1_r/devopsish
Ep27 - Ask Me Anything About Anything with Scott Rosenberg
There are no restrictions in this AMA session. You can ask anything about DevOps, AI, Cloud, Kubernetes, Platform Engineering, containers, or anything else. Scott Rosenberg, regular guest, will be here to help us out.
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Sponsor: Codefresh 🔗 GitOps Argo CD Certifications: https://learning.codefresh.io (use "viktor" for a 50% discount) ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬ ➡ BlueSky: https://vfarcic.bsky.social ➡ LinkedIn: https://www.linkedin.com/in/viktorfarcic/
▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬ 🎤 Podcast: https://www.devopsparadox.com/ 💬 Live streams: https://www.youtube.com/c/DevOpsParadox
via YouTube https://www.youtube.com/watch?v=3fNbnkzB-po
Better Code Reviews with AI? GitHub Copilot and Qodo Merge Tested
Discover how AI is transforming code reviews by comparing two prominent AI agents: GitHub Copilot Code Review and Qodo Merge. We'll explore how these tools integrate seamlessly into GitHub pull requests, evaluate their strengths and weaknesses, and see how their suggestions can be efficiently incorporated into your development workflow directly from your IDE. Whether you're already using AI for code reviews or just getting started, this comparison will help you understand which tool might best fit your needs and why second (or even third) opinions from AI can significantly improve your coding process.
In this video, we'll weigh Qodo's detailed and comprehensive suggestions against Copilot's more structured and familiar commenting style. You'll see firsthand how each tool performs in real-world scenarios, highlighting Qodo's superior issue detection and Copilot's cleaner presentation. By the end, you'll understand the practical benefits of integrating AI code reviews into your workflow and gain clarity on which AI-powered solution is right for you.
AIcodeReview #GitHubCopilot #QodoMerge
Consider joining the channel: https://www.youtube.com/c/devopstoolkit/join
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬ ➡ Transcript and commands: https://devopstoolkit.live/ai/better-code-reviews-with-ai-github-copilot-and-qodo-merge-tested 🔗 GitHub Copilot Code Review: https://docs.github.com/en/copilot 🔗 Qodo Merge: https://www.qodo.ai/products/qodo-merge/ 🎬 My Workflow With AI: How I Code, Test, and Deploy Faster Than Ever: https://youtu.be/2E610yzqQwg
▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬ If you are interested in sponsoring this channel, please visit https://devopstoolkit.live/sponsor for more information. Alternatively, feel free to contact me over Twitter or LinkedIn (see below).
▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬ ➡ BlueSky: https://vfarcic.bsky.social ➡ LinkedIn: https://www.linkedin.com/in/viktorfarcic/
▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬ 🎤 Podcast: https://www.devopsparadox.com/ 💬 Live streams: https://www.youtube.com/c/DevOpsParadox
▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬ 00:00 Introduction 01:18 AI Code Reviews 07:10 Fixing Issues Detected in Code Reviews 08:38 AI Code Reviews Pros and Cons
via YouTube https://www.youtube.com/watch?v=wmmMYFVNxA0
Week Ending June 22, 2025
https://lwkd.info/2025/20250627
Developer News
Having completed their work, WG-Policy is being archived. Congrats Policy team!
There is an ongoing discussion in the Kubernetes community regarding the Slack migration, and new platform options are currently being evaluated. Please share your thoughts to help shortlist a suitable new platform.
The CFPS for the CNCF-hosted Co-located Events North America 2025 are closing soon. Make sure to submit your proposals by June 30th.
The KubeCon North America 2025 Maintainer Summit CFP is also open. Please submit your sessions by July 20th.
Release Schedule
Next Deadline: Open Doc Placeholders, July 3
With 70 enhancements tracked, it’s time to wrap up work on those changes. The next step is opening a Docs placeholder PR so that the Docs team knows that you’ll be ready by Docs deadline on Jul 29. Didn’t get your Enhancement approved in time? You have until July 7th to request an exception.
Patch releases v1.33.2, 1.32.6, 1.31.10 and 1.30.14 are released, including a security update for Golang. This is likely to be the last patch release for Kubernetes 1.30, so users on that version should plan to upgrade soon.
Featured PRs
132504: Introduce OpenAPI format support for k8s-short-name and k8s-long-name
This PR introduces support for k8s-short-name and k8s-long-name in OpenAPI schema validation for Custom Resource Definitions (CRDs); These formats are now recognized in the OpenAPI validation of CRD schemas, allowing Kubernetes-native name formats to be used consistently in the validation of CRD fields.
126619: Show namespace on delete
This PR updates the kubectl delete command to include the namespace in the output, improving clarity when resources are deleted across multiple namespaces; Previously, the output could be ambiguous, especially when targeting resources in different namespaces; This enhancement helps to avoid confusion by explicitly showing the namespace during delete operations.
KEP of the Week
KEP 4800: Split UncoreCache Topology Awareness in CPU Manager
This KEP introduced a new static policy prefer-align-cpus-by-uncorecache for the CPU Manager that groups CPU resources by uncore cache where possible. An uncore cache refers to the cache that exists at a shared level among CPU cores. This is primarily beneficial for CPU architectures that utilize multiple uncore caches, or split uncore caches, within the processor.
This KEP is tracked for beta in v1.34.
Other Merges
Actively poll for namespace termination instead of sleeping
Fix for being able to custom resources with server side apply even when its CustomResourceDefinition was terminating
e2e/watchlist test for checking metadata informer
apimachinery/pkg/util/errors to deprecate MessageCountMap
API response for StorageClassList to return a graceful error message if the provided ResourceVersion is too large
MutableCSINodeAllocatableCount storage e2e test refactored to use the Mock CSI driver
omitempty and opt tag added to the API v1beta2 AdminAccess type in the DeviceRequestAllocationResult struct
Job controller now uses controller UID index for pod lookups
ListAll and ListAllByNamespace optimized to return directly when there is nothing to select
Cleanup after alpha feature MountContainers was removed
New runtime.ApplyConfiguration interface added that is implemented by all generated applyconfigs
cloud provider calls in storage/volume_provisioning.go removed
Usage of deprecated function ExtractCommentTags migrated to ExtractFunctionStyleCommentTags
Delay added to node updates after kubelet startup
Conntrack reconciler now considers service’s target port during cleanup of stale flow entries
kube-scheduler: Apply EnablePlugins to CoreResourceEnqueueTestCases
etcd server overrides to etcd probe factory for healthz and readyz
endpointsleases and configmapsleases options removed from leader-elect-resource-lock in LeaderElectionConfiguration
Deprecated –register-schedulable command line argument removed from the kubelet
Promotions
JobPodReplacementPolicy to GA
Subprojects and Dependency Updates
containerd v2.1.3: fixes registry fetch and transfer service issues
cluster-api v1.11.0-alpha.1: releases alpha version for testing
Shoutouts
Josh Berkus (@jberkus): Kudos to Mario Fahlandt (@Mario Fahlandt) for figuring out how to back up private channels from Slack.
via Last Week in Kubernetes Development https://lwkd.info/
June 27, 2025 at 09:08AM
On with the show
https://anonymoushash.vmbrasseur.com/2025/06/on-with-the-show.html
Well, that didn’t work out as hoped, but unfortunately it did work out as expected.
I was legitimately excited by the opportunity and potential for open source and open collaboration in the digital agriculture space. I still am, to be honest. Not only is it good for humanity, there are a lot of fantasticly strong business strategies that it could enable.
So when I noted some red flags during the interview process, that opportunity and potential were great enough that I made the informed choice to move forward with the job anyway. There were still far more unknowns than knowns and it was possible (and maybe even likely) that the red flags would turn out to be false alarms.
As you’ve already figured out, that wasn’t the case. First the CEO and other execs were shown the door in December, then the interim leadership made a number of large organisational changes. These changes included cutting a very significant percentage of total headcount, myself included. It’s little comfort knowing that I was in good company when the company laid me off in April, but little is better than none. At least it wasn’t personal.
In the past two months I’ve caught up on sleep, made my yearly pilgrimage to Montreal, hosted guests, and done a little work for the fantastic folks at Open Robotics. I’m feeling much better following my months at Semios and can once again turn my mind to all things strategy, operations, business, and open source.
I’m considering my options for what to do next and having conversations with folks to clarify that direction. Will I remain in the corporate world, or is it finally time for me to dedicate myself fully to the nonprofit space? Do I stay with open source or will I apply my experience and strategic skills more broadly?
I’m figuring out the answers to these and other questions. If you’d like to be a part of those conversations—or if you’d just like to catch up or say howdy—drop me a line. I’d welcome the chance to chat.
via {anonymous => 'hash'}; https://anonymoushash.vmbrasseur.com/
June 26, 2025 at 03:00AM