apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "25025" uid: 8b93b937-004a-4626-9a23-0c3ef324ed4f spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T17:10:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.984µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 1.245892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 1.188808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 847.318µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:28:54Z" - latency: 949.551µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:27:54Z" - latency: 949.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:26:54Z" - latency: 956.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:25:54Z" - latency: 907.021µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:24:54Z" - latency: 1.050415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:23:54Z" - latency: 1.051708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:22:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "26422" uid: c9524add-4a82-4f7e-9282-f9d62f8ea628 spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T17:09:54Z" message: 'load-balancer-api-external: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.37468ms message: 'load-balancer-api-external: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:33:54Z" - latency: 6.498492ms message: 'load-balancer-api-external: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:33:54Z" - latency: 4.800346ms message: 'load-balancer-api-external: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:32:54Z" - latency: 6.575778ms message: 'load-balancer-api-external: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:32:54Z" - latency: 5.389032ms message: 'load-balancer-api-external: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 6.348302ms message: 'load-balancer-api-external: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:31:54Z" - latency: 5.492645ms message: 'load-balancer-api-external: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 7.16806ms message: 'load-balancer-api-external: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:30:54Z" - latency: 5.272823ms message: 'load-balancer-api-external: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 6.738395ms message: 'load-balancer-api-external: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:29:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "26423" uid: 97e90037-e08d-4370-89d5-7c68094b48c1 spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T17:09:54Z" message: 'load-balancer-api-internal: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.386961ms message: 'load-balancer-api-internal: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:33:54Z" - latency: 6.469969ms message: 'load-balancer-api-internal: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:33:54Z" - latency: 4.591496ms message: 'load-balancer-api-internal: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:32:54Z" - latency: 6.479003ms message: 'load-balancer-api-internal: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:32:54Z" - latency: 7.429656ms message: 'load-balancer-api-internal: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 6.276255ms message: 'load-balancer-api-internal: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:31:54Z" - latency: 5.475019ms message: 'load-balancer-api-internal: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 7.109057ms message: 'load-balancer-api-internal: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:30:54Z" - latency: 5.424659ms message: 'load-balancer-api-internal: tcp connection to af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 6.616747ms message: 'load-balancer-api-internal: resolved host name af42676316cf5495787a76978deef5cb-b7baf14f63c82c18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:29:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-129-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "25022" uid: 3a949429-bf87-4e66-aaaa-6815e434b69c spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:10:54Z" message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.113007ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 2.373077ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 2.502253ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 2.454359ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:28:54Z" - latency: 2.21771ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:27:54Z" - latency: 2.517214ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:26:54Z" - latency: 2.589561ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:25:54Z" - latency: 2.229622ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:24:54Z" - latency: 2.327303ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:23:54Z" - latency: 2.138525ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:22:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-130-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "25024" uid: 6857d7c9-922d-4a95-90e6-502164a319c8 spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:10:54Z" message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 824.089µs message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 1.541639ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 932.813µs message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 1.264824ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:28:54Z" - latency: 1.262685ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:27:54Z" - latency: 1.39209ms message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:26:54Z" - latency: 939.368µs message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:25:54Z" - latency: 908.508µs message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:24:54Z" - latency: 856.349µs message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:23:54Z" - latency: 931.076µs message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:22:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-136-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "25023" uid: f465d767-1013-4300-b63a-c74a9a460329 spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:10:54Z" message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.470389ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 2.587173ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 2.651ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 2.299236ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:28:54Z" - latency: 2.772499ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:27:54Z" - latency: 2.569669ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:26:54Z" - latency: 2.228875ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:25:54Z" - latency: 2.257183ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:24:54Z" - latency: 2.633887ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:23:54Z" - latency: 2.155512ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:22:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-254-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-254.ec2.internal uid: 9567a066-ffda-447a-951f-1677441b604a resourceVersion: "26421" uid: 6bf1b806-51b5-448a-b9fd-3f0c80f2c0fe spec: sourcePod: network-check-source-7d88cb55d8-8bkcp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T17:09:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.13701ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:33:54Z" - latency: 1.747849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:33:54Z" - latency: 826.361µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:32:54Z" - latency: 1.985053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:32:54Z" - latency: 995.549µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:31:54Z" - latency: 1.664851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:31:54Z" - latency: 1.047164ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:30:54Z" - latency: 2.066523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:30:54Z" - latency: 907.24µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:29:54Z" - latency: 1.787817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:29:54Z" kind: List metadata: resourceVersion: ""