apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "70076" uid: 1cf42e83-09e0-4a0c-bf52-a8eb333c44d4 spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T18:47:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:04Z" - latency: 1.470964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 934.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 1.014505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 1.148854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 893.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 1.158469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:04Z" - latency: 1.336396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:04Z" - latency: 1.172977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:21:04Z" - latency: 876.312µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:20:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "68931" uid: 35c06fe2-27c0-4d7b-b40f-9e621542adaa spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:46:04Z" message: 'load-balancer-api-external: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.905835ms message: 'load-balancer-api-external: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 7.916063ms message: 'load-balancer-api-external: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:28:04Z" - latency: 4.358708ms message: 'load-balancer-api-external: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 6.453987ms message: 'load-balancer-api-external: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:27:04Z" - latency: 5.457875ms message: 'load-balancer-api-external: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 7.238813ms message: 'load-balancer-api-external: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:26:04Z" - latency: 4.886127ms message: 'load-balancer-api-external: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 7.482023ms message: 'load-balancer-api-external: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:25:04Z" - latency: 4.101984ms message: 'load-balancer-api-external: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 7.645094ms message: 'load-balancer-api-external: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:24:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "68930" uid: 6358b966-9486-485f-b6cf-a9d9e59db2b4 spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:46:04Z" message: 'load-balancer-api-internal: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.692617ms message: 'load-balancer-api-internal: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 7.856744ms message: 'load-balancer-api-internal: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:28:04Z" - latency: 4.523084ms message: 'load-balancer-api-internal: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 6.509592ms message: 'load-balancer-api-internal: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:27:04Z" - latency: 5.511404ms message: 'load-balancer-api-internal: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 7.325494ms message: 'load-balancer-api-internal: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:26:04Z" - latency: 4.854664ms message: 'load-balancer-api-internal: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 7.546146ms message: 'load-balancer-api-internal: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:25:04Z" - latency: 3.9817ms message: 'load-balancer-api-internal: tcp connection to a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 7.595867ms message: 'load-balancer-api-internal: resolved host name a9c49fc8617c442c3a80398b218dec19-2579672b185d933e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:24:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-network-check-target-ip-10-0-132-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "70073" uid: 53a92dbe-4995-4d33-8778-25455afda980 spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:47:04Z" message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.328414ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:04Z" - latency: 1.017963ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 1.333777ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 1.33242ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 1.039763ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 1.040028ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 3.54078ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:04Z" - latency: 1.095274ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:04Z" - latency: 1.171502ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:21:04Z" - latency: 1.060044ms message: 'network-check-target-ip-10-0-132-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:20:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-network-check-target-ip-10-0-138-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "70074" uid: 2990edec-03de-4383-9b7b-3dc080cfa624 spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:47:04Z" message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.713492ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:04Z" - latency: 2.39418ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 2.423169ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 2.363143ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 2.427212ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 2.368665ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 6.034997ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:04Z" - latency: 2.348633ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:04Z" - latency: 2.46772ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:21:04Z" - latency: 2.396883ms message: 'network-check-target-ip-10-0-138-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:20:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-network-check-target-ip-10-0-138-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "70075" uid: 8534f5a2-e187-4b4d-b268-1486b9e8e038 spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:47:04Z" message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.79741ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:04Z" - latency: 2.300969ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 1.985008ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 2.176164ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 3.018573ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 1.840989ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 4.433796ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:04Z" - latency: 2.234605ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:04Z" - latency: 2.479958ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:21:04Z" - latency: 2.161692ms message: 'network-check-target-ip-10-0-138-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:20:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:40:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-220-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-220.ec2.internal uid: 1ad4c453-0044-42b4-bc8f-e645f61b21cb resourceVersion: "68928" uid: 274f444d-6bef-45e3-8acf-b6590be75e04 spec: sourcePod: network-check-source-7bc5b6bf85-rk78j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T18:46:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.00568ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:04Z" - latency: 2.256313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:28:04Z" - latency: 1.167957ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:04Z" - latency: 1.862529ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:27:04Z" - latency: 1.035213ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:04Z" - latency: 2.154637ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:26:04Z" - latency: 1.353668ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:04Z" - latency: 2.148828ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:25:04Z" - latency: 1.013509ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:04Z" - latency: 2.528425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:24:04Z" kind: List metadata: resourceVersion: ""