apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "23366" uid: ba4ff2d3-fd67-434d-8575-c1fd1c8d8ccc spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T16:37:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.655µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 1.008997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 921.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:49:57Z" - latency: 963.112µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:48:57Z" - latency: 804.471µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:47:57Z" - latency: 1.343241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:46:57Z" - latency: 828.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:45:57Z" - latency: 935.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:44:57Z" - latency: 1.07595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:43:57Z" - latency: 1.563489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:42:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "24784" uid: 7dc251d8-cc00-40b8-9578-3dbe6e32b348 spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T16:36:57Z" message: 'load-balancer-api-external: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.866985ms message: 'load-balancer-api-external: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:54:57Z" - latency: 8.471028ms message: 'load-balancer-api-external: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:54:57Z" - latency: 4.473331ms message: 'load-balancer-api-external: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:53:57Z" - latency: 10.901264ms message: 'load-balancer-api-external: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:53:57Z" - latency: 4.582287ms message: 'load-balancer-api-external: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:52:57Z" - latency: 11.0399ms message: 'load-balancer-api-external: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:52:57Z" - latency: 4.399082ms message: 'load-balancer-api-external: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 12.364569ms message: 'load-balancer-api-external: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:51:57Z" - latency: 5.667323ms message: 'load-balancer-api-external: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 9.637096ms message: 'load-balancer-api-external: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:50:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "24783" uid: c311c1de-ac1e-40a3-922e-a8d6901576cb spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T16:36:57Z" message: 'load-balancer-api-internal: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.859565ms message: 'load-balancer-api-internal: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:54:57Z" - latency: 8.442396ms message: 'load-balancer-api-internal: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:54:57Z" - latency: 4.500044ms message: 'load-balancer-api-internal: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:53:57Z" - latency: 10.881484ms message: 'load-balancer-api-internal: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:53:57Z" - latency: 4.501778ms message: 'load-balancer-api-internal: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:52:57Z" - latency: 10.989265ms message: 'load-balancer-api-internal: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:52:57Z" - latency: 4.438324ms message: 'load-balancer-api-internal: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 12.275376ms message: 'load-balancer-api-internal: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:51:57Z" - latency: 5.384008ms message: 'load-balancer-api-internal: tcp connection to a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 9.55839ms message: 'load-balancer-api-internal: resolved host name a50e7bcbb4e8341b5893eaf79614f1b6-cb17aad9bd878c35.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T16:50:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-network-check-target-ip-10-0-130-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "23364" uid: db605e50-eee7-48d7-b7a0-40168fb78a2a spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T16:37:57Z" message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.937771ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 2.01432ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 1.936961ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:49:57Z" - latency: 2.087168ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:48:57Z" - latency: 1.848872ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:47:57Z" - latency: 1.963392ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:46:57Z" - latency: 1.744284ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:45:57Z" - latency: 2.007804ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:44:57Z" - latency: 2.013843ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:43:57Z" - latency: 1.954451ms message: 'network-check-target-ip-10-0-130-221: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:42:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-network-check-target-ip-10-0-141-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "23363" uid: dba36f46-d27a-4717-9a66-f0624b47d66f spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T16:37:57Z" message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.825µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 870.706µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 1.314176ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:49:57Z" - latency: 1.346436ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:48:57Z" - latency: 867.123µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:47:57Z" - latency: 725.092µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:46:57Z" - latency: 770.579µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:45:57Z" - latency: 855.248µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:44:57Z" - latency: 856.003µs message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:43:57Z" - latency: 1.009721ms message: 'network-check-target-ip-10-0-141-197: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:42:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-network-check-target-ip-10-0-141-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "23365" uid: 3c3f8b57-31b1-406a-ad6c-964ad09d5b27 spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T16:37:57Z" message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.28309ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 2.216234ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 2.329332ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:49:57Z" - latency: 2.152903ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:48:57Z" - latency: 2.060213ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:47:57Z" - latency: 1.953665ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:46:57Z" - latency: 1.708032ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:45:57Z" - latency: 1.677439ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:44:57Z" - latency: 1.713398ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:43:57Z" - latency: 1.808704ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:42:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T16:30:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-197-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-197.ec2.internal uid: e2dd6421-729b-4053-97ba-ab781ecea9dc resourceVersion: "24782" uid: d42d43e1-d0e7-41c2-84f0-39025d5e0ccf spec: sourcePod: network-check-source-6f8b768455-ck8fq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T16:36:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.888µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:54:57Z" - latency: 1.724117ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T16:54:57Z" - latency: 993.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:53:57Z" - latency: 1.888078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T16:53:57Z" - latency: 927.34µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:52:57Z" - latency: 1.710883ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T16:52:57Z" - latency: 813.851µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:51:57Z" - latency: 1.679876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T16:51:57Z" - latency: 705.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T16:50:57Z" - latency: 2.688234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T16:50:57Z" kind: List metadata: resourceVersion: ""