apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "11226"
    uid: 2f35f395-500b-4958-b270-a52797970d00
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "14806"
    uid: c0adf3a8-d5ff-4e84-a96e-f1dd9d4dcc19
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T11:53:48Z"
      message: 'load-balancer-api-external: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.250634ms
      message: 'load-balancer-api-external: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:53:48Z"
    - latency: 8.155837ms
      message: 'load-balancer-api-external: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:53:48Z"
    - latency: 4.82397ms
      message: 'load-balancer-api-external: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:52:48Z"
    - latency: 8.292197ms
      message: 'load-balancer-api-external: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:52:48Z"
    - latency: 5.566901ms
      message: 'load-balancer-api-external: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:51:48Z"
    - latency: 7.826111ms
      message: 'load-balancer-api-external: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:51:48Z"
    - latency: 4.493913ms
      message: 'load-balancer-api-external: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:50:48Z"
    - latency: 7.497696ms
      message: 'load-balancer-api-external: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:50:48Z"
    - latency: 6.643674ms
      message: 'load-balancer-api-external: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:49:48Z"
    - latency: 7.295491ms
      message: 'load-balancer-api-external: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:49:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "14807"
    uid: 12286f55-a87d-4a9a-9b9e-a50e4bbf5b44
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T11:53:48Z"
      message: 'load-balancer-api-internal: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.242526ms
      message: 'load-balancer-api-internal: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:53:48Z"
    - latency: 8.119336ms
      message: 'load-balancer-api-internal: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:53:48Z"
    - latency: 4.852306ms
      message: 'load-balancer-api-internal: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:52:48Z"
    - latency: 8.234005ms
      message: 'load-balancer-api-internal: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:52:48Z"
    - latency: 5.563768ms
      message: 'load-balancer-api-internal: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:51:48Z"
    - latency: 7.746947ms
      message: 'load-balancer-api-internal: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:51:48Z"
    - latency: 4.500232ms
      message: 'load-balancer-api-internal: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:50:48Z"
    - latency: 7.534118ms
      message: 'load-balancer-api-internal: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:50:48Z"
    - latency: 6.605665ms
      message: 'load-balancer-api-internal: tcp connection to ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:49:48Z"
    - latency: 7.268171ms
      message: 'load-balancer-api-internal: resolved host name ae09555d409b14b4a8fe37ede80af83d-69ffd0fb22e9008c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:49:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-network-check-target-ip-10-0-128-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "11232"
    uid: 3b4467ab-c01e-43d4-8fcf-b62374a38a21
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-network-check-target-ip-10-0-131-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "11231"
    uid: 586596bb-5288-465a-afad-5bea79203a1a
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-network-check-target-ip-10-0-138-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "11233"
    uid: 151d5353-6ba3-4dea-9f2d-570048ffaa87
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T11:47:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-118.ec2.internal
      uid: e1a8d1bb-cb57-4080-aec9-6c6878549fc4
    resourceVersion: "14804"
    uid: 06dc7d12-9ab5-4609-b537-409075b4d72a
  spec:
    sourcePod: network-check-source-7d88cb55d8-lvbdz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T11:53:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092752ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:53:48Z"
    - latency: 1.812168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:53:48Z"
    - latency: 893.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:52:48Z"
    - latency: 2.03373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:52:48Z"
    - latency: 1.021526ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:51:48Z"
    - latency: 2.155558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:51:48Z"
    - latency: 1.115608ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:50:48Z"
    - latency: 1.7235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:50:48Z"
    - latency: 1.472304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T11:49:48Z"
    - latency: 1.756465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T11:49:48Z"
kind: List
metadata:
  resourceVersion: ""