Local development against a remote Kubernetes or OpenShift cluster
https://github.com/telepresenceio/telepresence
https://github.com/telepresenceio/telepresence
GitHub
GitHub - telepresenceio/telepresence: Local development against a remote Kubernetes or OpenShift cluster
Local development against a remote Kubernetes or OpenShift cluster - telepresenceio/telepresence
👍3
The article emphasizes that while PSA is native and aligns with security standards, its customization capabilities are somewhat limited. The guide aims to modernize security approaches with practical, step-by-step guidance, catering to developers and administrators involved in cloud computing and Kubernetes environments. For a comprehensive understanding, you can read the full article here.
https://hackernoon.com/migrating-from-pod-security-policies-a-comprehensive-guide-part-1-transitioning-to-psa
https://hackernoon.com/migrating-from-pod-security-policies-a-comprehensive-guide-part-1-transitioning-to-psa
Hackernoon
Migrating from Pod Security Policies: A Comprehensive Guide (Part 1: Transitioning to PSA)
Transition to PSA: Migrate from Pod Security Policies (PSP) to native Pod Security Admission (PSA) in Kubernetes for enhanced security.
👍3
DevOps & SRE notes
Good news everyone. AWS should provide a solution https://twitter.com/jeffbarr/status/1785386554372042890
Good news in short. Bucket owners will never incur request or bandwidth charges for requests that return an HTTP 403 (Access Denied) error response if initiated from outside their individual AWS account or AWS Organization.
https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-s3-no-charge-http-error-codes/
https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-s3-no-charge-http-error-codes/
Amazon
Amazon S3 will no longer charge for several HTTP error codes - AWS
Discover more about what's new at AWS with Amazon S3 will no longer charge for several HTTP error codes
🔥6🎉2😱1
The blog post provides a comprehensive guide to using Docker Compose for managing multi-container Docker applications. It covers the basics of Docker Compose, differences between Docker and Docker Compose, and detailed instructions on writing a compose.yaml file. It also delves into starting, stopping, and managing services, volumes, and networks within Docker Compose, aiming to simplify the deployment and scaling of applications. For more detailed information and guidance, you can read the full post here.
https://devopscycle.com/blog/the-ultimate-docker-compose-cheat-sheet/
https://devopscycle.com/blog/the-ultimate-docker-compose-cheat-sheet/
Devopscycle
The Ultimate Docker Compose Cheat Sheet
Get your Docker Compose Cheat Sheet as PDF or PNG. In this article, you learn how to manage Multi Container Apps with Docker Compose.
👍7
https://github.com/TheCloudTheory/arm-estimator
ACE (Azure Cost Estimator) - automated cost estimations for ARM Templates, Bicep and Terraform
ACE (Azure Cost Estimator) - automated cost estimations for ARM Templates, Bicep and Terraform
GitHub
GitHub - TheCloudTheory/arm-estimator: ACE (Azure Cost Estimator) - automated cost estimations for ARM Templates, Bicep and Terraform
ACE (Azure Cost Estimator) - automated cost estimations for ARM Templates, Bicep and Terraform - TheCloudTheory/arm-estimator
👍5
🛡 Kubernetes Config Syncer (previously kubed)
https://github.com/config-syncer/config-syncer
https://github.com/config-syncer/config-syncer
GitHub
GitHub - config-syncer/config-syncer: 🛡️ Kubernetes Config Syncer (previously kubed)
🛡️ Kubernetes Config Syncer (previously kubed). Contribute to config-syncer/config-syncer development by creating an account on GitHub.
👍5
The post shares insights and experiences from Figma's database team on managing and scaling their database systems. Such articles typically cover challenges faced during growth, strategies for maintaining performance, and lessons learned throughout the process.
https://www.figma.com/blog/how-figmas-databases-team-lived-to-tell-the-scale/
https://www.figma.com/blog/how-figmas-databases-team-lived-to-tell-the-scale/
Figma
How Figma's Databases Team Lived to Tell the Scale | Figma Blog
Our nine month journey to horizontally shard Figma’s Postgres stack, and the key to unlocking (nearly) infinite scalability.
👍3
The blog post on VLT Technology discusses a significant vulnerability within the npm ecosystem known as "manifest confusion." This issue arises because npm package manifests are published independently from their tarball contents without thorough validation, leading to potential exploits through inconsistent or malicious data in package dependencies or noscripts. The post details the history, the problem's implications, and steps to reproduce the issue, emphasizing the widespread impact on security and package integrity.
https://blog.vlt.sh/blog/the-massive-hole-in-the-npm-ecosystem
https://blog.vlt.sh/blog/the-massive-hole-in-the-npm-ecosystem
vlt /vōlt/ - blog
The massive bug at the heart of the npm ecosystem
An article detailing the massive bug at the heart of the npm ecosystem; encompassing a lack of validation by the public registry, package manifest inconsistancies & assumptions about package managers & security products
👍4
Opensource IDE For Exploring and Testing Api's (lightweight alternative to postman/insomnia)
https://github.com/usebruno/bruno
https://github.com/usebruno/bruno
GitHub
GitHub - usebruno/bruno: Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia) - usebruno/bruno
👍6
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication features. Garnet can work with existing Redis clients.
https://github.com/microsoft/garnet
https://github.com/microsoft/garnet
GitHub
GitHub - microsoft/garnet: Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and…
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication feat...
👍4
Good introduction for starting set up on-call culture in your company.
https://grafana.com/blog/2024/03/28/call-me-maybe-designing-an-incident-response-process/
https://grafana.com/blog/2024/03/28/call-me-maybe-designing-an-incident-response-process/
Grafana Labs
Call me, maybe: designing an incident response process | Grafana Labs
An incident response process outlines the steps your team needs to take when an incident occurs. Use the tips and cheat sheet in this post to help formulate yours.
👍5
The blog post delves into the challenges faced by on-call personnel due to alert fatigue and the subsequent risk of burnout. It outlines Cloudflare's approach to enhancing alert observability within their systems, aiming to make alerts more actionable and reduce false positives. By leveraging open-source tools and implementing best practices, Cloudflare's observability team shares insights on improving alert management, thereby easing the on-call experience and promoting personnel well-being.
https://blog.cloudflare.com/alerts-observability/
https://blog.cloudflare.com/alerts-observability/
The Cloudflare Blog
Minimizing on-call burnout through alerts observability
Learn how Cloudflare used open-source tools to enhance alert observability, leading to increased resilience and improved on-call team well-being
👍3
Write tests against structured configuration data using the Open Policy Agent Rego query language
https://github.com/open-policy-agent/conftest
https://github.com/open-policy-agent/conftest
GitHub
GitHub - open-policy-agent/conftest: Write tests against structured configuration data using the Open Policy Agent Rego query language
Write tests against structured configuration data using the Open Policy Agent Rego query language - open-policy-agent/conftest
👍4
In the fast-paced world of Kubernetes and container orchestration, monitoring and metrics play a pivotal role in ensuring the health, efficiency, and reliability of applications. The article provides an insightful exploration into the criticality of pod metrics within the Kubernetes ecosystem
https://komodor.com/blog/harnessing-the-power-of-metrics-four-essential-use-cases-for-pod-metrics/
https://komodor.com/blog/harnessing-the-power-of-metrics-four-essential-use-cases-for-pod-metrics/
Komodor
Harnessing the Power of Metrics: Four Essential Use Cases for Pod Metrics
In this article, we will explore four essential use cases for pod metrics and their significance in driving operational excellence.
👍5
The introduction of Kubernetes Gateway API v1.0 marks a significant milestone, promising to enhance how developers and cluster operators manage and expose their services. The article dives deep into the nuances of this new API version, comparing it with the traditional Ingress controllers and highlighting its potential to redefine traffic routing within Kubernetes clusters. F
https://dev.to/apisix/kubernetes-gateway-api-v10-should-you-switch-45c0
https://dev.to/apisix/kubernetes-gateway-api-v10-should-you-switch-45c0
DEV Community
Kubernetes Gateway API v1.0: Should You Switch?
It has been over a month since the Kubernetes Gateway API made its v1.0 release, signifying...
👍4
Blog post addresses a critical aspect of container security—the ReadOnlyRootFilesystem flag. This insightful article elucidates the concept of making the root filesystem of a container read-only to prevent unauthorized modifications, which can be a common vector for security breaches.
https://alexandre-vazquez.com/readonlyrootfilesystem/
https://alexandre-vazquez.com/readonlyrootfilesystem/
Alexandre Vazquez
Enhancing Container Security: The Vital Role Of ReadOnlyRootFilesystem
Enhance container security with ReadOnlyRootFilesystem, a potent tool safeguarding your applications. Understand how ReadOnlyRootFilesystem limits write access to containers, bolstering their integrity amidst software development's dynamic landscape. Explore…
👍7
This article explores the underutilized Postgres feature of HOT (Heap Only Tuple) updates and the strategic use of fill factor to enhance database performance. It delves into how HOT updates allow for modifications within the same table page, bypassing index updates and reducing system load.
https://www.crunchydata.com/blog/postgres-performance-boost-hot-updates-and-fill-factor
https://www.crunchydata.com/blog/postgres-performance-boost-hot-updates-and-fill-factor
Crunchy Data
Postgres Performance Boost: HOT Updates and Fill Factor | Crunchy Data Blog
Elizabeth reviews HOT updates, what they are, how they work, and how you can put them to use for a performance improvement.
👏5