apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "10757"
    uid: b66e5207-8435-4db4-b106-18e308ebae29
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "14077"
    uid: 223aa043-303f-4a75-8903-46af9f87070c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T07:00:26Z"
      message: 'load-balancer-api-external: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.416873ms
      message: 'load-balancer-api-external: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:00:26Z"
    - latency: 13.745708ms
      message: 'load-balancer-api-external: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:00:26Z"
    - latency: 4.472345ms
      message: 'load-balancer-api-external: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:59:26Z"
    - latency: 8.360101ms
      message: 'load-balancer-api-external: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:59:26Z"
    - latency: 5.184584ms
      message: 'load-balancer-api-external: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:58:26Z"
    - latency: 7.957178ms
      message: 'load-balancer-api-external: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:58:26Z"
    - latency: 4.628471ms
      message: 'load-balancer-api-external: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:57:26Z"
    - latency: 8.709398ms
      message: 'load-balancer-api-external: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:57:26Z"
    - latency: 5.128824ms
      message: 'load-balancer-api-external: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:56:26Z"
    - latency: 6.763607ms
      message: 'load-balancer-api-external: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:56:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "14076"
    uid: cef5b863-bbf2-4bf2-8cc6-5ba75192ffaa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T07:00:26Z"
      message: 'load-balancer-api-internal: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.082481ms
      message: 'load-balancer-api-internal: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:00:26Z"
    - latency: 13.791951ms
      message: 'load-balancer-api-internal: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:00:26Z"
    - latency: 4.495789ms
      message: 'load-balancer-api-internal: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:59:26Z"
    - latency: 8.473242ms
      message: 'load-balancer-api-internal: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:59:26Z"
    - latency: 5.094502ms
      message: 'load-balancer-api-internal: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:58:26Z"
    - latency: 7.879472ms
      message: 'load-balancer-api-internal: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:58:26Z"
    - latency: 4.328317ms
      message: 'load-balancer-api-internal: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:57:26Z"
    - latency: 8.799077ms
      message: 'load-balancer-api-internal: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:57:26Z"
    - latency: 4.606723ms
      message: 'load-balancer-api-internal: tcp connection to a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:56:26Z"
    - latency: 6.727877ms
      message: 'load-balancer-api-internal: resolved host name a5d84f5c50d2442f1b2b41bccb96706e-da65c343f8261484.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:56:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-network-check-target-ip-10-0-128-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "10764"
    uid: 2db17911-38b6-42b5-80fc-a2b214246260
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-network-check-target-ip-10-0-128-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "10762"
    uid: f3a755a0-9bc9-4fdf-a63b-1ac9bd3420d2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-network-check-target-ip-10-0-143-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "10763"
    uid: e38f848c-1b33-41e2-87b1-a0f9f9a90a0c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T06:54:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-152.ec2.internal
      uid: 3be793e9-7f00-41ee-8483-d95122076c72
    resourceVersion: "14075"
    uid: 80d708e3-9e08-4efd-a264-ae4b2b385311
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bzw8j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T07:00:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.615µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T07:00:26Z"
    - latency: 1.836498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T07:00:26Z"
    - latency: 862.525µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:59:26Z"
    - latency: 1.628321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:59:26Z"
    - latency: 1.005408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:58:26Z"
    - latency: 1.562446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:58:26Z"
    - latency: 770.453µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:57:26Z"
    - latency: 1.722782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:57:26Z"
    - latency: 952.221µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T06:56:26Z"
    - latency: 1.804233ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T06:56:26Z"
kind: List
metadata:
  resourceVersion: ""