apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59652" uid: a0a06efd-17ae-4a90-a6e0-5c9591ba8d63 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T17:40:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.250018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:22Z" - latency: 1.100301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:22Z" - latency: 1.278006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:22Z" - latency: 1.331539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:22Z" - latency: 1.261444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:22Z" - latency: 1.404394ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:22Z" - latency: 1.723601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:22Z" - latency: 1.239259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:22Z" - latency: 988.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:22Z" - latency: 1.352253ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:06:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59653" uid: 42db21cc-dbde-4082-a0f8-8066e26b3e91 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T17:39:22Z" message: 'load-balancer-api-external: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.473003ms message: 'load-balancer-api-external: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:22Z" - latency: 15.266966ms message: 'load-balancer-api-external: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:15:22Z" - latency: 3.816687ms message: 'load-balancer-api-external: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:22Z" - latency: 8.27509ms message: 'load-balancer-api-external: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:14:22Z" - latency: 5.791019ms message: 'load-balancer-api-external: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:22Z" - latency: 6.80873ms message: 'load-balancer-api-external: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:13:22Z" - latency: 7.685421ms message: 'load-balancer-api-external: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:22Z" - latency: 11.526184ms message: 'load-balancer-api-external: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:12:22Z" - latency: 4.557741ms message: 'load-balancer-api-external: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:22Z" - latency: 7.191982ms message: 'load-balancer-api-external: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:11:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59654" uid: bbcf645f-8900-448d-aaf3-3e01742d3be2 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T17:39:22Z" message: 'load-balancer-api-internal: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.438154ms message: 'load-balancer-api-internal: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:22Z" - latency: 15.228991ms message: 'load-balancer-api-internal: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:15:22Z" - latency: 3.88471ms message: 'load-balancer-api-internal: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:22Z" - latency: 8.318413ms message: 'load-balancer-api-internal: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:14:22Z" - latency: 4.076658ms message: 'load-balancer-api-internal: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:22Z" - latency: 6.765505ms message: 'load-balancer-api-internal: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:13:22Z" - latency: 7.910282ms message: 'load-balancer-api-internal: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:22Z" - latency: 11.822149ms message: 'load-balancer-api-internal: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:12:22Z" - latency: 3.832725ms message: 'load-balancer-api-internal: tcp connection to a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:22Z" - latency: 7.283964ms message: 'load-balancer-api-internal: resolved host name a0651d57b87b645248f9ee666c5d19e4-9efec55643f5e522.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:11:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-network-check-target-ip-10-0-130-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59650" uid: 9dbf756a-8b88-48f4-a098-73191ef428d7 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:40:22Z" message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040945ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:22Z" - latency: 1.541795ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:22Z" - latency: 1.291575ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:22Z" - latency: 1.738607ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:22Z" - latency: 1.032121ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:22Z" - latency: 963.609µs message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:22Z" - latency: 1.283528ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:22Z" - latency: 931.602µs message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:22Z" - latency: 979.725µs message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:22Z" - latency: 904.485µs message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:06:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-network-check-target-ip-10-0-136-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59649" uid: 4c7977f1-ed66-4c5b-800e-b8d085658433 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:40:22Z" message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.026371ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:22Z" - latency: 2.014709ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:22Z" - latency: 2.224242ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:22Z" - latency: 2.01634ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:22Z" - latency: 1.794529ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:22Z" - latency: 1.758185ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:22Z" - latency: 1.962701ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:22Z" - latency: 1.958758ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:22Z" - latency: 1.651616ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:22Z" - latency: 1.945811ms message: 'network-check-target-ip-10-0-136-43: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:06:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-network-check-target-ip-10-0-142-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59993" uid: 5a6bcf78-1fa4-4a3e-8217-bb8cc0aebaa4 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T17:40:40Z" message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.5665ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:40Z" - latency: 2.523239ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:40Z" - latency: 2.52857ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:40Z" - latency: 2.163353ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:40Z" - latency: 2.529257ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:40Z" - latency: 2.0279ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:10:40Z" - latency: 2.519479ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:09:40Z" - latency: 2.267198ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:08:40Z" - latency: 2.435991ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:07:40Z" - latency: 2.423973ms message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:06:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:33:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-245-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-245.ec2.internal uid: 536036db-bbc3-461f-bfe5-7671adf1368d resourceVersion: "59651" uid: 29a510f3-5e34-4854-b33c-1ea6d71f9c78 spec: sourcePod: network-check-source-7bc5b6bf85-n4qth targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T17:39:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:15:22Z" - latency: 2.179659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:15:22Z" - latency: 2.165623ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:14:22Z" - latency: 1.838436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:14:22Z" - latency: 961.687µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:13:22Z" - latency: 1.911231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:13:22Z" - latency: 2.218253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:12:22Z" - latency: 3.656513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:12:22Z" - latency: 1.062935ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:11:22Z" - latency: 1.883231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:11:22Z" kind: List metadata: resourceVersion: ""