apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62885" uid: 52b33626-0058-4e82-891e-b6a4d0ea8666 spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T16:00:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 810.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 1.129894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 1.134698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 1.298294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 1.158924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:30:28Z" - latency: 2.045252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:29:28Z" - latency: 1.199631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:28:28Z" - latency: 1.141616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:27:28Z" - latency: 1.058995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:26:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62887" uid: b95d7ffd-b212-4cae-9659-f799b8f244dc spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T15:59:28Z" message: 'load-balancer-api-external: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.089324ms message: 'load-balancer-api-external: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 7.258605ms message: 'load-balancer-api-external: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:35:28Z" - latency: 4.421313ms message: 'load-balancer-api-external: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 8.36555ms message: 'load-balancer-api-external: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:34:28Z" - latency: 4.872081ms message: 'load-balancer-api-external: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 6.797243ms message: 'load-balancer-api-external: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:33:28Z" - latency: 5.248952ms message: 'load-balancer-api-external: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 8.09871ms message: 'load-balancer-api-external: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:32:28Z" - latency: 4.280033ms message: 'load-balancer-api-external: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 6.233535ms message: 'load-balancer-api-external: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:31:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62886" uid: b7320358-27ba-469e-88bc-4002af909938 spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T15:59:28Z" message: 'load-balancer-api-internal: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.050693ms message: 'load-balancer-api-internal: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 7.226124ms message: 'load-balancer-api-internal: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:35:28Z" - latency: 4.41535ms message: 'load-balancer-api-internal: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 8.319654ms message: 'load-balancer-api-internal: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:34:28Z" - latency: 4.893855ms message: 'load-balancer-api-internal: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 6.873871ms message: 'load-balancer-api-internal: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:33:28Z" - latency: 5.217633ms message: 'load-balancer-api-internal: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 8.112111ms message: 'load-balancer-api-internal: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:32:28Z" - latency: 4.441389ms message: 'load-balancer-api-internal: tcp connection to ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 6.26655ms message: 'load-balancer-api-internal: resolved host name ab47594fad99f4658b4d26e453ccd306-f9d452a26f3a2f32.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:31:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-network-check-target-ip-10-0-134-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62882" uid: 6cf96153-ddbd-44e7-b5b1-020889e5ba3a spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:00:28Z" message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.230556ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 2.17055ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 2.191ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 2.335365ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 2.231859ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 2.429958ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:30:28Z" - latency: 2.387772ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:29:28Z" - latency: 2.36422ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:28:28Z" - latency: 2.211231ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:27:28Z" - latency: 2.164516ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:26:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-network-check-target-ip-10-0-138-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62881" uid: a2453459-ecfd-472c-8f03-ef458509fca7 spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:00:28Z" message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161906ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 804.132µs message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 964.46µs message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 1.477959ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 1.172136ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 1.046897ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:30:28Z" - latency: 2.20083ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:29:28Z" - latency: 949.497µs message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:28:28Z" - latency: 1.414798ms message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:27:28Z" - latency: 937.487µs message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:26:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-network-check-target-ip-10-0-142-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62884" uid: ccde2668-c2dd-4f90-af49-7affeda630ad spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:00:28Z" message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.986791ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 1.896672ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 1.989492ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 1.96575ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 1.857708ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 1.916565ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:30:28Z" - latency: 2.05579ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:29:28Z" - latency: 1.961527ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:28:28Z" - latency: 1.894946ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:27:28Z" - latency: 2.742312ms message: 'network-check-target-ip-10-0-142-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:26:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T15:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-33-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-33.ec2.internal uid: 4999872b-30f7-426e-a522-782506387d00 resourceVersion: "62883" uid: 75d55877-2b56-49c6-87ed-fea5563e9acb spec: sourcePod: network-check-source-7bc5b6bf85-5bmb5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T15:59:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 836.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:35:28Z" - latency: 1.948149ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:35:28Z" - latency: 966.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:34:28Z" - latency: 1.927435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:34:28Z" - latency: 966.301µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:33:28Z" - latency: 1.712656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:33:28Z" - latency: 747.579µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:32:28Z" - latency: 1.976056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:32:28Z" - latency: 842.18µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:31:28Z" - latency: 1.806881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:31:28Z" kind: List metadata: resourceVersion: ""