apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14565"
    uid: 04001925-4d48-4f7f-a9e9-711bbca178e2
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.00092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:35Z"
    - latency: 943.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 825.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 958.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 981.691µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 1.112537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 911.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14234"
    uid: c36a1662-a2fb-4251-9c15-bf4515e3acc1
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:05:35Z"
      message: 'load-balancer-api-external: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.091502ms
      message: 'load-balancer-api-external: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 9.329907ms
      message: 'load-balancer-api-external: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 6.774859ms
      message: 'load-balancer-api-external: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 8.862602ms
      message: 'load-balancer-api-external: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 4.235427ms
      message: 'load-balancer-api-external: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 7.846527ms
      message: 'load-balancer-api-external: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 7.400731ms
      message: 'load-balancer-api-external: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 8.041985ms
      message: 'load-balancer-api-external: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 4.918368ms
      message: 'load-balancer-api-external: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 7.018071ms
      message: 'load-balancer-api-external: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:01:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14235"
    uid: eb4ab253-ca84-4124-b11b-988346d9a0e4
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:05:35Z"
      message: 'load-balancer-api-internal: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.099739ms
      message: 'load-balancer-api-internal: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 9.397102ms
      message: 'load-balancer-api-internal: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 6.771128ms
      message: 'load-balancer-api-internal: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 8.911207ms
      message: 'load-balancer-api-internal: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 3.383247ms
      message: 'load-balancer-api-internal: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 7.858135ms
      message: 'load-balancer-api-internal: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 4.116435ms
      message: 'load-balancer-api-internal: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 8.114982ms
      message: 'load-balancer-api-internal: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 4.876243ms
      message: 'load-balancer-api-internal: tcp connection to a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 7.125678ms
      message: 'load-balancer-api-internal: resolved host name a7ecaa12af40c4eecb79d98ab287316b-51503dbb0fffd7c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:01:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-128-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14562"
    uid: b22a1bd8-d682-4e89-aa9b-06f137801de9
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:35Z"
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.268µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:35Z"
    - latency: 918.767µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 1.349738ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 1.19033ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 941.608µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 937.717µs
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 1.055857ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-130-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14563"
    uid: 2c41a79a-9e57-403e-8da9-b3425bfe8f87
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:35Z"
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306658ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:35Z"
    - latency: 2.804031ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 2.476459ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 2.224315ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 2.255538ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 2.368217ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 2.327809ms
      message: 'network-check-target-ip-10-0-130-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-136-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14564"
    uid: 51f8de76-0ae4-4476-9447-445220d38ae0
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:35Z"
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173879ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:35Z"
    - latency: 2.395845ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 2.029658ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 2.27102ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 2.191608ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 2.352486ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 2.660626ms
      message: 'network-check-target-ip-10-0-136-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T10:59:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-61.ec2.internal
      uid: 979511d9-24e9-4a24-a9fe-5164c4dd0c35
    resourceVersion: "14233"
    uid: 25c5ecca-7ca9-4697-9a6c-d111c0e82389
  spec:
    sourcePod: network-check-source-685456655f-2tpzs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:05:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 2.138229ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:05:35Z"
    - latency: 934.481µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 1.722199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:04:35Z"
    - latency: 776.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 1.612693ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:03:35Z"
    - latency: 922.308µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 1.650269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:02:35Z"
    - latency: 1.065842ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:35Z"
    - latency: 1.910637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:01:35Z"
kind: List
metadata:
  resourceVersion: ""