apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "11178"
    uid: 7fb14c87-a6d7-4c05-a68e-be320bff8026
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "14808"
    uid: 071296b4-ced7-4df8-844f-a0b7e6322c2c
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:46:36Z"
      message: 'load-balancer-api-external: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.471455ms
      message: 'load-balancer-api-external: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:46:36Z"
    - latency: 6.385846ms
      message: 'load-balancer-api-external: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:46:36Z"
    - latency: 5.368551ms
      message: 'load-balancer-api-external: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:45:36Z"
    - latency: 7.473682ms
      message: 'load-balancer-api-external: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:45:36Z"
    - latency: 5.786162ms
      message: 'load-balancer-api-external: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:44:36Z"
    - latency: 10.272452ms
      message: 'load-balancer-api-external: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:44:36Z"
    - latency: 3.903659ms
      message: 'load-balancer-api-external: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:43:36Z"
    - latency: 6.88492ms
      message: 'load-balancer-api-external: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:43:36Z"
    - latency: 5.325486ms
      message: 'load-balancer-api-external: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:42:36Z"
    - latency: 6.340733ms
      message: 'load-balancer-api-external: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "14807"
    uid: 6d320e5e-13e0-4922-ab48-25f46b7227fd
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:46:36Z"
      message: 'load-balancer-api-internal: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.436805ms
      message: 'load-balancer-api-internal: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:46:36Z"
    - latency: 6.513726ms
      message: 'load-balancer-api-internal: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:46:36Z"
    - latency: 4.67283ms
      message: 'load-balancer-api-internal: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:45:36Z"
    - latency: 7.404576ms
      message: 'load-balancer-api-internal: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:45:36Z"
    - latency: 6.063268ms
      message: 'load-balancer-api-internal: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:44:36Z"
    - latency: 10.321456ms
      message: 'load-balancer-api-internal: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:44:36Z"
    - latency: 5.048043ms
      message: 'load-balancer-api-internal: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:43:36Z"
    - latency: 6.857866ms
      message: 'load-balancer-api-internal: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:43:36Z"
    - latency: 5.334339ms
      message: 'load-balancer-api-internal: tcp connection to a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:42:36Z"
    - latency: 6.388861ms
      message: 'load-balancer-api-internal: resolved host name a4be1868ec2f7460596e46a4765f3ff4-da721b0b17085b9c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-network-check-target-ip-10-0-133-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "11184"
    uid: 8f6241bf-fc93-4205-b3a3-be0e2fc97224
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-network-check-target-ip-10-0-136-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "11185"
    uid: 6cfd973c-0f46-405e-9beb-e4fa79061437
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-network-check-target-ip-10-0-142-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "11183"
    uid: 58286d28-b346-4035-aed8-423ea3a8c467
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:40:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-170-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-170.ec2.internal
      uid: d111ed76-6ac6-44d7-9479-eb65b1c882ac
    resourceVersion: "14806"
    uid: b191b24e-2611-4ebe-83cd-b43b958d1b45
  spec:
    sourcePod: network-check-source-7d88cb55d8-rc9s9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:46:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 808.469µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:46:36Z"
    - latency: 1.509024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:46:36Z"
    - latency: 806.041µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:45:36Z"
    - latency: 1.815157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:45:36Z"
    - latency: 965.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:44:36Z"
    - latency: 1.415754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:44:36Z"
    - latency: 1.016758ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:43:36Z"
    - latency: 1.993701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:43:36Z"
    - latency: 954.062µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:42:36Z"
    - latency: 1.776195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:42:36Z"
kind: List
metadata:
  resourceVersion: ""