apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "23652" uid: 7856e9c8-2449-435b-bc6f-eb47abe660b3 spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T16:30:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 995.579µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:37:21Z" - latency: 1.09083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:36:21Z" - latency: 1.025848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 1.027816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 1.119243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 1.059226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 1.08504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 1.063434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:21Z" - latency: 979.532µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:21Z" - latency: 1.087529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "22513" uid: 06937091-9ad8-4a99-ad35-5bd1b270dc11 spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T16:29:21Z" message: 'load-balancer-api-external: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.180728ms message: 'load-balancer-api-external: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 8.919273ms message: 'load-balancer-api-external: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:35:21Z" - latency: 5.738397ms message: 'load-balancer-api-external: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 8.827227ms message: 'load-balancer-api-external: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:34:21Z" - latency: 5.081232ms message: 'load-balancer-api-external: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 9.264992ms message: 'load-balancer-api-external: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:33:21Z" - latency: 5.228925ms message: 'load-balancer-api-external: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 8.716938ms message: 'load-balancer-api-external: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:32:21Z" - latency: 4.87939ms message: 'load-balancer-api-external: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 7.702013ms message: 'load-balancer-api-external: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:31:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "22514" uid: 40786c63-a3fb-4025-816e-2b8836bf107c spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T16:29:21Z" message: 'load-balancer-api-internal: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.754934ms message: 'load-balancer-api-internal: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 8.887952ms message: 'load-balancer-api-internal: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:35:21Z" - latency: 5.685763ms message: 'load-balancer-api-internal: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 8.931046ms message: 'load-balancer-api-internal: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:34:21Z" - latency: 5.141887ms message: 'load-balancer-api-internal: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 9.207293ms message: 'load-balancer-api-internal: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:33:21Z" - latency: 5.23725ms message: 'load-balancer-api-internal: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 8.769072ms message: 'load-balancer-api-internal: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:32:21Z" - latency: 4.83985ms message: 'load-balancer-api-internal: tcp connection to aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 7.610755ms message: 'load-balancer-api-internal: resolved host name aebbe949d2e8046c4b3447d36179749a-5992f225e884bf66.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:31:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-network-check-target-ip-10-0-134-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "23650" uid: 779a8d19-0a2b-4c25-8758-16c3ac55feb6 spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T16:30:21Z" message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.948133ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:37:21Z" - latency: 2.153908ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:36:21Z" - latency: 2.204522ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 2.319247ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 2.018967ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 2.155589ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 1.929454ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 2.136702ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:21Z" - latency: 2.209401ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:21Z" - latency: 2.237217ms message: 'network-check-target-ip-10-0-134-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-network-check-target-ip-10-0-141-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "23649" uid: b4aeed12-c557-438b-bb3a-c18be2872ce4 spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T16:30:21Z" message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 869.918µs message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:37:21Z" - latency: 1.39576ms message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:36:21Z" - latency: 910.039µs message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 896.971µs message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 954.849µs message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 1.565363ms message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 895.71µs message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 1.261394ms message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:21Z" - latency: 965.794µs message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:21Z" - latency: 1.517146ms message: 'network-check-target-ip-10-0-141-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-network-check-target-ip-10-0-141-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "23651" uid: 995e4ce3-4039-4921-88a9-aac65057bde8 spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T16:30:21Z" message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.836606ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:37:21Z" - latency: 2.616185ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:36:21Z" - latency: 2.248971ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 2.04372ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 1.949947ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 1.845834ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 1.966579ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 2.084149ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:30:21Z" - latency: 2.093465ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:29:21Z" - latency: 2.171831ms message: 'network-check-target-ip-10-0-141-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T16:23:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-20-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-20.ec2.internal uid: c2963eff-bc3c-4c53-baa9-170d9ad80a7c resourceVersion: "22511" uid: f218ad81-0e65-4463-8db5-fb5a8954784a spec: sourcePod: network-check-source-7d88cb55d8-5vhrv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T16:29:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.258427ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:35:21Z" - latency: 1.839357ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:35:21Z" - latency: 949.934µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:34:21Z" - latency: 1.948683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:34:21Z" - latency: 977.751µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:33:21Z" - latency: 1.928079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:33:21Z" - latency: 1.192074ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:32:21Z" - latency: 1.614234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:32:21Z" - latency: 915.128µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:31:21Z" - latency: 1.716058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:31:21Z" kind: List metadata: resourceVersion: ""