apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14573"
    uid: ff799a0a-e04f-47b2-8c6e-deaa07928cdc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:47:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.202944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:47:27Z"
    - latency: 808.258µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 989.82µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 1.118284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 1.150122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 1.135071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 1.009549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14224"
    uid: cc2c6748-2543-4b26-8d58-d84117a7e271
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:46:27Z"
      message: 'load-balancer-api-external: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.425732ms
      message: 'load-balancer-api-external: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 10.033277ms
      message: 'load-balancer-api-external: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 4.976944ms
      message: 'load-balancer-api-external: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 8.702362ms
      message: 'load-balancer-api-external: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 6.963616ms
      message: 'load-balancer-api-external: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 10.739208ms
      message: 'load-balancer-api-external: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 6.286949ms
      message: 'load-balancer-api-external: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 8.889776ms
      message: 'load-balancer-api-external: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 3.87773ms
      message: 'load-balancer-api-external: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 9.665824ms
      message: 'load-balancer-api-external: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14223"
    uid: 4a877a95-5146-426d-a575-366a6f179a89
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:46:27Z"
      message: 'load-balancer-api-internal: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.389593ms
      message: 'load-balancer-api-internal: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 10.069855ms
      message: 'load-balancer-api-internal: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 3.741715ms
      message: 'load-balancer-api-internal: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 8.71932ms
      message: 'load-balancer-api-internal: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 6.9854ms
      message: 'load-balancer-api-internal: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 10.78096ms
      message: 'load-balancer-api-internal: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 5.701345ms
      message: 'load-balancer-api-internal: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 9.03988ms
      message: 'load-balancer-api-internal: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 3.510682ms
      message: 'load-balancer-api-internal: tcp connection to ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 9.702238ms
      message: 'load-balancer-api-internal: resolved host name ae84b4dd48dcc411cb74526042728c92-36a3b5323d820454.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-ip-10-0-129-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14570"
    uid: 18e30016-c80e-4bd9-b820-34e1d8d24350
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:47:27Z"
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.392764ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:47:27Z"
    - latency: 2.10767ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 2.29045ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 2.259107ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 2.219675ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 2.302014ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 2.124566ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-ip-10-0-130-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14572"
    uid: 1dc0005b-4533-4d41-a129-f8f931a48b15
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:47:27Z"
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.005511ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:47:27Z"
    - latency: 1.878857ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 2.038383ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 1.927534ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 1.833851ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 2.287895ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 2.111109ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-ip-10-0-137-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14571"
    uid: 96306667-11ed-45a4-b1db-e14d79f54feb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:47:27Z"
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099558ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:47:27Z"
    - latency: 1.121618ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 963.189µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 783.138µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 766.826µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 1.400738ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 1.163298ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:41:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T09:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 22d0a3bd-02eb-43f1-945f-43f24ab450a9
    resourceVersion: "14222"
    uid: 16b45ef9-57a4-4017-8a7b-fa1e2c501d36
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pq5fp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T09:46:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 737.684µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 1.911478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:46:27Z"
    - latency: 1.208532ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 1.94326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:45:27Z"
    - latency: 1.132458ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 1.958107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:44:27Z"
    - latency: 1.442535ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 1.893911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:43:27Z"
    - latency: 1.252539ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T09:42:27Z"
    - latency: 2.110746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T09:42:27Z"
kind: List
metadata:
  resourceVersion: ""