apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "10852"
    uid: 4a99f493-f751-4ea1-ac95-0bed1baa83dc
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "14210"
    uid: 88baf53b-35fd-446c-9a69-a939aee47134
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:27:38Z"
      message: 'load-balancer-api-external: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.338204ms
      message: 'load-balancer-api-external: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:27:38Z"
    - latency: 10.474431ms
      message: 'load-balancer-api-external: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:27:38Z"
    - latency: 6.077796ms
      message: 'load-balancer-api-external: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:26:38Z"
    - latency: 10.010925ms
      message: 'load-balancer-api-external: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:26:38Z"
    - latency: 5.251367ms
      message: 'load-balancer-api-external: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:25:38Z"
    - latency: 9.07649ms
      message: 'load-balancer-api-external: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:25:38Z"
    - latency: 10.131318ms
      message: 'load-balancer-api-external: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:24:38Z"
    - latency: 6.496763ms
      message: 'load-balancer-api-external: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:24:38Z"
    - latency: 7.859743ms
      message: 'load-balancer-api-external: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:23:38Z"
    - latency: 11.71516ms
      message: 'load-balancer-api-external: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:23:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "14211"
    uid: ad30eb0e-099b-434a-a2fb-270ee5401582
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:27:38Z"
      message: 'load-balancer-api-internal: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.12951ms
      message: 'load-balancer-api-internal: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:27:38Z"
    - latency: 10.440512ms
      message: 'load-balancer-api-internal: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:27:38Z"
    - latency: 4.178978ms
      message: 'load-balancer-api-internal: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:26:38Z"
    - latency: 9.815084ms
      message: 'load-balancer-api-internal: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:26:38Z"
    - latency: 5.274863ms
      message: 'load-balancer-api-internal: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:25:38Z"
    - latency: 9.027831ms
      message: 'load-balancer-api-internal: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:25:38Z"
    - latency: 10.133509ms
      message: 'load-balancer-api-internal: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:24:38Z"
    - latency: 6.468138ms
      message: 'load-balancer-api-internal: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:24:38Z"
    - latency: 4.020822ms
      message: 'load-balancer-api-internal: tcp connection to a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:23:38Z"
    - latency: 11.631428ms
      message: 'load-balancer-api-internal: resolved host name a363b332e5f584e44b0be4c7b07fc696-b46e76685e49c746.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:23:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-network-check-target-ip-10-0-129-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "10848"
    uid: 51d59faa-a145-4270-9a24-17a06ea7d990
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-network-check-target-ip-10-0-131-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "10850"
    uid: d73efd25-135a-4c1a-8918-f46a15df91ac
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-network-check-target-ip-10-0-138-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "10847"
    uid: 4f2b175c-9373-4459-94e0-433dfc62e9d1
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T03:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-90.ec2.internal
      uid: 925f39cf-66fe-4cad-9fa5-8a8370f0a7bc
    resourceVersion: "14209"
    uid: fcf11991-fb46-493c-8043-122acd90a4f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-rz2qd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T03:27:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.136634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:27:38Z"
    - latency: 1.867977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:27:38Z"
    - latency: 1.085057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:26:38Z"
    - latency: 2.428713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:26:38Z"
    - latency: 910.188µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:25:38Z"
    - latency: 1.799181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:25:38Z"
    - latency: 1.073213ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:24:38Z"
    - latency: 1.820956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:24:38Z"
    - latency: 771.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T03:23:38Z"
    - latency: 6.317417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T03:23:38Z"
kind: List
metadata:
  resourceVersion: ""