apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "44341" uid: fd19c6a7-56a2-4d0d-a1b1-f63af7f5ed79 spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T17:22:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.058891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 1.41644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 1.232982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 910.116µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:04Z" - latency: 1.106092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:04Z" - latency: 1.205391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:38:04Z" - latency: 1.141758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:37:04Z" - latency: 872.135µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:36:04Z" - latency: 1.355924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:35:04Z" - latency: 927.788µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:34:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "46361" uid: 74ffae21-c18f-42e1-8709-ffd9b22dc233 spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:21:04Z" message: 'load-balancer-api-external: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.705517ms message: 'load-balancer-api-external: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:04Z" - latency: 6.37394ms message: 'load-balancer-api-external: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:45:04Z" - latency: 4.675965ms message: 'load-balancer-api-external: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:04Z" - latency: 6.665771ms message: 'load-balancer-api-external: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:44:04Z" - latency: 4.00494ms message: 'load-balancer-api-external: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 7.113874ms message: 'load-balancer-api-external: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:43:04Z" - latency: 3.669005ms message: 'load-balancer-api-external: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 6.62582ms message: 'load-balancer-api-external: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:42:04Z" - latency: 4.919558ms message: 'load-balancer-api-external: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 6.600055ms message: 'load-balancer-api-external: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:41:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "46362" uid: 198f99f7-6ece-4c45-b4e6-b4d609b70110 spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:21:04Z" message: 'load-balancer-api-internal: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.732404ms message: 'load-balancer-api-internal: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:04Z" - latency: 6.345729ms message: 'load-balancer-api-internal: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:45:04Z" - latency: 4.68103ms message: 'load-balancer-api-internal: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:04Z" - latency: 6.600957ms message: 'load-balancer-api-internal: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:44:04Z" - latency: 3.836217ms message: 'load-balancer-api-internal: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 7.027778ms message: 'load-balancer-api-internal: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:43:04Z" - latency: 5.46493ms message: 'load-balancer-api-internal: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 6.529456ms message: 'load-balancer-api-internal: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:42:04Z" - latency: 5.257021ms message: 'load-balancer-api-internal: tcp connection to a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 6.581091ms message: 'load-balancer-api-internal: resolved host name a6c4b69fa912a4dafa6254d010c17fad-122d68caf610e080.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:41:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-network-check-target-ip-10-0-130-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "44338" uid: 21a51d2c-6788-46d3-94db-033b6a1faacd spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:22:04Z" message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 739.223µs message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 693.759µs message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 1.21155ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 1.189997ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:04Z" - latency: 824.521µs message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:04Z" - latency: 788.038µs message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:38:04Z" - latency: 872.741µs message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:37:04Z" - latency: 1.308544ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:36:04Z" - latency: 1.170804ms message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:35:04Z" - latency: 744.822µs message: 'network-check-target-ip-10-0-130-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:34:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-network-check-target-ip-10-0-131-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "44340" uid: 02fc8cc6-ff9d-427c-b195-dae8bb93fec3 spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:22:04Z" message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.391446ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 2.965578ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 1.980463ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 1.921722ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:04Z" - latency: 2.282871ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:04Z" - latency: 2.464116ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:38:04Z" - latency: 2.136749ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:37:04Z" - latency: 2.196408ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:36:04Z" - latency: 2.198593ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:35:04Z" - latency: 2.168885ms message: 'network-check-target-ip-10-0-131-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:34:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-network-check-target-ip-10-0-141-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "44339" uid: 72e88edd-6ba5-4e6c-9a10-b86e00952a76 spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:22:04Z" message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.272808ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 2.237647ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 2.203717ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 2.397625ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:04Z" - latency: 2.202646ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:04Z" - latency: 2.376327ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:38:04Z" - latency: 2.19491ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:37:04Z" - latency: 2.422791ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:36:04Z" - latency: 2.597316ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:35:04Z" - latency: 2.001777ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:34:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:15:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-46-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-46.ec2.internal uid: d2e9d8d9-6cc6-4d0d-bf61-9f3569a40653 resourceVersion: "46360" uid: ac6676b8-0391-404f-a278-2f7c1a769124 spec: sourcePod: network-check-source-7f44b6dd87-r8pdq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T17:21:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.259µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:04Z" - latency: 1.764466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:45:04Z" - latency: 897.665µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:04Z" - latency: 1.537045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:44:04Z" - latency: 1.011287ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:04Z" - latency: 1.770589ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:43:04Z" - latency: 1.090018ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:04Z" - latency: 1.787386ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:42:04Z" - latency: 1.248882ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:04Z" - latency: 1.912352ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:41:04Z" kind: List metadata: resourceVersion: ""