apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "60629" uid: e56a5fb4-2823-4068-9d6a-ac36af242c21 spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T23:11:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.538µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:31Z" - latency: 835.565µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:31Z" - latency: 1.128453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:31Z" - latency: 1.225031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:31Z" - latency: 1.297707ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:35:31Z" - latency: 912.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:34:31Z" - latency: 1.22809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:33:31Z" - latency: 1.994541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:32:31Z" - latency: 813.287µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:31:31Z" - latency: 1.085896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "61822" uid: da73ad0c-9886-4316-9e8c-3f3621d5f1fc spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T23:10:32Z" message: 'load-balancer-api-external: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.504875ms message: 'load-balancer-api-external: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:40:32Z" - latency: 7.985093ms message: 'load-balancer-api-external: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:40:31Z" - latency: 4.989023ms message: 'load-balancer-api-external: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:32Z" - latency: 9.825459ms message: 'load-balancer-api-external: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:39:31Z" - latency: 4.677697ms message: 'load-balancer-api-external: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:32Z" - latency: 9.139487ms message: 'load-balancer-api-external: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:38:31Z" - latency: 3.307869ms message: 'load-balancer-api-external: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:32Z" - latency: 10.400375ms message: 'load-balancer-api-external: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:37:31Z" - latency: 5.140605ms message: 'load-balancer-api-external: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:32Z" - latency: 8.496825ms message: 'load-balancer-api-external: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:36:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "61823" uid: e0ae0b93-5422-4a13-b0a8-a7d98d9ad6e8 spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T23:10:32Z" message: 'load-balancer-api-internal: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.226ms message: 'load-balancer-api-internal: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:40:32Z" - latency: 8.04081ms message: 'load-balancer-api-internal: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:40:31Z" - latency: 4.905873ms message: 'load-balancer-api-internal: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:32Z" - latency: 9.966738ms message: 'load-balancer-api-internal: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:39:31Z" - latency: 3.582525ms message: 'load-balancer-api-internal: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:32Z" - latency: 9.170105ms message: 'load-balancer-api-internal: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:38:31Z" - latency: 3.334384ms message: 'load-balancer-api-internal: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:32Z" - latency: 10.36273ms message: 'load-balancer-api-internal: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:37:31Z" - latency: 5.123599ms message: 'load-balancer-api-internal: tcp connection to aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:32Z" - latency: 8.545929ms message: 'load-balancer-api-internal: resolved host name aaa05d99fa5014ca3bb9d978355ac3da-6b7eb1bd7d8a8a2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T23:36:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-network-check-target-ip-10-0-129-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "60626" uid: ea1b694a-9475-4690-bc2f-c3fe645ca622 spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T23:11:31Z" message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.476µs message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:31Z" - latency: 931.895µs message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:31Z" - latency: 1.010657ms message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:31Z" - latency: 858.633µs message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:31Z" - latency: 1.506459ms message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:35:31Z" - latency: 893.908µs message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:34:31Z" - latency: 1.982748ms message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:33:31Z" - latency: 1.057288ms message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:32:31Z" - latency: 885.778µs message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:31:31Z" - latency: 938.161µs message: 'network-check-target-ip-10-0-129-219: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-network-check-target-ip-10-0-130-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "60627" uid: d375f36f-ad62-4a88-ba45-2092ddf4ba2d spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T23:11:32Z" message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.137814ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:31Z" - latency: 2.241281ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:31Z" - latency: 2.015172ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:31Z" - latency: 2.058004ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:31Z" - latency: 2.209389ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:35:31Z" - latency: 1.56246ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:34:31Z" - latency: 2.385365ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:33:31Z" - latency: 2.621429ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:32:31Z" - latency: 1.848049ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:31:31Z" - latency: 2.146775ms message: 'network-check-target-ip-10-0-130-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-network-check-target-ip-10-0-135-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "60628" uid: 9ee6e514-13b5-4193-a982-602de6981638 spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T23:11:32Z" message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.487792ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:31Z" - latency: 2.278466ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:31Z" - latency: 2.203557ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:31Z" - latency: 2.432549ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:31Z" - latency: 2.222414ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:35:31Z" - latency: 1.809518ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:34:31Z" - latency: 2.423633ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:33:31Z" - latency: 2.646236ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:32:31Z" - latency: 2.17933ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:31:31Z" - latency: 2.314715ms message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T23:04:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-219-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-219.ec2.internal uid: 6f01a3d1-8371-49b2-89d2-f92f91755ba9 resourceVersion: "61821" uid: 6d70673a-b748-4051-835a-b8ec547d149b spec: sourcePod: network-check-source-6f8b768455-hnrpn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T23:10:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.211µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:40:31Z" - latency: 1.82666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T23:40:31Z" - latency: 1.168303ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:39:32Z" - latency: 2.122075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T23:39:31Z" - latency: 891.955µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:38:32Z" - latency: 2.871285ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T23:38:31Z" - latency: 1.007028ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:37:32Z" - latency: 1.774163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T23:37:31Z" - latency: 1.021007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T23:36:32Z" - latency: 1.93139ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T23:36:31Z" kind: List metadata: resourceVersion: ""