apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "23881" uid: eb1f320a-6e01-4650-bd35-cdae1c9db4e7 spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T22:41:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.009µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:48:13Z" - latency: 1.003484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:13Z" - latency: 1.087605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 1.055803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 1.403402ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 932.183µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 861.116µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 1.050628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:13Z" - latency: 1.055361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:13Z" - latency: 1.075704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "22803" uid: 41e937dd-d7a7-410d-b28a-853d009d0912 spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T22:40:13Z" message: 'load-balancer-api-external: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.039174ms message: 'load-balancer-api-external: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 5.87237ms message: 'load-balancer-api-external: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:46:13Z" - latency: 4.391155ms message: 'load-balancer-api-external: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 6.786513ms message: 'load-balancer-api-external: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:45:13Z" - latency: 4.932311ms message: 'load-balancer-api-external: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 6.246988ms message: 'load-balancer-api-external: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:44:13Z" - latency: 4.704457ms message: 'load-balancer-api-external: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 6.508823ms message: 'load-balancer-api-external: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:43:13Z" - latency: 4.972316ms message: 'load-balancer-api-external: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 6.261661ms message: 'load-balancer-api-external: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:42:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "22802" uid: daaee1a1-99ab-4a00-bb4d-4e5f0400bb9f spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T22:40:13Z" message: 'load-balancer-api-internal: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.215987ms message: 'load-balancer-api-internal: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 5.801425ms message: 'load-balancer-api-internal: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:46:13Z" - latency: 4.219246ms message: 'load-balancer-api-internal: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 6.727786ms message: 'load-balancer-api-internal: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:45:13Z" - latency: 4.923428ms message: 'load-balancer-api-internal: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 6.333774ms message: 'load-balancer-api-internal: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:44:13Z" - latency: 4.658642ms message: 'load-balancer-api-internal: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 6.551679ms message: 'load-balancer-api-internal: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:43:13Z" - latency: 4.055528ms message: 'load-balancer-api-internal: tcp connection to a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 6.210275ms message: 'load-balancer-api-internal: resolved host name a16c964a8ccb44254bb5bcfd1b743328-953989c56ee87df4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:42:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-network-check-target-ip-10-0-129-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "23878" uid: 30df4062-7c63-4d01-9212-f0e6f28a8757 spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:41:13Z" message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 722.03µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:48:13Z" - latency: 860.627µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:13Z" - latency: 756.11µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 1.204948ms message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 818.682µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 1.325065ms message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 1.16258ms message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 848.569µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:13Z" - latency: 791.911µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:13Z" - latency: 870.002µs message: 'network-check-target-ip-10-0-129-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-network-check-target-ip-10-0-133-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "23880" uid: a4b7c08d-892e-40b2-8032-7202e6eaf68c spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:41:13Z" message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.043567ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:48:13Z" - latency: 2.094061ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:13Z" - latency: 1.85352ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 1.895008ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 2.048281ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 2.072912ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 1.957241ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 1.966761ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:13Z" - latency: 2.131634ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:13Z" - latency: 1.97883ms message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-network-check-target-ip-10-0-134-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "23879" uid: 52ca68cd-42c2-4841-adf0-ff01aae90c8e spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:41:13Z" message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.059614ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:48:13Z" - latency: 1.857696ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:13Z" - latency: 1.91965ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 1.968376ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 1.962872ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 1.85718ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 1.904424ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 1.94905ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:13Z" - latency: 2.019164ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:13Z" - latency: 1.908579ms message: 'network-check-target-ip-10-0-134-101: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-176.ec2.internal uid: 543c2bd4-d9c2-4502-ba33-f8d866bee664 resourceVersion: "22801" uid: b52222b1-6cfb-4792-bd89-09f51160ddeb spec: sourcePod: network-check-source-8894fc9bd-pwmng targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T22:40:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.102795ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:13Z" - latency: 1.570393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:46:13Z" - latency: 943.237µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:13Z" - latency: 1.845937ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:45:13Z" - latency: 850.915µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:13Z" - latency: 2.250346ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:44:13Z" - latency: 795.114µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:13Z" - latency: 1.921142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:43:13Z" - latency: 890.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:13Z" - latency: 1.828413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:42:13Z" kind: List metadata: resourceVersion: ""