apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "68694" uid: 65a41773-80c1-46d4-9823-caa9efc8207e spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-19T07:53:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.185037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:35:38Z" - latency: 1.235066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:34:38Z" - latency: 1.289357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:33:38Z" - latency: 1.426333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:32:38Z" - latency: 1.139426ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:31:38Z" - latency: 805.543µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:30:38Z" - latency: 1.146922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:29:38Z" - latency: 1.292924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:28:38Z" - latency: 1.222305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:27:38Z" - latency: 940.084µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:26:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "74350" uid: e7928ae6-548b-4919-a47e-f449d36887c5 spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-19T07:52:38Z" message: 'load-balancer-api-external: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.066176ms message: 'load-balancer-api-external: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:40:38Z" - latency: 14.386277ms message: 'load-balancer-api-external: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:40:38Z" - latency: 4.928469ms message: 'load-balancer-api-external: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:39:38Z" - latency: 8.028471ms message: 'load-balancer-api-external: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:39:38Z" - latency: 3.818ms message: 'load-balancer-api-external: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:38:38Z" - latency: 8.518221ms message: 'load-balancer-api-external: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:38:38Z" - latency: 3.139979ms message: 'load-balancer-api-external: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:37:38Z" - latency: 8.701686ms message: 'load-balancer-api-external: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:37:38Z" - latency: 5.186235ms message: 'load-balancer-api-external: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:36:38Z" - latency: 8.306169ms message: 'load-balancer-api-external: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:36:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "74349" uid: c7df5a23-a928-47df-a2d0-6e5da6f4ede1 spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-19T07:52:38Z" message: 'load-balancer-api-internal: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.055341ms message: 'load-balancer-api-internal: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:40:38Z" - latency: 14.418379ms message: 'load-balancer-api-internal: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:40:38Z" - latency: 4.783167ms message: 'load-balancer-api-internal: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:39:38Z" - latency: 8.060274ms message: 'load-balancer-api-internal: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:39:38Z" - latency: 5.223791ms message: 'load-balancer-api-internal: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:38:38Z" - latency: 8.442113ms message: 'load-balancer-api-internal: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:38:38Z" - latency: 3.203914ms message: 'load-balancer-api-internal: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:37:38Z" - latency: 8.730028ms message: 'load-balancer-api-internal: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:37:38Z" - latency: 5.253379ms message: 'load-balancer-api-internal: tcp connection to aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:36:38Z" - latency: 8.32408ms message: 'load-balancer-api-internal: resolved host name aae618e554a82403799420c8793271e5-a1e156a74f87d810.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-19T08:36:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-129-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "68693" uid: ec862b42-4e0d-4280-bbac-93f8080fd354 spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-19T07:53:38Z" message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.444477ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:35:38Z" - latency: 2.190515ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:34:38Z" - latency: 2.280424ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:33:38Z" - latency: 2.434742ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:32:38Z" - latency: 2.259897ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:31:38Z" - latency: 2.302319ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:30:38Z" - latency: 1.998821ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:29:38Z" - latency: 2.43642ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:28:38Z" - latency: 2.617288ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:27:38Z" - latency: 2.255915ms message: 'network-check-target-ip-10-0-129-91: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:26:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-132-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "68692" uid: 686bd77e-4b5d-4b73-aadd-a26d5136938d spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-19T07:53:38Z" message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.316408ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:35:38Z" - latency: 2.112018ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:34:38Z" - latency: 1.827209ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:33:38Z" - latency: 2.268948ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:32:38Z" - latency: 2.130121ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:31:38Z" - latency: 1.629804ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:30:38Z" - latency: 2.237071ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:29:38Z" - latency: 2.031347ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:28:38Z" - latency: 2.268447ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:27:38Z" - latency: 2.099419ms message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:26:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-136-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "68691" uid: 6410f242-3e83-45ff-abff-c45e8edf79c7 spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-19T07:53:38Z" message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.120436ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:35:38Z" - latency: 1.057192ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:34:38Z" - latency: 883.806µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:33:38Z" - latency: 1.582671ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:32:38Z" - latency: 989.578µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:31:38Z" - latency: 1.01088ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:30:38Z" - latency: 1.10006ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:29:38Z" - latency: 1.66973ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:28:38Z" - latency: 1.160688ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:27:38Z" - latency: 1.126687ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:26:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-19T07:46:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 845d3054-87f3-4fc9-a423-ce7447a78c5f resourceVersion: "74348" uid: f8f3bb44-f27f-46e8-a0ca-46e2a0e21463 spec: sourcePod: network-check-source-7bc5b6bf85-x2qps targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-19T07:52:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013875ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:40:38Z" - latency: 2.394326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T08:40:38Z" - latency: 1.052759ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:39:38Z" - latency: 1.8257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T08:39:38Z" - latency: 1.167312ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:38:38Z" - latency: 1.839568ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T08:38:38Z" - latency: 1.235849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:37:38Z" - latency: 1.874889ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T08:37:38Z" - latency: 894.357µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-19T08:36:38Z" - latency: 1.954609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-19T08:36:38Z" kind: List metadata: resourceVersion: ""