apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "24767"
    uid: cbe70c2e-096a-41e7-b99f-173f5a8284c0
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:59:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.00417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:59:35Z"
    - latency: 1.424974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:58:35Z"
    - latency: 1.0257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:57:35Z"
    - latency: 1.093797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:56:35Z"
    - latency: 1.039586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:55:35Z"
    - latency: 1.033576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:54:35Z"
    - latency: 893.673µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:53:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "28877"
    uid: 7dea7d0a-72d2-4a58-a2e5-8c919004453c
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:58:35Z"
      message: 'load-balancer-api-external: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.453259ms
      message: 'load-balancer-api-external: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:35Z"
    - latency: 5.979276ms
      message: 'load-balancer-api-external: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:04:35Z"
    - latency: 4.819085ms
      message: 'load-balancer-api-external: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:35Z"
    - latency: 6.791418ms
      message: 'load-balancer-api-external: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:03:35Z"
    - latency: 5.858442ms
      message: 'load-balancer-api-external: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:02:35Z"
    - latency: 6.487496ms
      message: 'load-balancer-api-external: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:02:35Z"
    - latency: 4.890438ms
      message: 'load-balancer-api-external: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:01:35Z"
    - latency: 6.98235ms
      message: 'load-balancer-api-external: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:01:35Z"
    - latency: 5.077148ms
      message: 'load-balancer-api-external: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:00:35Z"
    - latency: 8.887926ms
      message: 'load-balancer-api-external: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "28878"
    uid: 430d40d2-db51-4771-ad6a-5ccc330a105a
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:58:35Z"
      message: 'load-balancer-api-internal: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.423509ms
      message: 'load-balancer-api-internal: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:35Z"
    - latency: 6.072324ms
      message: 'load-balancer-api-internal: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:04:35Z"
    - latency: 4.83109ms
      message: 'load-balancer-api-internal: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:35Z"
    - latency: 6.81122ms
      message: 'load-balancer-api-internal: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:03:35Z"
    - latency: 5.091803ms
      message: 'load-balancer-api-internal: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:02:35Z"
    - latency: 6.560005ms
      message: 'load-balancer-api-internal: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:02:35Z"
    - latency: 5.790387ms
      message: 'load-balancer-api-internal: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:01:35Z"
    - latency: 7.166591ms
      message: 'load-balancer-api-internal: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:01:35Z"
    - latency: 5.682379ms
      message: 'load-balancer-api-internal: tcp connection to ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:00:35Z"
    - latency: 8.988653ms
      message: 'load-balancer-api-internal: resolved host name ad80a6b69f2134127bfe2dfcb092950a-252bdfc62f34de5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-network-check-target-ip-10-0-137-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "24764"
    uid: 2153c9d0-952a-400e-85fd-3f68f9aafd88
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:59:35Z"
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.236093ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:59:35Z"
    - latency: 2.474667ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:58:35Z"
    - latency: 2.51979ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:57:35Z"
    - latency: 2.264919ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:56:35Z"
    - latency: 2.442747ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:55:35Z"
    - latency: 2.16033ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:54:35Z"
    - latency: 2.377962ms
      message: 'network-check-target-ip-10-0-137-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:53:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-network-check-target-ip-10-0-142-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "24765"
    uid: 1ba86c42-b1da-45f8-90f7-547308ceeb68
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:59:35Z"
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.504403ms
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:59:35Z"
    - latency: 1.358353ms
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:58:35Z"
    - latency: 945.943µs
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:57:35Z"
    - latency: 1.377774ms
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:56:35Z"
    - latency: 1.267478ms
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:55:35Z"
    - latency: 895.877µs
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:54:35Z"
    - latency: 1.621225ms
      message: 'network-check-target-ip-10-0-142-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:53:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-network-check-target-ip-10-0-142-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "24766"
    uid: 806312b2-9e3a-48d2-8773-0442a76cd7dd
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:59:35Z"
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.989219ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:59:35Z"
    - latency: 2.86451ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:58:35Z"
    - latency: 2.183262ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:57:35Z"
    - latency: 2.238704ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:56:35Z"
    - latency: 2.298985ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:55:35Z"
    - latency: 1.986064ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:54:35Z"
    - latency: 1.999017ms
      message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T00:53:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T00:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-142.ec2.internal
      uid: a3c26ffd-cffc-40a0-8078-c27837512318
    resourceVersion: "28876"
    uid: e343a0e1-027e-46de-bb7c-0f27ba1f8531
  spec:
    sourcePod: network-check-source-dbd9cf844-jjkfs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T00:58:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.62µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:04:35Z"
    - latency: 1.75893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:04:35Z"
    - latency: 1.118872ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:03:35Z"
    - latency: 1.898553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:03:35Z"
    - latency: 1.002589ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:02:35Z"
    - latency: 1.956101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:02:35Z"
    - latency: 874.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:01:35Z"
    - latency: 1.925378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:01:35Z"
    - latency: 963.051µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:00:35Z"
    - latency: 1.837177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:00:35Z"
kind: List
metadata:
  resourceVersion: ""