apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "69470" uid: ccbec6c2-dbcd-4b9b-8fdd-f8ef2e394996 spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T23:32: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.318423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:14:07Z" - latency: 1.199601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:13:07Z" - latency: 1.062688ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:12:07Z" - latency: 1.450676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:11:07Z" - latency: 1.24246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:10:07Z" - latency: 941.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:09:07Z" - latency: 859.732µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:08:07Z" - latency: 1.255694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:07:07Z" - latency: 1.074254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:06:07Z" - latency: 4.595531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "74668" uid: e55992fa-27ca-437e-809d-872e7233c7e5 spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T23:31:07Z" message: 'load-balancer-api-external: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.438743ms message: 'load-balancer-api-external: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:19:07Z" - latency: 7.12284ms message: 'load-balancer-api-external: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:19:07Z" - latency: 2.982142ms message: 'load-balancer-api-external: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:18:07Z" - latency: 6.7164ms message: 'load-balancer-api-external: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:18:07Z" - latency: 3.639682ms message: 'load-balancer-api-external: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:17:07Z" - latency: 7.67ms message: 'load-balancer-api-external: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:17:07Z" - latency: 3.869339ms message: 'load-balancer-api-external: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:16:07Z" - latency: 6.992151ms message: 'load-balancer-api-external: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:16:07Z" - latency: 4.451927ms message: 'load-balancer-api-external: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:15:07Z" - latency: 8.643214ms message: 'load-balancer-api-external: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:15:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "74667" uid: 63834afb-867a-4c98-8555-c321756aa449 spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T23:31:07Z" message: 'load-balancer-api-internal: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.478461ms message: 'load-balancer-api-internal: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:19:07Z" - latency: 7.052848ms message: 'load-balancer-api-internal: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:19:07Z" - latency: 2.957679ms message: 'load-balancer-api-internal: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:18:07Z" - latency: 6.575709ms message: 'load-balancer-api-internal: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:18:07Z" - latency: 5.698413ms message: 'load-balancer-api-internal: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:17:07Z" - latency: 7.707918ms message: 'load-balancer-api-internal: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:17:07Z" - latency: 4.665804ms message: 'load-balancer-api-internal: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:16:07Z" - latency: 6.897979ms message: 'load-balancer-api-internal: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:16:07Z" - latency: 4.542809ms message: 'load-balancer-api-internal: tcp connection to a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:15:07Z" - latency: 8.670977ms message: 'load-balancer-api-internal: resolved host name a5a3f760a33a5461194f53165aa43607-a15adc11e97a26e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T00:15:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-ip-10-0-131-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "69468" uid: a475e324-c1bb-4a23-9e0a-d7b57453e687 spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T23:32:07Z" message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.755487ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:14:07Z" - latency: 2.453587ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:13:07Z" - latency: 2.373124ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:12:07Z" - latency: 2.365194ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:11:07Z" - latency: 2.243042ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:10:07Z" - latency: 2.468705ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:09:07Z" - latency: 2.253654ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:08:07Z" - latency: 2.83275ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:07:07Z" - latency: 2.891094ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:06:07Z" - latency: 4.114474ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-ip-10-0-135-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "69469" uid: 9732ce31-c2a2-41f9-b75e-56587c526a7d spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T23:32:07Z" message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.812893ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:14:07Z" - latency: 2.69881ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:13:07Z" - latency: 2.443522ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:12:07Z" - latency: 2.788915ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:11:07Z" - latency: 2.736683ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:10:07Z" - latency: 2.846015ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:09:07Z" - latency: 2.776335ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:08:07Z" - latency: 2.734948ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:07:07Z" - latency: 2.817523ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:06:07Z" - latency: 4.064797ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-ip-10-0-135-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "69467" uid: 36108d29-83d8-4126-b7a3-808db1200113 spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T23:32:07Z" message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.420938ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:14:07Z" - latency: 942.082µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:13:07Z" - latency: 1.283287ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:12:07Z" - latency: 833.118µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:11:07Z" - latency: 1.138365ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:10:07Z" - latency: 1.517675ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:09:07Z" - latency: 900.416µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:08:07Z" - latency: 1.497927ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:07:07Z" - latency: 1.180322ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:06:07Z" - latency: 4.431288ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T23:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: d1033581-59d3-419a-a98f-eaf8395e8315 resourceVersion: "74666" uid: 0f50d8de-bc7c-4e58-96d9-76e3f94650e1 spec: sourcePod: network-check-source-7d88cb55d8-th9gl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T23:31:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.094603ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:19:07Z" - latency: 1.929147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:19:07Z" - latency: 1.036437ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:18:07Z" - latency: 1.653786ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:18:07Z" - latency: 1.059986ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:17:07Z" - latency: 2.340466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:17:07Z" - latency: 1.270654ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:16:07Z" - latency: 2.06845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:16:07Z" - latency: 1.637324ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T00:15:07Z" - latency: 1.995198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T00:15:07Z" kind: List metadata: resourceVersion: ""