apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "12451"
    uid: 54eb3413-fd8e-4081-ba18-e3cdb16324a5
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "15819"
    uid: e8a81258-4aab-417e-8128-270050e73c6f
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:33:09Z"
      message: 'load-balancer-api-external: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.543414ms
      message: 'load-balancer-api-external: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:09Z"
    - latency: 10.570477ms
      message: 'load-balancer-api-external: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:33:09Z"
    - latency: 4.632365ms
      message: 'load-balancer-api-external: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:09Z"
    - latency: 10.51847ms
      message: 'load-balancer-api-external: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:32:09Z"
    - latency: 3.758796ms
      message: 'load-balancer-api-external: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:09Z"
    - latency: 10.136625ms
      message: 'load-balancer-api-external: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:31:09Z"
    - latency: 3.796503ms
      message: 'load-balancer-api-external: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:09Z"
    - latency: 8.125817ms
      message: 'load-balancer-api-external: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:30:09Z"
    - latency: 4.921546ms
      message: 'load-balancer-api-external: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:09Z"
    - latency: 10.61296ms
      message: 'load-balancer-api-external: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "15820"
    uid: ddc1849e-7b59-4051-9a39-7bc5b429c737
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:33:09Z"
      message: 'load-balancer-api-internal: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.951783ms
      message: 'load-balancer-api-internal: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:09Z"
    - latency: 10.589148ms
      message: 'load-balancer-api-internal: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:33:09Z"
    - latency: 4.638974ms
      message: 'load-balancer-api-internal: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:09Z"
    - latency: 10.420533ms
      message: 'load-balancer-api-internal: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:32:09Z"
    - latency: 6.27925ms
      message: 'load-balancer-api-internal: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:09Z"
    - latency: 10.087122ms
      message: 'load-balancer-api-internal: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:31:09Z"
    - latency: 5.196945ms
      message: 'load-balancer-api-internal: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:09Z"
    - latency: 8.162564ms
      message: 'load-balancer-api-internal: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:30:09Z"
    - latency: 4.90571ms
      message: 'load-balancer-api-internal: tcp connection to addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:09Z"
    - latency: 10.528628ms
      message: 'load-balancer-api-internal: resolved host name addc8b70a614e44c0bc82b6e6717685d-1cbb3833157fd20e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-ip-10-0-131-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "12456"
    uid: 994773bb-5652-4cb0-8052-fc12e04bff2d
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-ip-10-0-139-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "12458"
    uid: 48951245-419a-4820-b3e7-e63700fec5d8
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-ip-10-0-140-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "12457"
    uid: f8dd1bf9-9799-407c-8e34-3e1221b76da6
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T15:27:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 11c316e6-db08-418f-9dee-6ba4742336ff
    resourceVersion: "15818"
    uid: a0ca7e1a-de8b-4648-b8b7-2709e3b7ba6a
  spec:
    sourcePod: network-check-source-dbd9cf844-4wp6k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T15:33:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.013µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:33:09Z"
    - latency: 1.69622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:33:09Z"
    - latency: 1.201117ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:32:09Z"
    - latency: 1.912889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:32:09Z"
    - latency: 732.148µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:31:09Z"
    - latency: 1.83592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:31:09Z"
    - latency: 791.894µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:30:09Z"
    - latency: 1.628296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:30:09Z"
    - latency: 761.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T15:29:09Z"
    - latency: 1.502988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T15:29:09Z"
kind: List
metadata:
  resourceVersion: ""