apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "24053"
    uid: 057b9daf-ed09-4c6c-9ded-32b249d71b64
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:36:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:36:29Z"
    - latency: 1.502193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 935.022µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 1.836528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 813.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 956.618µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 1.041471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "22920"
    uid: f17a5407-f424-4822-a479-13539bd8a869
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:35:29Z"
      message: 'load-balancer-api-external: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.385107ms
      message: 'load-balancer-api-external: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 7.760159ms
      message: 'load-balancer-api-external: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 3.90962ms
      message: 'load-balancer-api-external: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 7.272318ms
      message: 'load-balancer-api-external: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 3.758646ms
      message: 'load-balancer-api-external: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 9.398724ms
      message: 'load-balancer-api-external: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 3.5996ms
      message: 'load-balancer-api-external: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 8.321996ms
      message: 'load-balancer-api-external: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 3.741911ms
      message: 'load-balancer-api-external: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 8.050297ms
      message: 'load-balancer-api-external: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:31:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "22919"
    uid: 4877e7f4-2b5e-4a88-9661-1bd73c9d0b2b
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:35:29Z"
      message: 'load-balancer-api-internal: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.395186ms
      message: 'load-balancer-api-internal: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 7.845245ms
      message: 'load-balancer-api-internal: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 4.433167ms
      message: 'load-balancer-api-internal: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 7.389057ms
      message: 'load-balancer-api-internal: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 3.743319ms
      message: 'load-balancer-api-internal: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 9.414524ms
      message: 'load-balancer-api-internal: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 3.47711ms
      message: 'load-balancer-api-internal: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 8.398576ms
      message: 'load-balancer-api-internal: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 4.444746ms
      message: 'load-balancer-api-internal: tcp connection to ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 8.109015ms
      message: 'load-balancer-api-internal: resolved host name ad6492a8bbe2b4f8abb4fa1aa11deb95-4ab89290c172be9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:31:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-134-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "24051"
    uid: 1255e01e-940b-4c5a-9a1d-230ad44fbeb6
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:36:29Z"
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.004346ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:36:29Z"
    - latency: 2.5239ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 2.280027ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 2.822071ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 1.926059ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 2.485743ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 2.926189ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-139-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "24050"
    uid: ab947db4-a8f2-4de5-8e87-4959448efe23
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:36:29Z"
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 782.55µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:36:29Z"
    - latency: 727.034µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 789.924µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 2.293286ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 1.297863ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 1.134438ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 1.252437ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-140-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "24052"
    uid: f3bc955c-94d6-43b5-b576-e41b8acc59db
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:36:29Z"
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47662ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:36:29Z"
    - latency: 2.650128ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 2.49911ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 2.691428ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 2.146178ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 2.211975ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 2.34599ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 83b68a32-7288-4bd8-9af2-35b9f1b2e95c
    resourceVersion: "22918"
    uid: 7aa05dac-a317-4896-b08c-17438ced37b5
  spec:
    sourcePod: network-check-source-8894fc9bd-8t9hm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:35:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 1.556918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:35:29Z"
    - latency: 1.097683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 1.61547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:34:29Z"
    - latency: 902.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 2.538463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:33:29Z"
    - latency: 792.552µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 1.770023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:32:29Z"
    - latency: 1.108857ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:31:29Z"
    - latency: 1.619847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:31:29Z"
kind: List
metadata:
  resourceVersion: ""