apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "23634" uid: a172eb8c-b780-48fb-a386-8bbe80a924f1 spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T16:28:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.090369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:28:17Z" - latency: 940.339µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:27:17Z" - latency: 903.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:26:17Z" - latency: 1.049289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:25:17Z" - latency: 1.24333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:24:17Z" - latency: 1.088419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:23:17Z" - latency: 932.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:22:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "27514" uid: 066410b5-f8e8-44bf-a938-1f08ec10be71 spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T16:27:17Z" message: 'load-balancer-api-external: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.964221ms message: 'load-balancer-api-external: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:17Z" - latency: 7.087467ms message: 'load-balancer-api-external: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:33:17Z" - latency: 4.371767ms message: 'load-balancer-api-external: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:17Z" - latency: 7.012203ms message: 'load-balancer-api-external: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:32:17Z" - latency: 4.436201ms message: 'load-balancer-api-external: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:17Z" - latency: 8.315137ms message: 'load-balancer-api-external: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:31:17Z" - latency: 4.963105ms message: 'load-balancer-api-external: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:17Z" - latency: 8.64595ms message: 'load-balancer-api-external: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:30:17Z" - latency: 5.36056ms message: 'load-balancer-api-external: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:17Z" - latency: 7.360994ms message: 'load-balancer-api-external: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:29:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "27511" uid: 71c3de82-083c-4245-85ba-be30e8495179 spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T16:27:17Z" message: 'load-balancer-api-internal: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.937971ms message: 'load-balancer-api-internal: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:17Z" - latency: 7.230146ms message: 'load-balancer-api-internal: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:33:17Z" - latency: 5.36806ms message: 'load-balancer-api-internal: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:17Z" - latency: 6.941717ms message: 'load-balancer-api-internal: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:32:17Z" - latency: 4.380635ms message: 'load-balancer-api-internal: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:17Z" - latency: 8.362678ms message: 'load-balancer-api-internal: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:31:17Z" - latency: 4.977641ms message: 'load-balancer-api-internal: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:17Z" - latency: 8.658793ms message: 'load-balancer-api-internal: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:30:17Z" - latency: 5.393735ms message: 'load-balancer-api-internal: tcp connection to abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:17Z" - latency: 7.309805ms message: 'load-balancer-api-internal: resolved host name abe24558c0b8d4bc4a616130ddca0b21-e2e5009348c51030.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T16:29:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-network-check-target-ip-10-0-128-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "23633" uid: 491753b1-ad62-4748-bb5d-84bd887c82df spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T16:28:17Z" message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.947585ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:28:17Z" - latency: 2.002373ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:27:17Z" - latency: 1.923409ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:26:17Z" - latency: 1.968554ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:25:17Z" - latency: 2.01902ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:24:17Z" - latency: 1.757833ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:23:17Z" - latency: 1.977681ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:22:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-network-check-target-ip-10-0-133-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "23631" uid: 0517c180-a09a-4cd2-865f-d16274531d2b spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T16:28:17Z" message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.019µs message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:28:17Z" - latency: 922.935µs message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:27:17Z" - latency: 838.706µs message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:26:17Z" - latency: 928.262µs message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:25:17Z" - latency: 1.375615ms message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:24:17Z" - latency: 1.359323ms message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:23:17Z" - latency: 1.393284ms message: 'network-check-target-ip-10-0-133-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:22:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-network-check-target-ip-10-0-139-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "23632" uid: dabf7936-6b47-4169-b004-5307be92eda9 spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T16:28:17Z" message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.898152ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:28:17Z" - latency: 2.038666ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:27:17Z" - latency: 1.917092ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:26:17Z" - latency: 1.971841ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:25:17Z" - latency: 1.706544ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:24:17Z" - latency: 2.032388ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:23:17Z" - latency: 2.256653ms message: 'network-check-target-ip-10-0-139-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:22:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T16:21:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-169.ec2.internal uid: d496700f-c1f2-4355-95f1-138fc1dc63c6 resourceVersion: "27510" uid: 80804e78-f2b4-4a01-9e17-fc3704264a8b spec: sourcePod: network-check-source-56d84b9f44-skggv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T16:27:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.262011ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:33:17Z" - latency: 1.708885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:33:17Z" - latency: 892.639µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:32:17Z" - latency: 1.850416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:32:17Z" - latency: 824.59µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:31:17Z" - latency: 1.789376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:31:17Z" - latency: 859.198µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:30:17Z" - latency: 1.8427ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:30:17Z" - latency: 901.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T16:29:17Z" - latency: 2.088234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T16:29:17Z" kind: List metadata: resourceVersion: ""