apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63285" uid: 39b28942-be78-458b-834e-8d7e5b1b906b spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T11:35:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 1.019586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 866.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 845.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 1.321572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 1.002045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:05:24Z" - latency: 946.177µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:04:24Z" - latency: 1.048737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:03:24Z" - latency: 1.063318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:02:24Z" - latency: 1.300606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:01:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63287" uid: e925dcd0-26c8-44d7-ac77-7f9454be2ad0 spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T11:34:24Z" message: 'load-balancer-api-external: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.67217ms message: 'load-balancer-api-external: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 9.678708ms message: 'load-balancer-api-external: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:10:24Z" - latency: 4.315714ms message: 'load-balancer-api-external: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 7.390713ms message: 'load-balancer-api-external: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:09:24Z" - latency: 5.643685ms message: 'load-balancer-api-external: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 8.997894ms message: 'load-balancer-api-external: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:08:24Z" - latency: 4.703535ms message: 'load-balancer-api-external: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 8.517424ms message: 'load-balancer-api-external: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:07:24Z" - latency: 3.977305ms message: 'load-balancer-api-external: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 7.907885ms message: 'load-balancer-api-external: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:06:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63286" uid: 294e9e48-bded-42f5-b16b-a5f9d5a26332 spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T11:34:24Z" message: 'load-balancer-api-internal: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.726213ms message: 'load-balancer-api-internal: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 9.577239ms message: 'load-balancer-api-internal: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:10:24Z" - latency: 3.893599ms message: 'load-balancer-api-internal: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 7.34288ms message: 'load-balancer-api-internal: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:09:24Z" - latency: 6.503725ms message: 'load-balancer-api-internal: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 8.885647ms message: 'load-balancer-api-internal: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:08:24Z" - latency: 4.765798ms message: 'load-balancer-api-internal: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 8.430468ms message: 'load-balancer-api-internal: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:07:24Z" - latency: 4.688673ms message: 'load-balancer-api-internal: tcp connection to aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 7.751673ms message: 'load-balancer-api-internal: resolved host name aba1dd5b79e2d4f89a0a7347de7656f1-7b0f9e2d5257c4e5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T12:06:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-135-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63283" uid: cb50ed35-fefe-407a-8cab-af8c7f3d8c7f spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T11:35:24Z" message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.625083ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 2.116377ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 2.072274ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 2.015432ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 2.199985ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 2.393222ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:05:24Z" - latency: 2.227959ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:04:24Z" - latency: 2.477794ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:03:24Z" - latency: 2.564116ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:02:24Z" - latency: 1.976238ms message: 'network-check-target-ip-10-0-135-12: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:01:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-136-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63281" uid: 874c8101-25b1-428b-8f94-6c9fd38eaf56 spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T11:35:24Z" message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020373ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 926.443µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 1.143869ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 829.278µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 836.104µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 950.996µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:05:24Z" - latency: 1.33441ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:04:24Z" - latency: 1.222805ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:03:24Z" - latency: 810.332µs message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:02:24Z" - latency: 1.174596ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:01:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-136-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63282" uid: dafcc781-fec3-46f3-9ad6-a7a4536ac4d5 spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T11:35:24Z" message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.056412ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 2.055453ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 1.892889ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 2.176293ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 1.974315ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 2.064677ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:05:24Z" - latency: 1.92211ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:04:24Z" - latency: 2.030952ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:03:24Z" - latency: 1.879673ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:02:24Z" - latency: 2.197401ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:01:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T11:28:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-126-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-126.ec2.internal uid: a8527ad6-72b5-4c33-b645-1d49a33aaccc resourceVersion: "63284" uid: 8cfb0b7a-1365-4999-925f-9c49e1c3dbd5 spec: sourcePod: network-check-source-7bc5b6bf85-nhh8f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T11:34:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.863µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:10:24Z" - latency: 2.477654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:10:24Z" - latency: 979.244µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:09:24Z" - latency: 2.235112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:09:24Z" - latency: 1.019328ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:08:24Z" - latency: 1.591798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:08:24Z" - latency: 1.170936ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:07:24Z" - latency: 1.644993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:07:24Z" - latency: 1.151691ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T12:06:24Z" - latency: 1.835757ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T12:06:24Z" kind: List metadata: resourceVersion: ""