Engineering Glossary

A record in Git's index file representing the state of a file in the repository.

A connection between Git and other tools or services to enhance functionality and workflow.

A short sequence of bytes used to identify a longer public key in Git's GPG signing process.

A secure storage system for passwords and keys, often integrated with Git clients for credential management.

A reserved word in Git commands or configurations with a specific meaning or function.

A way to categorize and organize issues and pull requests in GitHub repositories.

A document in a Git repository specifying how the project can be used, modified, and distributed.

A feature in Git platforms allowing users to comment on specific lines of code in pull requests or commits.

Characters marking the end of a line, which can cause issues in Git when collaborating across different operating systems.

A GitHub account that has been restricted due to a violation of terms of service or suspicious activity.

The default name for the primary branch in many Git repositories, replacing 'master' in recent conventions.

An administrative interface for managing Git hosting services, often used in enterprise environments.

A system of annotation used to format text, often used in Git documentation and comments.

A visual representation of an organization's membership on Git hosting platforms.

A situation in Git where incompatible changes have been made to the same part of a file, requiring manual resolution.

A way to track progress on groups of issues or pull requests in GitHub projects.

A complete copy of a repository, including all branches and history, often used for backup or as a full replica.

A team within a GitHub organization that is a subset of a larger team, inheriting its permissions.

A visual representation of the commit history and branch structure of a Git repository.

A personalized list of recent activity on Git platforms, showing updates from followed users and repositories.

A Git push that introduces new commits to the remote branch that aren't direct descendants of the current remote HEAD.

An alert system on Git platforms to inform users about relevant activities and mentions.

A fundamental unit in Git's data model, representing content, commits, trees, or tags, identified by a unique SHA-1 hash.

The storage system in Git that contains all versions of project files and metadata, organized by SHA-1 hashes.

A unique SHA-1 hash that identifies a Git object, ensuring data integrity and enabling content-addressable storage.

Another term for the SHA-1 hash that uniquely identifies a Git object in the repository.

The classification of Git objects, including blob (file content), tree (directory structure), commit, and tag.

A Git merge involving more than two branches simultaneously, creating a commit with multiple parents.

A shared account on Git hosting platforms where businesses and open-source projects can collaborate across many projects.

A user with administrative privileges for an organization account on Git hosting platforms.

A branch in Git with no parent commit, typically used to start a new history unrelated to existing branches.

A user granted access to a repository but not a member of the organization that owns the repository.

A Git feature that allows files from one branch to temporarily override files in another branch without merging.

The user or organization with administrative rights to a Git repository, controlling access and settings.

A compressed file format used by Git to store multiple objects efficiently, reducing repository size.

A file that provides fast random access to objects stored within a packfile in Git.

A commit from which another commit is derived, establishing the hierarchical relationship in Git history.

A team in a Git platform that grants its permissions to nested sub-teams within an organization.

Alerts received when you're directly involved in repository activities like being assigned or mentioned.

A pattern used in Git commands to limit the scope of operations to specific files or directories.

The process of recursively dereferencing a Git object to reveal its underlying object type.

A reference specific to a particular working tree in a Git repository with multiple worktrees.

A URL that points to a specific version of a file or directory in a Git repository, ensuring consistent reference.

An individual account on Git platforms, used for personal projects and contributions.

A Git feature for searching the repository history to find when a particular change was introduced.

A featured repository prominently displayed on a user's or organization's profile page on their Git hosting platform of choice.

Low-level Git commands that expose internal workings, primarily used for scripting and advanced operations.

High-level Git commands designed for everyday use, providing a user-friendly interface to common version control tasks.

Server-side scripts that run before pushed commits are accepted, used to enforce policies or perform checks.

The main email associated with a Git account, used for communications and commit author identification.

Contributions made to private repositories, typically only visible to repository collaborators.

A Git repository with restricted access, visible only to the owner and explicitly granted collaborators.

A Git branch that represents the stable, deployed version of a project, often protected from direct changes.

A user's public page on a Git platform, displaying information about their activity and repositories.

An image representing a user on a Git platform, displayed alongside their contributions and activities.

A kanban-style board in Git platforms for organizing and prioritizing project issues and pull requests.

A branch with rules enforcing certain conditions before changes can be pushed, merged, or deleted.

A Git reference that doesn't follow the standard refs format but is treated similarly, like HEAD or MERGE_HEAD.

Contributions made to public repositories, visible on a user's profile and activity feed.

A Git repository that is openly accessible to anyone, allowing viewing and often cloning without authentication.

Permission level in Git allowing a user to clone a repository and fetch updates, but not push changes.

