apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31364" uid: 2d9b4dbe-378b-4b65-969c-8b58f33fbcb3 spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T19:33:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.685µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 885.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 956.32µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 1.499682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 1.074485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 896.565µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:20Z" - latency: 961.135µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:20Z" - latency: 1.730499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:20Z" - latency: 1.010605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:20Z" - latency: 988.613µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31365" uid: 67e1e423-dd03-497a-a0fd-7a306fcb0fff spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T19:32:20Z" message: 'load-balancer-api-external: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.198392ms message: 'load-balancer-api-external: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 6.927729ms message: 'load-balancer-api-external: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:08:20Z" - latency: 4.763785ms message: 'load-balancer-api-external: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 7.935055ms message: 'load-balancer-api-external: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:07:20Z" - latency: 3.992367ms message: 'load-balancer-api-external: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 8.407709ms message: 'load-balancer-api-external: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:06:20Z" - latency: 4.432974ms message: 'load-balancer-api-external: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 7.507896ms message: 'load-balancer-api-external: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:05:20Z" - latency: 3.706207ms message: 'load-balancer-api-external: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 6.785603ms message: 'load-balancer-api-external: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:04:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31366" uid: 55e0ba50-5623-4404-bebc-f8cb0ae7b96f spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T19:32:20Z" message: 'load-balancer-api-internal: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.181493ms message: 'load-balancer-api-internal: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 6.899929ms message: 'load-balancer-api-internal: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:08:20Z" - latency: 4.771268ms message: 'load-balancer-api-internal: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 7.853895ms message: 'load-balancer-api-internal: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:07:20Z" - latency: 3.987518ms message: 'load-balancer-api-internal: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 8.376204ms message: 'load-balancer-api-internal: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:06:20Z" - latency: 3.795381ms message: 'load-balancer-api-internal: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 7.605477ms message: 'load-balancer-api-internal: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:05:20Z" - latency: 4.273776ms message: 'load-balancer-api-internal: tcp connection to a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 6.842661ms message: 'load-balancer-api-internal: resolved host name a75a486813cee4842a5afcd860cec9be-f537167de743c855.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:04:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-network-check-target-ip-10-0-129-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31362" uid: 2589c249-ace8-4e6a-8855-81ffae4b3838 spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:33:20Z" message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186639ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 1.948028ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 2.296521ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 2.281837ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 2.174447ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 2.027209ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:20Z" - latency: 2.291737ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:20Z" - latency: 2.616396ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:20Z" - latency: 2.193092ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:20Z" - latency: 2.185966ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-network-check-target-ip-10-0-129-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31360" uid: 71ce2a85-8719-4760-b4b5-74e84c663913 spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:33:20Z" message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 803.26µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 809.425µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 864.809µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 919.671µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 859.355µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 1.280505ms message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:20Z" - latency: 775.066µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:20Z" - latency: 819.24µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:20Z" - latency: 907.104µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:20Z" - latency: 928.683µs message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-network-check-target-ip-10-0-143-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31361" uid: 10dddd9e-d3f9-4b60-9df9-0dabebab6d99 spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:33:20Z" message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.05959ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 1.881903ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 1.64803ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 1.942601ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 1.886238ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 1.967775ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:20Z" - latency: 1.769931ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:20Z" - latency: 1.935214ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:20Z" - latency: 1.829811ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:20Z" - latency: 1.67973ms message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:26:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-175.ec2.internal uid: 9669025e-102a-4637-a826-004c1e37fdba resourceVersion: "31363" uid: 3b837486-bbc7-4484-83a1-d91bbd81c212 spec: sourcePod: network-check-source-8894fc9bd-v2f7q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T19:32:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.746µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:08:20Z" - latency: 1.689376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:08:20Z" - latency: 988.879µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:07:20Z" - latency: 1.960208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:07:20Z" - latency: 771.477µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:06:20Z" - latency: 1.936843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:06:20Z" - latency: 740.146µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:05:20Z" - latency: 2.015553ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:05:20Z" - latency: 880.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:04:20Z" - latency: 1.639203ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:04:20Z" kind: List metadata: resourceVersion: ""