apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "44503" uid: fb36354f-47c6-42e8-a997-57f0e50c28b2 spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T01:15:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.470084ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 1.076011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 1.12224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 1.490033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:33:00Z" - latency: 818.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:32:00Z" - latency: 1.188843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:31:00Z" - latency: 1.331513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:30:00Z" - latency: 1.214451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:29:00Z" - latency: 1.465419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:28:00Z" - latency: 858.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:27:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "46426" uid: c5f2f9d9-9216-4348-9854-79649cc84237 spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T01:14:00Z" message: 'load-balancer-api-external: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.822938ms message: 'load-balancer-api-external: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:38:00Z" - latency: 8.055211ms message: 'load-balancer-api-external: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:38:00Z" - latency: 3.451528ms message: 'load-balancer-api-external: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:37:00Z" - latency: 7.900655ms message: 'load-balancer-api-external: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:37:00Z" - latency: 4.281316ms message: 'load-balancer-api-external: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 8.243227ms message: 'load-balancer-api-external: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:36:00Z" - latency: 3.859214ms message: 'load-balancer-api-external: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 7.968613ms message: 'load-balancer-api-external: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:35:00Z" - latency: 3.535745ms message: 'load-balancer-api-external: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 7.99899ms message: 'load-balancer-api-external: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:34:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "46427" uid: 1bc47b4f-dce8-4328-b55c-aeadf1a790d9 spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T01:14:00Z" message: 'load-balancer-api-internal: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.435621ms message: 'load-balancer-api-internal: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:38:00Z" - latency: 7.997444ms message: 'load-balancer-api-internal: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:38:00Z" - latency: 3.255402ms message: 'load-balancer-api-internal: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:37:00Z" - latency: 7.840069ms message: 'load-balancer-api-internal: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:37:00Z" - latency: 10.180891ms message: 'load-balancer-api-internal: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 8.20913ms message: 'load-balancer-api-internal: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:36:00Z" - latency: 3.839966ms message: 'load-balancer-api-internal: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 8.019152ms message: 'load-balancer-api-internal: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:35:00Z" - latency: 3.24307ms message: 'load-balancer-api-internal: tcp connection to a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 8.076616ms message: 'load-balancer-api-internal: resolved host name a371c185780c54bd5b49927fa056fd86-88c455a7f4bca07c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T01:34:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-133-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "44502" uid: 6ccf97cb-d75c-489b-aef1-4683179404d2 spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T01:15:00Z" message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.176721ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 1.946511ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 2.260805ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 2.275063ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:33:00Z" - latency: 2.257591ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:32:00Z" - latency: 2.349144ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:31:00Z" - latency: 2.202219ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:30:00Z" - latency: 2.010712ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:29:00Z" - latency: 2.447517ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:28:00Z" - latency: 2.29203ms message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:27:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-134-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "44500" uid: 3d8fc9f2-b4e9-40df-9880-5ac4318ecb5f spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T01:15:00Z" message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.262282ms message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 980.028µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 818.938µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 970.346µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:33:00Z" - latency: 853.204µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:32:00Z" - latency: 804.031µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:31:00Z" - latency: 1.602058ms message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:30:00Z" - latency: 1.17799ms message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:29:00Z" - latency: 1.232944ms message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:28:00Z" - latency: 889.595µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:27:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-142-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "44501" uid: 8b0a1656-86ff-4330-88a3-c3f6a729e98a spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T01:15:00Z" message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.678523ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 1.904169ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 2.095893ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 2.019266ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:33:00Z" - latency: 2.333449ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:32:00Z" - latency: 2.014314ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:31:00Z" - latency: 2.184511ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:30:00Z" - latency: 2.445381ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:29:00Z" - latency: 2.34943ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:28:00Z" - latency: 1.957264ms message: 'network-check-target-ip-10-0-142-62: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:27:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T01:07:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 61396775-8bf2-44de-9f05-36b7818e7783 resourceVersion: "46425" uid: 561c5cd4-a00d-4426-aa39-0a1417761fa2 spec: sourcePod: network-check-source-7f44b6dd87-p2ns9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T01:14:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 716.673µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:38:00Z" - latency: 1.625437ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T01:38:00Z" - latency: 840.952µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:37:00Z" - latency: 1.580412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T01:37:00Z" - latency: 793.019µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:36:00Z" - latency: 2.068553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T01:36:00Z" - latency: 1.115078ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:35:00Z" - latency: 1.567368ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T01:35:00Z" - latency: 745.872µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T01:34:00Z" - latency: 1.731563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T01:34:00Z" kind: List metadata: resourceVersion: ""