apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60491" uid: e70268ae-db9b-4763-831d-0443a8396325 spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T18:51:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 702.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 1.038281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 834.888µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 923.294µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 990.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 1.000887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:21:29Z" - latency: 791.988µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:20:29Z" - latency: 1.587177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:19:29Z" - latency: 817.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:18:29Z" - latency: 786.201µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60493" uid: e3c18316-3c3d-4b91-9697-e6a2d8b580bc spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:50:29Z" message: 'load-balancer-api-external: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.110399ms message: 'load-balancer-api-external: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 8.093368ms message: 'load-balancer-api-external: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:26:29Z" - latency: 3.824275ms message: 'load-balancer-api-external: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 6.741383ms message: 'load-balancer-api-external: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:25:29Z" - latency: 4.900969ms message: 'load-balancer-api-external: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 7.04121ms message: 'load-balancer-api-external: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:24:29Z" - latency: 5.305486ms message: 'load-balancer-api-external: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 7.008259ms message: 'load-balancer-api-external: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:23:29Z" - latency: 4.648553ms message: 'load-balancer-api-external: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 7.039803ms message: 'load-balancer-api-external: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:22:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60492" uid: 19fc91ee-8d08-413c-9f59-ef8d479d6824 spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:50:29Z" message: 'load-balancer-api-internal: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.077645ms message: 'load-balancer-api-internal: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 8.072804ms message: 'load-balancer-api-internal: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:26:29Z" - latency: 3.908138ms message: 'load-balancer-api-internal: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 6.732618ms message: 'load-balancer-api-internal: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:25:29Z" - latency: 3.774113ms message: 'load-balancer-api-internal: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 7.05921ms message: 'load-balancer-api-internal: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:24:29Z" - latency: 4.748732ms message: 'load-balancer-api-internal: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 7.035455ms message: 'load-balancer-api-internal: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:23:29Z" - latency: 4.626165ms message: 'load-balancer-api-internal: tcp connection to a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 7.125346ms message: 'load-balancer-api-internal: resolved host name a41d847dc387b4d23a060f4b3e353db8-e2cab9d2faf482cc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T19:22:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-network-check-target-ip-10-0-129-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60488" uid: fab8d330-2500-44f2-ad3e-541737d621c0 spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:51:29Z" message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.656736ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 1.84799ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 2.16158ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 1.86756ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 1.888315ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 1.984545ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:21:29Z" - latency: 1.92602ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:20:29Z" - latency: 1.876891ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:19:29Z" - latency: 1.952777ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:18:29Z" - latency: 2.384719ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-network-check-target-ip-10-0-141-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60487" uid: faf7af29-b19b-477c-bfbd-ad5e92e85a02 spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:51:29Z" message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 694.047µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 798.876µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 926.531µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 865.878µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 825.008µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 1.139067ms message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:21:29Z" - latency: 954.1µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:20:29Z" - latency: 814.806µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:19:29Z" - latency: 941.356µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:18:29Z" - latency: 721.6µs message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-network-check-target-ip-10-0-143-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60489" uid: 5df6762e-7fca-4926-ab6a-a9274b767ddf spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:51:29Z" message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.900809ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 1.966111ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 1.945896ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 2.236115ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 1.721814ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 2.106585ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:21:29Z" - latency: 1.869828ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:20:29Z" - latency: 1.999839ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:19:29Z" - latency: 1.779712ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:18:29Z" - latency: 1.936813ms message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:44:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-47.ec2.internal uid: 3ac02d17-93b3-46cf-8604-6061209a81ca resourceVersion: "60490" uid: f7bf5543-3453-439d-9d95-af7c0ccf188d spec: sourcePod: network-check-source-869dcfcdcd-r86dw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T18:50:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.988µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:26:29Z" - latency: 2.028526ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:26:29Z" - latency: 1.088745ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:25:29Z" - latency: 1.721801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:25:29Z" - latency: 962.304µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:24:29Z" - latency: 1.735616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:24:29Z" - latency: 806.882µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:23:29Z" - latency: 1.822788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:23:29Z" - latency: 830.544µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T19:22:29Z" - latency: 1.633455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T19:22:29Z" kind: List metadata: resourceVersion: ""