apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "14895"
    uid: 441db24b-b97d-4aef-a9c5-f0d7cc39cc59
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.959µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:05Z"
    - latency: 890.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:05Z"
    - latency: 905.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:05Z"
    - latency: 938.623µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:05Z"
    - latency: 1.137931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:05Z"
    - latency: 1.12774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:05Z"
    - latency: 923.178µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "16696"
    uid: 9a7c4407-275d-4d1b-94fb-f4e4cd9a0d43
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:18:05Z"
      message: 'load-balancer-api-external: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.068672ms
      message: 'load-balancer-api-external: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:24:05Z"
    - latency: 9.162736ms
      message: 'load-balancer-api-external: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:24:05Z"
    - latency: 4.758791ms
      message: 'load-balancer-api-external: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:23:05Z"
    - latency: 8.846347ms
      message: 'load-balancer-api-external: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:23:05Z"
    - latency: 4.674795ms
      message: 'load-balancer-api-external: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:22:05Z"
    - latency: 8.977909ms
      message: 'load-balancer-api-external: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:22:05Z"
    - latency: 4.77537ms
      message: 'load-balancer-api-external: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:21:05Z"
    - latency: 8.610639ms
      message: 'load-balancer-api-external: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:21:05Z"
    - latency: 5.705ms
      message: 'load-balancer-api-external: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:05Z"
    - latency: 9.223841ms
      message: 'load-balancer-api-external: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:20:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "16697"
    uid: 888cef9f-65fe-4c0f-857f-3089a42e7d59
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:18:05Z"
      message: 'load-balancer-api-internal: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.748007ms
      message: 'load-balancer-api-internal: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:24:05Z"
    - latency: 9.090216ms
      message: 'load-balancer-api-internal: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:24:05Z"
    - latency: 4.821532ms
      message: 'load-balancer-api-internal: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:23:05Z"
    - latency: 8.885327ms
      message: 'load-balancer-api-internal: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:23:05Z"
    - latency: 4.665419ms
      message: 'load-balancer-api-internal: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:22:05Z"
    - latency: 9.004214ms
      message: 'load-balancer-api-internal: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:22:05Z"
    - latency: 4.634061ms
      message: 'load-balancer-api-internal: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:21:05Z"
    - latency: 8.62833ms
      message: 'load-balancer-api-internal: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:21:05Z"
    - latency: 5.683198ms
      message: 'load-balancer-api-internal: tcp connection to a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:05Z"
    - latency: 9.29891ms
      message: 'load-balancer-api-internal: resolved host name a5beafa9a4bf7453d8d2f9d20a81f95d-fdeb85bc73dfd493.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:20:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-network-check-target-ip-10-0-128-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "14893"
    uid: 385a070f-1a68-467a-a98b-0ed58d8890c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:05Z"
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.251722ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:05Z"
    - latency: 2.890557ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:05Z"
    - latency: 2.336797ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:05Z"
    - latency: 2.113086ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:05Z"
    - latency: 2.495082ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:05Z"
    - latency: 2.273458ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:05Z"
    - latency: 2.553217ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-network-check-target-ip-10-0-135-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "14892"
    uid: f92067a7-5faf-49d7-acd9-25d42d71c26a
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:05Z"
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.3µs
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:05Z"
    - latency: 1.787012ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:05Z"
    - latency: 1.364592ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:05Z"
    - latency: 946.991µs
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:05Z"
    - latency: 1.347529ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:05Z"
    - latency: 855.717µs
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:05Z"
    - latency: 1.790331ms
      message: 'network-check-target-ip-10-0-135-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-network-check-target-ip-10-0-138-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "14894"
    uid: 265d9a33-65e7-4ca6-856e-5bd950a5bbbd
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:19:05Z"
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.214888ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:19:05Z"
    - latency: 2.365358ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:18:05Z"
    - latency: 2.272905ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:17:05Z"
    - latency: 1.989924ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:16:05Z"
    - latency: 2.357358ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:15:05Z"
    - latency: 2.053858ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:14:05Z"
    - latency: 1.924182ms
      message: 'network-check-target-ip-10-0-138-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-59-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-59.ec2.internal
      uid: f7be5ae4-1831-4f19-bbef-ee568a601f95
    resourceVersion: "16695"
    uid: 6436d5e9-3449-46d6-b769-4a64e2a1fd76
  spec:
    sourcePod: network-check-source-869dcfcdcd-dtfm2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:18:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 775.849µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:24:05Z"
    - latency: 2.100458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:24:05Z"
    - latency: 812.518µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:23:05Z"
    - latency: 1.807632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:23:05Z"
    - latency: 762.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:22:05Z"
    - latency: 1.869317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:22:05Z"
    - latency: 1.282312ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:21:05Z"
    - latency: 1.961372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:21:05Z"
    - latency: 812.529µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T10:20:05Z"
    - latency: 2.550073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T10:20:05Z"
kind: List
metadata:
  resourceVersion: ""