apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "10896" uid: a0847ebc-ae22-415c-868c-2ae14b8f301b spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: 172.31.0.1:443 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "14463" uid: 1f5f3049-1388-4319-a506-25d1eb76fa05 spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T13:06:26Z" message: 'load-balancer-api-external: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.332774ms message: 'load-balancer-api-external: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:06:26Z" - latency: 12.858298ms message: 'load-balancer-api-external: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:06:26Z" - latency: 6.905713ms message: 'load-balancer-api-external: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:05:26Z" - latency: 9.033309ms message: 'load-balancer-api-external: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:05:26Z" - latency: 5.454993ms message: 'load-balancer-api-external: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:04:26Z" - latency: 8.018323ms message: 'load-balancer-api-external: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:04:26Z" - latency: 5.197402ms message: 'load-balancer-api-external: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:03:26Z" - latency: 15.443681ms message: 'load-balancer-api-external: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:03:26Z" - latency: 5.798239ms message: 'load-balancer-api-external: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:02:26Z" - latency: 8.82894ms message: 'load-balancer-api-external: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:02:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "14462" uid: d844faf9-0960-40a7-8832-aca8373f7b23 spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T13:06:26Z" message: 'load-balancer-api-internal: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.349097ms message: 'load-balancer-api-internal: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:06:26Z" - latency: 12.763371ms message: 'load-balancer-api-internal: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:06:26Z" - latency: 5.254231ms message: 'load-balancer-api-internal: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:05:26Z" - latency: 8.962515ms message: 'load-balancer-api-internal: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:05:26Z" - latency: 5.198679ms message: 'load-balancer-api-internal: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:04:26Z" - latency: 7.940999ms message: 'load-balancer-api-internal: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:04:26Z" - latency: 5.200547ms message: 'load-balancer-api-internal: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:03:26Z" - latency: 15.478129ms message: 'load-balancer-api-internal: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:03:26Z" - latency: 5.73418ms message: 'load-balancer-api-internal: tcp connection to a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:02:26Z" - latency: 8.62981ms message: 'load-balancer-api-internal: resolved host name a88cb2c9ebb0b4056bf970d6108f8d00-5b715ab75257ecf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T13:02:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-ip-10-0-133-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "10892" uid: 1d8f7716-b1d1-41f5-bc30-c297a3590a8d spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: 10.132.0.5:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-ip-10-0-141-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "10893" uid: 59784dd9-c5f0-4073-8a48-d59e57f58bb6 spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: 10.133.0.4:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-ip-10-0-141-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "10894" uid: b427fbcb-ff9c-47af-a0fe-d07a45f7c145 spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: 10.134.0.4:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T13:00:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 5f90b780-7fd2-4f27-a4cd-764b125a1c7a resourceVersion: "14461" uid: cd5b9e3f-6898-4de6-a076-6a5d0e36d5d5 spec: sourcePod: network-check-source-7bc5b6bf85-4v57b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T13:06:26Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.502163ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:06:26Z" - latency: 1.754103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:06:26Z" - latency: 998.999µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:05:26Z" - latency: 1.976966ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:05:26Z" - latency: 946.67µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:04:26Z" - latency: 1.7727ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:04:26Z" - latency: 822.71µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:03:26Z" - latency: 1.67514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:03:26Z" - latency: 890.826µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T13:02:26Z" - latency: 2.417773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T13:02:26Z" kind: List metadata: resourceVersion: ""