apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "15415"
    uid: ab75394c-11a1-4c14-a832-9e3029cfd186
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:52:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:52:34Z"
    - latency: 1.049928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 907.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 974.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 1.220256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 795.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 1.039125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "14126"
    uid: 21258847-14fd-4684-9b1b-c2acdb56ad13
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:51:34Z"
      message: 'load-balancer-api-external: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.641134ms
      message: 'load-balancer-api-external: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 7.993561ms
      message: 'load-balancer-api-external: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 5.161339ms
      message: 'load-balancer-api-external: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 8.740798ms
      message: 'load-balancer-api-external: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 4.789481ms
      message: 'load-balancer-api-external: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 8.437818ms
      message: 'load-balancer-api-external: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 5.076455ms
      message: 'load-balancer-api-external: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 22.926592ms
      message: 'load-balancer-api-external: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 4.852992ms
      message: 'load-balancer-api-external: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 7.485978ms
      message: 'load-balancer-api-external: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:47:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "14127"
    uid: 3069ddc4-41ad-4f45-b84f-951d7930a1f6
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:51:34Z"
      message: 'load-balancer-api-internal: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.626928ms
      message: 'load-balancer-api-internal: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 8.054437ms
      message: 'load-balancer-api-internal: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 5.174931ms
      message: 'load-balancer-api-internal: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 8.63819ms
      message: 'load-balancer-api-internal: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 5.107235ms
      message: 'load-balancer-api-internal: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 8.383758ms
      message: 'load-balancer-api-internal: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 5.061443ms
      message: 'load-balancer-api-internal: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 22.881574ms
      message: 'load-balancer-api-internal: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 5.612686ms
      message: 'load-balancer-api-internal: tcp connection to aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 7.455448ms
      message: 'load-balancer-api-internal: resolved host name aba87d2898942414b9292fb1fbfc9486-7db76b7440c56794.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:47:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-network-check-target-ip-10-0-132-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "15413"
    uid: c1520d04-cc8c-4d9e-8798-d16b84ae69b4
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:52:34Z"
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.405669ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:52:34Z"
    - latency: 2.697039ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 2.22753ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 2.567177ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 2.165222ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 2.250916ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 2.454417ms
      message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-network-check-target-ip-10-0-132-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "15414"
    uid: f24136aa-143c-4463-9f16-e5ecdfd925d2
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:52:34Z"
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.23215ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:52:34Z"
    - latency: 2.507605ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 2.617353ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 2.452081ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 2.31268ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 2.244163ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 2.288382ms
      message: 'network-check-target-ip-10-0-132-89: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-network-check-target-ip-10-0-135-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "15412"
    uid: a2a0a6d0-5ae7-473b-971d-cdf865cdb6c6
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:52:34Z"
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255198ms
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:52:34Z"
    - latency: 1.474112ms
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 836.76µs
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 829.847µs
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 797.781µs
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 1.311352ms
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 1.389481ms
      message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T12:45:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-167.ec2.internal
      uid: fe3f43e2-0c94-46e5-884b-97fcb9088d7f
    resourceVersion: "14125"
    uid: 34640a08-7dd8-455f-a075-340fc320b2b2
  spec:
    sourcePod: network-check-source-dbd9cf844-spqw7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T12:51:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.265011ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 2.259286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:51:34Z"
    - latency: 859.486µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 2.192091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:50:34Z"
    - latency: 883.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 1.744864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:49:34Z"
    - latency: 865.907µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 6.931936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:48:34Z"
    - latency: 1.211597ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T12:47:34Z"
    - latency: 1.603024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T12:47:34Z"
kind: List
metadata:
  resourceVersion: ""