apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "42345" uid: 8cacd441-7631-4891-bfe3-43755c8ed8b2 spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T11:40:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.008µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:36:04Z" - latency: 1.176296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:35:04Z" - latency: 983.23µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:34:04Z" - latency: 812.749µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 1.242055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 939.596µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 1.088789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 1.061581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 905.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:28:04Z" - latency: 1.096556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "40723" uid: 198d6a68-c81d-411e-9028-c0053b5d79cf spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:39:04Z" message: 'load-balancer-api-external: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.446144ms message: 'load-balancer-api-external: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 6.190045ms message: 'load-balancer-api-external: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:33:04Z" - latency: 5.021729ms message: 'load-balancer-api-external: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 8.252638ms message: 'load-balancer-api-external: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:32:04Z" - latency: 4.73803ms message: 'load-balancer-api-external: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 8.167131ms message: 'load-balancer-api-external: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:31:04Z" - latency: 4.489828ms message: 'load-balancer-api-external: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 11.523235ms message: 'load-balancer-api-external: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:30:04Z" - latency: 4.378887ms message: 'load-balancer-api-external: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 7.925646ms message: 'load-balancer-api-external: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:29:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "40724" uid: c80a571a-0ee6-4a47-92ab-17c86bbef9be spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:39:04Z" message: 'load-balancer-api-internal: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.466715ms message: 'load-balancer-api-internal: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 6.307157ms message: 'load-balancer-api-internal: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:33:04Z" - latency: 5.057383ms message: 'load-balancer-api-internal: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 8.210824ms message: 'load-balancer-api-internal: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:32:04Z" - latency: 4.713453ms message: 'load-balancer-api-internal: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 8.116566ms message: 'load-balancer-api-internal: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:31:04Z" - latency: 4.469734ms message: 'load-balancer-api-internal: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 11.389937ms message: 'load-balancer-api-internal: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:30:04Z" - latency: 3.966104ms message: 'load-balancer-api-internal: tcp connection to a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 7.955548ms message: 'load-balancer-api-internal: resolved host name a8e781707b60a41bea7e48f6cda7b819-7ecd150e44b1f52f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:29:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-133-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "42342" uid: 2a588835-82e9-4adc-90d0-d8e3c1193ea5 spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:40:04Z" message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 760.14µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:36:04Z" - latency: 799.312µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:35:04Z" - latency: 1.131619ms message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:34:04Z" - latency: 936.741µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 751.801µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 832.125µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 1.285568ms message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 787.5µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 1.379694ms message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:28:04Z" - latency: 1.105492ms message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-136-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "42344" uid: 857597b8-45b7-4861-9a80-6573fd6f5314 spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:40:04Z" message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.013029ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:36:04Z" - latency: 2.163952ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:35:04Z" - latency: 2.442031ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:34:04Z" - latency: 2.05492ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 1.856124ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 2.311647ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 2.273993ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 1.980493ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 2.014878ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:28:04Z" - latency: 2.007227ms message: 'network-check-target-ip-10-0-136-60: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-138-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "42343" uid: 699daad5-615a-4427-80ca-0369835a7649 spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:40:04Z" message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.917122ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:36:04Z" - latency: 2.062871ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:35:04Z" - latency: 2.084377ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:34:04Z" - latency: 1.899804ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 1.873867ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 2.094474ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 2.3263ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 2.036688ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 2.164574ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:28:04Z" - latency: 2.054684ms message: 'network-check-target-ip-10-0-138-207: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: 9e31c2aa-81c5-429b-be0d-89bb78b9f3d2 resourceVersion: "40721" uid: 4e036eda-f86d-447e-8891-6659d10fac4c spec: sourcePod: network-check-source-7f44b6dd87-vsp5c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T11:39:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004555ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:33:04Z" - latency: 1.636843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:33:04Z" - latency: 884.532µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:32:04Z" - latency: 1.788022ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:32:04Z" - latency: 826.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:31:04Z" - latency: 1.686527ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:31:04Z" - latency: 1.20327ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:30:04Z" - latency: 1.714616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:30:04Z" - latency: 1.092375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:29:04Z" - latency: 1.844432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:29:04Z" kind: List metadata: resourceVersion: ""