apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "54980" uid: 36c6449b-894b-41c6-b805-c135b8b9c99d spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T19:16:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.339013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 908.227µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 1.098004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 1.564344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 768.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 1.157921ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 906.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 1.18128ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 1.508854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 828.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "56081" uid: e445601e-6fe1-4505-9a43-a054d4816cba spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:15:45Z" message: 'load-balancer-api-external: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.668905ms message: 'load-balancer-api-external: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:45Z" - latency: 7.479337ms message: 'load-balancer-api-external: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:45:45Z" - latency: 5.274449ms message: 'load-balancer-api-external: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 7.847118ms message: 'load-balancer-api-external: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:44:45Z" - latency: 4.521434ms message: 'load-balancer-api-external: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 6.78267ms message: 'load-balancer-api-external: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:45Z" - latency: 4.711197ms message: 'load-balancer-api-external: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 7.553474ms message: 'load-balancer-api-external: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:42:45Z" - latency: 4.195393ms message: 'load-balancer-api-external: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 7.459537ms message: 'load-balancer-api-external: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "56082" uid: e1c5fcc4-9ace-463a-9872-90009d7aee36 spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:15:45Z" message: 'load-balancer-api-internal: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.711291ms message: 'load-balancer-api-internal: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:45Z" - latency: 7.460055ms message: 'load-balancer-api-internal: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:45:45Z" - latency: 5.295162ms message: 'load-balancer-api-internal: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 7.780119ms message: 'load-balancer-api-internal: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:44:45Z" - latency: 4.519154ms message: 'load-balancer-api-internal: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 6.672287ms message: 'load-balancer-api-internal: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:45Z" - latency: 3.566982ms message: 'load-balancer-api-internal: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 7.461148ms message: 'load-balancer-api-internal: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:42:45Z" - latency: 4.204374ms message: 'load-balancer-api-internal: tcp connection to a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 7.416578ms message: 'load-balancer-api-internal: resolved host name a5655012d93ca4750b4bf24181a94b78-139b6c9ebf77e70b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-network-check-target-ip-10-0-130-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "54977" uid: a2f7cd9f-fe87-4dfb-8877-bc6e788738fd spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:16:45Z" message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.580973ms message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 874.156µs message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 970.728µs message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 1.243278ms message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 1.143971ms message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 806.833µs message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 1.433309ms message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 918.94µs message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 1.188099ms message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 981.635µs message: 'network-check-target-ip-10-0-130-68: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-network-check-target-ip-10-0-133-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "54979" uid: 913de8a3-1934-4eda-9ac7-023ef3b7e701 spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:16:45Z" message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.938621ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 1.832099ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 2.209771ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 1.951216ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 1.647639ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 1.547415ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 1.859735ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 2.106622ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 1.890466ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 1.913242ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-network-check-target-ip-10-0-143-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "54978" uid: 50f8cc17-b5cf-4a07-a7bc-718a2ed19baa spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:16:45Z" message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.253235ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 1.944566ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 2.157011ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 2.190447ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 2.175077ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 1.992056ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 2.259981ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 2.312006ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 2.34131ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 2.078716ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:09:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-68-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-68.ec2.internal uid: ce0583ac-0f3d-4681-8662-61887e51a7dc resourceVersion: "56080" uid: fdf7cf73-8951-4d05-bb42-c0b861a96cb1 spec: sourcePod: network-check-source-989f8b8dc-xpftx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T19:15:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.060478ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:45Z" - latency: 1.728747ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:45:45Z" - latency: 987.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:44:45Z" - latency: 1.671296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:44:45Z" - latency: 1.015679ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:43:45Z" - latency: 1.657227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:43:45Z" - latency: 1.301976ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:42:45Z" - latency: 1.711773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:42:45Z" - latency: 951.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 2.031354ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:45Z" kind: List metadata: resourceVersion: ""