apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "111277" uid: a0a6dd04-89cc-4f64-84d2-685bc10ab3b1 spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T07:09:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 730.921µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:12:15Z" - latency: 957.718µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:11:15Z" - latency: 1.050315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:10:15Z" - latency: 1.142043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:09:15Z" - latency: 1.11655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 1.226097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 1.07387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 1.302162ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 1.098722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 1.443235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "108427" uid: bd837ca6-1188-43cc-9b79-ea9f4b13f548 spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T07:08:15Z" message: 'load-balancer-api-external: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.435999ms message: 'load-balancer-api-external: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 5.751371ms message: 'load-balancer-api-external: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:08:15Z" - latency: 53.615592ms message: 'load-balancer-api-external: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 6.43698ms message: 'load-balancer-api-external: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:07:15Z" - latency: 53.387568ms message: 'load-balancer-api-external: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 6.053739ms message: 'load-balancer-api-external: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:06:15Z" - latency: 54.164997ms message: 'load-balancer-api-external: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 6.347091ms message: 'load-balancer-api-external: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:05:15Z" - latency: 53.445341ms message: 'load-balancer-api-external: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 6.32933ms message: 'load-balancer-api-external: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:04:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "108428" uid: f3484432-7957-4148-bb42-fa00c5869693 spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T07:08:15Z" message: 'load-balancer-api-internal: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.116684ms message: 'load-balancer-api-internal: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 5.812436ms message: 'load-balancer-api-internal: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:08:15Z" - latency: 54.317974ms message: 'load-balancer-api-internal: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 6.456566ms message: 'load-balancer-api-internal: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:07:15Z" - latency: 53.373724ms message: 'load-balancer-api-internal: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 6.094588ms message: 'load-balancer-api-internal: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:06:15Z" - latency: 54.164842ms message: 'load-balancer-api-internal: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 6.307233ms message: 'load-balancer-api-internal: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:05:15Z" - latency: 53.443716ms message: 'load-balancer-api-internal: tcp connection to aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 6.30757ms message: 'load-balancer-api-internal: resolved host name aa5d097cf21004010b37820ad9a97310-f5a8f4c20a3cd5e4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:04:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-network-check-target-ip-10-0-129-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "111276" uid: 56aa9e44-20d1-4b90-9867-2615f2da98db spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T07:09:15Z" message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.649736ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:12:15Z" - latency: 562.131µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:11:15Z" - latency: 605.85µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:10:15Z" - latency: 1.856095ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:09:15Z" - latency: 1.570653ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 517.889µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 591.991µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 1.973218ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 620.922µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 1.850212ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-network-check-target-ip-10-0-136-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "111274" uid: 6af230d0-a602-4a80-95f0-98fdfecf268c spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T07:09:15Z" message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013651ms message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:12:15Z" - latency: 848.627µs message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:11:15Z" - latency: 1.078212ms message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:10:15Z" - latency: 1.076098ms message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:09:15Z" - latency: 930.472µs message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 990.142µs message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 891.862µs message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 1.040369ms message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 1.020946ms message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 1.133967ms message: 'network-check-target-ip-10-0-136-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-network-check-target-ip-10-0-138-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "111275" uid: bc58ef7b-79da-403b-ae15-1e90570ce8e6 spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T07:09:15Z" message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.957186ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:12:15Z" - latency: 1.720947ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:11:15Z" - latency: 2.126613ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:10:15Z" - latency: 589.419µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:09:15Z" - latency: 2.212792ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 1.649605ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 1.838674ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 1.814648ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 1.66236ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 504.737µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:02:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-184-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-184.us-west-1.compute.internal uid: 4c764cc0-2d92-4256-93df-483fbf40a6c0 resourceVersion: "108424" uid: 776d0e32-b6fd-45cf-adb0-ab7e5150e467 spec: sourcePod: network-check-source-6f78d59f99-fb26v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T07:08:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.694µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:08:15Z" - latency: 1.848136ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:08:15Z" - latency: 1.800345ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:07:15Z" - latency: 1.776341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:07:15Z" - latency: 1.698429ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:06:15Z" - latency: 1.626297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:06:15Z" - latency: 680.523µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:05:15Z" - latency: 1.722883ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:05:15Z" - latency: 2.182325ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:04:15Z" - latency: 1.753827ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:04:15Z" kind: List metadata: resourceVersion: ""