The process of examining proposed changes in a pull request before they are merged into the main codebase.

A visual representation of a GitHub repository's recent activity, including commits, issues, and pull requests.

A visualization of commit frequency over time, often displayed as a heatmap on Git platforms.

The act of uploading commits from a local branch to a corresponding branch in a remote Git repository.

Permission to upload local changes to a remote Git repository, allowing direct modification of shared branches.

Data structures used to optimize Git operations by quickly determining which objects are reachable from a given commit.

Git objects that can be accessed by following the commit history from a given reference point.

Permission to view and clone a Git repository without the ability to make changes or push commits.

A backup method for accessing a Git account if two-factor authentication is enabled but unavailable.

A name that points to a specific Git object, typically a commit, such as branches or tags.

The collection of references in a Git repository, including branches, tags, and other named pointers to commits.

The address of a remote Git repository, used for fetching and pushing changes between local and remote repositories.

A version of a Git project hosted on a server, serving as a central point for collaboration and backup.

A local reference that represents the state of a corresponding branch in a remote repository.

A copy of a Git repository, often used in distributed systems for redundancy and load balancing.

A local storage of repository data used to improve performance in Git operations.

A visual representation of the commit history and branch structure in a Git repository.

A person responsible for managing a Git repository, reviewing contributions, and maintaining project quality.

A protection rule requiring one or more reviewers to approve changes before merging in Git platforms.

A condition that must be met, such as passing tests, before changes can be merged into a protected branch.

The process of addressing and fixing merge conflicts in Git, typically done manually by the developer.

A Git operation that creates a new commit that undoes the changes made by a previous commit.

The process of examining proposed changes in a pull request before merging them into the main codebase.

A specific version of a file, directory, or entire repository in Git, often referenced by a commit hash.

The act of moving a branch pointer to an earlier commit in Git, effectively undoing more recent commits.

The top-level directory of a Git repository, containing all project files and the .git subdirectory.

The base filesystem of a Git repository, from which all other directories and files are organized.

A pre-written response that can be quickly inserted into issues or pull request comments on Git platforms.

The range of access or permissions granted to a token or application in Git-based systems.

A licensed user in enterprise Git hosting plans, typically representing a single user account.

A team in a Git organization that is hidden from non-members and other teams within the organization.

A record of security-related events and actions in a system, used for monitoring and auditing purposes.

An authenticated request between Git servers, often used in integrations or automated processes.

A mechanism for Git platforms to send event notifications to external services or applications.

A Git repository with an intentionally truncated history, often created through shallow cloning.

An authentication process allowing users to access multiple Git-related services with one set of credentials.

A Git reference with a specific meaning or function, such as HEAD or FETCH_HEAD.

A deployment environment used for testing changes before releasing to production in Git-based workflows.

A feature on Git hosting platforms allowing users to bookmark repositories of interest.

Systems integrating blockchain technology with traditional cloud services for enhanced security and transparency.

Tools and practices for managing resources across public and private cloud environments.

Tracking performance and health of resources spanning both public and private cloud environments.

Coordinating and automating workflows across multiple cloud environments and on-premises infrastructure.

Data storage solutions that span both on-premises and cloud environments, offering flexible and scalable data management.

Network solutions that connect on-premises infrastructure with cloud services, enabling seamless integration and data flow.

Managing user identities and access across both on-premises systems and cloud services.

Tools for connecting applications, data, and processes across on-premises and cloud environments.

Computational methods combining quantum and classical processing in cloud environments.

Using both quantum and classical computing resources in tandem for cloud-based problem-solving.

Database systems supporting both real-time transactions and analytics in cloud environments.

Integrated compute, storage, and networking in a single cloud-managed system, simplifying data center architecture.

Process of optimizing machine learning model parameters in cloud-based environments.

Software layer that manages virtual machines in cloud computing environments, enabling efficient resource utilization and isolation.

Defined permissions and access controls for users and services in cloud environments.

International standard for information security management in cloud environments.

Security tools that verify user identity before granting access to cloud applications.

Automated process of examining container images for vulnerabilities in cloud environments.

Security approach based on replacing rather than modifying cloud infrastructure components.

Cloud storage that prevents data modification after writing, ensuring data integrity and compliance.

Database system that primarily uses main memory for data storage in cloud environments.

Distributed computing using the collective memory of networked computers in the cloud.

Processing data within network devices to reduce latency and bandwidth use in cloud architectures.

Systems for efficiently updating computation results when input data changes in cloud environments.

Process of organizing data to optimize query performance in cloud databases, enhancing search and retrieval efficiency.

