apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "12096"
    uid: 3a5fe626-1b2f-40e1-ba28-9c95a32d630d
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "15764"
    uid: 069cc472-d7d0-4487-907a-b22efd9fb722
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:17:02Z"
      message: 'load-balancer-api-external: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.192127ms
      message: 'load-balancer-api-external: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:17:02Z"
    - latency: 9.132213ms
      message: 'load-balancer-api-external: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:17:02Z"
    - latency: 4.751213ms
      message: 'load-balancer-api-external: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:16:02Z"
    - latency: 9.034839ms
      message: 'load-balancer-api-external: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:16:02Z"
    - latency: 5.639437ms
      message: 'load-balancer-api-external: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:15:02Z"
    - latency: 7.561006ms
      message: 'load-balancer-api-external: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:15:02Z"
    - latency: 4.113163ms
      message: 'load-balancer-api-external: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:14:02Z"
    - latency: 8.24233ms
      message: 'load-balancer-api-external: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:14:02Z"
    - latency: 8.187555ms
      message: 'load-balancer-api-external: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:13:02Z"
    - latency: 7.368229ms
      message: 'load-balancer-api-external: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "15763"
    uid: 2d5a59bd-5db9-4cd1-9a2c-553245b8be9e
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:17:02Z"
      message: 'load-balancer-api-internal: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.186935ms
      message: 'load-balancer-api-internal: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:17:02Z"
    - latency: 9.100676ms
      message: 'load-balancer-api-internal: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:17:02Z"
    - latency: 3.429818ms
      message: 'load-balancer-api-internal: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:16:02Z"
    - latency: 9.01081ms
      message: 'load-balancer-api-internal: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:16:02Z"
    - latency: 5.629257ms
      message: 'load-balancer-api-internal: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:15:02Z"
    - latency: 7.510103ms
      message: 'load-balancer-api-internal: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:15:02Z"
    - latency: 4.11766ms
      message: 'load-balancer-api-internal: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:14:02Z"
    - latency: 8.200793ms
      message: 'load-balancer-api-internal: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:14:02Z"
    - latency: 5.233439ms
      message: 'load-balancer-api-internal: tcp connection to a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:13:02Z"
    - latency: 7.308247ms
      message: 'load-balancer-api-internal: resolved host name a885e080b748849fe8d2c0e941da5c0e-627599c0405ae7d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-network-check-target-ip-10-0-134-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "12103"
    uid: 50c1fb02-053c-4690-b3b2-7c570f890e56
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-network-check-target-ip-10-0-141-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "12101"
    uid: f0b275ec-9235-471d-a823-9db65e85cc3c
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-network-check-target-ip-10-0-142-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "12102"
    uid: d8dc3ba1-f91b-4244-bfa8-f3c6af1e00b8
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T09:11:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-70.ec2.internal
      uid: 7c9fbbbe-aa0d-40a7-9173-b61a5751bfb3
    resourceVersion: "15762"
    uid: d1e07316-9fd5-4be1-a670-ebedf82286ff
  spec:
    sourcePod: network-check-source-7d88cb55d8-bcdfc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T09:17:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.033µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:17:02Z"
    - latency: 2.182054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:17:02Z"
    - latency: 1.003339ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:16:02Z"
    - latency: 2.004839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:16:02Z"
    - latency: 989.152µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:15:02Z"
    - latency: 2.112297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:15:02Z"
    - latency: 840.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:14:02Z"
    - latency: 1.761398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:14:02Z"
    - latency: 1.263904ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T09:13:02Z"
    - latency: 1.690421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T09:13:02Z"
kind: List
metadata:
  resourceVersion: ""