
1_r/devopsish
Terraform vs. Crossplane vs. Ansible - Rivals or Allies?
In this video we dive deep into the world of Infrastructure as Code (IaC) and resource management and explore tools like Terraform, Crossplane, Ansible, Helm, and a few others. Are they competitors, or can they function as allies within your DevOps toolkit?
Terraform #Ansible #Crossplane
Consider joining the channel: https://www.youtube.com/c/devopstoolkit/join
▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬ ➡ Transcript: https://devopstoolkit.live/infrastructure-as-code/ansible-vs-terraform-vs-crossplane
▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬ If you are interested in sponsoring this channel, please use https://calendar.app.google/Q9eaDUHN8ibWBaA7A to book a timeslot that suits you, and we'll go over the details. Or feel free to contact me over Twitter or LinkedIn (see below).
▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬ ➡ Twitter: https://twitter.com/vfarcic ➡ 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=tgwxMfIsLJY
Blog: Introducing Hydrophone
https://www.kubernetes.dev/blog/2024/05/23/introducing-hydrophone/
In the ever-changing landscape of Kubernetes, ensuring that clusters operate as intended is essential. This is where conformance testing becomes crucial, verifying that a Kubernetes cluster meets the required standards set by the community. Today, we’re thrilled to introduce Hydrophone, a lightweight runner designed to streamline Kubernetes tests using the official conformance images released by the Kubernetes release team.
Simplified Kubernetes testing with Hydrophone
Hydrophone’s design philosophy centers around ease of use. By starting the conformance image as a pod within the conformance namespace, Hydrophone waits for the tests to conclude, then prints and exports the results. This approach offers a hassle-free method for running either individual tests or the entire Conformance Test Suite.
Key features of Hydrophone
Ease of Use: Designed with simplicity in mind, Hydrophone provides an easy-to-use tool for conducting Kubernetes conformance tests.
Official Conformance Images: It leverages the official conformance images from the Kubernetes Release Team, ensuring that you’re using the most up-to-date and reliable resources for testing.
Flexible Test Execution: Whether you need to run a single test, the entire Conformance Test Suite, or anything in between.
Streamlining Kubernetes conformance with Hydrophone
In the Kubernetes world, where providers like EKS, Rancher, and k3s offer diverse environments, ensuring consistent experiences is vital. This consistency is anchored in conformance testing, which validates whether these environments adhere to Kubernetes community standards. Historically, this validation has either been cumbersome or requires third-party tools. Hydrophone offers a simple, single binary tool that streamlines running these essential conformance tests. It’s designed to be user-friendly, allowing for straightforward validation of Kubernetes clusters against community benchmarks, ensuring providers can offer a certified, consistent service.
Hydrophone doesn’t aim to replace the myriad of Kubernetes testing frameworks out there but rather to complement them. It focuses on facilitating conformance tests efficiently, without developing new tests or heavy integration with other tools.
Getting started with Hydrophone
Installing Hydrophone is straightforward. You need a Go development environment; once you have that:
go install sigs.k8s.io/hydrophone@latest
Running hydrophone by default will:
Create a pod, and supporting resources in the conformance namespace on your cluster.
Execute the entire conformance test suite for the cluster version you’re running.
Output the test results and export e2e.log and junit_01.xml needed for conformance validation.
There are supporting flags to specify which tests to run, which to skip, the cluster you’re targeting and much more!
Community and contributions
The Hydrophone project is part of SIG Testing and open to the community for bugs, feature requests, and other contributions. You can engage with the project maintainers via Kubernetes Slack channels
hydrophone, #sig-testing, and #k8s-conformance, or by filing an issue against the
repository. We’re also active in the Kubernetes SIG-Testing and SIG-Release Mailing Lists. We encourage pull requests and discussions to make Hydrophone even better.
Join us in simplifying Kubernetes testing
In SIG Testing, we believe Hydrophone will be a valuable tool for anyone looking to validate the conformance of their Kubernetes clusters easily. Whether you’re developing new features, or testing your application, Hydrophone offers an efficient testing experience.
via Kubernetes Contributors – Contributor Blog https://www.kubernetes.dev/blog/
May 22, 2024 at 08:00PM
Week Ending May 19, 2024
https://lwkd.info/2024/20240522
Developer News
CNCF TAG Environmental Sustainability is looking for best practice recommendations. MiniKube has fast 5-question survey.
The CNCF has shared a statement about Kubecon NA 2024 and Utah law.
Celebrate Kubernetes’ 10th anniversary on June 6! Contributors are planning events all over the world for our first decade.
Release Schedule
Next Deadline: Production Readiness Freeze, June 6th, 2024
Release Team Shadow notifications will be sent out by Wednesday, May 22, 2024, at the latest.
SIG Leads and contributors: time to decide which Enhancements are making 1.31.
Patch releases 1.30.1, 1.29.5, 1.28.10, and 1.27.14 are available. This is largely a bigfix release, including patch some 1.30 regressions, and an golang update.
KEP of the Week
KEP 4568: Resilient watchcache initialization
This KEP mitigates the issues that can lead to an overload of the of kube-apiserver and etcd during initialization or reinitialization of the watchcache layer.
The changes reduce the number of requests during initialization, by introducing a new PostStartHook that waits for watchcache of all builtin resources to be initialized first. It also implements rejecting hanging watches with a Too Many Requests 429 result. Other changes include adjusting which lists are delegated to etcd.
This KEP is tracked to be promoted to beta in the upcoming 1.31 release.
Other Merges
Reversion: DisableServiceLinks admission controller in favor of Mutating Admission Policies
Reverted Reversion: revert removing legacy cloud providers from staging, and then revert the reversion, so they are actually gone from staging, at least until next week
Ignore the grace period when terminating for resource outage or force-terminate
All scheduler profiles have access to all waiting pods
Add a whole set of “keeper flags” for kubectl debug
Prevent running with a errorful encryption config
Don’t require finalizer role for cronjobs, for backwards compatibility
Kubeadm: allow patching coredns deployment, use etcd’s livez & readyz, get image pull policy from UpgradeConfiguration
Move the remote CRI code to cri-client
Warn when the reflector bookmark wasn’t received
Test Improvements: swap stress tests
Deprecated
Remove ENABLE_CLIENT_GO_WATCH_LIST_ALPHA variable from reflector
Version Updates
go to 1.21.10 in release versions, and 1.22.3 in v1.31
Subprojects and Dependency Updates
cri-o to v1.30.1: fixed kubelet image garbage collection
kops to v1.29: (experimental) support for OpenTelemetry
minikube to v1.33.1: fix cilium pods failing to start-up
kind to v0.23.0: initial limited support for nerdctl and kube-proxy nftables mode
kubebuilder to v3.15.0: discontinue Kube RBAC Proxy in Default Kubebuilder Scaffolding
containerd to v1.7.17: handle unsupported config versions
via Last Week in Kubernetes Development https://lwkd.info/
May 22, 2024 at 03:00PM
About Winamp - Winamp has announced that it is opening up its source code to enable collaborative development of its legendary player for Windows.
Winamp • May 16, 2024 • Press Release Winamp has announced that on 24 September 2024, the application's source code will be open to developers worldwide. Winamp…
May 22, 2024 at 01:31PM
via Instapaper
semgrep/semgrep: Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
Code scanning at ludicrous speed. This repository contains the source code for Semgrep OSS (open-source software). Semgrep OSS is a fast, open-source, static…
May 22, 2024 at 09:33AM
via Instapaper