apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "23301"
    uid: 6a0f42e2-5dc6-474a-84c1-aeb836316794
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:56:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:56:04Z"
    - latency: 1.088888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:55:04Z"
    - latency: 1.314582ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:54:04Z"
    - latency: 1.088978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:53:04Z"
    - latency: 1.447232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:52:04Z"
    - latency: 919.761µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:51:04Z"
    - latency: 1.153088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:50:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "28507"
    uid: ff9bc003-5902-4ec4-bcdc-ccbad22d77b8
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:55:04Z"
      message: 'load-balancer-api-external: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.472091ms
      message: 'load-balancer-api-external: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T12:01:04Z"
    - latency: 13.258341ms
      message: 'load-balancer-api-external: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T12:01:04Z"
    - latency: 4.366637ms
      message: 'load-balancer-api-external: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T12:00:04Z"
    - latency: 10.468649ms
      message: 'load-balancer-api-external: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T12:00:04Z"
    - latency: 4.994091ms
      message: 'load-balancer-api-external: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:59:04Z"
    - latency: 9.498312ms
      message: 'load-balancer-api-external: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:59:04Z"
    - latency: 4.675761ms
      message: 'load-balancer-api-external: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:58:04Z"
    - latency: 9.212504ms
      message: 'load-balancer-api-external: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:58:04Z"
    - latency: 5.001068ms
      message: 'load-balancer-api-external: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:57:04Z"
    - latency: 9.347112ms
      message: 'load-balancer-api-external: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:57:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "28508"
    uid: 40d861cf-a316-46bb-a9a3-b6a4bf940129
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:55:04Z"
      message: 'load-balancer-api-internal: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.202781ms
      message: 'load-balancer-api-internal: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T12:01:04Z"
    - latency: 13.352773ms
      message: 'load-balancer-api-internal: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T12:01:04Z"
    - latency: 6.118889ms
      message: 'load-balancer-api-internal: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T12:00:04Z"
    - latency: 10.360023ms
      message: 'load-balancer-api-internal: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T12:00:04Z"
    - latency: 3.836747ms
      message: 'load-balancer-api-internal: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:59:04Z"
    - latency: 9.354151ms
      message: 'load-balancer-api-internal: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:59:04Z"
    - latency: 4.992822ms
      message: 'load-balancer-api-internal: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:58:04Z"
    - latency: 9.180776ms
      message: 'load-balancer-api-internal: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:58:04Z"
    - latency: 4.957288ms
      message: 'load-balancer-api-internal: tcp connection to aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:57:04Z"
    - latency: 9.300715ms
      message: 'load-balancer-api-internal: resolved host name aeed27703433c440483e056d86271ad2-ba339ad09d1db1be.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:57:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-ip-10-0-128-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "23298"
    uid: 1813b564-a127-4161-8a3e-aa2ff88843fe
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:56:04Z"
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.674836ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:56:04Z"
    - latency: 2.347498ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:55:04Z"
    - latency: 2.316488ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:54:04Z"
    - latency: 2.465619ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:53:04Z"
    - latency: 2.126942ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:52:04Z"
    - latency: 2.081649ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:51:04Z"
    - latency: 2.184472ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:50:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-ip-10-0-129-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "23299"
    uid: a91bb24b-f0a7-4022-8c6f-b4c53fa84e28
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:56:04Z"
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.203318ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:56:04Z"
    - latency: 2.36837ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:55:04Z"
    - latency: 2.238232ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:54:04Z"
    - latency: 2.390119ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:53:04Z"
    - latency: 2.21838ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:52:04Z"
    - latency: 2.181586ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:51:04Z"
    - latency: 2.450331ms
      message: 'network-check-target-ip-10-0-129-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:50:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-ip-10-0-142-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "23297"
    uid: d5f31949-a6ae-4482-b065-0bb280c9ea5e
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:56:04Z"
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.51µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:56:04Z"
    - latency: 965.229µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:55:04Z"
    - latency: 894.115µs
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:54:04Z"
    - latency: 1.332573ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:53:04Z"
    - latency: 1.411264ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:52:04Z"
    - latency: 1.212956ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:51:04Z"
    - latency: 1.106555ms
      message: 'network-check-target-ip-10-0-142-49: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:50:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T11:49:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-49.ec2.internal
      uid: 6419a53e-a4ef-4344-9f46-6afc57726b46
    resourceVersion: "28506"
    uid: ccede5f0-7741-4821-a2c5-0652d5ac2295
  spec:
    sourcePod: network-check-source-7f44b6dd87-w76bd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T11:55:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 770.077µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T12:01:04Z"
    - latency: 2.402862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T12:01:04Z"
    - latency: 1.018178ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T12:00:04Z"
    - latency: 1.982548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T12:00:04Z"
    - latency: 761.012µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:59:04Z"
    - latency: 1.617155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:59:04Z"
    - latency: 1.175989ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:58:04Z"
    - latency: 1.787568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:58:04Z"
    - latency: 743.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T11:57:04Z"
    - latency: 1.702622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T11:57:04Z"
kind: List
metadata:
  resourceVersion: ""