apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "54469" uid: 2ccdbf7b-e110-4c63-8dcd-0d8ad10e81c8 spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T13:39: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.044151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 773.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 1.178955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 1.44056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 1.1135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:03:03Z" - latency: 1.338678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:02:03Z" - latency: 1.142963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:01:03Z" - latency: 1.022833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:00:03Z" - latency: 1.145454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:59:03Z" - latency: 1.24938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:58:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "55480" uid: c9697bc9-321c-4f53-8375-fc211103aeb0 spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T13:38:03Z" message: 'load-balancer-api-external: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.694357ms message: 'load-balancer-api-external: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:08:03Z" - latency: 8.175968ms message: 'load-balancer-api-external: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:08:03Z" - latency: 4.938093ms message: 'load-balancer-api-external: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 9.038062ms message: 'load-balancer-api-external: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:07:03Z" - latency: 5.722286ms message: 'load-balancer-api-external: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 8.274415ms message: 'load-balancer-api-external: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:06:03Z" - latency: 5.873703ms message: 'load-balancer-api-external: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 10.031267ms message: 'load-balancer-api-external: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:05:03Z" - latency: 4.463043ms message: 'load-balancer-api-external: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 8.447845ms message: 'load-balancer-api-external: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:04:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "55481" uid: 9c722fcd-8a05-4e29-9ed7-55b172ba7521 spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T13:38:03Z" message: 'load-balancer-api-internal: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.709371ms message: 'load-balancer-api-internal: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:08:03Z" - latency: 8.119521ms message: 'load-balancer-api-internal: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:08:03Z" - latency: 4.360071ms message: 'load-balancer-api-internal: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 8.94152ms message: 'load-balancer-api-internal: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:07:03Z" - latency: 5.684786ms message: 'load-balancer-api-internal: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 8.122334ms message: 'load-balancer-api-internal: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:06:03Z" - latency: 5.923525ms message: 'load-balancer-api-internal: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 9.995018ms message: 'load-balancer-api-internal: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:05:03Z" - latency: 4.427263ms message: 'load-balancer-api-internal: tcp connection to ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 8.397894ms message: 'load-balancer-api-internal: resolved host name ae9f60875d437457b8f165edae82d926-0abfcdf4cf07f9e3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:04:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-network-check-target-ip-10-0-129-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "54468" uid: 46d9039f-dfb1-4aba-9129-8c99c15ec28f spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T13:39:03Z" message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.251313ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 2.002486ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 1.976208ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 1.921756ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 1.822198ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:03:03Z" - latency: 2.109384ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:02:03Z" - latency: 1.585989ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:01:03Z" - latency: 2.250277ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:00:03Z" - latency: 1.854029ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:59:03Z" - latency: 2.266306ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:58:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-network-check-target-ip-10-0-132-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "54467" uid: 88542ab0-93ca-4547-b645-c1a4721df098 spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T13:39:03Z" message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.303245ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 1.876144ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 2.181841ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 2.240725ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 2.719567ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:03:03Z" - latency: 1.996503ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:02:03Z" - latency: 2.157885ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:01:03Z" - latency: 2.285369ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:00:03Z" - latency: 2.129217ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:59:03Z" - latency: 2.304519ms message: 'network-check-target-ip-10-0-132-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:58:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-network-check-target-ip-10-0-138-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "54466" uid: 4c9a96e9-1118-430b-b5d2-95239dbcf326 spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T13:39:03Z" message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.412992ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 1.191434ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 858.59µs message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 811.049µs message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 942.14µs message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:03:03Z" - latency: 1.036413ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:02:03Z" - latency: 1.3173ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:01:03Z" - latency: 1.325498ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:00:03Z" - latency: 1.177138ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:59:03Z" - latency: 1.363565ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:58:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T13:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-57.ec2.internal uid: a9c39579-8dc9-4dfa-9f46-48aa81e04fe9 resourceVersion: "55479" uid: a02c841b-7532-4e4e-9dcb-d7d84750944e spec: sourcePod: network-check-source-989f8b8dc-v9985 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T13:38:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.316µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:08:03Z" - latency: 1.790677ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:08:03Z" - latency: 760.376µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:07:03Z" - latency: 2.303712ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:07:03Z" - latency: 890.982µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:06:03Z" - latency: 1.736721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:06:03Z" - latency: 777.723µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:05:03Z" - latency: 2.671602ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:05:03Z" - latency: 909.328µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:04:03Z" - latency: 1.730235ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:04:03Z" kind: List metadata: resourceVersion: ""