apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "175119" uid: bf77351d-0268-44a0-b289-409e862173ef spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T12:42:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.717759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 1.964929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 1.100605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 1.256875ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 1.758303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:48:08Z" - latency: 1.579545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:47:08Z" - latency: 20.200744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:46:08Z" - latency: 32.724828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:45:08Z" - latency: 906.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:44:08Z" - latency: 1.492453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:43:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "177141" uid: 6fbc29eb-2c27-4a33-93b9-6eb4939878bc spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T12:41:08Z" message: 'load-balancer-api-external: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.744771ms message: 'load-balancer-api-external: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:53:08Z" - latency: 7.218813ms message: 'load-balancer-api-external: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:53:08Z" - latency: 16.749136ms message: 'load-balancer-api-external: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 8.05207ms message: 'load-balancer-api-external: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:52:08Z" - latency: 17.094897ms message: 'load-balancer-api-external: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 8.266195ms message: 'load-balancer-api-external: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:51:08Z" - latency: 20.153276ms message: 'load-balancer-api-external: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 7.375618ms message: 'load-balancer-api-external: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:50:08Z" - latency: 19.103054ms message: 'load-balancer-api-external: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 7.864249ms message: 'load-balancer-api-external: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:49:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "177142" uid: b5488721-a3b6-4f80-a0fc-48f38ece9810 spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T12:41:08Z" message: 'load-balancer-api-internal: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.014081ms message: 'load-balancer-api-internal: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:53:08Z" - latency: 7.316306ms message: 'load-balancer-api-internal: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:53:08Z" - latency: 16.758984ms message: 'load-balancer-api-internal: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 7.967851ms message: 'load-balancer-api-internal: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:52:08Z" - latency: 19.151309ms message: 'load-balancer-api-internal: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 8.280139ms message: 'load-balancer-api-internal: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:51:08Z" - latency: 20.581746ms message: 'load-balancer-api-internal: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 7.107228ms message: 'load-balancer-api-internal: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:50:08Z" - latency: 19.054626ms message: 'load-balancer-api-internal: tcp connection to a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 7.798813ms message: 'load-balancer-api-internal: resolved host name a364d69ec5d5643948301d0fcb25c179-adcb7c02390296c1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T13:49:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-134-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "175116" uid: e08e0618-f4ed-4699-9c9e-dbcabe56911d spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T12:42:08Z" message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.131468ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 3.177615ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 2.440762ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 3.004443ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 2.34327ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:48:08Z" - latency: 3.402642ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:47:08Z" - latency: 20.014357ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:46:08Z" - latency: 32.103886ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:45:08Z" - latency: 2.553884ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:44:08Z" - latency: 2.371536ms message: 'network-check-target-ip-10-0-134-193: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:43:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-135-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "175112" uid: 65f4ea47-edf7-4e46-9f9b-23d30b58d9f8 spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T12:42:08Z" message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.882041ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 2.079458ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 1.264035ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 1.238818ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 3.498039ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:48:08Z" - latency: 1.087446ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:47:08Z" - latency: 19.97199ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:46:08Z" - latency: 31.613395ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:45:08Z" - latency: 1.98251ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:44:08Z" - latency: 1.036253ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:43:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-136-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "175113" uid: e43ee202-daac-4de6-8d46-954ddaff6183 spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T12:42:08Z" message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.862795ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 2.776492ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 2.710123ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 2.52894ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 9.54644ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:48:08Z" - latency: 3.453629ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:47:08Z" - latency: 20.498215ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:46:08Z" - latency: 32.940368ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:45:08Z" - latency: 2.643678ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:44:08Z" - latency: 2.394889ms message: 'network-check-target-ip-10-0-136-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:43:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T12:35:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.ec2.internal uid: dd0035a2-df0a-4e05-ae94-0fd6a21c9b62 resourceVersion: "177139" uid: 82d03285-be0c-4825-847e-0f3aea05830f spec: sourcePod: network-check-source-6f78d59f99-fc5ft targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T12:41:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.108274ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:53:08Z" - latency: 1.983168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T13:53:08Z" - latency: 1.072767ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:52:08Z" - latency: 3.055315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T13:52:08Z" - latency: 958.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:51:08Z" - latency: 3.193041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T13:51:08Z" - latency: 1.193053ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:50:08Z" - latency: 2.224274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T13:50:08Z" - latency: 1.314905ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T13:49:08Z" - latency: 2.7437ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T13:49:08Z" kind: List metadata: resourceVersion: ""