apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17922" uid: 6bbad78d-2b53-4cc5-b794-709b816d5565 spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T10:28:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.821µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:35:35Z" - latency: 1.091404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:34:35Z" - latency: 1.005841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 1.168648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 1.005669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 800.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 1.020443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 1.014777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:28:35Z" - latency: 809.735µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:27:35Z" - latency: 1.353736ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:26:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17164" uid: 833b8821-9acb-451f-87b0-666cc0643064 spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T10:27:35Z" message: 'load-balancer-api-external: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.587528ms message: 'load-balancer-api-external: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 6.671864ms message: 'load-balancer-api-external: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:33:35Z" - latency: 4.10806ms message: 'load-balancer-api-external: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 7.695744ms message: 'load-balancer-api-external: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:32:35Z" - latency: 4.139248ms message: 'load-balancer-api-external: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 7.39393ms message: 'load-balancer-api-external: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:31:35Z" - latency: 6.375228ms message: 'load-balancer-api-external: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 6.692588ms message: 'load-balancer-api-external: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:30:35Z" - latency: 4.721615ms message: 'load-balancer-api-external: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 7.583061ms message: 'load-balancer-api-external: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:29:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17163" uid: 9fe8d6cd-49d5-4599-817b-932150fda675 spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T10:27:35Z" message: 'load-balancer-api-internal: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.544522ms message: 'load-balancer-api-internal: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 6.625874ms message: 'load-balancer-api-internal: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:33:35Z" - latency: 5.894556ms message: 'load-balancer-api-internal: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 7.776692ms message: 'load-balancer-api-internal: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:32:35Z" - latency: 4.107624ms message: 'load-balancer-api-internal: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 7.344941ms message: 'load-balancer-api-internal: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:31:35Z" - latency: 6.366849ms message: 'load-balancer-api-internal: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 6.781562ms message: 'load-balancer-api-internal: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:30:35Z" - latency: 4.734372ms message: 'load-balancer-api-internal: tcp connection to a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 7.504003ms message: 'load-balancer-api-internal: resolved host name a77a474ca97204a18a751000cd24a55b-ae18a8f489841682.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T10:29:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-network-check-target-ip-10-0-140-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17919" uid: 92a0ed2c-40ef-404a-ac4a-7eb6a678fbf7 spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T10:28:35Z" message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.038399ms message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:35:35Z" - latency: 826.124µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:34:35Z" - latency: 833.115µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 891.954µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 716.878µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 986.932µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 895.211µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 1.159323ms message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:28:35Z" - latency: 1.515952ms message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:27:35Z" - latency: 813.972µs message: 'network-check-target-ip-10-0-140-176: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:26:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-network-check-target-ip-10-0-141-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17920" uid: f269f659-2ccb-4829-b65a-5da5c1119838 spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T10:28:35Z" message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.256025ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:35:35Z" - latency: 1.99522ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:34:35Z" - latency: 2.005815ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 2.283103ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 2.113415ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 2.004809ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 2.214034ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 1.881814ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:28:35Z" - latency: 2.030973ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:27:35Z" - latency: 2.026564ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:26:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-network-check-target-ip-10-0-141-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17921" uid: ca7e9a76-cfa9-4528-aa57-e0e4f0c042a0 spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T10:28:35Z" message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.972115ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:35:35Z" - latency: 2.081883ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:34:35Z" - latency: 2.24391ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 1.934511ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 2.058269ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 1.807686ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 1.931317ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 1.957808ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:28:35Z" - latency: 2.168626ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:27:35Z" - latency: 1.827437ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:26:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T10:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-176.ec2.internal uid: 14d4b6cb-e652-4890-8d76-46e50f8494ce resourceVersion: "17162" uid: 800c64c7-b96b-4acd-9f5b-4eabf4fa2f8e spec: sourcePod: network-check-source-dbd9cf844-82z77 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T10:27:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.192857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:33:35Z" - latency: 1.670072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T10:33:35Z" - latency: 1.417858ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:32:35Z" - latency: 1.642648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T10:32:35Z" - latency: 758.754µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:31:35Z" - latency: 1.658033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T10:31:35Z" - latency: 681.811µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:30:35Z" - latency: 1.716411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T10:30:35Z" - latency: 720.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T10:29:35Z" - latency: 1.638681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T10:29:35Z" kind: List metadata: resourceVersion: ""