apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "68203" uid: 38e81900-5b66-48c9-b090-7d986be7307e spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T18:56:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.64901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 1.020634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 1.271922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 1.310242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 1.243365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:20:07Z" - latency: 921.162µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:19:07Z" - latency: 1.367096ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:18:07Z" - latency: 1.280473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:17:07Z" - latency: 1.336799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:16:07Z" - latency: 1.067224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:15:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "69407" uid: d1895a29-acc3-4f39-8fff-cb6477b4ddfe spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:55:07Z" message: 'load-balancer-api-external: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.2376ms message: 'load-balancer-api-external: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:07Z" - latency: 6.855863ms message: 'load-balancer-api-external: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:25:07Z" - latency: 8.709669ms message: 'load-balancer-api-external: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 6.613201ms message: 'load-balancer-api-external: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:24:07Z" - latency: 4.02781ms message: 'load-balancer-api-external: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 7.371828ms message: 'load-balancer-api-external: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:23:07Z" - latency: 6.051143ms message: 'load-balancer-api-external: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 7.31736ms message: 'load-balancer-api-external: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:22:07Z" - latency: 23.536941ms message: 'load-balancer-api-external: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 7.520488ms message: 'load-balancer-api-external: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:21:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "69408" uid: 530f4287-7a3b-4add-b7be-3ae1b16b4b61 spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:55:07Z" message: 'load-balancer-api-internal: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.234328ms message: 'load-balancer-api-internal: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:07Z" - latency: 6.830651ms message: 'load-balancer-api-internal: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:25:07Z" - latency: 4.12319ms message: 'load-balancer-api-internal: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 6.5865ms message: 'load-balancer-api-internal: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:24:07Z" - latency: 4.280061ms message: 'load-balancer-api-internal: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 7.34502ms message: 'load-balancer-api-internal: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:23:07Z" - latency: 7.276109ms message: 'load-balancer-api-internal: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 7.262291ms message: 'load-balancer-api-internal: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:22:07Z" - latency: 23.546669ms message: 'load-balancer-api-internal: tcp connection to a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 7.486505ms message: 'load-balancer-api-internal: resolved host name a90759423049c4d1487f8aa38e62b1f4-4c68dbe07c38b58f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:21:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-network-check-target-ip-10-0-134-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "68198" uid: 82181f4c-3bec-4eed-bdac-fb058112b9ff spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:56:07Z" message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140594ms message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 963.865µs message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 904.349µs message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 1.827972ms message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 993.258µs message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:20:07Z" - latency: 1.00179ms message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:19:07Z" - latency: 1.065848ms message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:18:07Z" - latency: 938.276µs message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:17:07Z" - latency: 935.808µs message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:16:07Z" - latency: 1.33982ms message: 'network-check-target-ip-10-0-134-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:15:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-network-check-target-ip-10-0-138-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "68202" uid: 5a797287-abe7-4978-aa1c-6d8a0edd252c spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:56:07Z" message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.895341ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 2.006169ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 1.888895ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 2.147055ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 2.136069ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:20:07Z" - latency: 1.867497ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:19:07Z" - latency: 2.316548ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:18:07Z" - latency: 1.959553ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:17:07Z" - latency: 2.046503ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:16:07Z" - latency: 2.238789ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:15:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-network-check-target-ip-10-0-141-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "68199" uid: 1fb7c182-9b62-4bcf-bc13-239a8163e402 spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:56:07Z" message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.39636ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 2.124543ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 2.205975ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 2.310508ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 2.390167ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:20:07Z" - latency: 1.948813ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:19:07Z" - latency: 2.542978ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:18:07Z" - latency: 2.399259ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:17:07Z" - latency: 2.318734ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:16:07Z" - latency: 2.112443ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:15:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:49:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-234.ec2.internal uid: c414582a-489e-4d3f-bc1d-de6459c8100b resourceVersion: "69406" uid: 3108fa72-9fc3-47fc-a137-a3706fee97d2 spec: sourcePod: network-check-source-6f8b768455-gwwbr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T18:55:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.92µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:25:07Z" - latency: 1.910247ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:25:07Z" - latency: 1.32609ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:24:07Z" - latency: 1.801257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:24:07Z" - latency: 1.005468ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:23:07Z" - latency: 2.448777ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:23:07Z" - latency: 1.13591ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:22:07Z" - latency: 1.771469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:22:07Z" - latency: 912.811µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:21:07Z" - latency: 2.432281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:21:07Z" kind: List metadata: resourceVersion: ""