apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "53910" uid: e5249f5f-e7ea-49b1-8178-5ab6b316b0d6 spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T07:09:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.772944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 1.093876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 1.001446ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 1.341195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 1.185145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:33:29Z" - latency: 917.945µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:32:29Z" - latency: 1.133353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:31:29Z" - latency: 1.114543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:30:29Z" - latency: 948.2µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:29:29Z" - latency: 1.078861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:28:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "54946" uid: 337b51a9-acac-4ac8-8d1a-c40fc282aa4b spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T07:08:29Z" message: 'load-balancer-api-external: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.732354ms message: 'load-balancer-api-external: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:38:29Z" - latency: 7.481317ms message: 'load-balancer-api-external: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:38:29Z" - latency: 11.187157ms message: 'load-balancer-api-external: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 10.425273ms message: 'load-balancer-api-external: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:37:29Z" - latency: 4.146018ms message: 'load-balancer-api-external: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 9.309191ms message: 'load-balancer-api-external: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:36:29Z" - latency: 4.741801ms message: 'load-balancer-api-external: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 9.392921ms message: 'load-balancer-api-external: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:35:29Z" - latency: 5.461677ms message: 'load-balancer-api-external: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 7.842442ms message: 'load-balancer-api-external: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:34:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "54947" uid: d241e742-9604-474f-a580-e4228f436543 spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T07:08:29Z" message: 'load-balancer-api-internal: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.766149ms message: 'load-balancer-api-internal: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:38:29Z" - latency: 7.422601ms message: 'load-balancer-api-internal: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:38:29Z" - latency: 11.232699ms message: 'load-balancer-api-internal: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 10.397678ms message: 'load-balancer-api-internal: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:37:29Z" - latency: 5.125632ms message: 'load-balancer-api-internal: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 9.279986ms message: 'load-balancer-api-internal: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:36:29Z" - latency: 4.766096ms message: 'load-balancer-api-internal: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 9.36503ms message: 'load-balancer-api-internal: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:35:29Z" - latency: 5.735676ms message: 'load-balancer-api-internal: tcp connection to aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 7.80758ms message: 'load-balancer-api-internal: resolved host name aa9043ace029949559aaae7db55574b6-5133be8abe771c36.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T07:34:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-ip-10-0-131-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "53908" uid: a6f796c6-a9e9-401d-b188-c6ea0a423d1a spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T07:09:29Z" message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.085985ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 2.623155ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 2.271129ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 2.355877ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 2.320278ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:33:29Z" - latency: 2.172289ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:32:29Z" - latency: 2.049845ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:31:29Z" - latency: 2.193287ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:30:29Z" - latency: 2.404945ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:29:29Z" - latency: 2.152009ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:28:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-ip-10-0-138-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "53909" uid: b7225e95-0964-462f-b202-eed07e3b17ec spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T07:09:29Z" message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.151082ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 2.457165ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 2.341513ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 2.354659ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 2.524633ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:33:29Z" - latency: 2.729627ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:32:29Z" - latency: 2.441634ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:31:29Z" - latency: 2.30455ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:30:29Z" - latency: 2.619605ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:29:29Z" - latency: 2.382383ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:28:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-ip-10-0-138-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "53907" uid: dda42529-e3b3-4996-aadf-a57849f50e16 spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T07:09:29Z" message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.222µs message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 1.223441ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 877.63µs message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 1.490404ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 1.104079ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:33:29Z" - latency: 1.207031ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:32:29Z" - latency: 1.321409ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:31:29Z" - latency: 1.32479ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:30:29Z" - latency: 938.886µs message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:29:29Z" - latency: 1.279644ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:28:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T07:02:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: c609f4f2-637a-4a2a-a19d-9a6fdbbc3c58 resourceVersion: "54945" uid: 749c64ed-612c-4d6d-b2d9-cd2c79eec2b6 spec: sourcePod: network-check-source-989f8b8dc-b8lvb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T07:08:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.305989ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:38:29Z" - latency: 1.942528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:38:29Z" - latency: 1.161691ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:37:29Z" - latency: 2.610133ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:37:29Z" - latency: 1.036068ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:36:29Z" - latency: 1.821963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:36:29Z" - latency: 1.053681ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:35:29Z" - latency: 1.762487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:35:29Z" - latency: 1.141827ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T07:34:29Z" - latency: 1.810411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T07:34:29Z" kind: List metadata: resourceVersion: ""