apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "44931" uid: 31e035d2-6149-4459-9ecf-4c774efe5bf8 spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T13:53:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.203736ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 1.520098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 1.122303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 1.104002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:11:29Z" - latency: 822.906µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:10:29Z" - latency: 897.423µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:09:29Z" - latency: 1.195014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:08:29Z" - latency: 1.82788ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:07:29Z" - latency: 1.062946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:06:29Z" - latency: 2.371855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:05:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "47004" uid: 62711e25-c82f-460c-a2ba-d9c54ab76783 spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T13:52:29Z" message: 'load-balancer-api-external: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.780814ms message: 'load-balancer-api-external: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:16:29Z" - latency: 13.829442ms message: 'load-balancer-api-external: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:16:29Z" - latency: 5.195949ms message: 'load-balancer-api-external: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:15:29Z" - latency: 9.070685ms message: 'load-balancer-api-external: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:15:29Z" - latency: 4.736455ms message: 'load-balancer-api-external: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 8.19312ms message: 'load-balancer-api-external: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:14:29Z" - latency: 5.117285ms message: 'load-balancer-api-external: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 10.434113ms message: 'load-balancer-api-external: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:13:29Z" - latency: 5.103578ms message: 'load-balancer-api-external: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 11.340196ms message: 'load-balancer-api-external: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:12:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "47005" uid: d48aaeb4-7d2a-4cef-a80b-0b8776be4011 spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T13:52:29Z" message: 'load-balancer-api-internal: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.428269ms message: 'load-balancer-api-internal: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:16:29Z" - latency: 13.911612ms message: 'load-balancer-api-internal: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:16:29Z" - latency: 5.225494ms message: 'load-balancer-api-internal: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:15:29Z" - latency: 9.126181ms message: 'load-balancer-api-internal: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:15:29Z" - latency: 4.744357ms message: 'load-balancer-api-internal: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 8.156503ms message: 'load-balancer-api-internal: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:14:29Z" - latency: 4.998618ms message: 'load-balancer-api-internal: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 10.369491ms message: 'load-balancer-api-internal: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:13:29Z" - latency: 5.108678ms message: 'load-balancer-api-internal: tcp connection to ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 11.386029ms message: 'load-balancer-api-internal: resolved host name ac64bfbcc5c9443e0850bd681620c08a-daf78c03b802f3f9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T14:12:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-ip-10-0-132-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "44928" uid: 5e66e702-feb4-492d-b386-f40b97804f00 spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:53:29Z" message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.047271ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 1.382257ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 928.832µs message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 1.006648ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:11:29Z" - latency: 1.425285ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:10:29Z" - latency: 844.483µs message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:09:29Z" - latency: 1.00547ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:08:29Z" - latency: 1.011943ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:07:29Z" - latency: 974.199µs message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:06:29Z" - latency: 2.77074ms message: 'network-check-target-ip-10-0-132-92: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:05:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-ip-10-0-141-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "44929" uid: 19c18f91-38a0-4a34-831f-353b12b7800b spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:53:29Z" message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.816348ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 2.221906ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 2.311408ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 2.653724ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:11:29Z" - latency: 2.150312ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:10:29Z" - latency: 1.852361ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:09:29Z" - latency: 2.350472ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:08:29Z" - latency: 2.278201ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:07:29Z" - latency: 2.293438ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:06:29Z" - latency: 2.354421ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:05:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-ip-10-0-141-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "44930" uid: cf16280d-ecb0-4620-b953-b50e643f1c20 spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:53:29Z" message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.854445ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 1.985504ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 1.995444ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 2.477958ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:11:29Z" - latency: 1.832629ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:10:29Z" - latency: 1.409278ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:09:29Z" - latency: 1.961502ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:08:29Z" - latency: 1.939685ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:07:29Z" - latency: 2.044974ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:06:29Z" - latency: 3.270222ms message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:05:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T13:46:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-92-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-92.ec2.internal uid: e43fe479-a6d2-4e69-a57d-f38adf2cea37 resourceVersion: "47002" uid: 30e0e2c8-8fe8-43db-8ba0-1b74d286c937 spec: sourcePod: network-check-source-dbd9cf844-8rmnl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T13:52:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.261µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:16:29Z" - latency: 1.802516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T14:16:29Z" - latency: 852.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:15:29Z" - latency: 1.77082ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T14:15:29Z" - latency: 1.011806ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:14:29Z" - latency: 1.992987ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T14:14:29Z" - latency: 926.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:13:29Z" - latency: 1.783576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T14:13:29Z" - latency: 943.65µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T14:12:29Z" - latency: 1.831013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T14:12:29Z" kind: List metadata: resourceVersion: ""