apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "40099" uid: bbc4fd74-ef51-422e-947c-db6c9dad7d76 spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T14:11:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.015818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:00:44Z" - latency: 709.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:59:44Z" - latency: 1.08974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 692.076µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 740.681µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 847.472µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 838.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 768.894µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:53:44Z" - latency: 770.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:52:44Z" - latency: 926.186µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:51:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "38995" uid: ee31eccc-ac5f-46f9-81f1-9c8d567ac123 spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:10:44Z" message: 'load-balancer-api-external: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.710363ms message: 'load-balancer-api-external: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 9.850825ms message: 'load-balancer-api-external: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:58:44Z" - latency: 4.356187ms message: 'load-balancer-api-external: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 6.32648ms message: 'load-balancer-api-external: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:57:44Z" - latency: 3.223489ms message: 'load-balancer-api-external: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 8.300432ms message: 'load-balancer-api-external: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:56:44Z" - latency: 3.492337ms message: 'load-balancer-api-external: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 7.159005ms message: 'load-balancer-api-external: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:55:44Z" - latency: 4.965956ms message: 'load-balancer-api-external: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 6.075273ms message: 'load-balancer-api-external: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:54:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "38994" uid: 8925ec18-694e-4b88-bab2-24e9c7326c72 spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:10:44Z" message: 'load-balancer-api-internal: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.735026ms message: 'load-balancer-api-internal: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 9.899613ms message: 'load-balancer-api-internal: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:58:44Z" - latency: 4.323055ms message: 'load-balancer-api-internal: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 6.383934ms message: 'load-balancer-api-internal: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:57:44Z" - latency: 4.002755ms message: 'load-balancer-api-internal: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 8.368451ms message: 'load-balancer-api-internal: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:56:44Z" - latency: 4.217766ms message: 'load-balancer-api-internal: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 7.20479ms message: 'load-balancer-api-internal: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:55:44Z" - latency: 4.9512ms message: 'load-balancer-api-internal: tcp connection to ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 6.131965ms message: 'load-balancer-api-internal: resolved host name ad943c13dc4d443c7bef721ff7333d0d-c40f5b9fd25ac32f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:54:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-128-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "40097" uid: 477a904e-8f79-480f-b575-49d81c5285f6 spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:11:44Z" message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.952931ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:00:44Z" - latency: 1.716989ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:59:44Z" - latency: 2.116289ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 2.055346ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 1.815661ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 1.7552ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 2.030188ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 1.974271ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:53:44Z" - latency: 2.028334ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:52:44Z" - latency: 1.909777ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:51:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-139-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "40096" uid: 2b9602ac-f22c-4817-9dcd-12f0fbdd96ff spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:11:44Z" message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.734562ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:00:44Z" - latency: 1.853998ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:59:44Z" - latency: 1.939068ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 1.690483ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 1.747366ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 1.754419ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 1.825874ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 1.793129ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:53:44Z" - latency: 1.951482ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:52:44Z" - latency: 1.792476ms message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:51:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-142-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "40098" uid: 42134d6a-aa16-42ea-a8ad-94c0e9aa219f spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:11:44Z" message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 759.088µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:00:44Z" - latency: 1.152377ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:59:44Z" - latency: 934.746µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 682.113µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 675.812µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 1.059383ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 636.399µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 639.18µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:53:44Z" - latency: 1.438101ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:52:44Z" - latency: 733.622µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:51:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: ab89ad2e-d2a6-4606-b2fa-d0b8c1498949 resourceVersion: "38993" uid: 480b79d7-2b00-40bd-b09d-534927ad369c spec: sourcePod: network-check-source-7b678d77c7-7t4bf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T14:10:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:58:44Z" - latency: 1.636912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:58:44Z" - latency: 868.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:57:44Z" - latency: 1.635051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:57:44Z" - latency: 771.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:56:44Z" - latency: 1.741294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:56:44Z" - latency: 837.454µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:55:44Z" - latency: 1.696653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:55:44Z" - latency: 773.553µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:54:44Z" - latency: 1.515344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:54:44Z" kind: List metadata: resourceVersion: ""