apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62539" uid: d9d57287-8922-4940-a756-45d02eccdd03 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T13:05:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.727µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 969.384µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 970.361µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 882.565µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 1.211775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 768.576µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:35:13Z" - latency: 1.279165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:34:13Z" - latency: 1.250872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:33:13Z" - latency: 1.286528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:32:13Z" - latency: 1.260284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62540" uid: 4accc120-e4d6-4acc-b667-7c1a459723c6 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T13:04:13Z" message: 'load-balancer-api-external: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.229926ms message: 'load-balancer-api-external: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 9.153835ms message: 'load-balancer-api-external: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:40:13Z" - latency: 4.09695ms message: 'load-balancer-api-external: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 10.110544ms message: 'load-balancer-api-external: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:39:13Z" - latency: 5.723863ms message: 'load-balancer-api-external: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 8.897946ms message: 'load-balancer-api-external: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:38:13Z" - latency: 5.808817ms message: 'load-balancer-api-external: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 7.79952ms message: 'load-balancer-api-external: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:37:13Z" - latency: 5.390647ms message: 'load-balancer-api-external: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 9.14269ms message: 'load-balancer-api-external: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:36:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62541" uid: 808fc16c-b21a-436b-9d41-22d6737cd885 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T13:04:13Z" message: 'load-balancer-api-internal: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.199612ms message: 'load-balancer-api-internal: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 9.122845ms message: 'load-balancer-api-internal: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:40:13Z" - latency: 4.071561ms message: 'load-balancer-api-internal: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 10.058362ms message: 'load-balancer-api-internal: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:39:13Z" - latency: 5.734358ms message: 'load-balancer-api-internal: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 8.868554ms message: 'load-balancer-api-internal: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:38:13Z" - latency: 5.394762ms message: 'load-balancer-api-internal: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 7.724266ms message: 'load-balancer-api-internal: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:37:13Z" - latency: 5.258281ms message: 'load-balancer-api-internal: tcp connection to a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 9.005917ms message: 'load-balancer-api-internal: resolved host name a82950ba039114880954bc739d3489ad-84853a5b10a0c450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T13:36:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-network-check-target-ip-10-0-134-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62535" uid: 8894dc65-424d-477a-9b40-51a6ddb47317 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T13:05:13Z" message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035479ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 1.270087ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 1.150509ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 1.058596ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 1.644667ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 946.311µs message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:35:13Z" - latency: 1.058224ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:34:13Z" - latency: 927.126µs message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:33:13Z" - latency: 1.472358ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:32:13Z" - latency: 1.095483ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-network-check-target-ip-10-0-140-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62536" uid: 2804667b-db68-4d60-be17-fc973ce65e95 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T13:05:13Z" message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.210493ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 2.325519ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 2.077202ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 2.224066ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 2.231103ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 2.100401ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:35:13Z" - latency: 2.268055ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:34:13Z" - latency: 2.22492ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:33:13Z" - latency: 1.985472ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:32:13Z" - latency: 2.310251ms message: 'network-check-target-ip-10-0-140-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-network-check-target-ip-10-0-141-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62537" uid: 940c89df-cb8d-4b06-9a08-1b3a7d0d0967 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T13:05:13Z" message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.141752ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 2.143583ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 1.876921ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 2.208878ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 2.468913ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 2.055964ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:35:13Z" - latency: 2.113382ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:34:13Z" - latency: 2.1624ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:33:13Z" - latency: 2.210935ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:32:13Z" - latency: 2.394273ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T12:58:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-155-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-155.ec2.internal uid: 15ff7dbc-92da-4ad9-807d-d48c9fcc24c2 resourceVersion: "62538" uid: 01308b24-f3e9-4a83-bc8a-e8db6a137599 spec: sourcePod: network-check-source-7bc5b6bf85-slhwr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T13:04:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.182748ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:40:13Z" - latency: 2.042258ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:40:13Z" - latency: 910.622µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:39:13Z" - latency: 2.008793ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:39:13Z" - latency: 895.667µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:38:13Z" - latency: 2.126148ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:38:13Z" - latency: 1.416787ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:37:13Z" - latency: 1.692572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:37:13Z" - latency: 844.092µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T13:36:13Z" - latency: 2.261408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T13:36:13Z" kind: List metadata: resourceVersion: ""