apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "11128"
    uid: 3cc64a47-6410-41d5-bd7c-e5ad877b5108
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "14382"
    uid: 1fb6c34f-e93a-4472-b035-b615a16a8aff
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:36:44Z"
      message: 'load-balancer-api-external: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.976656ms
      message: 'load-balancer-api-external: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:44Z"
    - latency: 9.063979ms
      message: 'load-balancer-api-external: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:44Z"
    - latency: 6.852086ms
      message: 'load-balancer-api-external: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:44Z"
    - latency: 7.557194ms
      message: 'load-balancer-api-external: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:44Z"
    - latency: 5.341392ms
      message: 'load-balancer-api-external: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:44Z"
    - latency: 8.905048ms
      message: 'load-balancer-api-external: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:44Z"
    - latency: 5.664452ms
      message: 'load-balancer-api-external: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:44Z"
    - latency: 7.58404ms
      message: 'load-balancer-api-external: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:44Z"
    - latency: 6.161317ms
      message: 'load-balancer-api-external: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:44Z"
    - latency: 9.15708ms
      message: 'load-balancer-api-external: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:32:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "14383"
    uid: f5d6c1bf-06c3-4064-897d-125256610dbc
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:36:44Z"
      message: 'load-balancer-api-internal: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.303707ms
      message: 'load-balancer-api-internal: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:44Z"
    - latency: 8.995113ms
      message: 'load-balancer-api-internal: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:44Z"
    - latency: 5.063152ms
      message: 'load-balancer-api-internal: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:44Z"
    - latency: 7.621839ms
      message: 'load-balancer-api-internal: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:44Z"
    - latency: 5.304859ms
      message: 'load-balancer-api-internal: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:44Z"
    - latency: 8.967238ms
      message: 'load-balancer-api-internal: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:44Z"
    - latency: 6.852444ms
      message: 'load-balancer-api-internal: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:44Z"
    - latency: 7.623784ms
      message: 'load-balancer-api-internal: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:44Z"
    - latency: 4.766073ms
      message: 'load-balancer-api-internal: tcp connection to a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:44Z"
    - latency: 9.115017ms
      message: 'load-balancer-api-internal: resolved host name a47e05adf985d437cbaedc4a543d5fff-9fd6e8e12d2ed626.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:32:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-network-check-target-ip-10-0-128-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "11134"
    uid: 60fb334a-f92f-41e4-85a2-a4c67ef702db
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-network-check-target-ip-10-0-131-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "11135"
    uid: a959babf-1fc6-4945-a3e9-8ed35945af04
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-network-check-target-ip-10-0-139-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "11133"
    uid: 43a2cd40-0118-4055-a62f-cb94a75d04bc
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:30:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-86-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-86.ec2.internal
      uid: e4ec9c15-aa9d-45b9-9c22-dfdd1447306d
    resourceVersion: "14381"
    uid: 33d70f2e-7e4b-4699-9458-e5e69b2f1163
  spec:
    sourcePod: network-check-source-989f8b8dc-tl4m7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:36:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04404ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:44Z"
    - latency: 2.331554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:44Z"
    - latency: 1.53955ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:44Z"
    - latency: 1.842847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:44Z"
    - latency: 932.914µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:44Z"
    - latency: 1.987981ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:44Z"
    - latency: 1.24756ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:44Z"
    - latency: 2.166401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:44Z"
    - latency: 795.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:44Z"
    - latency: 2.39948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:32:44Z"
kind: List
metadata:
  resourceVersion: ""