apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "71537" uid: ea655d66-9176-4c80-9761-09cdf2c9adae spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T20:56:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.314289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:23Z" - latency: 1.217222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 1.183009ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 1.317904ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 1.720206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 1.045153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 950.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:23Z" - latency: 995.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:23Z" - latency: 1.62989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:23Z" - latency: 1.308107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:29:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "69160" uid: 99626278-b735-48d9-b7f7-9b562ea7f08c spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T20:55:23Z" message: 'load-balancer-api-external: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.966809ms message: 'load-balancer-api-external: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 16.599712ms message: 'load-balancer-api-external: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:37:23Z" - latency: 5.961872ms message: 'load-balancer-api-external: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 9.117334ms message: 'load-balancer-api-external: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:36:23Z" - latency: 5.740824ms message: 'load-balancer-api-external: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 7.236281ms message: 'load-balancer-api-external: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:35:23Z" - latency: 5.281743ms message: 'load-balancer-api-external: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 8.36247ms message: 'load-balancer-api-external: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:34:23Z" - latency: 4.782246ms message: 'load-balancer-api-external: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 7.402082ms message: 'load-balancer-api-external: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "69159" uid: 8ad9c67d-8e0a-4c2f-9076-b1602d7be29d spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T20:55:23Z" message: 'load-balancer-api-internal: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.898295ms message: 'load-balancer-api-internal: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 12.312401ms message: 'load-balancer-api-internal: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:37:23Z" - latency: 5.947367ms message: 'load-balancer-api-internal: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 9.101479ms message: 'load-balancer-api-internal: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:36:23Z" - latency: 5.778292ms message: 'load-balancer-api-internal: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 7.197461ms message: 'load-balancer-api-internal: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:35:23Z" - latency: 5.314794ms message: 'load-balancer-api-internal: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 8.33705ms message: 'load-balancer-api-internal: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:34:23Z" - latency: 4.890133ms message: 'load-balancer-api-internal: tcp connection to ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 7.301044ms message: 'load-balancer-api-internal: resolved host name ad2c39384e2f943fb9efa356eec78dfb-b9cc1e730c897823.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:33:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-network-check-target-ip-10-0-133-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "71534" uid: ee72180c-deeb-4dcc-8335-988920c66a32 spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:56:23Z" message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.127006ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:23Z" - latency: 4.838211ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 1.207484ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 1.055485ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 1.106018ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 1.115379ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 1.079547ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:23Z" - latency: 1.073594ms message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:23Z" - latency: 962.857µs message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:23Z" - latency: 858.006µs message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:29:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-network-check-target-ip-10-0-138-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "71535" uid: 4655fd51-2def-4a41-a991-93f445b94356 spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:56:23Z" message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.475897ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:23Z" - latency: 3.391112ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 2.490203ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 2.082437ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 2.541526ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 2.298625ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 2.518933ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:23Z" - latency: 2.687958ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:23Z" - latency: 2.238026ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:23Z" - latency: 2.471341ms message: 'network-check-target-ip-10-0-138-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:29:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-network-check-target-ip-10-0-140-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "71536" uid: 53de85de-3123-4b7c-92fe-18504e84585f spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:56:23Z" message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.489294ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:23Z" - latency: 4.303583ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 2.337954ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 2.170839ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 2.493717ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 2.09929ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 2.47683ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:23Z" - latency: 2.355762ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:23Z" - latency: 2.441294ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:23Z" - latency: 2.137643ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:29:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-57.ec2.internal uid: 8c0ccadc-31d8-4d74-94c0-367121de8604 resourceVersion: "69158" uid: 019ea90e-d5a8-4d4b-ba07-d00b0d2e379a spec: sourcePod: network-check-source-7d88cb55d8-rh4gn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T20:55:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.120392ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:23Z" - latency: 4.676618ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:37:23Z" - latency: 969.821µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:23Z" - latency: 2.227042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:36:23Z" - latency: 1.000705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:23Z" - latency: 2.025742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:35:23Z" - latency: 1.067595ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:23Z" - latency: 2.361882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:34:23Z" - latency: 1.020853ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:23Z" - latency: 2.209923ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:33:23Z" kind: List metadata: resourceVersion: ""