apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "40041" uid: f66454f0-ab6d-42b6-857c-79655dac01f4 spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:39:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.168469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:02Z" - latency: 920.63µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:02Z" - latency: 1.61065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 1.566613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 1.175617ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 753.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 807.318µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 990.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:02Z" - latency: 790.793µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:02Z" - latency: 1.148166ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "38911" uid: 61fb92bc-a053-46c8-86d7-8bd4eb397b2c spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:38:02Z" message: 'load-balancer-api-external: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.123483ms message: 'load-balancer-api-external: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 7.18092ms message: 'load-balancer-api-external: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:26:02Z" - latency: 5.069259ms message: 'load-balancer-api-external: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 6.5554ms message: 'load-balancer-api-external: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:25:02Z" - latency: 3.92282ms message: 'load-balancer-api-external: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 6.803763ms message: 'load-balancer-api-external: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:24:02Z" - latency: 4.239295ms message: 'load-balancer-api-external: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 6.277952ms message: 'load-balancer-api-external: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:23:02Z" - latency: 3.840329ms message: 'load-balancer-api-external: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 6.653518ms message: 'load-balancer-api-external: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:22:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "38912" uid: 960fcdb4-81c3-49be-8714-4ab69101a418 spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:38:02Z" message: 'load-balancer-api-internal: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.008116ms message: 'load-balancer-api-internal: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 7.145239ms message: 'load-balancer-api-internal: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:26:02Z" - latency: 5.746582ms message: 'load-balancer-api-internal: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 6.500338ms message: 'load-balancer-api-internal: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:25:02Z" - latency: 4.142072ms message: 'load-balancer-api-internal: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 6.783854ms message: 'load-balancer-api-internal: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:24:02Z" - latency: 4.305512ms message: 'load-balancer-api-internal: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 6.252638ms message: 'load-balancer-api-internal: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:23:02Z" - latency: 4.447794ms message: 'load-balancer-api-internal: tcp connection to aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 6.563915ms message: 'load-balancer-api-internal: resolved host name aab5836303ae744c2af2376e22c38be1-238655e137282b64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:22:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-ip-10-0-129-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "40039" uid: d6e3612c-9505-4c7b-a059-927719ed1faf spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:39:02Z" message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.239996ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:02Z" - latency: 2.472165ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:02Z" - latency: 2.209627ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 2.330481ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 2.247683ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 2.262967ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 2.074921ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 2.353134ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:02Z" - latency: 2.107907ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:02Z" - latency: 2.252596ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-ip-10-0-129-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "40040" uid: 2f1d05f5-10a0-4fb9-8ff4-b9c79175f637 spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:39:02Z" message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.166742ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:02Z" - latency: 1.981028ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:02Z" - latency: 2.003334ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 1.761232ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 1.936218ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 1.997703ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 1.622125ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 1.906395ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:02Z" - latency: 1.602158ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:02Z" - latency: 1.782391ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-ip-10-0-136-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "40038" uid: 98ac403c-4f7e-4abd-b3a5-3319d639fa19 spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:39:02Z" message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.266131ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:02Z" - latency: 1.495427ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:02Z" - latency: 795.826µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 1.354359ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 919.441µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 998.088µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 1.098929ms message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 889.03µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:02Z" - latency: 998.988µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:02Z" - latency: 820.115µs message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-160.ec2.internal uid: 2e366257-9f43-466d-919c-725239252652 resourceVersion: "38910" uid: 40648d95-637a-4cc5-822a-818d319ff76c spec: sourcePod: network-check-source-8894fc9bd-c2lfl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:38:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175551ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:02Z" - latency: 1.782091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:26:02Z" - latency: 1.269533ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:02Z" - latency: 1.94655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:25:02Z" - latency: 875.354µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:02Z" - latency: 1.901234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:24:02Z" - latency: 971.079µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:02Z" - latency: 1.601257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:23:02Z" - latency: 1.333552ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:02Z" - latency: 1.684474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:22:02Z" kind: List metadata: resourceVersion: ""