apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53463" uid: 9d06d659-f525-4621-8008-5e09ab65c65a spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T10:18:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 887.724µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 808.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 1.319486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 1.334784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 1.350044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:30:33Z" - latency: 1.125585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:29:33Z" - latency: 1.064048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:28:33Z" - latency: 1.447967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:27:33Z" - latency: 1.355489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:26:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53464" uid: 205fae0b-1641-4a00-928c-90386607044c spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:17:33Z" message: 'load-balancer-api-external: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.133159ms message: 'load-balancer-api-external: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 9.260331ms message: 'load-balancer-api-external: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:35:33Z" - latency: 5.020869ms message: 'load-balancer-api-external: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 8.166708ms message: 'load-balancer-api-external: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:34:33Z" - latency: 4.655577ms message: 'load-balancer-api-external: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 8.683283ms message: 'load-balancer-api-external: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:33:33Z" - latency: 8.020103ms message: 'load-balancer-api-external: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 7.831323ms message: 'load-balancer-api-external: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:32:33Z" - latency: 4.999325ms message: 'load-balancer-api-external: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 11.477728ms message: 'load-balancer-api-external: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:31:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53465" uid: 898f625c-2e21-446f-8b0b-3529f8de86ce spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T10:17:33Z" message: 'load-balancer-api-internal: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.159651ms message: 'load-balancer-api-internal: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 9.324683ms message: 'load-balancer-api-internal: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:35:33Z" - latency: 5.029141ms message: 'load-balancer-api-internal: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 8.123399ms message: 'load-balancer-api-internal: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:34:33Z" - latency: 4.080508ms message: 'load-balancer-api-internal: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 8.642458ms message: 'load-balancer-api-internal: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:33:33Z" - latency: 7.369639ms message: 'load-balancer-api-internal: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 7.881846ms message: 'load-balancer-api-internal: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:32:33Z" - latency: 4.991166ms message: 'load-balancer-api-internal: tcp connection to ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 11.56042ms message: 'load-balancer-api-internal: resolved host name ad468ea50ea3c4150812a35c7ea52d17-79c2b193014c27c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:31:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-ip-10-0-133-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53462" uid: 24ffa9b1-7ac8-48e2-b47b-84120a2b4a87 spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:18:33Z" message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.23258ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 1.985072ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 1.621683ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 2.037047ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 1.86724ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 1.793965ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:30:33Z" - latency: 1.927969ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:29:33Z" - latency: 1.914296ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:28:33Z" - latency: 1.753242ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:27:33Z" - latency: 1.955203ms message: 'network-check-target-ip-10-0-133-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:26:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-ip-10-0-136-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53461" uid: db7de154-e150-46e8-9ccf-c69a2b184f12 spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:18:33Z" message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.024064ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 2.127232ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 1.803639ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 2.138902ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 2.322722ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 2.03027ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:30:33Z" - latency: 1.897214ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:29:33Z" - latency: 2.127255ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:28:33Z" - latency: 2.304102ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:27:33Z" - latency: 2.078624ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:26:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-ip-10-0-136-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53459" uid: 06f17460-9d94-48aa-8c79-3c173c6d78af spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T10:18:33Z" message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 636.98µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 949.964µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 807.445µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 1.46515ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 850.266µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 976.317µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:30:33Z" - latency: 882.498µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:29:33Z" - latency: 861.287µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:28:33Z" - latency: 790.964µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:27:33Z" - latency: 976.643µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:26:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T10:11:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 5640dc02-dba7-4818-a30c-75fb6b0765fb resourceVersion: "53460" uid: d74067b3-1108-4655-afd9-3ab804512a31 spec: sourcePod: network-check-source-7d88cb55d8-xt754 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T10:17:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 745.464µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:35:33Z" - latency: 1.496626ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:35:33Z" - latency: 828.041µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:34:33Z" - latency: 1.718631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:34:33Z" - latency: 779.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:33:33Z" - latency: 1.800971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:33:33Z" - latency: 897.31µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:32:33Z" - latency: 1.571399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:32:33Z" - latency: 867.532µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:31:33Z" - latency: 1.861347ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:31:33Z" kind: List metadata: resourceVersion: ""