Automated tools for identifying security issues in infrastructure definition files.

Validating infrastructure definitions before deployment in cloud environments, ensuring reliability and consistency.

Cloud-based provision of virtualized computing resources over the internet, including servers, storage, and networking.

Generating cloud infrastructure configurations directly from application code, streamlining development and deployment processes.

Predefined virtual server configurations optimized for different use cases in cloud environments.

Visual tool for creating and managing data integration processes in cloud environments.

Tools for tracking and analyzing the performance of integrated cloud systems and processes.

Automated data storage class selection based on access patterns in cloud environments.

Automatic movement of data between storage tiers based on usage patterns in the cloud.

Network management approach using AI to automate configuration based on business intent.

Network node that connects cloud VPCs to the internet, enabling communication with external resources.

Decentralized storage system for distributing and accessing files in the cloud, enhancing data availability and resilience.

Security tool that monitors network traffic for suspicious activity in cloud environments.

Security system that not only detects but also blocks potential threats in cloud networks.

Processing and analyzing data from Internet of Things devices in cloud environments.

Identifying unusual patterns in data from IoT devices using cloud-based analytics.

Fully managed IoT application platform in the Azure cloud for connecting, monitoring, and managing IoT devices at scale.

Process of collecting and importing data from IoT devices into cloud systems for storage, analysis, and processing.

Centralized repository in the cloud for storing large volumes of IoT device data.

Cloud-based systems for monitoring, updating, and controlling IoT devices, ensuring efficient operation and security at scale.

Process of setting up and configuring IoT devices for secure cloud connectivity.

Software development kit for building applications that connect IoT devices to cloud services.

Deploying cloud intelligence directly to IoT devices for local processing and analytics.

Processing data from IoT devices locally before sending to the cloud, reducing latency and bandwidth usage.

AWS service for running local compute, messaging, and data caching for connected IoT devices.

Central message hub for bi-directional communication between IoT applications and devices.

Tools for connecting and managing diverse IoT devices and data streams in cloud environments.

Cloud-based tools for managing IoT devices from deployment through retirement, ensuring efficient device administration.

Remote software updates for IoT devices managed through cloud platforms, ensuring device security and functionality.

Cloud-based platform for developing, managing, and integrating IoT applications and devices.

Lightweight communication protocols designed for IoT devices in cloud environments.

Cloud service for processing and acting on data from IoT devices based on predefined conditions.

Measures to protect IoT devices, data, and infrastructure in cloud-connected environments.

Real-time processing and analysis of data streams from IoT devices in the cloud.

Cloud service for creating and managing cryptographic keys for data encryption, ensuring secure data protection.

Kubernetes-based platform for building, deploying, and managing serverless workloads.

Kubernetes-native serverless framework enabling function deployment without managing underlying infrastructure.

Rules for controlling network traffic between pods in Kubernetes clusters, enhancing security in cloud-native environments.

Tools for assessing and improving security configurations in Kubernetes environments.

Managed Kubernetes platforms offered by major cloud providers for container orchestration.

Kubernetes native configuration management tool for customizing application configurations.

AWS service for running Lambda functions at edge locations to customize content delivery.

Template for EC2 instance settings used in Auto Scaling groups, defining instance type, AMI, and other parameters.

Security concept of granting only the minimum permissions necessary in cloud environments.

Managing software licenses efficiently to reduce costs in cloud environments, ensuring compliance and cost-effectiveness.

Migration strategy of moving applications to the cloud without significant modifications.

Minimalist virtual machines designed for fast startup and low resource usage in cloud environments.

Lightweight service mesh for Kubernetes, providing observability, reliability, and security for microservices.

Using liquid to dissipate heat in densely packed cloud data centers for improved efficiency.

Service that distributes incoming network traffic across multiple servers to ensure no single server becomes overwhelmed.

Process of collecting, analyzing, and visualizing log data from cloud resources for insights and troubleshooting.

AI-driven analysis of log data to identify patterns, anomalies, and insights in cloud environments.

Tools for building application integrations with minimal hand-coding in cloud environments.

Cloud-based tools for creating applications with little to no traditional programming.

Cloud services enabling app development with minimal coding, using visual interfaces and pre-built components.

Lightweight messaging protocol designed for IoT devices and low-bandwidth networks in cloud ecosystems.

Cloud-based services for building, training, and deploying machine learning models at scale.

Centralized management of critical business data entities in cloud environments.

Tools for developing AI models that can learn how to learn, improving adaptability in cloud environments.

Cloud tools for organizing, integrating, and governing metadata across various data sources.

Advanced antenna designs using engineered materials to enhance cloud network performance.

