apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "89591" uid: 1eead396-b8cd-4e51-8fb6-05faf7ca828b spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T01:07:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.521441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:56:53Z" - latency: 1.252136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:55:53Z" - latency: 4.542566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 1.060112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 993.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 1.288288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 1.019616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 1.248806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:53Z" - latency: 1.118206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:53Z" - latency: 1.190273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "88377" uid: 4d09a4e7-3e89-487b-bc57-ae07d1d48947 spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:06:54Z" message: 'load-balancer-api-external: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.161855ms message: 'load-balancer-api-external: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 32.98517ms message: 'load-balancer-api-external: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:54:53Z" - latency: 49.338106ms message: 'load-balancer-api-external: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 7.226493ms message: 'load-balancer-api-external: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:53:53Z" - latency: 50.112322ms message: 'load-balancer-api-external: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 6.609354ms message: 'load-balancer-api-external: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:53Z" - latency: 54.237175ms message: 'load-balancer-api-external: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 6.576776ms message: 'load-balancer-api-external: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:53Z" - latency: 50.108274ms message: 'load-balancer-api-external: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 6.284326ms message: 'load-balancer-api-external: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "88376" uid: 71c4ccd1-106c-4887-a615-7175b7ff1e37 spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:06:54Z" message: 'load-balancer-api-internal: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.748701ms message: 'load-balancer-api-internal: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 32.432929ms message: 'load-balancer-api-internal: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:54:53Z" - latency: 49.398142ms message: 'load-balancer-api-internal: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 7.215136ms message: 'load-balancer-api-internal: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:53:53Z" - latency: 52.810892ms message: 'load-balancer-api-internal: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 6.574589ms message: 'load-balancer-api-internal: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:53Z" - latency: 54.185904ms message: 'load-balancer-api-internal: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 6.64536ms message: 'load-balancer-api-internal: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:53Z" - latency: 49.273768ms message: 'load-balancer-api-internal: tcp connection to ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 6.231687ms message: 'load-balancer-api-internal: resolved host name ab4f6215569114d8cb596808b4941cb0-c1f4c936e9dcd2c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-network-check-target-ip-10-0-129-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "89590" uid: 70c39858-1415-46ac-8bb3-0f02c203faac spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:07:53Z" message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.297021ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:56:53Z" - latency: 2.476724ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:55:53Z" - latency: 4.557971ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 2.494585ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 2.400596ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 2.301724ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 2.186643ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 2.363089ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:53Z" - latency: 2.499503ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:53Z" - latency: 2.323541ms message: 'network-check-target-ip-10-0-129-114: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-network-check-target-ip-10-0-136-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "89589" uid: 12d53fde-6285-433e-b878-50fafd172554 spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:07:53Z" message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.085778ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:56:53Z" - latency: 2.026093ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:55:53Z" - latency: 4.787446ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 2.135813ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 2.348ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 2.182187ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 1.942971ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 1.901524ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:53Z" - latency: 1.983477ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:53Z" - latency: 2.178341ms message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-network-check-target-ip-10-0-136-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "89588" uid: 7fc2f37d-0f05-4cb5-ac22-11057913c39c spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:07:53Z" message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.272205ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:56:53Z" - latency: 1.214885ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:55:53Z" - latency: 4.83629ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 1.162832ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 1.237802ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 1.470161ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 1.231402ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 856.422µs message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:53Z" - latency: 893.541µs message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:53Z" - latency: 1.109443ms message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:00:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-94-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-94.us-west-2.compute.internal uid: 872373d1-c015-49db-906b-9b440a00df65 resourceVersion: "88374" uid: 038400c8-6548-47a4-869e-b87e538da5ce spec: sourcePod: network-check-source-6f78d59f99-cm7m6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T01:06:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.739325ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:53Z" - latency: 4.748895ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:54:53Z" - latency: 832.362µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:53Z" - latency: 577.734µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:53:53Z" - latency: 795.022µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:53Z" - latency: 537.765µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:53Z" - latency: 826.659µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:53Z" - latency: 513.437µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:53Z" - latency: 801.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:53Z" - latency: 498.34µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:53Z" kind: List metadata: resourceVersion: ""