apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "15335"
    uid: 6f28be83-f22c-4158-b8cb-58f02ce735c8
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:07:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.258µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:07:21Z"
    - latency: 1.038902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 943.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 839.588µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 807.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 737.746µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 1.045427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:01:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "14995"
    uid: f6beab26-87c4-43a6-bd9d-ca2de163a327
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:06:21Z"
      message: 'load-balancer-api-external: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.449877ms
      message: 'load-balancer-api-external: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 7.812393ms
      message: 'load-balancer-api-external: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 5.910474ms
      message: 'load-balancer-api-external: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 9.00003ms
      message: 'load-balancer-api-external: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 4.438991ms
      message: 'load-balancer-api-external: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 8.48624ms
      message: 'load-balancer-api-external: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 4.974327ms
      message: 'load-balancer-api-external: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 8.127294ms
      message: 'load-balancer-api-external: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 4.911634ms
      message: 'load-balancer-api-external: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 9.582354ms
      message: 'load-balancer-api-external: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:02:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "14996"
    uid: aaf24aa6-9821-4100-9d5f-2bd05ceef388
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:06:21Z"
      message: 'load-balancer-api-internal: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.856484ms
      message: 'load-balancer-api-internal: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 7.83724ms
      message: 'load-balancer-api-internal: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 5.561587ms
      message: 'load-balancer-api-internal: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 9.149646ms
      message: 'load-balancer-api-internal: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 4.394758ms
      message: 'load-balancer-api-internal: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 8.517664ms
      message: 'load-balancer-api-internal: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 5.013477ms
      message: 'load-balancer-api-internal: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 8.107567ms
      message: 'load-balancer-api-internal: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 4.898472ms
      message: 'load-balancer-api-internal: tcp connection to a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 9.61632ms
      message: 'load-balancer-api-internal: resolved host name a774d66f8aa5144818258a037d712d0f-bf069272e127db18.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:02:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-network-check-target-ip-10-0-129-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "15333"
    uid: 40f6562f-5590-4490-86cd-8f629160c87a
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:07:21Z"
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.932893ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:07:21Z"
    - latency: 1.853416ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 1.91023ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 2.289267ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 2.249456ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 2.227155ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 1.896309ms
      message: 'network-check-target-ip-10-0-129-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:01:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-network-check-target-ip-10-0-140-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "15332"
    uid: 493db968-63a6-446c-8655-f5dd4927dc07
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:07:21Z"
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 708.632µs
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:07:21Z"
    - latency: 800.937µs
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 869.533µs
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 1.047633ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 712.095µs
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 1.610247ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 2.149683ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:01:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-network-check-target-ip-10-0-141-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "15334"
    uid: c2c0e2d0-8df1-43bb-8439-51290dc383ee
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:07:21Z"
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.870154ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:07:21Z"
    - latency: 2.164417ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 1.741537ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 1.829665ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 1.846822ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 1.956398ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 2.035343ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:01:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T12:00:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-135-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-135.ec2.internal
      uid: 42da5e1c-1fc2-46f0-ba5c-2cf6004983c4
    resourceVersion: "14994"
    uid: 768a6279-da4f-49f2-afc9-d0bfaba57fa3
  spec:
    sourcePod: network-check-source-dbd9cf844-mxlzc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T12:06:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014069ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 1.902631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:06:21Z"
    - latency: 730.768µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 2.000269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:05:21Z"
    - latency: 884.573µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 1.793265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:04:21Z"
    - latency: 920.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 1.639474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:03:21Z"
    - latency: 878.103µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T12:02:21Z"
    - latency: 2.362088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T12:02:21Z"
kind: List
metadata:
  resourceVersion: ""