apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "17705" uid: 8d787b62-653e-4711-a24e-f3b6807d322b spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T11:43:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 995.479µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:50:03Z" - latency: 1.188433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:49:03Z" - latency: 1.866206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 944.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 1.183383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 938.18µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 1.109295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 824.607µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:43:03Z" - latency: 1.00738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:42:03Z" - latency: 843.411µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:41:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "16943" uid: 73b1490d-f9c2-4312-948b-f3cbd3b632de spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T11:42:03Z" message: 'load-balancer-api-external: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.932399ms message: 'load-balancer-api-external: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 8.113584ms message: 'load-balancer-api-external: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:48:03Z" - latency: 4.843351ms message: 'load-balancer-api-external: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 7.064934ms message: 'load-balancer-api-external: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:47:03Z" - latency: 4.642853ms message: 'load-balancer-api-external: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 6.768753ms message: 'load-balancer-api-external: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:46:03Z" - latency: 4.878793ms message: 'load-balancer-api-external: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 6.633552ms message: 'load-balancer-api-external: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:45:03Z" - latency: 4.518595ms message: 'load-balancer-api-external: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 6.137638ms message: 'load-balancer-api-external: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:44:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "16944" uid: fdfa41cf-d4b4-43d8-a8bc-9d036a4635d5 spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T11:42:03Z" message: 'load-balancer-api-internal: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.944796ms message: 'load-balancer-api-internal: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 8.303909ms message: 'load-balancer-api-internal: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:48:03Z" - latency: 4.861457ms message: 'load-balancer-api-internal: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 6.999738ms message: 'load-balancer-api-internal: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:47:03Z" - latency: 4.639917ms message: 'load-balancer-api-internal: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 6.803063ms message: 'load-balancer-api-internal: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:46:03Z" - latency: 4.923156ms message: 'load-balancer-api-internal: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 6.597573ms message: 'load-balancer-api-internal: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:45:03Z" - latency: 4.85634ms message: 'load-balancer-api-internal: tcp connection to aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 6.080629ms message: 'load-balancer-api-internal: resolved host name aaef9ce604850460fae35142faf94f93-0c412fd5bf113bc4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T11:44:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-network-check-target-ip-10-0-130-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "17704" uid: 03e9f94e-b4e3-4ade-a62c-58b9815c70e0 spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T11:43:03Z" message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.359275ms message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:50:03Z" - latency: 993.865µs message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:49:03Z" - latency: 1.338304ms message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 1.135713ms message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 1.264113ms message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 1.341969ms message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 765.896µs message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 929.941µs message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:43:03Z" - latency: 1.361706ms message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:42:03Z" - latency: 840.054µs message: 'network-check-target-ip-10-0-130-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:41:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-network-check-target-ip-10-0-134-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "17703" uid: 4ff910e2-efb6-400a-8c5e-5860d350eb65 spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T11:43:03Z" message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.766692ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:50:03Z" - latency: 1.899161ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:49:03Z" - latency: 2.63086ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 1.895251ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 1.915502ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 1.697238ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 1.536403ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 1.740323ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:43:03Z" - latency: 1.761659ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:42:03Z" - latency: 2.01494ms message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:41:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-network-check-target-ip-10-0-140-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "17702" uid: acb2375d-a579-464d-bf58-e5fdd4329809 spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T11:43:03Z" message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.063562ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:50:03Z" - latency: 2.320764ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:49:03Z" - latency: 2.574702ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 2.218136ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 1.954665ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 2.051145ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 2.057789ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 1.995677ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:43:03Z" - latency: 2.000383ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:42:03Z" - latency: 1.823344ms message: 'network-check-target-ip-10-0-140-245: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:41:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T11:36:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-210-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-210.ec2.internal uid: a75e127c-96d8-40fa-bb0b-94db65720948 resourceVersion: "16942" uid: 8146b82e-cc85-4457-a073-ad6b64b3b6db spec: sourcePod: network-check-source-8894fc9bd-78fsm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T11:42:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 741.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:48:03Z" - latency: 1.74909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T11:48:03Z" - latency: 956.561µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:47:03Z" - latency: 1.87577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T11:47:03Z" - latency: 885.732µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:46:03Z" - latency: 1.800963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T11:46:03Z" - latency: 689.217µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:45:03Z" - latency: 1.791929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T11:45:03Z" - latency: 971.446µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T11:44:03Z" - latency: 1.74326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T11:44:03Z" kind: List metadata: resourceVersion: ""