apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57909" uid: f2ea9d96-062f-405f-8fd2-e2d4bbae6cec spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T18:20:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 952.655µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 966.583µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 825.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 799.998µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 1.39791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:04Z" - latency: 942.167µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:04Z" - latency: 889.313µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:04Z" - latency: 874.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:04Z" - latency: 889.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57911" uid: 837769d1-4d53-4331-af88-befcb3724816 spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:19:04Z" message: 'load-balancer-api-external: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.45852ms message: 'load-balancer-api-external: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 8.10824ms message: 'load-balancer-api-external: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:55:04Z" - latency: 4.346638ms message: 'load-balancer-api-external: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 9.804095ms message: 'load-balancer-api-external: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:54:04Z" - latency: 3.820753ms message: 'load-balancer-api-external: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 10.404266ms message: 'load-balancer-api-external: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:53:04Z" - latency: 5.066645ms message: 'load-balancer-api-external: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 8.875008ms message: 'load-balancer-api-external: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:52:04Z" - latency: 4.979385ms message: 'load-balancer-api-external: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 8.406707ms message: 'load-balancer-api-external: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57912" uid: 4f63824c-5a3f-4274-b918-25d556b76758 spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:19:04Z" message: 'load-balancer-api-internal: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.429017ms message: 'load-balancer-api-internal: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 8.050769ms message: 'load-balancer-api-internal: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:55:04Z" - latency: 5.486374ms message: 'load-balancer-api-internal: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 9.701381ms message: 'load-balancer-api-internal: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:54:04Z" - latency: 6.304765ms message: 'load-balancer-api-internal: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 10.446277ms message: 'load-balancer-api-internal: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:53:04Z" - latency: 6.210339ms message: 'load-balancer-api-internal: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 8.769936ms message: 'load-balancer-api-internal: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:52:04Z" - latency: 6.20727ms message: 'load-balancer-api-internal: tcp connection to abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 8.419156ms message: 'load-balancer-api-internal: resolved host name abb312c9ec5dd49188cea5710d3169c7-425244f00a42e862.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-network-check-target-ip-10-0-132-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57907" uid: 1b0af246-daf0-4af3-ae55-a1e93ebd4400 spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:20:04Z" message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.306388ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 811.769µs message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 1.204341ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 812.389µs message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 1.491254ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 865.623µs message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:04Z" - latency: 862.921µs message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:04Z" - latency: 784.484µs message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:04Z" - latency: 926.828µs message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:04Z" - latency: 1.445958ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-network-check-target-ip-10-0-136-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57905" uid: 86ec907b-883d-4a4f-b1ee-a33dd47eb859 spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:20:04Z" message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.224581ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 1.903956ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 2.43491ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 2.266383ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 2.276111ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 2.270068ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:04Z" - latency: 2.268384ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:04Z" - latency: 2.245981ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:04Z" - latency: 2.17796ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:04Z" - latency: 2.220154ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-network-check-target-ip-10-0-137-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57906" uid: 71542970-76c4-414b-850a-c91e44372b1e spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:20:04Z" message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.063684ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 2.11285ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 2.264035ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 2.357615ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 2.196214ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 1.990962ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:04Z" - latency: 2.320223ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:04Z" - latency: 2.449315ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:04Z" - latency: 2.028877ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:04Z" - latency: 2.456568ms message: 'network-check-target-ip-10-0-137-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:13:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-68-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-68.ec2.internal uid: cb55d676-d3f5-4040-9d91-fd4ca58d77c7 resourceVersion: "57908" uid: 242d24e6-0a5e-4638-9de3-aa2598553327 spec: sourcePod: network-check-source-7bc5b6bf85-9bn2j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T18:19:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.849µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:04Z" - latency: 2.095871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:55:04Z" - latency: 785.457µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:04Z" - latency: 1.936295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:54:04Z" - latency: 839.704µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:04Z" - latency: 1.772585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:53:04Z" - latency: 936.895µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:04Z" - latency: 2.163291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:52:04Z" - latency: 889.696µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:04Z" - latency: 1.607249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:51:04Z" kind: List metadata: resourceVersion: ""