apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "47430" uid: e9bccd3a-fdce-4ec6-a80c-32c814450998 spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T11:25:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.114345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 871.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 913.399µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 977.633µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:43:06Z" - latency: 1.039506ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:42:06Z" - latency: 1.109711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:41:06Z" - latency: 1.128079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:40:06Z" - latency: 1.04038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:39:06Z" - latency: 1.086567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:38:06Z" - latency: 1.438065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:37:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "49774" uid: 552268de-95e9-46b1-b6c1-63424abbafaf spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T11:24:06Z" message: 'load-balancer-api-external: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.60982ms message: 'load-balancer-api-external: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:48:06Z" - latency: 7.000875ms message: 'load-balancer-api-external: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:48:06Z" - latency: 4.681758ms message: 'load-balancer-api-external: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:47:06Z" - latency: 7.019043ms message: 'load-balancer-api-external: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:47:06Z" - latency: 5.428189ms message: 'load-balancer-api-external: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 6.725661ms message: 'load-balancer-api-external: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:46:06Z" - latency: 4.009675ms message: 'load-balancer-api-external: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 6.932791ms message: 'load-balancer-api-external: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:45:06Z" - latency: 4.640708ms message: 'load-balancer-api-external: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 6.20116ms message: 'load-balancer-api-external: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:44:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "49775" uid: 262b7241-1b04-404f-a540-ced729c78cfe spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T11:24:06Z" message: 'load-balancer-api-internal: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.559342ms message: 'load-balancer-api-internal: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:48:06Z" - latency: 7.079866ms message: 'load-balancer-api-internal: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:48:06Z" - latency: 6.11238ms message: 'load-balancer-api-internal: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:47:06Z" - latency: 7.049536ms message: 'load-balancer-api-internal: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:47:06Z" - latency: 5.404971ms message: 'load-balancer-api-internal: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 6.670594ms message: 'load-balancer-api-internal: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:46:06Z" - latency: 4.49625ms message: 'load-balancer-api-internal: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 6.95639ms message: 'load-balancer-api-internal: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:45:06Z" - latency: 4.281434ms message: 'load-balancer-api-internal: tcp connection to a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 6.274456ms message: 'load-balancer-api-internal: resolved host name a6d024c40e3d14f2bbae49bb6e457ff7-026aed46bf6b6969.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T11:44:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-ip-10-0-131-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "47427" uid: 9a416117-1788-4d45-aa63-677ec27730de spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T11:25:06Z" message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.461524ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 1.362764ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 827.521µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 926.454µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:43:06Z" - latency: 1.620676ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:42:06Z" - latency: 1.285773ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:41:06Z" - latency: 833.166µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:40:06Z" - latency: 1.026475ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:39:06Z" - latency: 1.179491ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:38:06Z" - latency: 929.448µs message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:37:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-ip-10-0-138-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "47428" uid: 8bb2e928-294d-4675-82a7-542c16117bea spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T11:25:06Z" message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.648582ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 2.079189ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 2.224092ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 2.148067ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:43:06Z" - latency: 2.288854ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:42:06Z" - latency: 2.483883ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:41:06Z" - latency: 2.466512ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:40:06Z" - latency: 2.300293ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:39:06Z" - latency: 2.438292ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:38:06Z" - latency: 2.320674ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:37:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-ip-10-0-143-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "47429" uid: 1e161817-5e8c-4ffe-bc33-7892a0150b2b spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T11:25:06Z" message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.588199ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 2.541504ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 2.267969ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 1.869845ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:43:06Z" - latency: 2.341106ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:42:06Z" - latency: 2.578685ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:41:06Z" - latency: 2.352533ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:40:06Z" - latency: 2.25967ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:39:06Z" - latency: 2.347588ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:38:06Z" - latency: 2.344723ms message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:37:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T11:18:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-226.ec2.internal uid: 88c658ad-43df-40d2-8880-fb0d422eebe1 resourceVersion: "49772" uid: 21010c6b-a2d3-4afe-a999-0ed0129c9aeb spec: sourcePod: network-check-source-989f8b8dc-7lrnr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T11:24:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.916µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:48:06Z" - latency: 1.789834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T11:48:06Z" - latency: 944.723µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:47:06Z" - latency: 1.702401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T11:47:06Z" - latency: 1.047041ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:46:06Z" - latency: 1.655723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T11:46:06Z" - latency: 931.393µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:45:06Z" - latency: 1.615229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T11:45:06Z" - latency: 812.638µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T11:44:06Z" - latency: 1.659623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T11:44:06Z" kind: List metadata: resourceVersion: ""