apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "43882" uid: cd8bae74-f347-4f4a-8d0b-7a73a5215432 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T08:02:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.112µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 1.207582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 1.023737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 1.078782ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:20:59Z" - latency: 1.028065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:19:59Z" - latency: 820.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:18:59Z" - latency: 972.861µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:17:59Z" - latency: 1.033262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:16:59Z" - latency: 1.053193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:15:59Z" - latency: 1.333264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "46098" uid: a1ed4f0b-1f5b-4f91-9d00-40e772c3b031 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T08:01:59Z" message: 'load-balancer-api-external: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.85877ms message: 'load-balancer-api-external: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:25:59Z" - latency: 7.933671ms message: 'load-balancer-api-external: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:25:59Z" - latency: 4.493049ms message: 'load-balancer-api-external: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:24:59Z" - latency: 7.541337ms message: 'load-balancer-api-external: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:24:59Z" - latency: 5.193215ms message: 'load-balancer-api-external: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 7.906368ms message: 'load-balancer-api-external: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:23:59Z" - latency: 4.421639ms message: 'load-balancer-api-external: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 7.78302ms message: 'load-balancer-api-external: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:22:59Z" - latency: 3.840364ms message: 'load-balancer-api-external: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 8.265482ms message: 'load-balancer-api-external: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:21:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "46099" uid: 5e95895f-0cab-45b3-998b-41b29e742499 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T08:01:59Z" message: 'load-balancer-api-internal: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.851823ms message: 'load-balancer-api-internal: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:25:59Z" - latency: 7.828169ms message: 'load-balancer-api-internal: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:25:59Z" - latency: 3.835744ms message: 'load-balancer-api-internal: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:24:59Z" - latency: 7.425164ms message: 'load-balancer-api-internal: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:24:59Z" - latency: 5.148766ms message: 'load-balancer-api-internal: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 7.843834ms message: 'load-balancer-api-internal: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:23:59Z" - latency: 4.334566ms message: 'load-balancer-api-internal: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 7.698728ms message: 'load-balancer-api-internal: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:22:59Z" - latency: 3.851325ms message: 'load-balancer-api-internal: tcp connection to a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 8.230543ms message: 'load-balancer-api-internal: resolved host name a5e47b4022c804b5c934a7982b51e16a-8bcf9b91b4326da9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T08:21:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-network-check-target-ip-10-0-129-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "43879" uid: 41d7f46d-1c62-4b4b-af84-e798f457cc66 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T08:02:59Z" message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.62µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 858.874µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 810.584µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 812.998µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:20:59Z" - latency: 858.233µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:19:59Z" - latency: 852.506µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:18:59Z" - latency: 851.803µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:17:59Z" - latency: 808.941µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:16:59Z" - latency: 740.137µs message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:15:59Z" - latency: 1.472894ms message: 'network-check-target-ip-10-0-129-24: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-network-check-target-ip-10-0-133-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "43880" uid: 444f0ef2-ffb3-431f-a77a-0699c9c3d638 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T08:02:59Z" message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.082046ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 2.105995ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 2.410877ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 1.930511ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:20:59Z" - latency: 2.310009ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:19:59Z" - latency: 1.992454ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:18:59Z" - latency: 2.109315ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:17:59Z" - latency: 2.249371ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:16:59Z" - latency: 2.150749ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:15:59Z" - latency: 2.663394ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-network-check-target-ip-10-0-138-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "43881" uid: bed7e02f-7173-4cc9-8fb5-2e497a145c98 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T08:02:59Z" message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.321731ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 2.07795ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 2.105128ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 2.280087ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:20:59Z" - latency: 1.946907ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:19:59Z" - latency: 2.134197ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:18:59Z" - latency: 2.354013ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:17:59Z" - latency: 2.149342ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:16:59Z" - latency: 2.030797ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:15:59Z" - latency: 2.38442ms message: 'network-check-target-ip-10-0-138-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:55:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-24.ec2.internal uid: d90eb8d5-4e4a-4ccd-980d-8c8cb465bd72 resourceVersion: "46097" uid: cf9344ec-e72e-4812-8a76-de919226af76 spec: sourcePod: network-check-source-8894fc9bd-84g2g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T08:01:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 817.901µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:25:59Z" - latency: 1.82056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T08:25:59Z" - latency: 1.131527ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:24:59Z" - latency: 1.651539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T08:24:59Z" - latency: 808.862µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:23:59Z" - latency: 1.87978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T08:23:59Z" - latency: 766.849µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:22:59Z" - latency: 1.750095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T08:22:59Z" - latency: 1.063422ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T08:21:59Z" - latency: 1.734667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T08:21:59Z" kind: List metadata: resourceVersion: ""