Gathering and storing quantitative data about cloud resource performance and usage.

Architectural style where frontend apps are composed from independently deployable components in the cloud.

Automating the process of dividing cloud networks into secure zones for enhanced protection.

Connecting and coordinating interactions between independent microservices in cloud architectures.

Strategic process of preparing and scheduling the move of applications and data to cloud environments.

Cloud-based platforms for developing and deploying mixed reality applications, combining virtual and physical environments.

Bringing cloud computing capabilities closer to mobile users to reduce latency and improve performance.

Extending cloud computing capabilities to the edge of mobile networks for lower latency.

Process of making machine learning models available for use in cloud production environments.

Techniques for understanding and interpreting decisions made by AI models in cloud environments.

Tracking the performance and behavior of deployed machine learning models in cloud environments.

Centralized repository for storing and managing machine learning models in cloud environments.

Process of making trained machine learning models available for real-time predictions in cloud environments.

Process of teaching machine learning algorithms to make predictions using data in cloud environments.

Integration of 5G mobile edge computing with container platforms for low-latency applications and services at network edges.

Application of AI and machine learning for automated operations, monitoring, and management of containerized environments.

Guidelines for phasing out older API versions in Kubernetes, ensuring smooth transitions for users.

Mechanisms to extend the Kubernetes API with custom resources and functionalities, enhancing platform capabilities.

Containerized service that acts as a single entry point for all client requests to a microservices architecture.

Core component of Kubernetes that exposes the cluster's API and handles all administrative operations.

Kubernetes feature allowing the API server to be extended with additional APIs without modifying core Kubernetes code.

Approach prioritizing API design before implementation, crucial for developing scalable containerized microservices.

Serverless compute engine for containers, allowing you to run containers without managing the underlying infrastructure.

Design pattern in containerized microservices that wraps a service's interface to make it compatible with other services.

Plugins that intercept requests to the Kubernetes API server before object persistence, enforcing policies or modifying objects.

Admission controllers specifically focused on enforcing security policies and validating security-related configurations.

HTTP callbacks that receive admission requests and can modify or validate objects before they are persisted.

Use of admission webhooks within Kubernetes operators to enforce custom policies or modify resources.

Kubernetes feature providing detailed logging of all requests processed by the API server for security and compliance.

Extension of the Kubernetes API server to include custom resources and functionalities without modifying core Kubernetes.

Combination of multiple ClusterRoles into a single role, simplifying RBAC management in Kubernetes.

Container registries isolated from public networks, used in secure or restricted environments.

Open-source project for exposing heterogeneous leaf devices as resources in Kubernetes clusters.

Setup and management of Prometheus Alertmanager for handling alerts from monitoring systems.

Fully managed Docker container registry provided by AWS for storing, managing, and deploying container images.

Microservices design pattern where a dedicated service acts as an API gateway for other services.

Service mesh implementation that doesn't require sidecars, reducing resource overhead and simplifying deployment.

Open-source tool for deep inspection of container images, including vulnerability scanning and policy enforcement.

Kubernetes operators implemented using Ansible for automating application lifecycle management.

Network policies specific to the Antrea CNI plugin, offering fine-grained control over pod-to-pod communication.

Kubernetes networking solution using Open vSwitch for improved performance and advanced networking features.

Open-source serverless platform that executes functions in response to events or direct invocations.

Security profiles for Linux that restrict program capabilities, enhancing container isolation and security.

Logging implemented within applications, providing detailed insights into application behavior and performance.

Platform providing security and compliance for container-based and cloud-native applications throughout their lifecycle.

Comprehensive security solution for containerized and cloud-native environments, offering vulnerability management and runtime protection.

GitOps continuous delivery tool for Kubernetes, automating application deployment and lifecycle management.

Kubernetes controller for advanced deployment strategies like canary and blue-green deployments.

Declarative GitOps tool for Kubernetes, automating application deployment and synchronization with Git repositories.

Process of storing, organizing, and managing container images and related artifacts in container registries.

Open-source platform for fine-grained access control and authentication in distributed systems.

Access control paradigm where authorization decisions are based on attributes of users, resources, and environment.

Additional metadata added to Kubernetes audit events for enhanced context and analysis, improving audit trails.

Components responsible for processing and storing Kubernetes audit logs, supporting various storage and analysis options.

Records of requests and activities within a Kubernetes cluster, used for security monitoring and compliance.

Configurable detail levels for Kubernetes audit logs, ranging from metadata-only to full request and response details.

Process of recording API server requests and responses for security, troubleshooting, and compliance purposes.

