apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "14201"
    uid: 530a03c1-7713-43e4-873f-b3fc55dddd1b
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:12Z"
    - latency: 834.743µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 1.29023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 896.457µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 796.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 1.134163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 905.178µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "13844"
    uid: b312d197-8194-4621-af6e-3d3295242d48
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:43:12Z"
      message: 'load-balancer-api-external: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.835338ms
      message: 'load-balancer-api-external: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 7.490173ms
      message: 'load-balancer-api-external: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 4.573709ms
      message: 'load-balancer-api-external: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 6.676837ms
      message: 'load-balancer-api-external: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 5.819305ms
      message: 'load-balancer-api-external: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 6.934133ms
      message: 'load-balancer-api-external: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 5.115868ms
      message: 'load-balancer-api-external: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 7.006ms
      message: 'load-balancer-api-external: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 4.081666ms
      message: 'load-balancer-api-external: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 7.89962ms
      message: 'load-balancer-api-external: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:39:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "13843"
    uid: d4240548-806a-40c8-b93d-72f80ff477b7
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:43:12Z"
      message: 'load-balancer-api-internal: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.84304ms
      message: 'load-balancer-api-internal: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 7.416021ms
      message: 'load-balancer-api-internal: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 4.768868ms
      message: 'load-balancer-api-internal: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 6.623293ms
      message: 'load-balancer-api-internal: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 5.437795ms
      message: 'load-balancer-api-internal: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 6.982333ms
      message: 'load-balancer-api-internal: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 6.706035ms
      message: 'load-balancer-api-internal: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 7.496331ms
      message: 'load-balancer-api-internal: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 4.069825ms
      message: 'load-balancer-api-internal: tcp connection to a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 7.923423ms
      message: 'load-balancer-api-internal: resolved host name a8088fa1e4c954f1fa2c98ffbbc193cc-7564bdb2a519525d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:39:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-network-check-target-ip-10-0-131-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "14200"
    uid: 0dea1031-5d54-403c-ae0b-f71b40372c61
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:12Z"
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.314224ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:12Z"
    - latency: 2.287349ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 2.261889ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 2.003687ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 2.752377ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 2.162735ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 2.235241ms
      message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-network-check-target-ip-10-0-139-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "14198"
    uid: 1a24483c-a678-45d6-8994-1a5de2994d7e
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:12Z"
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.799649ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:12Z"
    - latency: 1.986387ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 1.914861ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 1.732873ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 1.750438ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 1.863055ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 1.991627ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-network-check-target-ip-10-0-143-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "14197"
    uid: b66ba2e5-2add-4d64-a938-5b4a343eed61
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:12Z"
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024886ms
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:12Z"
    - latency: 882.058µs
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 1.066752ms
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 926.069µs
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 1.810111ms
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 1.070527ms
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 1.510724ms
      message: 'network-check-target-ip-10-0-143-111: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:38:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:37:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-111.ec2.internal
      uid: b92bdc4a-075f-4110-9cab-d61371e459fe
    resourceVersion: "13841"
    uid: f44b3a32-3603-4f23-ac92-dedeb97aaa92
  spec:
    sourcePod: network-check-source-869dcfcdcd-hd7b2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:43:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 722.425µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 2.046776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:12Z"
    - latency: 898.527µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 1.764035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:12Z"
    - latency: 883.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 1.850468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:12Z"
    - latency: 963.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 2.081454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:40:12Z"
    - latency: 1.115955ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:12Z"
    - latency: 2.156379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:39:12Z"
kind: List
metadata:
  resourceVersion: ""