Create Configure Knative Networking page #6518

iRaindrop · 2025-11-19T05:58:48Z

The content for the Kourier, Contour, Gateway API, and Istio is could be helpful consolidated as opposed to separate install and config topics.

Proposed Changes

Create "Configure network adapters" under "Administration->Configuring Knative->Networking options

Create file - table test

netlify · 2025-11-19T05:58:54Z

✅ Deploy Preview for knative ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	`1a4ba6c`
🔍 Latest deploy log	https://app.netlify.com/projects/knative/deploys/69609be6d6f87a0008a552d7
😎 Deploy Preview	https://deploy-preview-6518--knative.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Added Nav and fixed H1

Formatting test

More writing

Snippet testing

snippet testing

Snippet name fix

Formatting tests

Formatting fix

Test

Rebuild

Formmating

Typo fix

Formatting

Updates

Snippet formatting

Misc edits

Link issue fix

Added tabs for Network layer setup

Minor edit to rebuild

Mermaid fixes

Mermaid adjustments

iRaindrop · 2026-01-08T06:34:43Z

docs/versioned/serving/config-network-adapters.md

+
+# Configure Knative networking
+
+This page provides configuration guidance for Knative Serving's integration with Kubernetes ingress controllers. Knative leverages existing ingress controls in your Kubernetes cluster, allowing you to use the same monitoring features and capabilities.


added "features and capabilities" at end of sentence.

iRaindrop · 2026-01-08T06:43:29Z

docs/versioned/serving/config-network-adapters.md

+
+The Knative `networking.internal.knative.dev` Ingress type is generally referred to as KIngress objects.
+
+In scenarios where there are multiple networking implementations, you can create a custom ingress class to specify different ingress class annotations for each service. For more information, see [Configuring Services custom ingress class](./services/ingress-class.md)


FYI - I added this link to the custom ingress class (new).

Also name change to "Configure Istio's ingress gateway"

And tab test with snippet references

tabs with snippet references fix

tab test again

Formatting tasks

evankanderson

For the tab thing - it looks like you'll probably want to use the following format to indent the tabs:

{% filter indent(width=4) %}
{% include "netadapter-foo.md" %}
{% endfilter %}

The other edits are fairly confined, I think, with the possible exception of the gatewayclass discussion at the end of "configuring network adapters", which needs to be clarified that it only applies to Gateway API.

evankanderson · 2026-01-08T20:10:05Z

docs/snippets/netadapter-gatewayapi.md

+1. Clone the Gateway API repo:
+
+    ```bash
+    git clone https://github.com/knative-extensions/net-gateway-api.git
+    cd net-gateway-api
+    ```
+
+1. Set environment variables:
+
+    ```bash
+    export KO_DOCKER_REPO=kind.local
+    export KIND_CLUSTER_NAME=knative  # (keep this if your cluster is named "knative")
+    ```
+
+1. Deploy Gateway API resources:
+
+    ```bash
+    ko apply -f config/
+    ```


We don't need these if people are installing the release version (which they should).

docs/snippets/netadapter-gatewayapi.md

evankanderson · 2026-01-08T20:20:26Z

docs/snippets/netadapter-gatewayapi.md

