apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14804"
    uid: a7cdbe5d-7bcf-434a-907f-2aacf27c8b1a
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:06:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:23Z"
    - latency: 885.918µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 1.066582ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 1.03334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 866.194µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 827.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 1.074883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14447"
    uid: 76f0cbfe-24b7-4be9-a5b6-203a38c31997
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:23Z"
      message: 'load-balancer-api-external: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.208928ms
      message: 'load-balancer-api-external: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 7.619831ms
      message: 'load-balancer-api-external: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 5.981475ms
      message: 'load-balancer-api-external: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 8.209869ms
      message: 'load-balancer-api-external: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 4.278944ms
      message: 'load-balancer-api-external: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 8.43649ms
      message: 'load-balancer-api-external: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 4.597425ms
      message: 'load-balancer-api-external: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 8.725904ms
      message: 'load-balancer-api-external: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 6.208392ms
      message: 'load-balancer-api-external: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 8.276042ms
      message: 'load-balancer-api-external: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:01:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14448"
    uid: 71a79779-4535-42c7-af78-5f8e9319f15d
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:23Z"
      message: 'load-balancer-api-internal: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.90376ms
      message: 'load-balancer-api-internal: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 7.639863ms
      message: 'load-balancer-api-internal: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 5.989886ms
      message: 'load-balancer-api-internal: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 8.231379ms
      message: 'load-balancer-api-internal: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 4.331362ms
      message: 'load-balancer-api-internal: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 8.518708ms
      message: 'load-balancer-api-internal: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 4.694731ms
      message: 'load-balancer-api-internal: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 8.742118ms
      message: 'load-balancer-api-internal: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 4.372519ms
      message: 'load-balancer-api-internal: tcp connection to a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 8.152587ms
      message: 'load-balancer-api-internal: resolved host name a9d832d9b7e67427599f19facb62babe-7bf74c8fff72b2a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:01:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-128-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14803"
    uid: e8275e0b-836e-4cd1-9f2b-1618599c488a
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:06:23Z"
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.959411ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:23Z"
    - latency: 2.196917ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 2.216693ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 2.247345ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 2.349255ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 2.231512ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 2.193557ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14801"
    uid: 59cd46cb-5653-4268-9a3b-668aee81e1fb
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:06:23Z"
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 765.429µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:23Z"
    - latency: 1.023418ms
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 977.463µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 1.363515ms
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 890.259µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 968.576µs
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 1.530348ms
      message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-143-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14802"
    uid: f4b062f8-c04d-4eff-84b8-19f1684d4cc2
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:06:23Z"
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.587412ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:06:23Z"
    - latency: 1.807729ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 1.688643ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 1.96889ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 1.826965ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 1.774389ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 2.157416ms
      message: 'network-check-target-ip-10-0-143-166: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-52.ec2.internal
      uid: 086def55-1ba9-4a52-bea9-00f225b10ac8
    resourceVersion: "14446"
    uid: 5714c405-6d87-49bc-b6de-42fe68835de3
  spec:
    sourcePod: network-check-source-6f8b768455-phtg9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109286ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 1.644808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:05:23Z"
    - latency: 888.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 1.690819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:23Z"
    - latency: 1.099238ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 1.712946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:03:23Z"
    - latency: 796.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 1.786117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:02:23Z"
    - latency: 839.949µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:23Z"
    - latency: 1.736712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:01:23Z"
kind: List
metadata:
  resourceVersion: ""