Search Results for "kubernetes"

Jenkins plugin to run dynamic agents in a Kubernetes cluster. Based on the Scaling Docker with Kubernetes article, automates the scaling of Jenkins agents running in Kubernetes. The plugin creates a Kubernetes Pod for each agent started and stops it after each build. Agents are launched as inbound agents, so it is expected that the container connects automatically to the Jenkins controller.

Automate certificate management in cloud native environments. Cert-manager builds on top of Kubernetes, introducing certificate authorities and certificates as first-class resource types in the Kubernetes API. This makes it possible to provide 'certificates as a service' to developers working within your Kubernetes cluster. upport for popular CA types. Out of the box, cert-manager supports ACME (i.e. Let's Encrypt), HashiCorp Vault, Venafi, self signed and internal CA issuer types. cert-manager is Kubernetes native, and as such, it natively targets Kubernetes and OpenShift. ...

kubectl tree is a kubectl plugin that lets you visualize Kubernetes object hierarchies as a tree by following the ownerReferences set on API objects. Instead of manually chasing which ReplicaSet owns which Pods or which higher-level controller is responsible for a given resource, it prints an ASCII tree that shows parent-child relationships at a glance. This is especially useful for understanding how complex workloads like Deployments, StatefulSets, Knative Services, or Agones Fleets fan out into lower-level resources across the cluster. ...

Aimeos Headless is an open-source headless eCommerce distribution built on top of the Laravel framework, designed to provide a fast and scalable API-driven commerce backend. The project exposes a comprehensive REST and GraphQL API that allows developers to build custom storefronts or commerce applications using any frontend technology. Because the platform follows a headless architecture, it separates the commerce logic from the presentation layer, enabling developers to build web, mobile,...

...As the data within a shard are coarsely ordered, you will get all your logs from one container in one shard roughly in order. Nested partition key is supported and you can use -> to point to your target key which is nested under another key. For example, your partition_key could be kubernetes->pod_name. If you don't set a partition key or put an invalid one, a random key will be generated, and the logs will be directed to random shards.