apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "9575"
    uid: cbc52d5f-d584-4ae8-abdb-992bea6dd283
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "10829"
    uid: 8d5dc3ba-e528-4e64-9f39-e56059a0102f
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T03:32:28Z"
      message: 'load-balancer-api-external: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.564632ms
      message: 'load-balancer-api-external: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:32:28Z"
    - latency: 6.236584ms
      message: 'load-balancer-api-external: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:32:28Z"
    - latency: 55.003669ms
      message: 'load-balancer-api-external: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:31:28Z"
    - latency: 6.533652ms
      message: 'load-balancer-api-external: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:31:28Z"
    - latency: 53.318666ms
      message: 'load-balancer-api-external: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:30:28Z"
    - latency: 6.220098ms
      message: 'load-balancer-api-external: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:30:28Z"
    - latency: 54.253235ms
      message: 'load-balancer-api-external: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:29:28Z"
    - latency: 6.636175ms
      message: 'load-balancer-api-external: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:29:28Z"
    - latency: 53.387208ms
      message: 'load-balancer-api-external: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:28:28Z"
    - latency: 6.108999ms
      message: 'load-balancer-api-external: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "10830"
    uid: 75ba4bc1-8f29-44e5-825c-0caa7ca45c83
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T03:32:28Z"
      message: 'load-balancer-api-internal: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.059316ms
      message: 'load-balancer-api-internal: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:32:28Z"
    - latency: 6.297991ms
      message: 'load-balancer-api-internal: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:32:28Z"
    - latency: 53.53266ms
      message: 'load-balancer-api-internal: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:31:28Z"
    - latency: 6.465035ms
      message: 'load-balancer-api-internal: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:31:28Z"
    - latency: 53.260887ms
      message: 'load-balancer-api-internal: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:30:28Z"
    - latency: 6.156628ms
      message: 'load-balancer-api-internal: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:30:28Z"
    - latency: 54.202087ms
      message: 'load-balancer-api-internal: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:29:28Z"
    - latency: 6.711099ms
      message: 'load-balancer-api-internal: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:29:28Z"
    - latency: 53.397395ms
      message: 'load-balancer-api-internal: tcp connection to aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:28:28Z"
    - latency: 6.032396ms
      message: 'load-balancer-api-internal: resolved host name aa5537d3c89224dc4affa3f21f798176-2985b66dc015ef61.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-ip-10-0-128-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "9572"
    uid: 0ed2426e-6fe5-4e87-aa34-05b8fc71ba16
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-ip-10-0-130-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "9573"
    uid: 4b063648-d5e6-4e7c-a57a-5e7b0b7d32f7
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-ip-10-0-139-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "9574"
    uid: 18c8c999-7e34-442b-8fc5-43df480d1045
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T03:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.us-west-1.compute.internal
      uid: 5debe88d-04d2-49f3-9d7e-4d4759fd03b5
    resourceVersion: "10828"
    uid: c68f86c4-4c1a-4c6d-aa28-c096d1014b5e
  spec:
    sourcePod: network-check-source-6f78d59f99-54x6f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T03:32:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.201µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:32:28Z"
    - latency: 1.968183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:32:28Z"
    - latency: 929.837µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:31:28Z"
    - latency: 1.918909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:31:28Z"
    - latency: 997.206µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:30:28Z"
    - latency: 2.092453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:30:28Z"
    - latency: 851.645µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:29:28Z"
    - latency: 2.582619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:29:28Z"
    - latency: 1.076119ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T03:28:28Z"
    - latency: 2.132963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T03:28:28Z"
kind: List
metadata:
  resourceVersion: ""