apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "44730" uid: 6d130ca3-a4f9-4dda-8df3-8f2d64614ae2 spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T19:20:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 686.553µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 1.696324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 797.064µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 1.031683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:38:53Z" - latency: 902.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:37:53Z" - latency: 1.66606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:36:53Z" - latency: 853.543µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:35:53Z" - latency: 1.908394ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:34:53Z" - latency: 1.632533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:33:53Z" - latency: 834.604µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "46750" uid: ec8abfc3-28b8-40d7-91e0-b20f190ab71f spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T19:19:53Z" message: 'load-balancer-api-external: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.292051ms message: 'load-balancer-api-external: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:43:53Z" - latency: 6.693152ms message: 'load-balancer-api-external: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:43:53Z" - latency: 3.028037ms message: 'load-balancer-api-external: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:42:53Z" - latency: 7.456151ms message: 'load-balancer-api-external: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:42:53Z" - latency: 3.752359ms message: 'load-balancer-api-external: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 8.117496ms message: 'load-balancer-api-external: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:41:53Z" - latency: 4.910895ms message: 'load-balancer-api-external: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 8.761927ms message: 'load-balancer-api-external: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:40:53Z" - latency: 5.843497ms message: 'load-balancer-api-external: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 8.008648ms message: 'load-balancer-api-external: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:39:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "46749" uid: 028d1278-f47d-4f5a-bde2-4507dd536cad spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T19:19:53Z" message: 'load-balancer-api-internal: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.644529ms message: 'load-balancer-api-internal: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:43:53Z" - latency: 6.73282ms message: 'load-balancer-api-internal: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:43:53Z" - latency: 3.138826ms message: 'load-balancer-api-internal: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:42:53Z" - latency: 7.378662ms message: 'load-balancer-api-internal: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:42:53Z" - latency: 4.360753ms message: 'load-balancer-api-internal: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 8.165567ms message: 'load-balancer-api-internal: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:41:53Z" - latency: 4.144471ms message: 'load-balancer-api-internal: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 8.788314ms message: 'load-balancer-api-internal: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:40:53Z" - latency: 5.800556ms message: 'load-balancer-api-internal: tcp connection to a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 8.200613ms message: 'load-balancer-api-internal: resolved host name a4482560531464bafb24cd0657abd893-a4fc7915b724f474.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T19:39:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-network-check-target-ip-10-0-134-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "44729" uid: 27debc58-6a7a-4078-a167-5bc2e2e16b22 spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T19:20:53Z" message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.431012ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 2.282889ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 2.097298ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 2.106086ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:38:53Z" - latency: 2.269336ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:37:53Z" - latency: 2.031357ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:36:53Z" - latency: 1.975727ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:35:53Z" - latency: 2.445811ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:34:53Z" - latency: 2.823118ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:33:53Z" - latency: 1.870028ms message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-network-check-target-ip-10-0-136-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "44728" uid: 8b55cad2-d51e-4764-b91d-99b86de416eb spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T19:20:53Z" message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.14372ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 1.744011ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 1.817789ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 1.951324ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:38:53Z" - latency: 1.979422ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:37:53Z" - latency: 2.561127ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:36:53Z" - latency: 1.717655ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:35:53Z" - latency: 2.050256ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:34:53Z" - latency: 1.974851ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:33:53Z" - latency: 2.247922ms message: 'network-check-target-ip-10-0-136-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-network-check-target-ip-10-0-139-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "44727" uid: 8df9d7c0-c509-479c-9f47-5b669c75284d spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T19:20:53Z" message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.029µs message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 1.213997ms message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 1.449291ms message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 1.346616ms message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:38:53Z" - latency: 1.211017ms message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:37:53Z" - latency: 1.007539ms message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:36:53Z" - latency: 797.268µs message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:35:53Z" - latency: 1.46135ms message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:34:53Z" - latency: 959.212µs message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:33:53Z" - latency: 919.092µs message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T19:13:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-126-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-126.ec2.internal uid: 7edbf693-6fe7-40e5-a695-b655da4a966a resourceVersion: "46748" uid: 3eae4bf3-0f9d-4818-860d-824f3bcde6d1 spec: sourcePod: network-check-source-8894fc9bd-6tvvj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T19:19:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.20637ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:43:53Z" - latency: 1.849358ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:43:53Z" - latency: 1.08891ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:42:53Z" - latency: 1.728635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:42:53Z" - latency: 896.125µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:41:53Z" - latency: 1.753151ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:41:53Z" - latency: 897.941µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:40:53Z" - latency: 1.712894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:40:53Z" - latency: 887.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T19:39:53Z" - latency: 2.261235ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T19:39:53Z" kind: List metadata: resourceVersion: ""