Detailed records of activities and operations within a Kubernetes cluster, used for security and compliance monitoring.

Configuration defining which events should be recorded in Kubernetes audit logs and at what level of detail.

Predefined set of audit policy rules for common use cases in Kubernetes, simplifying audit configuration.

Different phases of request processing where audit events can be generated in Kubernetes, providing comprehensive auditing.

Setup for sending Kubernetes audit events to external webhook endpoints for processing or analysis.

Process of systematically recording and examining activities within a Kubernetes cluster for security and compliance purposes.

Intermediary service that handles authentication before forwarding requests to the Kubernetes API server.

Pluggable components in container orchestration platforms for verifying user identities using various methods.

Rules defining access permissions for users and services in container orchestration platforms.

Serverless container hosting service in Azure, offering rapid deployment of containers without cluster management.

Managed Docker registry service for storing and managing container images in Azure cloud environments.

Implementation of Border Gateway Protocol within containerized network environments for advanced routing.

In container networks, BGP (Border Gateway Protocol) manages routing information between containers and external networks for efficient traffic routing.

Microservices design pattern where a dedicated service acts as an API gateway for specific frontend needs.

Processes for preserving and recovering container data and configurations in orchestration platforms.

Foundation Docker image upon which other images are built, containing core OS and runtime components.

Process of choosing appropriate foundation images for container builds, balancing size, security, and functionality.

Kubernetes quality of service class for pods with no resource guarantees, scheduled when resources are available.

Deployment strategy using two identical environments to minimize downtime and risk during updates.

Temporary tokens used for secure cluster initialization and node joining in Kubernetes, simplifying cluster setup.

Minimalist Linux-based operating system optimized for running containers in cloud environments.

Advanced container image building toolkit offering improved performance and caching capabilities.

Use of BuildKit for efficient, concurrent, and cache-optimized container image creation, improving build performance.

Isolation technique in microservices to contain failures and prevent system-wide cascading failures.

The Bulkhead Pattern in microservices isolates failures by dividing services into separate compartments, preventing issues in one from affecting others.

Kubernetes quality of service class for pods that can use more resources than requested when available.

Security configuration guidelines for deploying containers securely in various environments.

Technique of using multiple Container Network Interface plugins together for advanced networking capabilities.

Kubernetes feature for fine-grained CPU resource management and allocation to containers, optimizing performance.

Technique to limit CPU usage of containers to prevent resource monopolization and ensure fair allocation.

Architectural pattern separating read and write operations in distributed systems, often used in microservices.

Architectural pattern separating read and write operations in distributed systems, often used in microservices.

Standard interface between container runtimes and Kubernetes, allowing pluggable runtime implementations.

Functionality within CRI for pulling, inspecting, and removing container images, standardizing image operations.

Standardized logging interface for container runtimes implementing the Container Runtime Interface.

Performance and resource usage data exposed by container runtimes adhering to the CRI specification.

Kubernetes feature allowing selection of different runtime configurations for containers, enabling specialized runtimes.

Unix domain socket used for communication between Kubelet and the CRI-compatible container runtime.

Process of verifying that a container runtime correctly implements the CRI specification, ensuring compatibility.

Lightweight container runtime specifically designed for Kubernetes, implementing the CRI specification.

Core components and architecture of the CRI-O container runtime, including its interaction with Kubernetes.

Use of CRI-O, a lightweight container runtime, as the primary runtime in a Kubernetes cluster.

Component of CSI responsible for volume provisioning and attachment operations in container orchestration systems.

Plugins implementing the Container Storage Interface for various storage systems in Kubernetes.

Short-lived volumes in Kubernetes, created and deleted alongside a pod using CSI drivers, for temporary storage.

Process of transitioning from in-tree volume plugins to CSI drivers in Kubernetes, improving storage extensibility.

Component of CSI responsible for mounting volumes and making them available to containers.

Feature allowing storage provisioning based on topology constraints in Kubernetes, optimizing data locality.

Caching strategy where the application checks the cache before retrieving data from the main data store.

Techniques for implementing and managing caches in containerized applications for improved performance.

Open-source networking and network security solution for containers, providing a rich set of security policies.

High-performance networking mode in Calico using extended Berkeley Packet Filter for packet processing.

Technique of releasing new versions to a subset of users or servers to minimize risk and gather feedback.

Fine-grained privileges that can be assigned to containers, enhancing security by limiting root-level access.

Mechanisms for managing and restricting Linux capabilities assigned to containers for improved security.

Groupings or classifications of container-related resources or components for easier management and discovery.

Ceph's block storage system, often used for persistent volumes in container orchestration platforms.