apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "43844" uid: 2a4fd050-ca5c-4f27-9e6f-30b1fce06de2 spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T16:43:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.6µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 875.124µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 865.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 1.062854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:01:37Z" - latency: 792.11µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:00:37Z" - latency: 1.062753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:59:37Z" - latency: 800.303µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:58:37Z" - latency: 857.239µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:57:37Z" - latency: 844.765µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:56:37Z" - latency: 1.031302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "45819" uid: 30d83b75-b187-43f3-9cbb-6bdb609104fa spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T16:42:37Z" message: 'load-balancer-api-external: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.589746ms message: 'load-balancer-api-external: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:06:37Z" - latency: 8.544027ms message: 'load-balancer-api-external: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:06:37Z" - latency: 3.281089ms message: 'load-balancer-api-external: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:05:37Z" - latency: 8.277535ms message: 'load-balancer-api-external: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:05:37Z" - latency: 5.36879ms message: 'load-balancer-api-external: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 7.97069ms message: 'load-balancer-api-external: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:04:37Z" - latency: 5.432469ms message: 'load-balancer-api-external: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 8.686722ms message: 'load-balancer-api-external: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:03:37Z" - latency: 5.174535ms message: 'load-balancer-api-external: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 7.861521ms message: 'load-balancer-api-external: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:02:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "45818" uid: acc3d3e5-7f26-4bbe-aafe-a3089532fba7 spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T16:42:37Z" message: 'load-balancer-api-internal: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.609779ms message: 'load-balancer-api-internal: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:06:37Z" - latency: 8.507427ms message: 'load-balancer-api-internal: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:06:37Z" - latency: 4.938941ms message: 'load-balancer-api-internal: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:05:37Z" - latency: 8.257329ms message: 'load-balancer-api-internal: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:05:37Z" - latency: 3.836452ms message: 'load-balancer-api-internal: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 7.941512ms message: 'load-balancer-api-internal: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:04:37Z" - latency: 3.372097ms message: 'load-balancer-api-internal: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 8.645737ms message: 'load-balancer-api-internal: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:03:37Z" - latency: 5.205714ms message: 'load-balancer-api-internal: tcp connection to aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 7.841771ms message: 'load-balancer-api-internal: resolved host name aa717aab008844f988a4214fb7059392-bb82a67bb276d00e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T17:02:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-ip-10-0-130-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "43841" uid: 6566d7d6-2098-4513-a38c-ebf4f0945729 spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T16:43:37Z" message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.75µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 798.633µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 1.236683ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 1.520516ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:01:37Z" - latency: 830.548µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:00:37Z" - latency: 805.236µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:59:37Z" - latency: 1.273317ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:58:37Z" - latency: 1.031828ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:57:37Z" - latency: 1.509236ms message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:56:37Z" - latency: 795.507µs message: 'network-check-target-ip-10-0-130-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-ip-10-0-136-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "43843" uid: d2fdf81d-76e4-42af-9689-3d7d20b8efdb spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T16:43:37Z" message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.104451ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 2.33988ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 2.350272ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 2.767268ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:01:37Z" - latency: 2.145399ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:00:37Z" - latency: 2.448901ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:59:37Z" - latency: 2.159616ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:58:37Z" - latency: 2.348821ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:57:37Z" - latency: 2.281676ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:56:37Z" - latency: 2.058282ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-ip-10-0-141-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "43842" uid: 45e6e8bb-66b9-47e9-9639-6c26a64bb410 spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T16:43:37Z" message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.945085ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 2.001592ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 1.991489ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 2.620544ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:01:37Z" - latency: 2.194739ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:00:37Z" - latency: 2.042073ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:59:37Z" - latency: 2.052627ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:58:37Z" - latency: 2.286864ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:57:37Z" - latency: 2.038178ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:56:37Z" - latency: 2.469493ms message: 'network-check-target-ip-10-0-141-23: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T16:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T16:36:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-217-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-217.ec2.internal uid: 15ac7b4b-c915-489c-b04e-036fd0560523 resourceVersion: "45817" uid: 3cfede40-09ec-4e21-be96-16735b91f170 spec: sourcePod: network-check-source-7f44b6dd87-r2xzj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T16:42:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.371µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:06:37Z" - latency: 2.231288ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T17:06:37Z" - latency: 1.078852ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:05:37Z" - latency: 1.675438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T17:05:37Z" - latency: 986.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:04:37Z" - latency: 1.465439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T17:04:37Z" - latency: 803.544µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:03:37Z" - latency: 1.889036ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T17:03:37Z" - latency: 941.119µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:02:37Z" - latency: 1.628951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T17:02:37Z" kind: List metadata: resourceVersion: ""