You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
psycholog1st
letronghoangminh
A script kiddie who like to make possible things impossible
This documentation provides a comprehensive guide on implementing Role-Based Access Control (RBAC) in a Kubernetes environment seamlessly integrated with AWS Identity and Access Management (IAM). This integration allows organizations to leverage our existing AWS IAM infrastructure to manage and control access to Kubernetes resources.
This RBAC module is implemented by Terraform and can be found at: <github_placeholder>
Using Renovate on Azure DevOps for automatic Nuget packages version upgrades
Overview
Renovate Bot is an automated tool that helps keep software dependencies up to date. It scans repositories, detects outdated dependencies, and creates pull requests to update them, reducing the risk of security vulnerabilities and compatibility issues. Renovate supports multiple package managers, integrates with platforms like GitHub and GitLab, and offers customization options for scheduling and update rules.
In this article, we will focus on integrating Renovate bot to Azure DevOps services for Nuget packages upgrade.
To be honest, this article is more like a personal note & experiments on .NET deployment models, the knowledge will mainly taken from the Microsoft's official docs. I’ll try to keep the article clear and useful.
.NET applications can be deployed in two main ways: Framework-dependent and Self-contained.
The first one, as its name already tells, requires local .NET runtime that's compatible with the application, the other packs everything up and distributes as a single runnable binary.
If the case "one thing fail, everything stops" cannot be accepted, we must find a way to tolerate the fault => Build general-purpose abstractions with useful guarantees, let applications rely on those abstractions.
Consistency Guarantees
Transaction isolation is primarily about avoiding race conditions due to concurrently executing transactions, whereas distributed consistency is mostly about coordinating the state of replicas in the face of delays and faults.
Linearizability
Knowned as atomic consistency, strong consistency. The idea is to make a system appear as if there were only one copy of the data, and all operations on it are atomic.