apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "29271" uid: e19cb83b-f27d-43ba-ab2c-4294b47e28ec spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T11:26:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:33:16Z" - latency: 1.073511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:32:16Z" - latency: 1.107721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 1.208344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 1.011822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 1.008332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 1.029934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 1.300874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:26:16Z" - latency: 1.204805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:25:16Z" - latency: 1.042084ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "27113" uid: b9c6253b-492a-4a20-b024-441840ca35fc spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T11:25:16Z" message: 'load-balancer-api-external: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.026745ms message: 'load-balancer-api-external: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 7.072403ms message: 'load-balancer-api-external: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:31:16Z" - latency: 5.034498ms message: 'load-balancer-api-external: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 7.504665ms message: 'load-balancer-api-external: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:30:16Z" - latency: 5.405756ms message: 'load-balancer-api-external: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 6.447599ms message: 'load-balancer-api-external: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:29:16Z" - latency: 5.161495ms message: 'load-balancer-api-external: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 7.261258ms message: 'load-balancer-api-external: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:28:16Z" - latency: 5.67902ms message: 'load-balancer-api-external: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 7.421307ms message: 'load-balancer-api-external: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:27:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "27112" uid: 0dd280e9-bd75-49a3-bc19-d0268b992f64 spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T11:25:16Z" message: 'load-balancer-api-internal: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.074841ms message: 'load-balancer-api-internal: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 7.015166ms message: 'load-balancer-api-internal: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:31:16Z" - latency: 4.74442ms message: 'load-balancer-api-internal: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 7.313426ms message: 'load-balancer-api-internal: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:30:16Z" - latency: 5.366974ms message: 'load-balancer-api-internal: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 6.536544ms message: 'load-balancer-api-internal: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:29:16Z" - latency: 7.351588ms message: 'load-balancer-api-internal: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 7.162549ms message: 'load-balancer-api-internal: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:28:16Z" - latency: 8.065172ms message: 'load-balancer-api-internal: tcp connection to ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 7.334602ms message: 'load-balancer-api-internal: resolved host name ac770e3eb01aa4c73a205bbbee1af87e-537b87ac01a1d1df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T11:27:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-network-check-target-ip-10-0-139-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "29268" uid: 6bfe10e3-1dff-4d32-b7fb-7be6d374c4d2 spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T11:26:16Z" message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.351574ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:33:16Z" - latency: 966.309µs message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:32:16Z" - latency: 1.26063ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 1.236083ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 1.230654ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 1.67493ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 940.799µs message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 1.3938ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:26:16Z" - latency: 1.392563ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:25:16Z" - latency: 1.29306ms message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-network-check-target-ip-10-0-141-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "29270" uid: f044e63f-921c-4bd5-831d-cc8598d16fee spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T11:26:16Z" message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286264ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:33:16Z" - latency: 2.595698ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:32:16Z" - latency: 2.410046ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 2.485135ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 2.450399ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 2.482125ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 3.261831ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 2.635301ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:26:16Z" - latency: 2.27719ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:25:16Z" - latency: 2.332738ms message: 'network-check-target-ip-10-0-141-138: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-network-check-target-ip-10-0-142-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "29269" uid: 05bda2f2-a466-4fda-8baa-b91c67441639 spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T11:26:16Z" message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.262865ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:33:16Z" - latency: 2.258204ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:32:16Z" - latency: 2.360273ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 2.464128ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 2.090802ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 2.48523ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 2.429466ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 2.562369ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:26:16Z" - latency: 2.375895ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:25:16Z" - latency: 2.474082ms message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:24:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:19:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-35.ec2.internal uid: cae98a16-552b-446f-9dfc-1082803cc008 resourceVersion: "27111" uid: 66bec2f6-5830-4420-8fc5-197f543434eb spec: sourcePod: network-check-source-869dcfcdcd-rjdxb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T11:25:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 837.492µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:31:16Z" - latency: 1.790042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T11:31:16Z" - latency: 940.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:30:16Z" - latency: 2.15283ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T11:30:16Z" - latency: 929.702µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:29:16Z" - latency: 1.699107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T11:29:16Z" - latency: 898.551µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:28:16Z" - latency: 1.80294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T11:28:16Z" - latency: 1.478963ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T11:27:16Z" - latency: 2.058353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T11:27:16Z" kind: List metadata: resourceVersion: ""