apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "70841" uid: f2a4c6d7-c263-4a62-91d2-89dbe13ff136 spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T19:24:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:55Z" - latency: 877.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 1.061364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 1.158627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 1.181708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 1.474446ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 755.488µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:00:55Z" - latency: 1.028635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:59:55Z" - latency: 1.081123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:58:55Z" - latency: 1.309513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:57:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "68663" uid: d5124cd2-4c83-451c-97af-3c5ab555921d spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T19:23:55Z" message: 'load-balancer-api-external: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.683389ms message: 'load-balancer-api-external: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 7.39972ms message: 'load-balancer-api-external: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:05:55Z" - latency: 5.629241ms message: 'load-balancer-api-external: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 8.510773ms message: 'load-balancer-api-external: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:04:55Z" - latency: 4.878338ms message: 'load-balancer-api-external: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 8.390318ms message: 'load-balancer-api-external: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:03:55Z" - latency: 4.705886ms message: 'load-balancer-api-external: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 8.279635ms message: 'load-balancer-api-external: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:02:55Z" - latency: 4.906355ms message: 'load-balancer-api-external: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 7.809993ms message: 'load-balancer-api-external: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:01:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "68662" uid: b2e68443-99fb-47dd-992f-b596656db7ba spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T19:23:55Z" message: 'load-balancer-api-internal: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.724094ms message: 'load-balancer-api-internal: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 7.376594ms message: 'load-balancer-api-internal: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:05:55Z" - latency: 5.65499ms message: 'load-balancer-api-internal: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 8.471356ms message: 'load-balancer-api-internal: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:04:55Z" - latency: 4.257376ms message: 'load-balancer-api-internal: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 8.510733ms message: 'load-balancer-api-internal: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:03:55Z" - latency: 4.666338ms message: 'load-balancer-api-internal: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 8.367154ms message: 'load-balancer-api-internal: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:02:55Z" - latency: 4.069906ms message: 'load-balancer-api-internal: tcp connection to a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 7.754855ms message: 'load-balancer-api-internal: resolved host name a6a43ff03d56749e683f9fcb8dbbe96c-48a50e8869520362.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T20:01:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-network-check-target-ip-10-0-130-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "70839" uid: 389653c6-f355-4c05-9c40-6ef6874c6f13 spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:24:55Z" message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.877446ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:55Z" - latency: 2.034455ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 2.046996ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 2.08718ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 2.175963ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 1.951704ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 2.008412ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:00:55Z" - latency: 2.171451ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:59:55Z" - latency: 1.566851ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:58:55Z" - latency: 1.994421ms message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:57:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-network-check-target-ip-10-0-131-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "70840" uid: 0bf1018d-4966-4254-a7df-99d32cb3c884 spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:24:55Z" message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.253995ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:55Z" - latency: 2.036105ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 2.296417ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 2.390005ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 2.090457ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 2.307091ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 2.437866ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:00:55Z" - latency: 2.471021ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:59:55Z" - latency: 2.242258ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:58:55Z" - latency: 2.362676ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:57:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-network-check-target-ip-10-0-132-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "70838" uid: 6c2fa157-e2eb-4355-a459-4aca38e30769 spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:24:55Z" message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.07µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:06:55Z" - latency: 807.642µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 814.361µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 923.747µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 832.373µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 836.206µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 1.098567ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:00:55Z" - latency: 949.754µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:59:55Z" - latency: 862.076µs message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:58:55Z" - latency: 1.239569ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:57:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:17:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-216-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-216.ec2.internal uid: 5abd7d49-0a16-42d7-9e1e-eb343b43f9b5 resourceVersion: "68661" uid: 54a6bc0b-9e7d-4f24-9778-e7a8a9b6a770 spec: sourcePod: network-check-source-7d88cb55d8-cbfnl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T19:23:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:05:55Z" - latency: 2.195891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:05:55Z" - latency: 1.029124ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:04:55Z" - latency: 1.733158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:04:55Z" - latency: 844.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:03:55Z" - latency: 1.706089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:03:55Z" - latency: 1.140645ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:02:55Z" - latency: 1.79581ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:02:55Z" - latency: 1.005716ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T20:01:55Z" - latency: 1.738104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T20:01:55Z" kind: List metadata: resourceVersion: ""