apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "43669" uid: cac307d1-0b4c-4192-891c-5f3d326c6c1d spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-22T10:44:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.264235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 1.319583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 978.76µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 1.01284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:02:52Z" - latency: 799.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:01:52Z" - latency: 1.127119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:00:52Z" - latency: 806.244µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:59:52Z" - latency: 908.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:58:52Z" - latency: 1.155024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:57:52Z" - latency: 1.058633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:56:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "45828" uid: c57c8f6d-976b-48e0-a28d-24fc91c3470e spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-22T10:43:52Z" message: 'load-balancer-api-external: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.423714ms message: 'load-balancer-api-external: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:07:52Z" - latency: 7.06154ms message: 'load-balancer-api-external: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:07:52Z" - latency: 4.343292ms message: 'load-balancer-api-external: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:06:52Z" - latency: 9.174368ms message: 'load-balancer-api-external: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:06:52Z" - latency: 4.047014ms message: 'load-balancer-api-external: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 7.715126ms message: 'load-balancer-api-external: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:05:52Z" - latency: 3.556644ms message: 'load-balancer-api-external: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 6.869305ms message: 'load-balancer-api-external: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:04:52Z" - latency: 3.814978ms message: 'load-balancer-api-external: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 8.566841ms message: 'load-balancer-api-external: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:03:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "45827" uid: 607af381-6511-4e5b-b269-86195e0c6571 spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-22T10:43:52Z" message: 'load-balancer-api-internal: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.956669ms message: 'load-balancer-api-internal: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:07:52Z" - latency: 6.959446ms message: 'load-balancer-api-internal: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:07:52Z" - latency: 4.333864ms message: 'load-balancer-api-internal: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:06:52Z" - latency: 9.088505ms message: 'load-balancer-api-internal: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:06:52Z" - latency: 4.39895ms message: 'load-balancer-api-internal: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 7.485409ms message: 'load-balancer-api-internal: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:05:52Z" - latency: 3.546009ms message: 'load-balancer-api-internal: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 6.893438ms message: 'load-balancer-api-internal: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:04:52Z" - latency: 3.819955ms message: 'load-balancer-api-internal: tcp connection to a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 8.499167ms message: 'load-balancer-api-internal: resolved host name a656eb0fcce8a4007b8965ffd148c47c-621c44e2bd0531bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-22T11:03:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-129-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "43666" uid: 7da192e8-495a-472c-a7ae-ea7458aeaf43 spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-22T10:44:52Z" message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.607443ms message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 1.797077ms message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 871.587µs message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 1.117937ms message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:02:52Z" - latency: 825.102µs message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:01:52Z" - latency: 855.343µs message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:00:52Z" - latency: 1.063626ms message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:59:52Z" - latency: 1.434916ms message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:58:52Z" - latency: 850.936µs message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:57:52Z" - latency: 797.064µs message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:56:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-138-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "43667" uid: 6d2403c8-4f22-4cba-8d74-84ea104b2284 spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-22T10:44:52Z" message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.855181ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 1.765256ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 1.976648ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 1.939875ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:02:52Z" - latency: 1.824781ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:01:52Z" - latency: 2.13363ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:00:52Z" - latency: 2.076091ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:59:52Z" - latency: 2.033323ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:58:52Z" - latency: 2.000159ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:57:52Z" - latency: 1.909761ms message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:56:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-142-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "43668" uid: 24ba59ac-19b3-413b-809d-7aa9c80eec76 spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-22T10:44:52Z" message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.37166ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 2.129735ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 2.066687ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 2.415516ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:02:52Z" - latency: 2.105873ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:01:52Z" - latency: 1.982813ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:00:52Z" - latency: 2.224436ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:59:52Z" - latency: 2.326467ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:58:52Z" - latency: 1.958787ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:57:52Z" - latency: 2.148682ms message: 'network-check-target-ip-10-0-142-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-22T10:56:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-22T10:37:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-37-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-37.ec2.internal uid: 8a434fbe-0d95-4fd0-a119-81fe9664ad42 resourceVersion: "45826" uid: f3fffa67-eb4b-43f8-af09-396254876707 spec: sourcePod: network-check-source-7f44b6dd87-gjxzn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-22T10:43:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 819.355µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:07:52Z" - latency: 1.796206ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-22T11:07:52Z" - latency: 794.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:06:52Z" - latency: 2.099603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-22T11:06:52Z" - latency: 832.028µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:05:52Z" - latency: 2.345993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-22T11:05:52Z" - latency: 822.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:04:52Z" - latency: 2.592285ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-22T11:04:52Z" - latency: 780.771µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-22T11:03:52Z" - latency: 1.76776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-22T11:03:52Z" kind: List metadata: resourceVersion: ""