+
+Pepr is on a mission to save Kubernetes from the tyranny of YAML, intimidating glue code, bash scripts, and other makeshift solutions. As a Kubernetes controller, Pepr empowers you to define Kubernetes transformations using TypeScript, without software development expertise thanks to plain-english configurations. Pepr transforms a patchwork of forks, scripts, overlays, and other chaos into a cohesive, well-structured, and maintainable system. With Pepr, you can seamlessly transition IT ops tribal knowledge into code, simplifying documentation, testing, validation, and coordination of changes for a more predictable outcome.
+
+#### _Note: Pepr is still in active development so breaking changes may occur, but will be documented in release notes._
+
+## Features
+
+- Zero-config K8s webhook mutations and validations
+- Automatic leader-elected K8s resource watching
+- Lightweight async key-value store backed by K8s for stateful operations with the [Pepr Store](./store/)
+- Human-readable fluent API for generating [Pepr Capabilities](#capability)
+- A fluent API for creating/modifying/watching and server-side applying K8s resources via [Kubernetes Fluent Client](https://github.com/defenseunicorns/kubernetes-fluent-client)
+- Generate new K8s resources based off of cluster resource changes
+- Perform other exec/API calls based off of cluster resources changes or any other arbitrary schedule
+- Out of the box airgap support with [Zarf](https://zarf.dev)
+- Entire NPM ecosystem available for advanced operations
+- Realtime K8s debugging system for testing/reacting to cluster changes
+- Controller network isolation and tamper-resistent module execution
+- Least-privilege [RBAC](https://github.com/defenseunicorns/pepr/blob/main/docs/rbac/) generation
+- AMD64 and ARM64 support
+
+## Example Pepr Action
+
+This quick sample shows how to react to a ConfigMap being created or updated in the cluster. It adds a label and annotation to the ConfigMap and adds some data to the ConfigMap. It also creates a Validating Webhook to make sure the "pepr" label still exists. Finally, after the ConfigMap is created, it logs a message to the Pepr controller and creates or updates a separate ConfigMap with the [kubernetes-fluent-client](https://github.com/defenseunicorns/kubernetes-fluent-client) using server-side apply. For more details see [actions](./actions/) section.
+
+```ts
+When(a.ConfigMap)
+ .IsCreatedOrUpdated()
+ .InNamespace("pepr-demo")
+ .WithLabel("unicorn", "rainbow")
+ // Create a Mutate Action for the ConfigMap
+ .Mutate(request => {
+ // Add a label and annotation to the ConfigMap
+ request.SetLabel("pepr", "was-here").SetAnnotation("pepr.dev", "annotations-work-too");
+
+ // Add some data to the ConfigMap
+ request.Raw.data["doug-says"] = "Pepr is awesome!";
+
+ // Log a message to the Pepr controller logs
+ Log.info("A 🦄 ConfigMap was created or updated:");
+ })
+ // Create a Validate Action for the ConfigMap
+ .Validate(request => {
+ // Validate the ConfigMap has a specific label
+ if (request.HasLabel("pepr")) {
+ return request.Approve();
+ }
+
+ // Reject the ConfigMap if it doesn't have the label
+ return request.Deny("ConfigMap must have a unicorn label");
+ })
+ // Watch behaves like controller-runtime's Manager.Watch()
+ .Watch(async (cm, phase) => {
+ Log.info(cm, `ConfigMap was ${phase}.`);
+
+ // Apply a ConfigMap using K8s server-side apply (will create or update)
+ await K8s(kind.ConfigMap).Apply({
+ metadata: {
+ name: "pepr-ssa-demo",
+ namespace: "pepr-demo-2",
+ },
+ data: {
+ uid: cm.metadata.uid,
+ },
+ });
+ });
+```
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/) v18.0.0+ (even-numbered releases only)
+ - To ensure compatability and optimal performance, it is recommended to use even-numbered releases of Node.js as they are stable releases and receive long-term support for three years. Odd-numbered releases are experimental and may not be supported by certain libraries utilized in Pepr.
+
+- [npm](https://www.npmjs.com/) v10.1.0+
+
+- Recommended (optional) tools:
+ - [Visual Studio Code](https://code.visualstudio.com/) for inline debugging and [Pepr Capabilities](#capability) creation.
+ - A Kubernetes cluster for `npx pepr dev`. Pepr modules include `npm run k3d-setup` if you want to test locally with [K3d](https://k3d.io/) and [Docker](https://www.docker.com/).
+
+## Wow too many words! tl;dr;
+
+```bash
+# Create a new Pepr Module
+npx pepr init
+
+# If you already have a Kind or K3d cluster you want to use, skip this step
+npm run k3d-setup
+
+# Start playing with Pepr now
+# If using another local K8s distro instead of k3d, run `npx pepr dev --host host.docker.internal`
+npx pepr dev
+kubectl apply -f capabilities/hello-pepr.samples.yaml
+
+# Be amazed and ⭐️ this repo
+```
+
+
+
+## Concepts
+
+### Module
+
+A module is the top-level collection of capabilities. It is a single, complete TypeScript project that includes an entry point to load all the configuration and capabilities, along with their actions. During the Pepr build process, each module produces a unique Kubernetes MutatingWebhookConfiguration and ValidatingWebhookConfiguration, along with a secret containing the transpiled and compressed TypeScript code. The webhooks and secret are deployed into the Kubernetes cluster with their own isolated controller.
+
+See [Module](./module/) for more details.
+
+### Capability
+
+A capability is set of related actions that work together to achieve a specific transformation or operation on Kubernetes resources. Capabilities are user-defined and can include one or more actions. They are defined within a Pepr module and can be used in both MutatingWebhookConfigurations and ValidatingWebhookConfigurations. A Capability can have a specific scope, such as mutating or validating, and can be reused in multiple Pepr modules.
+
+See [Capabilities](./capabilities/) for more details.
+
+### Action
+
+Action is a discrete set of behaviors defined in a single function that acts on a given Kubernetes GroupVersionKind (GVK) passed in from Kubernetes. Actions are the atomic operations that are performed on Kubernetes resources by Pepr.
+
+For example, an action could be responsible for adding a specific label to a Kubernetes resource, or for modifying a specific field in a resource's metadata. Actions can be grouped together within a Capability to provide a more comprehensive set of operations that can be performed on Kubernetes resources.
+
+There are both `Mutate()` and `Validate()` Actions that can be used to modify or validate Kubernetes resources within the admission controller lifecycle. There is also a `Watch()` Action that can be used to watch for changes to Kubernetes resources that already exist.
+
+See [actions](./actions/) for more details.
+
+## Logical Pepr Flow
+
+
+[Source Diagram](_images/pepr-arch.svg)
+
+## TypeScript
+
+[TypeScript](https://www.typescriptlang.org/) is a strongly typed, object-oriented programming language built on top of JavaScript. It provides optional static typing and a rich type system, allowing developers to write more robust code. TypeScript is transpiled to JavaScript, enabling it to run in any environment that supports JavaScript. Pepr allows you to use JavaScript or TypeScript to write capabilities, but TypeScript is recommended for its type safety and rich type system. You can learn more about TypeScript [here](https://www.typescriptlang.org/docs/handbook/typescript-from-scratch.html).
+
+## Community
+
+To join our channel go to [Kubernetes Slack](https://communityinviter.com/apps/kubernetes/community) and join the `#pepr` channel.
+
+
+
+
+Pepr is on a mission to save Kubernetes from the tyranny of YAML, intimidating glue code, bash scripts, and other makeshift solutions. As a Kubernetes controller, Pepr empowers you to define Kubernetes transformations using TypeScript, without software development expertise thanks to plain-english configurations. Pepr transforms a patchwork of forks, scripts, overlays, and other chaos into a cohesive, well-structured, and maintainable system. With Pepr, you can seamlessly transition IT ops tribal knowledge into code, simplifying documentation, testing, validation, and coordination of changes for a more predictable outcome.
+
+#### _Note: Pepr is still in active development so breaking changes may occur, but will be documented in release notes._
+
+## Features
+
+- Zero-config K8s webhook mutations and validations
+- Automatic leader-elected K8s resource watching
+- Lightweight async key-value store backed by K8s for stateful operations with the [Pepr Store](./store/)
+- Human-readable fluent API for generating [Pepr Capabilities](#capability)
+- A fluent API for creating/modifying/watching and server-side applying K8s resources via [Kubernetes Fluent Client](https://github.com/defenseunicorns/kubernetes-fluent-client)
+- Generate new K8s resources based off of cluster resource changes
+- Perform other exec/API calls based off of cluster resources changes or any other arbitrary schedule
+- Out of the box airgap support with [Zarf](https://zarf.dev)
+- Entire NPM ecosystem available for advanced operations
+- Realtime K8s debugging system for testing/reacting to cluster changes
+- Controller network isolation and tamper-resistent module execution
+- Least-privilege [RBAC](https://github.com/defenseunicorns/pepr/blob/main/docs/rbac/) generation
+- AMD64 and ARM64 support
+
+## Example Pepr Action
+
+This quick sample shows how to react to a ConfigMap being created or updated in the cluster. It adds a label and annotation to the ConfigMap and adds some data to the ConfigMap. It also creates a Validating Webhook to make sure the "pepr" label still exists. Finally, after the ConfigMap is created, it logs a message to the Pepr controller and creates or updates a separate ConfigMap with the [kubernetes-fluent-client](https://github.com/defenseunicorns/kubernetes-fluent-client) using server-side apply. For more details see [actions](./actions/) section.
+
+```ts
+When(a.ConfigMap)
+ .IsCreatedOrUpdated()
+ .InNamespace("pepr-demo")
+ .WithLabel("unicorn", "rainbow")
+ // Create a Mutate Action for the ConfigMap
+ .Mutate(request => {
+ // Add a label and annotation to the ConfigMap
+ request.SetLabel("pepr", "was-here").SetAnnotation("pepr.dev", "annotations-work-too");
+
+ // Add some data to the ConfigMap
+ request.Raw.data["doug-says"] = "Pepr is awesome!";
+
+ // Log a message to the Pepr controller logs
+ Log.info("A 🦄 ConfigMap was created or updated:");
+ })
+ // Create a Validate Action for the ConfigMap
+ .Validate(request => {
+ // Validate the ConfigMap has a specific label
+ if (request.HasLabel("pepr")) {
+ return request.Approve();
+ }
+
+ // Reject the ConfigMap if it doesn't have the label
+ return request.Deny("ConfigMap must have a unicorn label");
+ })
+ // Watch behaves like controller-runtime's Manager.Watch()
+ .Watch(async (cm, phase) => {
+ Log.info(cm, `ConfigMap was ${phase}.`);
+
+ // Apply a ConfigMap using K8s server-side apply (will create or update)
+ await K8s(kind.ConfigMap).Apply({
+ metadata: {
+ name: "pepr-ssa-demo",
+ namespace: "pepr-demo-2",
+ },
+ data: {
+ uid: cm.metadata.uid,
+ },
+ });
+ });
+```
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/) v18.0.0+ (even-numbered releases only)
+ - To ensure compatability and optimal performance, it is recommended to use even-numbered releases of Node.js as they are stable releases and receive long-term support for three years. Odd-numbered releases are experimental and may not be supported by certain libraries utilized in Pepr.
+
+- [npm](https://www.npmjs.com/) v10.1.0+
+
+- Recommended (optional) tools:
+ - [Visual Studio Code](https://code.visualstudio.com/) for inline debugging and [Pepr Capabilities](#capability) creation.
+ - A Kubernetes cluster for `npx pepr dev`. Pepr modules include `npm run k3d-setup` if you want to test locally with [K3d](https://k3d.io/) and [Docker](https://www.docker.com/).
+
+## Wow too many words! tl;dr;
+
+```bash
+# Create a new Pepr Module
+npx pepr init
+
+# If you already have a Kind or K3d cluster you want to use, skip this step
+npm run k3d-setup
+
+# Start playing with Pepr now
+# If using another local K8s distro instead of k3d, run `npx pepr dev --host host.docker.internal`
+npx pepr dev
+kubectl apply -f capabilities/hello-pepr.samples.yaml
+
+# Be amazed and ⭐️ this repo
+```
+
+
+
+## Concepts
+
+### Module
+
+A module is the top-level collection of capabilities. It is a single, complete TypeScript project that includes an entry point to load all the configuration and capabilities, along with their actions. During the Pepr build process, each module produces a unique Kubernetes MutatingWebhookConfiguration and ValidatingWebhookConfiguration, along with a secret containing the transpiled and compressed TypeScript code. The webhooks and secret are deployed into the Kubernetes cluster with their own isolated controller.
+
+See [Module](./module/) for more details.
+
+### Capability
+
+A capability is set of related actions that work together to achieve a specific transformation or operation on Kubernetes resources. Capabilities are user-defined and can include one or more actions. They are defined within a Pepr module and can be used in both MutatingWebhookConfigurations and ValidatingWebhookConfigurations. A Capability can have a specific scope, such as mutating or validating, and can be reused in multiple Pepr modules.
+
+See [Capabilities](./capabilities/) for more details.
+
+### Action
+
+Action is a discrete set of behaviors defined in a single function that acts on a given Kubernetes GroupVersionKind (GVK) passed in from Kubernetes. Actions are the atomic operations that are performed on Kubernetes resources by Pepr.
+
+For example, an action could be responsible for adding a specific label to a Kubernetes resource, or for modifying a specific field in a resource's metadata. Actions can be grouped together within a Capability to provide a more comprehensive set of operations that can be performed on Kubernetes resources.
+
+There are both `Mutate()` and `Validate()` Actions that can be used to modify or validate Kubernetes resources within the admission controller lifecycle. There is also a `Watch()` Action that can be used to watch for changes to Kubernetes resources that already exist.
+
+See [actions](./actions/) for more details.
+
+## Logical Pepr Flow
+
+
+[Source Diagram](_images/pepr-arch.svg)
+
+## TypeScript
+
+[TypeScript](https://www.typescriptlang.org/) is a strongly typed, object-oriented programming language built on top of JavaScript. It provides optional static typing and a rich type system, allowing developers to write more robust code. TypeScript is transpiled to JavaScript, enabling it to run in any environment that supports JavaScript. Pepr allows you to use JavaScript or TypeScript to write capabilities, but TypeScript is recommended for its type safety and rich type system. You can learn more about TypeScript [here](https://www.typescriptlang.org/docs/handbook/typescript-from-scratch.html).
+
+## Community
+
+To join our channel go to [Kubernetes Slack](https://communityinviter.com/apps/kubernetes/community) and join the `#pepr` channel.
+
+
+
+
+Pepr is on a mission to save Kubernetes from the tyranny of YAML, intimidating glue code, bash scripts, and other makeshift solutions. As a Kubernetes controller, Pepr empowers you to define Kubernetes transformations using TypeScript, without software development expertise thanks to plain-english configurations. Pepr transforms a patchwork of forks, scripts, overlays, and other chaos into a cohesive, well-structured, and maintainable system. With Pepr, you can seamlessly transition IT ops tribal knowledge into code, simplifying documentation, testing, validation, and coordination of changes for a more predictable outcome.
+
+#### _Note: Pepr is still in active development so breaking changes may occur, but will be documented in release notes._
+
+## Features
+
+- Zero-config K8s webhook mutations and validations
+- Automatic leader-elected K8s resource watching
+- Lightweight async key-value store backed by K8s for stateful operations with the [Pepr Store](./store/)
+- Human-readable fluent API for generating [Pepr Capabilities](#capability)
+- A fluent API for creating/modifying/watching and server-side applying K8s resources via [Kubernetes Fluent Client](https://github.com/defenseunicorns/kubernetes-fluent-client)
+- Generate new K8s resources based off of cluster resource changes
+- Perform other exec/API calls based off of cluster resources changes or any other arbitrary schedule
+- Out of the box airgap support with [Zarf](https://zarf.dev)
+- Entire NPM ecosystem available for advanced operations
+- Realtime K8s debugging system for testing/reacting to cluster changes
+- Controller network isolation and tamper-resistent module execution
+- Least-privilege [RBAC](https://github.com/defenseunicorns/pepr/blob/main/docs/rbac/) generation
+- AMD64 and ARM64 support
+
+## Example Pepr Action
+
+This quick sample shows how to react to a ConfigMap being created or updated in the cluster. It adds a label and annotation to the ConfigMap and adds some data to the ConfigMap. It also creates a Validating Webhook to make sure the "pepr" label still exists. Finally, after the ConfigMap is created, it logs a message to the Pepr controller and creates or updates a separate ConfigMap with the [kubernetes-fluent-client](https://github.com/defenseunicorns/kubernetes-fluent-client) using server-side apply. For more details see [actions](./actions/) section.
+
+```ts
+When(a.ConfigMap)
+ .IsCreatedOrUpdated()
+ .InNamespace("pepr-demo")
+ .WithLabel("unicorn", "rainbow")
+ // Create a Mutate Action for the ConfigMap
+ .Mutate(request => {
+ // Add a label and annotation to the ConfigMap
+ request.SetLabel("pepr", "was-here").SetAnnotation("pepr.dev", "annotations-work-too");
+
+ // Add some data to the ConfigMap
+ request.Raw.data["doug-says"] = "Pepr is awesome!";
+
+ // Log a message to the Pepr controller logs
+ Log.info("A 🦄 ConfigMap was created or updated:");
+ })
+ // Create a Validate Action for the ConfigMap
+ .Validate(request => {
+ // Validate the ConfigMap has a specific label
+ if (request.HasLabel("pepr")) {
+ return request.Approve();
+ }
+
+ // Reject the ConfigMap if it doesn't have the label
+ return request.Deny("ConfigMap must have a unicorn label");
+ })
+ // Watch behaves like controller-runtime's Manager.Watch()
+ .Watch(async (cm, phase) => {
+ Log.info(cm, `ConfigMap was ${phase}.`);
+
+ // Apply a ConfigMap using K8s server-side apply (will create or update)
+ await K8s(kind.ConfigMap).Apply({
+ metadata: {
+ name: "pepr-ssa-demo",
+ namespace: "pepr-demo-2",
+ },
+ data: {
+ uid: cm.metadata.uid,
+ },
+ });
+ });
+```
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/) v18.0.0+ (even-numbered releases only)
+ - To ensure compatability and optimal performance, it is recommended to use even-numbered releases of Node.js as they are stable releases and receive long-term support for three years. Odd-numbered releases are experimental and may not be supported by certain libraries utilized in Pepr.
+
+- [npm](https://www.npmjs.com/) v10.1.0+
+
+- Recommended (optional) tools:
+ - [Visual Studio Code](https://code.visualstudio.com/) for inline debugging and [Pepr Capabilities](#capability) creation.
+ - A Kubernetes cluster for `npx pepr dev`. Pepr modules include `npm run k3d-setup` if you want to test locally with [K3d](https://k3d.io/) and [Docker](https://www.docker.com/).
+
+## Wow too many words! tl;dr;
+
+```bash
+# Create a new Pepr Module
+npx pepr init
+
+# If you already have a Kind or K3d cluster you want to use, skip this step
+npm run k3d-setup
+
+# Start playing with Pepr now
+# If using another local K8s distro instead of k3d, run `npx pepr dev --host host.docker.internal`
+npx pepr dev
+kubectl apply -f capabilities/hello-pepr.samples.yaml
+
+# Be amazed and ⭐️ this repo
+```
+
+
+
+## Concepts
+
+### Module
+
+A module is the top-level collection of capabilities. It is a single, complete TypeScript project that includes an entry point to load all the configuration and capabilities, along with their actions. During the Pepr build process, each module produces a unique Kubernetes MutatingWebhookConfiguration and ValidatingWebhookConfiguration, along with a secret containing the transpiled and compressed TypeScript code. The webhooks and secret are deployed into the Kubernetes cluster with their own isolated controller.
+
+See [Module](./module/) for more details.
+
+### Capability
+
+A capability is set of related actions that work together to achieve a specific transformation or operation on Kubernetes resources. Capabilities are user-defined and can include one or more actions. They are defined within a Pepr module and can be used in both MutatingWebhookConfigurations and ValidatingWebhookConfigurations. A Capability can have a specific scope, such as mutating or validating, and can be reused in multiple Pepr modules.
+
+See [Capabilities](./capabilities/) for more details.
+
+### Action
+
+Action is a discrete set of behaviors defined in a single function that acts on a given Kubernetes GroupVersionKind (GVK) passed in from Kubernetes. Actions are the atomic operations that are performed on Kubernetes resources by Pepr.
+
+For example, an action could be responsible for adding a specific label to a Kubernetes resource, or for modifying a specific field in a resource's metadata. Actions can be grouped together within a Capability to provide a more comprehensive set of operations that can be performed on Kubernetes resources.
+
+There are both `Mutate()` and `Validate()` Actions that can be used to modify or validate Kubernetes resources within the admission controller lifecycle. There is also a `Watch()` Action that can be used to watch for changes to Kubernetes resources that already exist.
+
+See [actions](./actions/) for more details.
+
+## Logical Pepr Flow
+
+
+[Source Diagram](_images/pepr-arch.svg)
+
+## TypeScript
+
+[TypeScript](https://www.typescriptlang.org/) is a strongly typed, object-oriented programming language built on top of JavaScript. It provides optional static typing and a rich type system, allowing developers to write more robust code. TypeScript is transpiled to JavaScript, enabling it to run in any environment that supports JavaScript. Pepr allows you to use JavaScript or TypeScript to write capabilities, but TypeScript is recommended for its type safety and rich type system. You can learn more about TypeScript [here](https://www.typescriptlang.org/docs/handbook/typescript-from-scratch.html).
+
+## Community
+
+To join our channel go to [Kubernetes Slack](https://communityinviter.com/apps/kubernetes/community) and join the `#pepr` channel.
+
+
+
+
+Pepr is on a mission to save Kubernetes from the tyranny of YAML, intimidating glue code, bash scripts, and other makeshift solutions. As a Kubernetes controller, Pepr empowers you to define Kubernetes transformations using TypeScript, without software development expertise thanks to plain-english configurations. Pepr transforms a patchwork of forks, scripts, overlays, and other chaos into a cohesive, well-structured, and maintainable system. With Pepr, you can seamlessly transition IT ops tribal knowledge into code, simplifying documentation, testing, validation, and coordination of changes for a more predictable outcome.
+
+#### _Note: Pepr is still in active development so breaking changes may occur, but will be documented in release notes._
+
+## Features
+
+- Zero-config K8s webhook mutations and validations
+- Automatic leader-elected K8s resource watching
+- Lightweight async key-value store backed by K8s for stateful operations with the [Pepr Store](./store/)
+- Human-readable fluent API for generating [Pepr Capabilities](#capability)
+- A fluent API for creating/modifying/watching and server-side applying K8s resources via [Kubernetes Fluent Client](https://github.com/defenseunicorns/kubernetes-fluent-client)
+- Generate new K8s resources based off of cluster resource changes
+- Perform other exec/API calls based off of cluster resources changes or any other arbitrary schedule
+- Out of the box airgap support with [Zarf](https://zarf.dev)
+- Entire NPM ecosystem available for advanced operations
+- Realtime K8s debugging system for testing/reacting to cluster changes
+- Controller network isolation and tamper-resistent module execution
+- Least-privilege [RBAC](https://github.com/defenseunicorns/pepr/blob/main/docs/rbac/) generation
+- AMD64 and ARM64 support
+
+## Example Pepr Action
+
+This quick sample shows how to react to a ConfigMap being created or updated in the cluster. It adds a label and annotation to the ConfigMap and adds some data to the ConfigMap. It also creates a Validating Webhook to make sure the "pepr" label still exists. Finally, after the ConfigMap is created, it logs a message to the Pepr controller and creates or updates a separate ConfigMap with the [kubernetes-fluent-client](https://github.com/defenseunicorns/kubernetes-fluent-client) using server-side apply. For more details see [actions](./actions/) section.
+
+```ts
+When(a.ConfigMap)
+ .IsCreatedOrUpdated()
+ .InNamespace("pepr-demo")
+ .WithLabel("unicorn", "rainbow")
+ // Create a Mutate Action for the ConfigMap
+ .Mutate(request => {
+ // Add a label and annotation to the ConfigMap
+ request.SetLabel("pepr", "was-here").SetAnnotation("pepr.dev", "annotations-work-too");
+
+ // Add some data to the ConfigMap
+ request.Raw.data["doug-says"] = "Pepr is awesome!";
+
+ // Log a message to the Pepr controller logs
+ Log.info("A 🦄 ConfigMap was created or updated:");
+ })
+ // Create a Validate Action for the ConfigMap
+ .Validate(request => {
+ // Validate the ConfigMap has a specific label
+ if (request.HasLabel("pepr")) {
+ return request.Approve();
+ }
+
+ // Reject the ConfigMap if it doesn't have the label
+ return request.Deny("ConfigMap must have a unicorn label");
+ })
+ // Watch behaves like controller-runtime's Manager.Watch()
+ .Watch(async (cm, phase) => {
+ Log.info(cm, `ConfigMap was ${phase}.`);
+
+ // Apply a ConfigMap using K8s server-side apply (will create or update)
+ await K8s(kind.ConfigMap).Apply({
+ metadata: {
+ name: "pepr-ssa-demo",
+ namespace: "pepr-demo-2",
+ },
+ data: {
+ uid: cm.metadata.uid,
+ },
+ });
+ });
+```
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/) v18.0.0+ (even-numbered releases only)
+ - To ensure compatability and optimal performance, it is recommended to use even-numbered releases of Node.js as they are stable releases and receive long-term support for three years. Odd-numbered releases are experimental and may not be supported by certain libraries utilized in Pepr.
+
+- [npm](https://www.npmjs.com/) v10.1.0+
+
+- Recommended (optional) tools:
+ - [Visual Studio Code](https://code.visualstudio.com/) for inline debugging and [Pepr Capabilities](#capability) creation.
+ - A Kubernetes cluster for `npx pepr dev`. Pepr modules include `npm run k3d-setup` if you want to test locally with [K3d](https://k3d.io/) and [Docker](https://www.docker.com/).
+
+## Wow too many words! tl;dr;
+
+```bash
+# Create a new Pepr Module
+npx pepr init
+
+# If you already have a Kind or K3d cluster you want to use, skip this step
+npm run k3d-setup
+
+# Start playing with Pepr now
+# If using another local K8s distro instead of k3d, run `npx pepr dev --host host.docker.internal`
+npx pepr dev
+kubectl apply -f capabilities/hello-pepr.samples.yaml
+
+# Be amazed and ⭐️ this repo
+```
+
+
+
+## Concepts
+
+### Module
+
+A module is the top-level collection of capabilities. It is a single, complete TypeScript project that includes an entry point to load all the configuration and capabilities, along with their actions. During the Pepr build process, each module produces a unique Kubernetes MutatingWebhookConfiguration and ValidatingWebhookConfiguration, along with a secret containing the transpiled and compressed TypeScript code. The webhooks and secret are deployed into the Kubernetes cluster with their own isolated controller.
+
+See [Module](./module/) for more details.
+
+### Capability
+
+A capability is set of related actions that work together to achieve a specific transformation or operation on Kubernetes resources. Capabilities are user-defined and can include one or more actions. They are defined within a Pepr module and can be used in both MutatingWebhookConfigurations and ValidatingWebhookConfigurations. A Capability can have a specific scope, such as mutating or validating, and can be reused in multiple Pepr modules.
+
+See [Capabilities](./capabilities/) for more details.
+
+### Action
+
+Action is a discrete set of behaviors defined in a single function that acts on a given Kubernetes GroupVersionKind (GVK) passed in from Kubernetes. Actions are the atomic operations that are performed on Kubernetes resources by Pepr.
+
+For example, an action could be responsible for adding a specific label to a Kubernetes resource, or for modifying a specific field in a resource's metadata. Actions can be grouped together within a Capability to provide a more comprehensive set of operations that can be performed on Kubernetes resources.
+
+There are both `Mutate()` and `Validate()` Actions that can be used to modify or validate Kubernetes resources within the admission controller lifecycle. There is also a `Watch()` Action that can be used to watch for changes to Kubernetes resources that already exist.
+
+See [actions](./actions/) for more details.
+
+## Logical Pepr Flow
+
+
+[Source Diagram](_images/pepr-arch.svg)
+
+## TypeScript
+
+[TypeScript](https://www.typescriptlang.org/) is a strongly typed, object-oriented programming language built on top of JavaScript. It provides optional static typing and a rich type system, allowing developers to write more robust code. TypeScript is transpiled to JavaScript, enabling it to run in any environment that supports JavaScript. Pepr allows you to use JavaScript or TypeScript to write capabilities, but TypeScript is recommended for its type safety and rich type system. You can learn more about TypeScript [here](https://www.typescriptlang.org/docs/handbook/typescript-from-scratch.html).
+
+## Community
+
+To join our channel go to [Kubernetes Slack](https://communityinviter.com/apps/kubernetes/community) and join the `#pepr` channel.
+
+
+ vk!nFU^%!f)&n1G|?-rJg&
zpf^_?-4rmWNOUX_)PiCY%EMo(OXXheP`UAJV)uatd0JLwt=LN4&4|w6>)IPPi06c6
zt`(yf{=8l6b^Si-uePIe+J9R&59+z)583<