+      --patch '{"data":{"ingress-class":"gateway-api.ingress.networking.knative.dev"}}'
+    ```
+
+1. Edit the `config-gateway` ConfigMap in the knative-serving namespace to specify gateway resources for external and local traffic. For the `external-gateways` key, specify the value for `name` and for `service` as needed. Do the same for the `local gateways`. The `namespace` should be kept at `knative-serving`.


Suggested change

1. Edit the `config-gateway` ConfigMap in the knative-serving namespace to specify gateway resources for external and local traffic. For the `external-gateways` key, specify the value for `name` and for `service` as needed. Do the same for the `local gateways`. The `namespace` should be kept at `knative-serving`.

1. Create Gateway resources for use by external ("north-south") Knative traffic, and local ("east-west") traffic. If you do not need separate routing for local traffic (or [private Knative services](../../../serving/services/private-services.md)), you can use the external Gateway for both. Note both the Kubernetes namespace and name of the Gateways, and an underlying DNS name (such as a Kubernetes service DNS name) corresponding to the Gateway, which will be used by Knative to verify traffic routing.

1. Edit the `config-gateway` ConfigMap in the `knative-serving` namespace to specify the Gateway resources for external and local traffic. For the `external-gateways` key, specify the values for `name`, `namespace` and for `service` corresponding to the external Gateway resource. Do the same for the `local-gateways` key:

evankanderson · 2026-01-08T20:20:54Z

docs/snippets/netadapter-gatewayapi.md

+      labels:
+        app.kubernetes.io/component: net-gateway-api
+        app.kubernetes.io/name: knative-serving


You don't need these labels on the ConfigMap.

Suggested change

labels:

app.kubernetes.io/component: net-gateway-api

app.kubernetes.io/name: knative-serving

evankanderson · 2026-01-08T20:43:42Z

docs/versioned/serving/config-network-adapters.md

+    ExtGateway -- Routes external HTTP/HTTPS traffic --> KServe
+    IntGateway -- Routes internal traffic --> KServe
+    ExternalClient["External Client<br>Internet / Outside cluster"] -- Ingress --> ExtGateway
+    InternalClient["Internal Client<br>Pod / Service inside cluster"] -- "Cluster-internal" --> IntGateway


"InternalClient" needs to be in the "Knative Cluster" subgraph.

evankanderson · 2026-01-08T20:43:50Z

docs/versioned/serving/config-network-adapters.md

+  layout: elk
+---
+flowchart LR
+ subgraph Cluster["Knative Cluster"]


Suggested change

subgraph Cluster["Knative Cluster"]

subgraph Cluster["Kubernetes Cluster"]

evankanderson · 2026-01-08T20:44:42Z

docs/versioned/serving/config-network-adapters.md

+    direction TB
+        ExtGateway["External Gateway<br>Exposed to external traffic"]
+        IntGateway["Internal Gateway<br>Only for local internal traffic"]
+        KServe["Knative Services<br>Serving and Eventing"]


Suggested change

KServe["Knative Services Serving and Eventing"]

KServe["Knative Services"]

This is all Serving. Unfortunately, Eventing has a somewhat different model and doesn't have clear abstractions for exposing the event ingress from outside the cluster.

evankanderson · 2026-01-08T20:49:29Z

docs/versioned/serving/config-network-adapters.md

+istio-remote   istio.io/unmanaged-gateway    True       11d
+```
+
+When gateways are installed, the `config-gateway` ConfigMap is updated to track the `class`, `gateway`, and `service`. The service is the Kubernetes Service name that points to the pods in the Gateway implementation.


This doesn't happen automatically -- this needs to be done by a cluster administrator when they want to change the Gateways used by a certain type of traffic. There's one extra layer here which I didn't describe previously (because it's Gateway-API general, rather than Knative-specific):

NAME CONTROLLER ACCEPTED AGE cilium io.cilium/gateway-controller True 134d default gateway.envoyproxy.io/gatewayclass-controller True 127d $ kubectl get gateway --context prod --all-namespaces NAMESPACE NAME CLASS ADDRESS PROGRAMMED AGE envoy-gateway-system shared default 100.100.100.100 True 127d

So specific Gateways (which go in config-network) will reference a GatewayClass, which says which implementation that Gateway should use. But it may make more sense to simply have people list the Gateway objects in their cluster, and ignore the GatewayClass in this document.

The "Edit the config-gateway ConfigMap" step in netadapter-gateway.api (in the installation instructions) show editing the YAML for the external and internal clusters. Does that step suffice? Should it be repeated here?

evankanderson · 2026-01-08T21:01:59Z

docs/versioned/install/yaml-install/serving/install-serving-with-yaml.md

