apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14866"
    uid: b43c043c-e1f9-4c68-9bde-e01467a22ed6
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:45:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.689691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:39Z"
    - latency: 1.1614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 2.582932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 1.085896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 1.057765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 1.196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 1.045234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14533"
    uid: ca0d7335-c7a4-40ae-878f-fd3aeec0eb80
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:44:39Z"
      message: 'load-balancer-api-external: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.954754ms
      message: 'load-balancer-api-external: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 9.358917ms
      message: 'load-balancer-api-external: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 6.255324ms
      message: 'load-balancer-api-external: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 11.227069ms
      message: 'load-balancer-api-external: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 4.433791ms
      message: 'load-balancer-api-external: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 7.356459ms
      message: 'load-balancer-api-external: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 5.132164ms
      message: 'load-balancer-api-external: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 8.411125ms
      message: 'load-balancer-api-external: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 4.418541ms
      message: 'load-balancer-api-external: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 8.155614ms
      message: 'load-balancer-api-external: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:40:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14532"
    uid: 90811bec-eb9d-41b6-b012-08443126e93f
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:44:39Z"
      message: 'load-balancer-api-internal: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.9494ms
      message: 'load-balancer-api-internal: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 9.306947ms
      message: 'load-balancer-api-internal: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 5.05843ms
      message: 'load-balancer-api-internal: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 11.024288ms
      message: 'load-balancer-api-internal: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 4.443949ms
      message: 'load-balancer-api-internal: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 7.326347ms
      message: 'load-balancer-api-internal: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 4.68745ms
      message: 'load-balancer-api-internal: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 8.343671ms
      message: 'load-balancer-api-internal: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 4.607266ms
      message: 'load-balancer-api-internal: tcp connection to a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 8.115231ms
      message: 'load-balancer-api-internal: resolved host name a71c682e6b9034d45922cd7dc5268d9d-86855029e26be379.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:40:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-ip-10-0-131-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14863"
    uid: 373a6a02-c648-47ef-bec8-89c0ed7fd26b
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:45:39Z"
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 741.584µs
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:39Z"
    - latency: 1.356519ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 1.513935ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 830.973µs
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 825.079µs
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 827.962µs
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 1.179847ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-ip-10-0-136-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14864"
    uid: 9f3c8d64-8b6b-4e06-aad5-1aa8bbd2d8b3
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:45:39Z"
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.189866ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:39Z"
    - latency: 2.325383ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 3.336939ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 2.188391ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 2.092563ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 2.072532ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 2.130809ms
      message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-ip-10-0-137-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14865"
    uid: c4b38d27-f68d-4ce8-835e-f4f4487d54d7
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:45:39Z"
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.454553ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:45:39Z"
    - latency: 2.112884ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 2.613813ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 2.285221ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 2.414959ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 2.150006ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 2.39594ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:39:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T15:38:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 36533271-fc24-4226-b403-f6420f1f6f27
    resourceVersion: "14531"
    uid: 140239a4-86c2-4478-b99f-d3742924e719
  spec:
    sourcePod: network-check-source-7f44b6dd87-q4w6k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T15:44:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.508µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 1.940938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:44:39Z"
    - latency: 1.191615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 2.735354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:43:39Z"
    - latency: 769.356µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 1.505781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:42:39Z"
    - latency: 738.229µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 1.737945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:41:39Z"
    - latency: 862.973µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T15:40:39Z"
    - latency: 1.844639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T15:40:39Z"
kind: List
metadata:
  resourceVersion: ""