apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "19002"
    uid: 6db83c00-93ca-40ca-a043-6b556c4d591a
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:28Z"
    - latency: 925.884µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 946.996µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 826.115µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 852.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 1.102286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 920.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:51:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "18244"
    uid: d0fa1726-63cd-45d1-a84b-e1d2cf1727d7
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:56:28Z"
      message: 'load-balancer-api-external: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.346092ms
      message: 'load-balancer-api-external: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 7.07164ms
      message: 'load-balancer-api-external: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 4.786455ms
      message: 'load-balancer-api-external: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 7.699692ms
      message: 'load-balancer-api-external: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 3.874345ms
      message: 'load-balancer-api-external: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 13.670921ms
      message: 'load-balancer-api-external: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 4.880601ms
      message: 'load-balancer-api-external: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 6.00161ms
      message: 'load-balancer-api-external: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 4.655226ms
      message: 'load-balancer-api-external: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 6.370819ms
      message: 'load-balancer-api-external: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "18243"
    uid: c21a3c52-4f12-4c50-a5ec-7ff899e3eaac
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:56:28Z"
      message: 'load-balancer-api-internal: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.539169ms
      message: 'load-balancer-api-internal: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 7.101515ms
      message: 'load-balancer-api-internal: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 5.744978ms
      message: 'load-balancer-api-internal: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 7.732976ms
      message: 'load-balancer-api-internal: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 3.784398ms
      message: 'load-balancer-api-internal: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 13.434651ms
      message: 'load-balancer-api-internal: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 4.868253ms
      message: 'load-balancer-api-internal: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 6.029284ms
      message: 'load-balancer-api-internal: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 5.241868ms
      message: 'load-balancer-api-internal: tcp connection to ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 6.34526ms
      message: 'load-balancer-api-internal: resolved host name ada971426a9e440adb3987491f559f77-5598f030cdd802b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:52:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-ip-10-0-130-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "19001"
    uid: 3971139b-5695-4d1c-8918-57d98042fe36
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:28Z"
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192029ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:28Z"
    - latency: 2.362417ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 2.184346ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 8.887308ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 1.824352ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 2.085854ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 2.46777ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:51:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-ip-10-0-132-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "18999"
    uid: d9171c17-59e3-413b-8437-3680c2cc5b98
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:28Z"
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.23411ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:28Z"
    - latency: 1.428355ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 811.322µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 1.183797ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 713.925µs
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 1.146201ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 1.138932ms
      message: 'network-check-target-ip-10-0-132-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:51:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-ip-10-0-135-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "19000"
    uid: 1fc63922-a402-4a04-805d-ee13b85ac94b
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:57:28Z"
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16591ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:57:28Z"
    - latency: 1.865577ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 2.108335ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 7.416032ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 2.21193ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 2.126687ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 2.278698ms
      message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:51:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T16:50:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-224-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-224.ec2.internal
      uid: 95d71aa4-83d9-462d-921f-13fa0b2aef4f
    resourceVersion: "18242"
    uid: 07305e51-983c-4642-a9a9-5e93df1eb462
  spec:
    sourcePod: network-check-source-cc88fdd44-2r9d4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T16:56:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.58µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 1.965009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:56:28Z"
    - latency: 874.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 1.788994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:55:28Z"
    - latency: 812.741µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 9.189773ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:54:28Z"
    - latency: 877.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 1.577373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:53:28Z"
    - latency: 1.101747ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T16:52:28Z"
    - latency: 1.669822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T16:52:28Z"
kind: List
metadata:
  resourceVersion: ""