apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "48921" uid: 2d8629f5-4c61-4e49-af18-6e64c60b6371 spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T04:43:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 943.316µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 1.06852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 1.086525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:01:21Z" - latency: 965.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:00:21Z" - latency: 921.735µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:59:21Z" - latency: 1.05245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:58:21Z" - latency: 1.016759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:57:21Z" - latency: 974.296µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:56:21Z" - latency: 997.874µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "51216" uid: 3701970f-4178-44e9-ab3b-f02b503a9846 spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:42:21Z" message: 'load-balancer-api-external: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.290349ms message: 'load-balancer-api-external: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:06:21Z" - latency: 6.834292ms message: 'load-balancer-api-external: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:06:21Z" - latency: 5.532273ms message: 'load-balancer-api-external: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:05:21Z" - latency: 8.953566ms message: 'load-balancer-api-external: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:05:21Z" - latency: 4.219369ms message: 'load-balancer-api-external: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 7.110911ms message: 'load-balancer-api-external: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:04:21Z" - latency: 4.466162ms message: 'load-balancer-api-external: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 7.588421ms message: 'load-balancer-api-external: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:03:21Z" - latency: 4.5276ms message: 'load-balancer-api-external: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 7.544673ms message: 'load-balancer-api-external: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:02:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "51217" uid: 215a3671-f53f-48c8-971e-fb420094397d spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:42:21Z" message: 'load-balancer-api-internal: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.337235ms message: 'load-balancer-api-internal: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:06:21Z" - latency: 6.802746ms message: 'load-balancer-api-internal: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:06:21Z" - latency: 5.545583ms message: 'load-balancer-api-internal: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:05:21Z" - latency: 8.913495ms message: 'load-balancer-api-internal: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:05:21Z" - latency: 5.156254ms message: 'load-balancer-api-internal: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 7.078228ms message: 'load-balancer-api-internal: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:04:21Z" - latency: 5.167893ms message: 'load-balancer-api-internal: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 7.496949ms message: 'load-balancer-api-internal: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:03:21Z" - latency: 4.57462ms message: 'load-balancer-api-internal: tcp connection to ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 7.49961ms message: 'load-balancer-api-internal: resolved host name ac606f396fce4489e854526349ffef89-afea8b7f8440b007.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T05:02:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-network-check-target-ip-10-0-134-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "48920" uid: 323361e3-4e00-451d-ad31-f576c2b6042d spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:43:21Z" message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.401055ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 2.299316ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 2.44426ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 2.750412ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:01:21Z" - latency: 2.376304ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:00:21Z" - latency: 2.250847ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:59:21Z" - latency: 2.334885ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:58:21Z" - latency: 2.439473ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:57:21Z" - latency: 2.449926ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:56:21Z" - latency: 2.31978ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-network-check-target-ip-10-0-139-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "48919" uid: 87cc434e-7238-4cf5-91b8-3f5eaeb6616d spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:43:21Z" message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.394617ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 2.919431ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 2.385944ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 2.950581ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:01:21Z" - latency: 2.502996ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:00:21Z" - latency: 2.466409ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:59:21Z" - latency: 2.505574ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:58:21Z" - latency: 2.938509ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:57:21Z" - latency: 2.459154ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:56:21Z" - latency: 2.170517ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-network-check-target-ip-10-0-142-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "48918" uid: 89bd30a6-debd-4825-9102-ce3643632c4b spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:43:21Z" message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 977.269µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 814.55µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 824.837µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 1.086634ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:01:21Z" - latency: 922.374µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:00:21Z" - latency: 884.794µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:59:21Z" - latency: 972.765µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:58:21Z" - latency: 1.591427ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:57:21Z" - latency: 1.406437ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:56:21Z" - latency: 916.318µs message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:36:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-255-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-255.ec2.internal uid: 8b76c98a-064e-4c2d-a4ac-e30d8dff935b resourceVersion: "51215" uid: e9c01e8d-c639-4849-a849-eebe02d73e86 spec: sourcePod: network-check-source-989f8b8dc-llhnw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T04:42:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.51µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:06:21Z" - latency: 1.766444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T05:06:21Z" - latency: 1.068407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:05:21Z" - latency: 2.067482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T05:05:21Z" - latency: 1.267156ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:04:21Z" - latency: 1.782195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T05:04:21Z" - latency: 1.004623ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:03:21Z" - latency: 2.191422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T05:03:21Z" - latency: 770.858µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T05:02:21Z" - latency: 1.765859ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T05:02:21Z" kind: List metadata: resourceVersion: ""