&udm=14 | the disenshittification Konami code
What is "&udm=14"? • TenBlueLinks • FrogFind • Built by Tedium Grab the code: Glitch | Github Versions Regular | SFW Note: The feature this relies on, while…
May 28, 2024 at 10:10AM
via Instapaper
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?
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
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
%2Fcdn.vox-cdn.com%2Fuploads%2Fchorus_asset%2Ffile%2F24440533%2FAI_Hands_A_Bernis_02.jpg?width=92&height=&ar=&mode=&format=avif&dpr=2)
%2Fcdn.vox-cdn.com%2Fuploads%2Fchorus_asset%2Ffile%2F25461932%2FScreenshot_2024_05_23_at_1.02.54_PM.png?width=92&height=&ar=&mode=&format=avif&dpr=2)
