apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "20811" uid: d60978bc-d89a-47cf-b00b-32c4fefdddbe spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T23:20:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.034068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 863.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 950.358µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:27Z" - latency: 1.277965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:27Z" - latency: 933.125µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:27Z" - latency: 1.177612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:27Z" - latency: 971.636µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:27Z" - latency: 865.71µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:27Z" - latency: 803.887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:27Z" - latency: 980.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "22244" uid: 9f72e6bc-dd46-4740-96d0-4fb3775ae62d spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T23:19:27Z" message: 'load-balancer-api-external: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.419798ms message: 'load-balancer-api-external: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:37:27Z" - latency: 7.709763ms message: 'load-balancer-api-external: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:37:27Z" - latency: 4.123152ms message: 'load-balancer-api-external: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:36:27Z" - latency: 8.54027ms message: 'load-balancer-api-external: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:36:27Z" - latency: 4.702143ms message: 'load-balancer-api-external: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:35:27Z" - latency: 8.640002ms message: 'load-balancer-api-external: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:35:27Z" - latency: 4.683508ms message: 'load-balancer-api-external: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 8.811985ms message: 'load-balancer-api-external: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:34:27Z" - latency: 4.740272ms message: 'load-balancer-api-external: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 10.81165ms message: 'load-balancer-api-external: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:33:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "22243" uid: 6426ae63-0591-49c9-851a-9a1aa837159d spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T23:19:27Z" message: 'load-balancer-api-internal: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.331366ms message: 'load-balancer-api-internal: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:37:27Z" - latency: 7.679979ms message: 'load-balancer-api-internal: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:37:27Z" - latency: 4.39127ms message: 'load-balancer-api-internal: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:36:27Z" - latency: 8.728572ms message: 'load-balancer-api-internal: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:36:27Z" - latency: 5.001293ms message: 'load-balancer-api-internal: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:35:27Z" - latency: 8.687525ms message: 'load-balancer-api-internal: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:35:27Z" - latency: 3.681555ms message: 'load-balancer-api-internal: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 8.864958ms message: 'load-balancer-api-internal: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:34:27Z" - latency: 4.716433ms message: 'load-balancer-api-internal: tcp connection to a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 10.785036ms message: 'load-balancer-api-internal: resolved host name a1221b8a3cfcd4e738fabf7920f9d087-fa62578265f58b8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T23:33:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-network-check-target-ip-10-0-134-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "20808" uid: 20648615-0f8f-45ee-89da-150c17a4a200 spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:20:27Z" message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.56749ms message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 1.143344ms message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 1.062901ms message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:27Z" - latency: 976.652µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:27Z" - latency: 845.22µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:27Z" - latency: 819.179µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:27Z" - latency: 932.94µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:27Z" - latency: 750.82µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:27Z" - latency: 792.753µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:27Z" - latency: 778.778µs message: 'network-check-target-ip-10-0-134-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-network-check-target-ip-10-0-137-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "20810" uid: 71e40886-6154-4aa7-8002-876b0d00c3a7 spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:20:27Z" message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.304986ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 2.117464ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 2.204711ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:27Z" - latency: 1.985631ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:27Z" - latency: 2.597303ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:27Z" - latency: 2.379607ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:27Z" - latency: 2.1465ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:27Z" - latency: 2.122181ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:27Z" - latency: 2.234269ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:27Z" - latency: 2.156237ms message: 'network-check-target-ip-10-0-137-2: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-network-check-target-ip-10-0-138-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "20809" uid: b53c352f-c918-48ac-904a-60ebfa1b46f1 spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:20:27Z" message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.348488ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 1.958848ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 2.049117ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:32:27Z" - latency: 2.192558ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:31:27Z" - latency: 2.315282ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:30:27Z" - latency: 2.243278ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:29:27Z" - latency: 2.118675ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:28:27Z" - latency: 2.236768ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:27:27Z" - latency: 1.902739ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:26:27Z" - latency: 2.203561ms message: 'network-check-target-ip-10-0-138-124: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:25:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:13:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-32.ec2.internal uid: 19720fc2-a1a2-42f3-8c78-7de9f2f8cdc8 resourceVersion: "22242" uid: bdcc0f04-7f59-4ec4-bf55-d277074071d8 spec: sourcePod: network-check-source-6947749cfc-gwgvf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T23:19:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 981.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:37:27Z" - latency: 1.532993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:37:27Z" - latency: 836.272µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:36:27Z" - latency: 1.632172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:36:27Z" - latency: 1.196689ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:35:27Z" - latency: 1.735837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:35:27Z" - latency: 953.055µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:34:27Z" - latency: 2.011788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:34:27Z" - latency: 825.283µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:33:27Z" - latency: 1.473236ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T23:33:27Z" kind: List metadata: resourceVersion: ""