apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "29142" uid: ec8cce14-3c6d-4746-b06a-3b1c234668db spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T15:13:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.12191ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:20:02Z" - latency: 905.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:19:02Z" - latency: 833.209µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 1.425545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 810.06µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 980µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 1.258154ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 1.250191ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:13:02Z" - latency: 862.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:12:02Z" - latency: 965.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "27599" uid: 21780bc3-46f4-43fd-8967-cdc4dd12bce3 spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T15:12:02Z" message: 'load-balancer-api-external: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.280866ms message: 'load-balancer-api-external: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 6.23561ms message: 'load-balancer-api-external: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:18:02Z" - latency: 5.221064ms message: 'load-balancer-api-external: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 7.15634ms message: 'load-balancer-api-external: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:17:02Z" - latency: 4.37723ms message: 'load-balancer-api-external: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 6.433117ms message: 'load-balancer-api-external: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:16:02Z" - latency: 4.060109ms message: 'load-balancer-api-external: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 7.156799ms message: 'load-balancer-api-external: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:15:02Z" - latency: 4.158485ms message: 'load-balancer-api-external: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 6.107218ms message: 'load-balancer-api-external: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:14:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "27598" uid: 08f736f4-beb4-4beb-884f-737735ef3ae5 spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T15:12:02Z" message: 'load-balancer-api-internal: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.237641ms message: 'load-balancer-api-internal: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 6.115412ms message: 'load-balancer-api-internal: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:18:02Z" - latency: 5.194364ms message: 'load-balancer-api-internal: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 7.204598ms message: 'load-balancer-api-internal: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:17:02Z" - latency: 4.394052ms message: 'load-balancer-api-internal: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 6.529803ms message: 'load-balancer-api-internal: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:16:02Z" - latency: 4.045282ms message: 'load-balancer-api-internal: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 7.223416ms message: 'load-balancer-api-internal: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:15:02Z" - latency: 5.025485ms message: 'load-balancer-api-internal: tcp connection to a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 6.143022ms message: 'load-balancer-api-internal: resolved host name a62da06dd13414e75aeb166d41c36bb3-f91f6f2c12547689.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T15:14:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-130-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "29139" uid: 9b5fa9fa-8763-49d4-9a56-84b40e853585 spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T15:13:02Z" message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.205076ms message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:20:02Z" - latency: 974.117µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:19:02Z" - latency: 987.099µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 991.011µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 1.543722ms message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 746.218µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 1.332943ms message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 899.436µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:13:02Z" - latency: 928.075µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:12:02Z" - latency: 888.748µs message: 'network-check-target-ip-10-0-130-78: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-133-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "29141" uid: e4b15aa9-7874-4849-bd24-84b512e2c4c3 spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T15:13:02Z" message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.450268ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:20:02Z" - latency: 1.917148ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:19:02Z" - latency: 2.469879ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 2.307092ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 2.236697ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 2.14997ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 1.937399ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 2.290071ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:13:02Z" - latency: 2.132877ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:12:02Z" - latency: 2.200301ms message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-ip-10-0-133-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "29140" uid: 206b4b44-aaff-4cc1-bc6e-097760e614a9 spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T15:13:02Z" message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.437013ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:20:02Z" - latency: 2.288149ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:19:02Z" - latency: 2.421914ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 2.244361ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 2.280276ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 2.527879ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 2.223373ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 2.304374ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:13:02Z" - latency: 2.500057ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:12:02Z" - latency: 2.565245ms message: 'network-check-target-ip-10-0-133-25: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:11:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T15:06:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-78-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-78.ec2.internal uid: eec7a557-b8dc-4731-9370-4dd70f92835d resourceVersion: "27597" uid: 122b3087-28de-45d6-8ffd-768adc49b23b spec: sourcePod: network-check-source-56d84b9f44-rdm7h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T15:12:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:18:02Z" - latency: 1.548165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T15:18:02Z" - latency: 707.611µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:17:02Z" - latency: 2.278962ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T15:17:02Z" - latency: 906.263µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:16:02Z" - latency: 1.877879ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T15:16:02Z" - latency: 819.506µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:15:02Z" - latency: 1.674077ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T15:15:02Z" - latency: 1.057906ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T15:14:02Z" - latency: 1.584004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T15:14:02Z" kind: List metadata: resourceVersion: ""