apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "54224" uid: 573ac247-4910-402f-b41b-f94def13f247 spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T12:59:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 933.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 769.898µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 999.232µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 1.153203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 676.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:23:40Z" - latency: 1.45928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:22:40Z" - latency: 1.43598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 1.141357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 870.027µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 1.09269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "55374" uid: 062e73b4-e56d-4d46-8a3f-62dfca1cdc5d spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T12:58:40Z" message: 'load-balancer-api-external: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.795265ms message: 'load-balancer-api-external: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:28:40Z" - latency: 8.101324ms message: 'load-balancer-api-external: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:28:40Z" - latency: 5.334683ms message: 'load-balancer-api-external: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 7.351356ms message: 'load-balancer-api-external: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:27:40Z" - latency: 4.283697ms message: 'load-balancer-api-external: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 7.172514ms message: 'load-balancer-api-external: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:26:40Z" - latency: 5.264222ms message: 'load-balancer-api-external: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 9.579813ms message: 'load-balancer-api-external: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:25:40Z" - latency: 3.438463ms message: 'load-balancer-api-external: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 6.932002ms message: 'load-balancer-api-external: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:24:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "55375" uid: bdc26174-d51d-4a91-9741-37a73d196eaa spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T12:58:40Z" message: 'load-balancer-api-internal: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.71111ms message: 'load-balancer-api-internal: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:28:40Z" - latency: 8.167845ms message: 'load-balancer-api-internal: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:28:40Z" - latency: 4.8471ms message: 'load-balancer-api-internal: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 7.332888ms message: 'load-balancer-api-internal: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:27:40Z" - latency: 5.250585ms message: 'load-balancer-api-internal: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 7.125583ms message: 'load-balancer-api-internal: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:26:40Z" - latency: 5.284105ms message: 'load-balancer-api-internal: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 9.550986ms message: 'load-balancer-api-internal: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:25:40Z" - latency: 3.401569ms message: 'load-balancer-api-internal: tcp connection to a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 6.862722ms message: 'load-balancer-api-internal: resolved host name a04760c5722a249958468edc4d9423a1-617aad913a3a2060.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:24:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-network-check-target-ip-10-0-131-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "54223" uid: 287907d3-7a13-4480-a817-46b54b3b4751 spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T12:59:40Z" message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.139514ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 1.975257ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 2.066522ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 2.096206ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 1.781287ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:23:40Z" - latency: 1.952984ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:22:40Z" - latency: 1.895245ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 1.861042ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 2.718007ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 2.034447ms message: 'network-check-target-ip-10-0-131-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-network-check-target-ip-10-0-135-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "54222" uid: 9415aa4d-44a7-4388-8c87-b9326f36e951 spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T12:59:40Z" message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.526766ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 2.169196ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 2.227126ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 2.217047ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 2.046771ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:23:40Z" - latency: 2.390665ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:22:40Z" - latency: 2.138259ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 1.99125ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 2.68791ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 2.440071ms message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-network-check-target-ip-10-0-136-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "54221" uid: 38413fd4-cd42-4fda-9a73-c5b2b2debbd0 spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T12:59:40Z" message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.364992ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 762.902µs message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 894.714µs message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 832.776µs message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 984.267µs message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:23:40Z" - latency: 1.13204ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:22:40Z" - latency: 1.039787ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 923.297µs message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 1.132163ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 739.954µs message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:52:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-245-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-245.ec2.internal uid: 40084195-c980-43fa-88dd-6325d61c45d6 resourceVersion: "55373" uid: eb0d62c4-6769-4d33-946f-552caa63ee89 spec: sourcePod: network-check-source-989f8b8dc-x9vgr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T12:58:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.365µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:28:40Z" - latency: 2.528396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:28:40Z" - latency: 1.050746ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:27:40Z" - latency: 1.772053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:27:40Z" - latency: 864.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:26:40Z" - latency: 1.660294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:26:40Z" - latency: 919.865µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:25:40Z" - latency: 1.797602ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:25:40Z" - latency: 1.125734ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:24:40Z" - latency: 1.734912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:24:40Z" kind: List metadata: resourceVersion: ""