apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "54017" uid: db2e8b8d-19fa-48f1-bfc3-ec1fc15b84c9 spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T18:05:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.915µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 1.3181ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 1.118281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 1.051621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 1.351486ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:29:32Z" - latency: 1.358252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:28:32Z" - latency: 1.118203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:27:32Z" - latency: 1.203928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:26:32Z" - latency: 1.29968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:25:32Z" - latency: 1.159903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:24:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "55074" uid: 451a80a7-a90d-4acf-bb98-2b8e72e6c85f spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T18:04:32Z" message: 'load-balancer-api-external: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.265375ms message: 'load-balancer-api-external: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:34:32Z" - latency: 8.32681ms message: 'load-balancer-api-external: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:34:32Z" - latency: 4.977667ms message: 'load-balancer-api-external: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 8.490777ms message: 'load-balancer-api-external: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:33:32Z" - latency: 3.190068ms message: 'load-balancer-api-external: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 8.307998ms message: 'load-balancer-api-external: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:32:32Z" - latency: 5.573584ms message: 'load-balancer-api-external: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 8.447202ms message: 'load-balancer-api-external: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:31:32Z" - latency: 4.365053ms message: 'load-balancer-api-external: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 7.829523ms message: 'load-balancer-api-external: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:30:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "55073" uid: b709c5f6-76e1-4d0d-b46c-5a5720d19eee spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T18:04:32Z" message: 'load-balancer-api-internal: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.89373ms message: 'load-balancer-api-internal: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:34:32Z" - latency: 8.253403ms message: 'load-balancer-api-internal: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:34:32Z" - latency: 4.234508ms message: 'load-balancer-api-internal: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 8.497691ms message: 'load-balancer-api-internal: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:33:32Z" - latency: 3.2131ms message: 'load-balancer-api-internal: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 8.283661ms message: 'load-balancer-api-internal: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:32:32Z" - latency: 5.596818ms message: 'load-balancer-api-internal: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 8.473081ms message: 'load-balancer-api-internal: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:31:32Z" - latency: 5.094517ms message: 'load-balancer-api-internal: tcp connection to ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 7.902985ms message: 'load-balancer-api-internal: resolved host name ad162c2ee72814f2c97c906ea8481af9-ffc6a908ca164519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:30:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-134-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "54018" uid: 1e7ea8e0-0a09-44a3-a067-550518bddc57 spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:05:32Z" message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 690.976µs message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 1.992798ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 1.866732ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 2.03682ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 2.025262ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:29:32Z" - latency: 1.966219ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:28:32Z" - latency: 588.199µs message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:27:32Z" - latency: 720.126µs message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:26:32Z" - latency: 2.302668ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:25:32Z" - latency: 2.159196ms message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:24:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-136-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "54019" uid: 6d3fc612-9afd-4b06-b4bf-328661b51b03 spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:05:32Z" message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.931725ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 1.55131ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 621.71µs message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 1.67616ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 1.971351ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:29:32Z" - latency: 1.96909ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:28:32Z" - latency: 1.922394ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:27:32Z" - latency: 1.872816ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:26:32Z" - latency: 596.23µs message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:25:32Z" - latency: 654.168µs message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:24:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-137-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "54021" uid: b32dda6d-ef32-4225-bf48-88bf7c6f9314 spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:05:32Z" message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 663.613µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 518.464µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 705.914µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 518.18µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 426.79µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:29:32Z" - latency: 598.609µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:28:32Z" - latency: 727.819µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:27:32Z" - latency: 698.293µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:26:32Z" - latency: 740.272µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:25:32Z" - latency: 795.39µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:24:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:58:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: ad1ffee0-71b7-4943-acff-6e5dd3427d07 resourceVersion: "55071" uid: ba4d5553-c41f-46e2-955e-dfbbef29fc7a spec: sourcePod: network-check-source-989f8b8dc-tz7ng targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T18:04:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:34:32Z" - latency: 1.731635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:34:32Z" - latency: 2.278443ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:33:32Z" - latency: 1.569509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:33:32Z" - latency: 1.025705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:32:32Z" - latency: 1.692537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:32:32Z" - latency: 2.188934ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:31:32Z" - latency: 1.714813ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:31:32Z" - latency: 983.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:30:32Z" - latency: 1.579805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:30:32Z" kind: List metadata: resourceVersion: ""