apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "11924"
    uid: 466427da-bda8-42c4-91ae-bcd6c8b794da
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "15294"
    uid: e990eca3-81f9-4bc3-a1e5-50247356bcbd
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T14:34:46Z"
      message: 'load-balancer-api-external: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.165323ms
      message: 'load-balancer-api-external: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:34:46Z"
    - latency: 8.355544ms
      message: 'load-balancer-api-external: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:34:46Z"
    - latency: 5.621785ms
      message: 'load-balancer-api-external: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:33:46Z"
    - latency: 9.182156ms
      message: 'load-balancer-api-external: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:33:46Z"
    - latency: 5.57133ms
      message: 'load-balancer-api-external: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:32:46Z"
    - latency: 7.965983ms
      message: 'load-balancer-api-external: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:32:46Z"
    - latency: 4.777493ms
      message: 'load-balancer-api-external: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:31:46Z"
    - latency: 9.075105ms
      message: 'load-balancer-api-external: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:31:46Z"
    - latency: 5.11677ms
      message: 'load-balancer-api-external: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:30:46Z"
    - latency: 9.211799ms
      message: 'load-balancer-api-external: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:30:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "15295"
    uid: eb8c183f-dbc6-44ef-9510-984c37c4bbeb
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T14:34:46Z"
      message: 'load-balancer-api-internal: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.981654ms
      message: 'load-balancer-api-internal: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:34:46Z"
    - latency: 8.270464ms
      message: 'load-balancer-api-internal: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:34:46Z"
    - latency: 6.091026ms
      message: 'load-balancer-api-internal: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:33:46Z"
    - latency: 9.148691ms
      message: 'load-balancer-api-internal: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:33:46Z"
    - latency: 5.561169ms
      message: 'load-balancer-api-internal: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:32:46Z"
    - latency: 7.976976ms
      message: 'load-balancer-api-internal: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:32:46Z"
    - latency: 3.849108ms
      message: 'load-balancer-api-internal: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:31:46Z"
    - latency: 9.11637ms
      message: 'load-balancer-api-internal: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:31:46Z"
    - latency: 5.187339ms
      message: 'load-balancer-api-internal: tcp connection to af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:30:46Z"
    - latency: 9.124686ms
      message: 'load-balancer-api-internal: resolved host name af62122030017471dbe3c3e11a02434a-4c8587207ea7e381.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:30:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-ip-10-0-131-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "11923"
    uid: 09f60683-6fc4-48b2-96a8-e15ccd7b32f9
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-ip-10-0-137-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "11922"
    uid: ef64db51-eebe-4642-97f4-75d0a81b4e98
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-ip-10-0-143-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "11920"
    uid: 4539e010-4f26-4ed2-8330-b3fc37d951bf
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T14:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: e82b6d78-fde8-44c3-8536-b6e00025d935
    resourceVersion: "15293"
    uid: 9d29ccea-537d-4310-9b5f-54e4466f3994
  spec:
    sourcePod: network-check-source-dbd9cf844-j856m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T14:34:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.329µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:34:46Z"
    - latency: 1.681962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:34:46Z"
    - latency: 856.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:33:46Z"
    - latency: 2.20913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:33:46Z"
    - latency: 713.077µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:32:46Z"
    - latency: 1.682922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:32:46Z"
    - latency: 1.04766ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:31:46Z"
    - latency: 1.642516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:31:46Z"
    - latency: 728.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:30:46Z"
    - latency: 5.81843ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:30:46Z"
kind: List
metadata:
  resourceVersion: ""