apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "111595" uid: 5d2ba8d3-ce32-40e5-b1ec-9506eacbfd1e spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T22:31:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.084976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:03Z" - latency: 1.227293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:03Z" - latency: 1.22668ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:03Z" - latency: 1.017193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:31:03Z" - latency: 1.080277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:30:03Z" - latency: 1.628744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:29:03Z" - latency: 1.268249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:28:03Z" - latency: 4.351543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:27:03Z" - latency: 1.00722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:26:03Z" - latency: 1.154367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:25:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "112771" uid: 2b219771-13cf-4746-954b-0b6cc53b6dba spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T22:30:03Z" message: 'load-balancer-api-external: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.149182ms message: 'load-balancer-api-external: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:36:03Z" - latency: 6.64433ms message: 'load-balancer-api-external: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:36:03Z" - latency: 56.082927ms message: 'load-balancer-api-external: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:35:03Z" - latency: 7.035782ms message: 'load-balancer-api-external: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:35:03Z" - latency: 55.164416ms message: 'load-balancer-api-external: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:03Z" - latency: 6.627471ms message: 'load-balancer-api-external: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:34:03Z" - latency: 55.67692ms message: 'load-balancer-api-external: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:03Z" - latency: 7.187673ms message: 'load-balancer-api-external: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:33:03Z" - latency: 56.669118ms message: 'load-balancer-api-external: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:03Z" - latency: 6.555388ms message: 'load-balancer-api-external: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:32:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "112772" uid: 6f76da66-9960-4b02-a80b-617c36a77405 spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T22:30:03Z" message: 'load-balancer-api-internal: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.133611ms message: 'load-balancer-api-internal: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:36:03Z" - latency: 6.70915ms message: 'load-balancer-api-internal: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:36:03Z" - latency: 52.275587ms message: 'load-balancer-api-internal: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:35:03Z" - latency: 7.013981ms message: 'load-balancer-api-internal: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:35:03Z" - latency: 55.700843ms message: 'load-balancer-api-internal: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:03Z" - latency: 6.548695ms message: 'load-balancer-api-internal: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:34:03Z" - latency: 54.455251ms message: 'load-balancer-api-internal: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:03Z" - latency: 7.213093ms message: 'load-balancer-api-internal: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:33:03Z" - latency: 57.866901ms message: 'load-balancer-api-internal: tcp connection to a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:03Z" - latency: 6.59948ms message: 'load-balancer-api-internal: resolved host name a16baf3e91ce6443fadccbde99d65a93-20d6be8647d4ee72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:32:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-ip-10-0-128-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "111752" uid: f7ed107d-ac5a-42c8-a3bf-c2c51c44ba29 spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:31:17Z" message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.157586ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:17Z" - latency: 2.009234ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:17Z" - latency: 2.69565ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:17Z" - latency: 2.536933ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:31:17Z" - latency: 2.39224ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:30:17Z" - latency: 2.068161ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:29:17Z" - latency: 2.659301ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:28:17Z" - latency: 2.57453ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:27:17Z" - latency: 2.707604ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:26:17Z" - latency: 2.670666ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:25:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-ip-10-0-139-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "111592" uid: ec723280-2000-42e4-a5ad-956ec5dfe185 spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:31:03Z" message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.371273ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:03Z" - latency: 1.211197ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:03Z" - latency: 1.01774ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:03Z" - latency: 1.341573ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:31:03Z" - latency: 1.049677ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:30:03Z" - latency: 1.241413ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:29:03Z" - latency: 1.168008ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:28:03Z" - latency: 5.825911ms message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:27:03Z" - latency: 968.419µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:26:03Z" - latency: 928.265µs message: 'network-check-target-ip-10-0-139-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:25:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-ip-10-0-143-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "111593" uid: 33056ad7-07bd-4424-8be7-e5df15b78ab6 spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:31:03Z" message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.496209ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:03Z" - latency: 2.713835ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:03Z" - latency: 2.543864ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:03Z" - latency: 2.38532ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:31:03Z" - latency: 2.392582ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:30:03Z" - latency: 3.136954ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:29:03Z" - latency: 2.712614ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:28:03Z" - latency: 6.392494ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:27:03Z" - latency: 2.732641ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:26:03Z" - latency: 2.461359ms message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:25:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:24:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-173.us-west-2.compute.internal uid: 56b76859-427b-4f13-b9bc-578a77a13615 resourceVersion: "112767" uid: 560bf85c-6352-4e19-9b90-7b4f3d6fb195 spec: sourcePod: network-check-source-6f78d59f99-7hx9j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T22:30:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.184879ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:36:03Z" - latency: 1.969344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:36:03Z" - latency: 2.210784ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:35:03Z" - latency: 1.947817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:35:03Z" - latency: 873.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:34:03Z" - latency: 1.761803ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:34:03Z" - latency: 957.728µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:33:03Z" - latency: 1.9613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:33:03Z" - latency: 2.160299ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:32:03Z" - latency: 1.804137ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:32:03Z" kind: List metadata: resourceVersion: ""