-            Save this to use in the following [Configure DNS](#configure-dns) section.
+=== "Kourier"

+    {% include "netadapter-kourier.md" %}


I did a little more digging, and it looks like we can use the indent jinja2 filter here to avoid needing to indent the contents of each netadapter-* file:

Suggested change

{% include "netadapter-kourier.md" %}

{% filter indent(width=4) %}

{% include "netadapter-kourier.md" %}

{% endfilter %}

Misc fixes and edits

testing...

evankanderson · 2026-01-08T22:27:44Z

docs/versioned/install/yaml-install/serving/install-serving-with-yaml.md

+{% filter indent(width=4) %}
+{% include "netadapter-kourier.md" %}
+{% include "netadapter-contour.md" %}
+{% include "netadapter-istio.md" %}
+{% include "netadapter-gatewayapi.md" %}
+{% endfilter %}


You don't need (or want) {% filter indent(width=4) %} if you're going to put the tab headers in the included documents. A 4-space indent (absent other context) in Markdown is going to mean "preformatted text", which is what we see in the render.

evankanderson · 2026-01-08T22:30:59Z

docs/versioned/install/yaml-install/serving/install-serving-with-yaml.md

+{% include "netadapter-kourier.md" %}
+{% filter indent(width=4) %}
+{% include "netadapter-contour.md" %}
+{% include "netadapter-istio.md" %}
+{% include "netadapter-gatewayapi.md" %}
+{% endfilter %}


You don't want to include the {% filter indent(width=4) %} directive if you're putting the tab headers into the included documents. Absent other context, a 4-space indent means "preformatted text" in markdown, which is what you get in the render. So, either:

=== Kourier {% filter indent(width=4) %} {% include "netadapter-kourier.md" %} {% endfilter %}

with no indent in the netadapter-kourier.md file, OR:

{% include "netadapter-kourier.md" %}

Where the included file looks like:

=== Kourier Some words about kourier...

Yeah, I've been trying the right combo. But not this yet:
=== Kourier
{% filter indent(width=4) %}
{% include "netadapter-kourier.md" %}
{% endfilter %}

Fingers crossed!

Indentation formatting, wordsmithing

minor edit to rebuld

Misc edits

minor edit

Edit to rebuild

Steps rearrangement

evankanderson

A small number of comments left:

We should move the introduction of KIngress to the top of the configuring networking page, and use that to extract the common [Route] -> (controller) -> [KIngress] diagram.
A few details on Gateway API implementation that were missing -- a link to how to configure request handling with Gateway API, and how to tell that Gateway API is present.
A couple other spots where clarification might be needed.

evankanderson · 2026-01-09T20:14:40Z

docs/snippets/netadapter-gatewayapi.md

+      kubectl apply -f {{ artifact(repo="net-gateway-api",org="knative-extensions",file="net-gateway-api.yaml") }}
+    ```
+
+    Alternatively, you can also install a preconfigured Gateways for either Contour or Istio. Replace the filename in this step with either `contour-gateway.yaml` or `istio-gateway.yaml`. If you use either file  you can skip the next step to configure gateway resources.


The contour-gateway.yaml and istio-gateway.yaml don't replace the net-gateway-api.yaml file, but they replace steps 2 and 3. Not sure how to make that clearer here, but right now, it reads as if you can just install those files instead of the net-gateway-api.yaml (which won't produce a working system, but the commands will succeed).

docs/snippets/netadapter-istio.md

evankanderson · 2026-01-09T20:19:57Z

docs/versioned/serving/config-network-adapters.md

+    flowchart LR
+      subgraph top[" "]
+        direction LR
+            kingress1["Ingress object (KIngress)<br>networking.internal.knative.dev"]
+            serving["Serving<br>controller"]
+            route["Route object"]
+      end
+        route -- read by --> serving
+        serving -- creates --> kingress1
+        style kingress1 fill:#BBDEFB,stroke-width:1px,stroke-dasharray: 0
+        style serving fill:#FFE0B2
+        style top fill:transparent


Moving this content out of each tab still needs to happen. I'd suggest moving the diagram up to the first section (maybe around line 11), and also moving line 222 explaining what a KIngress is up to that area. I'd probably also include an explanation of why the type exists:

The Knative networking.internal.knative.dev Ingress type is generally referred to as KIngress objects. Knative uses the KIngress type to provide a common interface across multiple ingress implementations.

(bold added)

I'd also use this diagram, which includes the Knative Route object to make it clear what user-visible resource maps to the "hidden" KIngress resource:

```mermaid --- config: layout: elk theme: default --- flowchart LR subgraph top[" "] direction LR kingress1["Ingress object (KIngress) networking.internal.knative.dev"] serving("Serving controller") route["Route object serving.knative.dev"] end route -- read by --> serving serving -- creates --> kingress1 style kingress1 fill:#BBDEFB,stroke-width:1px,stroke-dasharray: 0 style serving fill:#FFE0B2 style top fill:transparent ```

evankanderson · 2026-01-09T20:27:07Z

docs/versioned/serving/config-network-adapters.md

+
+    Kourier is is the only supported option for IBM-Z and IBM-P platforms. These IBM platforms require additional steps as documented in [Install Serving th YAML on IBM-Z and IBM-P](../install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.md).
+
+    Kourier provides the following additional configuration options:


https://github.com/knative-extensions/net-kourier?tab=readme-ov-file#deployment would be a reasonable link, or https://github.com/knative-extensions/net-kourier/blob/main/README.md#deployment

evankanderson · 2026-01-09T20:28:30Z

docs/versioned/serving/config-network-adapters.md

+
+    The Knative `net-gateway-api` is a KIngress implementation for Knative integration with the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). A recommended choice for many teams adopting the Gateway API to unify ingress across Kubernetes. Clusters with large numbers of Knative Services however, may experience limitations.
+
+    The Kubernetes Gateway API requires a controller or service mesh. Istio and Contour implementations are tested. For more information see [Tested Gateway API version and Ingress](https://github.com/knative-extensions/net-gateway-api/blob/main/docs/test-version.md).


Suggested change

The Kubernetes Gateway API requires a controller or service mesh. Istio and Contour implementations are tested. For more information see [Tested Gateway API version and Ingress](https://github.com/knative-extensions/net-gateway-api/blob/main/docs/test-version.md).

The Kubernetes Gateway API supports a number of implementations. Istio, Contour, and Envoy-Gateway implementations are tested. For more information see [Tested Gateway API version and Ingress](https://github.com/knative-extensions/net-gateway-api/blob/main/docs/test-version.md).

Service meshes and controllers are different types of things. It would be like saying "gardens need fruit or paths". Let's call them implementations, and include envoy-gateway.

I'd also suggested another sentence here covering how options were configured, to match the other tabs. In this case, I'd probably say:

Knative is designed to support attaching Gateway API policies to both Knative-created HTTPRoutes and the existing Gateway resources which manage with those routes.

evankanderson · 2026-01-09T20:30:31Z

docs/versioned/serving/config-network-adapters.md

+      theme: default
+    ---
+    flowchart LR
+     net-gateway["net-gateway-api controller"]


Suggested change

net-gateway["net-gateway-api controller"]

net-gateway("net-gateway-api controller")

Let's narrow this text so we can get slightly bigger font here. Also, let's use rounded-boxes for software components like controllers, and square boxes for Kubernetes resources (objects).

evankanderson · 2026-01-09T20:31:45Z

docs/versioned/serving/config-network-adapters.md

+            envoy["Envoy deployment<br>kourier-system namespace"]
+            kourier["net-kourier<br>controller"]


Suggested change

envoy["Envoy deployment kourier-system namespace"]

kourier["net-kourier controller"]

envoy("Envoy deployment kourier-system namespace")

kourier("net-kourier controller")

Let's use rounded-boxes for software components.

evankanderson · 2026-01-09T20:36:53Z

docs/versioned/serving/config-network-adapters.md

+
+- Kourier: `kourier-control-*`, and `kourier-gateway-*`. Kourier is included in the Knative Serving installation should appear in the results when your cluster is first created.
+- Contour: `contour-*`
+- Istio: `istio-webhook-*`. The main Istio control plane pods such as `istiod-*` are in the `istio-system` namespace. Knative adds the `istio-webhook-*` pod in the `knative-serving` namespace when Istio is the chosen networking layer.


Again, I think I had a comment here, but Gateway API will create net-gateway-api-* pods in the knative-serving namespace, which can be used to recognize that Gateway API KIngress class is available. (The same as the other directions.)

you did - thanks for catching it

evankanderson · 2026-01-09T20:38:17Z

docs/versioned/serving/config-network-adapters.md

+
+There are also third-party Knative networking options and Knative products available but are not tested or managed by the Knative community. For more information, see [Knative offerings](../install/knative-offerings.md).
+
+## Gateway configurations


This is all Gateway-API specific. I don't know if you want to create a parallel page with "Configure Istio's ingress gateway" (e.g. "Configure Gateway API's ingress gateway"), or if you just want to add a clarification banner here that the following section only applies to Gateway API.

Your call, I can create a new page - would it need additional content? Added the clarification for now.

Create config-network-adapters.md

cbc1aa6

Create file - table test

knative-prow bot requested review from mmejia02 and nainaz November 19, 2025 05:58

knative-prow bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 19, 2025

iRaindrop marked this pull request as draft November 19, 2025 05:59

knative-prow bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 19, 2025

iRaindrop added 3 commits November 18, 2025 22:00

Added Nav

14b81f4

Added Nav and fixed H1

Update config-network-adapters.md

3b315cb

Formatting test

Update config-network-adapters.md

9a212b2

More writing

knative-prow bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 19, 2025

iRaindrop added 10 commits November 19, 2025 23:58

Added snippet file for Kourier

2300e4f

Snippet testing

Update config-network-adapters.md

e6167d0

snippet testing

Update config-network-adapters.md

d283146

Snippet name fix

Snippet fix

5062101

Formatting tests

Update config-network-adapters.md

916f3b4

Formatting fix

Update config-network-adapters.md

81fd46e

Test

Update config-network-adapters.md

d10ab27

Rebuild

Added Contour snippet

9aec3ac

Formmating

Update config-network-adapters.md

1c48767

Typo fix

Added istio and gateway api snippet files

205ecae

Formatting

knative-prow bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 22, 2025

iRaindrop added 6 commits November 22, 2025 19:19

Writing and snippet work

310d9eb

Updates

Misc fixes

84f0b03

Snippet formatting

Link fixes

92d24f1

Misc edits

Update netadapter-istio.md

55a8c41

Link issue fix

Tab work

e35130c

Added tabs for Network layer setup

Update config-network-adapters.md

77cb4b8

Minor edit to rebuild

iRaindrop added 2 commits January 7, 2026 22:13

Update config-network-adapters.md

aba1034

Mermaid fixes

Update config-network-adapters.md

d2af6d9

Mermaid adjustments

iRaindrop commented Jan 8, 2026

View reviewed changes

iRaindrop added 6 commits January 8, 2026 00:30

Snippet references and fixes

c988447

Also name change to "Configure Istio's ingress gateway"

Misc edits

214e7ba

And tab test with snippet references

Update install-serving-with-yaml.md

4df6d8c

tabs with snippet references fix

Update install-serving-with-yaml.md

92670a8

tab test again

Snippet and Tab fixes

edea5c3

Formatting tasks

Tab fixes

25438dd

evankanderson reviewed Jan 8, 2026

View reviewed changes

iRaindrop added 4 commits January 8, 2026 14:06

Tab fixes and reviewer edits

b77528c

Misc fixes and edits

tab tweaks

6365583

tab and include test

b6c8203

tab include test

0bd2122

testing...

evankanderson reviewed Jan 8, 2026

View reviewed changes

iRaindrop added 13 commits January 8, 2026 14:40

tab test

0674346

A hopeful test

57ac62f

Tab test with indent filter

7f0a3cd

Indent test

087728b

Test edit to rebuild

c8d8a94

Install snippets and DNS snippets

07f9f94

Indentation formatting, wordsmithing

Update install-serving-with-yaml.md

726cb82

minor edit to rebuld

file name fix

cb169ef

Format fixes and rerognization

75ba64c

Misc edits

formatting fixes

d804895

Link improvment

ce7742e

minor edit

link format edits

1927664

Edit to rebuild

Update netadapter-gatewayapi.md

1a4ba6c

Steps rearrangement

evankanderson reviewed Jan 9, 2026

View reviewed changes


		# Configure Knative networking

		This page provides configuration guidance for Knative Serving's integration with Kubernetes ingress controllers. Knative leverages existing ingress controls in your Kubernetes cluster, allowing you to use the same monitoring features and capabilities.


		The Knative `networking.internal.knative.dev` Ingress type is generally referred to as KIngress objects.

		In scenarios where there are multiple networking implementations, you can create a custom ingress class to specify different ingress class annotations for each service. For more information, see [Configuring Services custom ingress class](./services/ingress-class.md)

-. Edit the `config-gateway` ConfigMap in the knative-serving namespace to specify gateway resources for external and local traffic. For the `external-gateways` key, specify the value for `name` and for `service` as needed. Do the same for the `local gateways`. The `namespace` should be kept at `knative-serving`.
+. Create Gateway resources for use by external ("north-south") Knative traffic, and local ("east-west") traffic.  If you do not need separate routing for local traffic (or [private Knative services](../../../serving/services/private-services.md)), you can use the external Gateway for both.  Note both the Kubernetes namespace and name of the Gateways, and an underlying DNS name (such as a Kubernetes service DNS name) corresponding to the Gateway, which will be used by Knative to verify traffic routing.
+. Edit the `config-gateway` ConfigMap in the `knative-serving` namespace to specify the Gateway resources for external and local traffic. For the `external-gateways` key, specify the values for `name`, `namespace` and for `service` corresponding to the external Gateway resource. Do the same for the `local-gateways` key:

	labels:
	app.kubernetes.io/component: net-gateway-api
	app.kubernetes.io/name: knative-serving

	subgraph Cluster["Knative Cluster"]
	subgraph Cluster["Kubernetes Cluster"]

	KServe["Knative Services<br>Serving and Eventing"]
	KServe["Knative Services"]


		Kourier is is the only supported option for IBM-Z and IBM-P platforms. These IBM platforms require additional steps as documented in [Install Serving th YAML on IBM-Z and IBM-P](../install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.md).

		Kourier provides the following additional configuration options:


		The Knative `net-gateway-api` is a KIngress implementation for Knative integration with the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). A recommended choice for many teams adopting the Gateway API to unify ingress across Kubernetes. Clusters with large numbers of Knative Services however, may experience limitations.

		The Kubernetes Gateway API requires a controller or service mesh. Istio and Contour implementations are tested. For more information see [Tested Gateway API version and Ingress](https://github.com/knative-extensions/net-gateway-api/blob/main/docs/test-version.md).

	The Kubernetes Gateway API requires a controller or service mesh. Istio and Contour implementations are tested. For more information see [Tested Gateway API version and Ingress](https://github.com/knative-extensions/net-gateway-api/blob/main/docs/test-version.md).
	The Kubernetes Gateway API supports a number of implementations. Istio, Contour, and Envoy-Gateway implementations are tested. For more information see [Tested Gateway API version and Ingress](https://github.com/knative-extensions/net-gateway-api/blob/main/docs/test-version.md).

	net-gateway["net-gateway-api controller"]
	net-gateway("net-gateway-api<br>controller")

		envoy["Envoy deployment<br>kourier-system namespace"]
		kourier["net-kourier<br>controller"]


		There are also third-party Knative networking options and Knative products available but are not tested or managed by the Knative community. For more information, see [Knative offerings](../install/knative-offerings.md).

		## Gateway configurations

Create Configure Knative Networking page #6518

Are you sure you want to change the base?

Create Configure Knative Networking page #6518

Conversation

iRaindrop commented Nov 19, 2025

Proposed Changes

Uh oh!

netlify bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for knative ready!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

iRaindrop Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

evankanderson left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

evankanderson left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

iRaindrop Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

netlify bot commented Nov 19, 2025 •

edited

Loading

iRaindrop Jan 8, 2026 •

edited

Loading

iRaindrop Jan 9, 2026 •

edited

Loading