apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "22565"
    uid: 112d0fd7-2399-46d2-91c7-1119b7d3ed89
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:45:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:45:32Z"
    - latency: 848.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 1.34948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 1.105708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 977.965µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 792.149µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 1.379538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "21664"
    uid: c8c76021-7f26-4bab-8be0-f8f88f72d884
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:44:32Z"
      message: 'load-balancer-api-external: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.223897ms
      message: 'load-balancer-api-external: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 8.408322ms
      message: 'load-balancer-api-external: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 4.95729ms
      message: 'load-balancer-api-external: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 8.47025ms
      message: 'load-balancer-api-external: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 4.872606ms
      message: 'load-balancer-api-external: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 9.287955ms
      message: 'load-balancer-api-external: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 6.268878ms
      message: 'load-balancer-api-external: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 8.675975ms
      message: 'load-balancer-api-external: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 5.696455ms
      message: 'load-balancer-api-external: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 8.014325ms
      message: 'load-balancer-api-external: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:40:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "21663"
    uid: 4d81fe3d-0cb0-48f7-967a-d7fddab70f07
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:44:32Z"
      message: 'load-balancer-api-internal: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.977943ms
      message: 'load-balancer-api-internal: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 8.441811ms
      message: 'load-balancer-api-internal: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 5.803394ms
      message: 'load-balancer-api-internal: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 8.530957ms
      message: 'load-balancer-api-internal: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 4.832743ms
      message: 'load-balancer-api-internal: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 9.31236ms
      message: 'load-balancer-api-internal: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 6.388634ms
      message: 'load-balancer-api-internal: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 8.5889ms
      message: 'load-balancer-api-internal: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 6.063882ms
      message: 'load-balancer-api-internal: tcp connection to a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 8.09736ms
      message: 'load-balancer-api-internal: resolved host name a1e39233f9eb3478494b2aff9c4ce33e-986fde7cc1f5aebd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:40:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-network-check-target-ip-10-0-128-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "22562"
    uid: e74a5f3d-6946-49d5-aef0-a0198ec147f7
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:45:32Z"
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.25405ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:45:32Z"
    - latency: 913.104µs
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 1.62223ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 1.697225ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 889.042µs
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 1.247178ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 1.314411ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-network-check-target-ip-10-0-131-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "22564"
    uid: c9d79c99-06a2-4296-a413-e61012572dd4
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:45:32Z"
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.985347ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:45:32Z"
    - latency: 2.103072ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 2.186174ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 2.092635ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 2.397562ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 2.084923ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 2.200339ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-network-check-target-ip-10-0-141-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "22563"
    uid: a9e1f055-5e15-47f5-9d0a-93ff707787bb
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:45:32Z"
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.022507ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:45:32Z"
    - latency: 1.925899ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 2.074382ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 1.919213ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 2.02709ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 1.87441ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 1.993607ms
      message: 'network-check-target-ip-10-0-141-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:38:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-139.ec2.internal
      uid: 728cace8-f566-4765-9832-6d5760d8179e
    resourceVersion: "21662"
    uid: d9a388a8-1100-475c-b001-29c47dcadf50
  spec:
    sourcePod: network-check-source-56499946bc-xdsdn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:44:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 788.889µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 1.683804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:44:32Z"
    - latency: 672.947µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 2.119822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:43:32Z"
    - latency: 937.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 1.811694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:42:32Z"
    - latency: 795.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 2.001785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:41:32Z"
    - latency: 814.768µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:32Z"
    - latency: 1.762715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:40:32Z"
kind: List
metadata:
  resourceVersion: ""