apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14965"
    uid: 9adaa072-9a77-4a48-aa21-5a55f830c72f
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:57:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:57:11Z"
    - latency: 1.105623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 1.602875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 1.085109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 940.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 1.487073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 1.071247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:51:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14541"
    uid: 34dbe4fe-e736-4086-a634-186bec356f15
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:56:11Z"
      message: 'load-balancer-api-external: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.211215ms
      message: 'load-balancer-api-external: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 9.395839ms
      message: 'load-balancer-api-external: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 4.407546ms
      message: 'load-balancer-api-external: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 9.49732ms
      message: 'load-balancer-api-external: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 4.986462ms
      message: 'load-balancer-api-external: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 9.001628ms
      message: 'load-balancer-api-external: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 4.640396ms
      message: 'load-balancer-api-external: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 21.496534ms
      message: 'load-balancer-api-external: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 4.764736ms
      message: 'load-balancer-api-external: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 8.47088ms
      message: 'load-balancer-api-external: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:52:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14542"
    uid: 24c1132a-345a-4b3b-8cf7-5de3af292230
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:56:11Z"
      message: 'load-balancer-api-internal: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.187942ms
      message: 'load-balancer-api-internal: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 9.531569ms
      message: 'load-balancer-api-internal: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 4.392918ms
      message: 'load-balancer-api-internal: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 9.363301ms
      message: 'load-balancer-api-internal: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 4.952751ms
      message: 'load-balancer-api-internal: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 8.955737ms
      message: 'load-balancer-api-internal: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 4.628493ms
      message: 'load-balancer-api-internal: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 21.46385ms
      message: 'load-balancer-api-internal: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 4.791674ms
      message: 'load-balancer-api-internal: tcp connection to aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 8.440689ms
      message: 'load-balancer-api-internal: resolved host name aab76284eff1a4d43a90b5d87e4fd3b0-02bfa2458fa47119.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:52:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-ip-10-0-131-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14964"
    uid: 5cb8969c-db92-4412-a52a-54130ca440e3
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:57:11Z"
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.154656ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:57:11Z"
    - latency: 2.45131ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 2.170708ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 2.204347ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 2.570488ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 2.095105ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 2.376489ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:51:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-ip-10-0-132-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14962"
    uid: 576781e6-c66c-48b0-b3cc-6f467eeed6c8
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:57:11Z"
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 796.647µs
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:57:11Z"
    - latency: 901.336µs
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 1.312751ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 698.224µs
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 1.19985ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 788.963µs
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 1.122968ms
      message: 'network-check-target-ip-10-0-132-33: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:51:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-ip-10-0-138-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14963"
    uid: a612acf8-3486-4c41-8a2d-70f3e7249a62
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:57:11Z"
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.102737ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:57:11Z"
    - latency: 2.284142ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 2.47765ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 2.194255ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 2.192255ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 2.483651ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 2.648327ms
      message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:51:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T07:50:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-33.ec2.internal
      uid: e4a84b36-fa35-4223-b8a4-02032d9f1be1
    resourceVersion: "14540"
    uid: de473c3d-0e06-42e4-be27-63707bb571bf
  spec:
    sourcePod: network-check-source-7d88cb55d8-6b2tp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T07:56:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.089604ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 2.301209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:56:11Z"
    - latency: 783.996µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 2.10528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:55:11Z"
    - latency: 720.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 2.275159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:54:11Z"
    - latency: 1.015239ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 1.605511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:53:11Z"
    - latency: 746.648µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T07:52:11Z"
    - latency: 1.731674ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T07:52:11Z"
kind: List
metadata:
  resourceVersion: ""