apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "11004"
    uid: 04a30d78-b2c1-4a78-b6c2-d01d96e70f2e
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "14626"
    uid: d39fa6dd-3d82-4eb7-aa69-8de27172fa7f
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T09:09:38Z"
      message: 'load-balancer-api-external: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.699572ms
      message: 'load-balancer-api-external: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:09:38Z"
    - latency: 10.895321ms
      message: 'load-balancer-api-external: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:09:38Z"
    - latency: 4.034229ms
      message: 'load-balancer-api-external: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:08:38Z"
    - latency: 13.597294ms
      message: 'load-balancer-api-external: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:08:38Z"
    - latency: 4.321874ms
      message: 'load-balancer-api-external: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:07:38Z"
    - latency: 8.660453ms
      message: 'load-balancer-api-external: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:07:38Z"
    - latency: 5.883625ms
      message: 'load-balancer-api-external: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:06:38Z"
    - latency: 11.302927ms
      message: 'load-balancer-api-external: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:06:38Z"
    - latency: 3.810633ms
      message: 'load-balancer-api-external: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:05:38Z"
    - latency: 8.963902ms
      message: 'load-balancer-api-external: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:05:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "14625"
    uid: a38b76e8-2b74-461a-9fa4-c6ded2624ec7
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T09:09:38Z"
      message: 'load-balancer-api-internal: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.740204ms
      message: 'load-balancer-api-internal: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:09:38Z"
    - latency: 10.819841ms
      message: 'load-balancer-api-internal: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:09:38Z"
    - latency: 4.578142ms
      message: 'load-balancer-api-internal: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:08:38Z"
    - latency: 13.654418ms
      message: 'load-balancer-api-internal: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:08:38Z"
    - latency: 4.951293ms
      message: 'load-balancer-api-internal: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:07:38Z"
    - latency: 8.611021ms
      message: 'load-balancer-api-internal: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:07:38Z"
    - latency: 7.337565ms
      message: 'load-balancer-api-internal: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:06:38Z"
    - latency: 11.22419ms
      message: 'load-balancer-api-internal: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:06:38Z"
    - latency: 3.817672ms
      message: 'load-balancer-api-internal: tcp connection to a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:05:38Z"
    - latency: 8.899533ms
      message: 'load-balancer-api-internal: resolved host name a03eedb5405744e468eaf8ce3db2ea33-cef3e06394d46352.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:05:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-network-check-target-ip-10-0-134-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "11002"
    uid: 2844c05d-c83f-466a-9435-eeaab84c20a1
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-network-check-target-ip-10-0-135-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "11003"
    uid: 9c3e5e85-206b-48de-bd7d-6e6d772f519b
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-network-check-target-ip-10-0-139-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "11001"
    uid: 4060110f-5879-4ae6-9093-dd6e95874e97
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T09:03:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-159.ec2.internal
      uid: f03c4811-58fa-4a3b-a100-d48f4a93edf9
    resourceVersion: "14624"
    uid: 490bca04-3148-46da-85b6-b927e0bc5bb4
  spec:
    sourcePod: network-check-source-7d88cb55d8-zrpmq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T09:09:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.038363ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:09:38Z"
    - latency: 1.684745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:09:38Z"
    - latency: 1.255122ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:08:38Z"
    - latency: 1.828577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:08:38Z"
    - latency: 940.7µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:07:38Z"
    - latency: 1.899977ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:07:38Z"
    - latency: 860.456µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:06:38Z"
    - latency: 1.623691ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:06:38Z"
    - latency: 818.684µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T09:05:38Z"
    - latency: 1.997929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T09:05:38Z"
kind: List
metadata:
  resourceVersion: ""