apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "10712"
    uid: 578845b9-a1cd-49f2-86b9-5dfb0563b600
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "14278"
    uid: ae6c5967-64a1-4248-b7f1-78a5fc4c66f0
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:45:47Z"
      message: 'load-balancer-api-external: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.654531ms
      message: 'load-balancer-api-external: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:45:47Z"
    - latency: 11.300343ms
      message: 'load-balancer-api-external: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:45:47Z"
    - latency: 5.021465ms
      message: 'load-balancer-api-external: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:44:47Z"
    - latency: 8.28969ms
      message: 'load-balancer-api-external: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:44:47Z"
    - latency: 4.422818ms
      message: 'load-balancer-api-external: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:43:47Z"
    - latency: 6.467319ms
      message: 'load-balancer-api-external: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:43:47Z"
    - latency: 4.325455ms
      message: 'load-balancer-api-external: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:42:47Z"
    - latency: 8.090144ms
      message: 'load-balancer-api-external: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:42:47Z"
    - latency: 3.955432ms
      message: 'load-balancer-api-external: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:41:47Z"
    - latency: 10.296719ms
      message: 'load-balancer-api-external: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:41:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "14277"
    uid: 1ee2e652-6bf4-4212-8157-d2cdbd6d357b
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:45:47Z"
      message: 'load-balancer-api-internal: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.682739ms
      message: 'load-balancer-api-internal: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:45:47Z"
    - latency: 11.277386ms
      message: 'load-balancer-api-internal: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:45:47Z"
    - latency: 5.387449ms
      message: 'load-balancer-api-internal: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:44:47Z"
    - latency: 8.355438ms
      message: 'load-balancer-api-internal: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:44:47Z"
    - latency: 4.406434ms
      message: 'load-balancer-api-internal: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:43:47Z"
    - latency: 6.372504ms
      message: 'load-balancer-api-internal: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:43:47Z"
    - latency: 3.774785ms
      message: 'load-balancer-api-internal: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:42:47Z"
    - latency: 8.173638ms
      message: 'load-balancer-api-internal: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:42:47Z"
    - latency: 3.973502ms
      message: 'load-balancer-api-internal: tcp connection to a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:41:47Z"
    - latency: 10.362973ms
      message: 'load-balancer-api-internal: resolved host name a29e437b8352d4095add9e5b89f24e01-3409e8c506b17606.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:41:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-129-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "10718"
    uid: a76752f7-10c3-480f-b40a-e99c5fab3012
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-130-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "10716"
    uid: fba4b942-ec53-488e-82ef-5ca0b806a62a
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-131-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "10717"
    uid: 14ed3c1b-027a-454c-8208-dc5f56353789
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T16:39:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-238.ec2.internal
      uid: 044fafa9-645e-4ae6-9358-50eec219d189
    resourceVersion: "14276"
    uid: 05a65fcf-2966-46df-8139-37b036231230
  spec:
    sourcePod: network-check-source-56d84b9f44-nfvwt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T16:45:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 793.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:45:47Z"
    - latency: 1.772295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:45:47Z"
    - latency: 939.711µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:44:47Z"
    - latency: 1.900583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:44:47Z"
    - latency: 724.416µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:43:47Z"
    - latency: 1.843619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:43:47Z"
    - latency: 1.217117ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:42:47Z"
    - latency: 1.605787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:42:47Z"
    - latency: 838.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:41:47Z"
    - latency: 1.665297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:41:47Z"
kind: List
metadata:
  resourceVersion: ""