apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14555"
    uid: 981fe2a1-4225-4ca7-8faf-c87ddf4e117d
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:46:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:46:41Z"
    - latency: 830.148µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 1.020384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 757.153µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 1.159656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 1.322439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 1.296602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:40:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14055"
    uid: ba8f900d-34af-449d-9aa9-08616ec4ad33
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:45:41Z"
      message: 'load-balancer-api-external: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.770647ms
      message: 'load-balancer-api-external: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 10.082079ms
      message: 'load-balancer-api-external: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 6.055286ms
      message: 'load-balancer-api-external: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 8.667547ms
      message: 'load-balancer-api-external: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 4.935338ms
      message: 'load-balancer-api-external: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 7.671408ms
      message: 'load-balancer-api-external: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 4.940665ms
      message: 'load-balancer-api-external: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 8.267803ms
      message: 'load-balancer-api-external: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 4.957287ms
      message: 'load-balancer-api-external: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 7.605995ms
      message: 'load-balancer-api-external: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:41:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14054"
    uid: b6f16d75-d1a1-4e3e-866e-69bfe8581dc8
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:45:41Z"
      message: 'load-balancer-api-internal: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.799721ms
      message: 'load-balancer-api-internal: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 10.053585ms
      message: 'load-balancer-api-internal: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 6.079887ms
      message: 'load-balancer-api-internal: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 8.596798ms
      message: 'load-balancer-api-internal: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 5.502014ms
      message: 'load-balancer-api-internal: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 7.660093ms
      message: 'load-balancer-api-internal: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 4.807999ms
      message: 'load-balancer-api-internal: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 8.252258ms
      message: 'load-balancer-api-internal: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 4.92083ms
      message: 'load-balancer-api-internal: tcp connection to ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 7.593819ms
      message: 'load-balancer-api-internal: resolved host name ae80e9e463cc54126946b05246463a9a-e66a4dc8647ae2c1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:41:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-network-check-target-ip-10-0-141-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14552"
    uid: 8bd78481-c445-4f66-87da-6674422b3242
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:46:41Z"
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.44295ms
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:46:41Z"
    - latency: 1.087299ms
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 1.35465ms
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 749.264µs
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 666.47µs
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 1.17087ms
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 1.025198ms
      message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:40:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-network-check-target-ip-10-0-141-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14553"
    uid: f79bc0a1-bda7-41f7-a460-22175c5e58e2
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:46:41Z"
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.055148ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:46:41Z"
    - latency: 1.871216ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 2.042712ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 1.82864ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 1.72662ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 1.833525ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 2.050212ms
      message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:40:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-network-check-target-ip-10-0-142-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14554"
    uid: 8895fa59-030f-4bb2-bc88-34507bdf406a
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:46:41Z"
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.410598ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:46:41Z"
    - latency: 1.874242ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 2.095584ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 1.862267ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 1.587788ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 1.844187ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 2.147553ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:40:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T15:39:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-171.ec2.internal
      uid: eecf7193-22d7-426e-bf82-9e3ec169777b
    resourceVersion: "14053"
    uid: a6158b42-bd76-4435-86d8-0a1db739e46a
  spec:
    sourcePod: network-check-source-7d88cb55d8-4lmrd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T15:45:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 761.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 1.694723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:45:41Z"
    - latency: 825.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 1.538467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:44:41Z"
    - latency: 782.224µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 1.583521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:43:41Z"
    - latency: 787.88µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 2.035984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:42:41Z"
    - latency: 887.494µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T15:41:41Z"
    - latency: 1.858293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T15:41:41Z"
kind: List
metadata:
  resourceVersion: ""