apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "22246" uid: f8dd9bde-eb59-4722-94b4-61fbc879c921 spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T17:50:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.941µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:04:38Z" - latency: 1.113843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:03:38Z" - latency: 973.201µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:02:38Z" - latency: 1.485734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 942.87µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 1.134373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 1.059933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 889.485µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 1.114704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:56:38Z" - latency: 731.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:55:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "20689" uid: 582a63a0-a44d-43d2-be8a-60fd095835ed spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:49:38Z" message: 'load-balancer-api-external: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.208955ms message: 'load-balancer-api-external: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 6.664836ms message: 'load-balancer-api-external: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:01:38Z" - latency: 3.629536ms message: 'load-balancer-api-external: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 8.636895ms message: 'load-balancer-api-external: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:00:38Z" - latency: 4.936106ms message: 'load-balancer-api-external: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 7.861593ms message: 'load-balancer-api-external: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:59:38Z" - latency: 4.839159ms message: 'load-balancer-api-external: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 15.276447ms message: 'load-balancer-api-external: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:58:38Z" - latency: 5.373163ms message: 'load-balancer-api-external: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 13.297525ms message: 'load-balancer-api-external: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:57:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "20690" uid: 4ea735c3-2783-4009-ab78-e7ee73e9fa47 spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:49:38Z" message: 'load-balancer-api-internal: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.590256ms message: 'load-balancer-api-internal: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 6.615039ms message: 'load-balancer-api-internal: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:01:38Z" - latency: 3.609912ms message: 'load-balancer-api-internal: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 8.662581ms message: 'load-balancer-api-internal: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:00:38Z" - latency: 4.9515ms message: 'load-balancer-api-internal: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 7.983759ms message: 'load-balancer-api-internal: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:59:38Z" - latency: 4.871814ms message: 'load-balancer-api-internal: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 15.206911ms message: 'load-balancer-api-internal: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:58:38Z" - latency: 5.379648ms message: 'load-balancer-api-internal: tcp connection to aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 13.242416ms message: 'load-balancer-api-internal: resolved host name aed027ddc15e947208e1e0e5d3aac6d2-4f135cdd5ed82b56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:57:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-network-check-target-ip-10-0-128-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "22244" uid: 72737319-ac68-415b-a387-0fd41cf3b7a8 spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:50:38Z" message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.885618ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:04:38Z" - latency: 1.886578ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:03:38Z" - latency: 1.991181ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:02:38Z" - latency: 1.727023ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 1.937327ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 1.887699ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 1.841594ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 2.012917ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 1.716515ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:56:38Z" - latency: 1.593779ms message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:55:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-network-check-target-ip-10-0-135-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "22245" uid: e7cbc938-d663-4276-91f6-df25cf044eeb spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:50:38Z" message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.372935ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:04:38Z" - latency: 2.3209ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:03:38Z" - latency: 2.476373ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:02:38Z" - latency: 2.12094ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 2.09228ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 2.228726ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 2.122737ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 2.260559ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 2.063681ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:56:38Z" - latency: 1.750004ms message: 'network-check-target-ip-10-0-135-252: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:55:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-network-check-target-ip-10-0-143-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "22243" uid: 53682fae-4cf2-47a9-a74a-03480d79f9f7 spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:50:38Z" message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.377861ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:04:38Z" - latency: 1.258579ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:03:38Z" - latency: 1.380787ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:02:38Z" - latency: 747µs message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 744.023µs message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 810.995µs message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 1.346703ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 990.445µs message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 922.929µs message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:56:38Z" - latency: 729.437µs message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:55:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-142-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-142.ec2.internal uid: f85ffb4b-620d-45b5-8757-babae0bafc5e resourceVersion: "20688" uid: b4938a0a-f702-4fca-a98a-866c5317b5e9 spec: sourcePod: network-check-source-869dcfcdcd-dkxlh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T17:49:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174926ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:01:38Z" - latency: 1.575766ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:01:38Z" - latency: 1.049512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:00:38Z" - latency: 1.912832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:00:38Z" - latency: 1.029051ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:59:38Z" - latency: 1.687993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:59:38Z" - latency: 932.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:58:38Z" - latency: 1.682492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:58:38Z" - latency: 983.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:57:38Z" - latency: 1.952723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:57:38Z" kind: List metadata: resourceVersion: ""