apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14979"
    uid: 9b64152c-f8c1-431f-bc8d-f33c932deec3
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:44:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.555781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:44:01Z"
    - latency: 866.308µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 841.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 828.084µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 1.423287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 759.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 1.018952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:38:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14533"
    uid: ba17cb67-94c7-4f68-8264-fcfc434e4c8d
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:43:01Z"
      message: 'load-balancer-api-external: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.440838ms
      message: 'load-balancer-api-external: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 8.854819ms
      message: 'load-balancer-api-external: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 5.541778ms
      message: 'load-balancer-api-external: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 8.430141ms
      message: 'load-balancer-api-external: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 4.607223ms
      message: 'load-balancer-api-external: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 8.70692ms
      message: 'load-balancer-api-external: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 5.858674ms
      message: 'load-balancer-api-external: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 9.029315ms
      message: 'load-balancer-api-external: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 5.052171ms
      message: 'load-balancer-api-external: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 8.154663ms
      message: 'load-balancer-api-external: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:39:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14534"
    uid: 6d305fa6-eb0f-42b2-ac51-795bc3937468
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:43:01Z"
      message: 'load-balancer-api-internal: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.531713ms
      message: 'load-balancer-api-internal: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 8.829196ms
      message: 'load-balancer-api-internal: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 5.561257ms
      message: 'load-balancer-api-internal: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 8.411975ms
      message: 'load-balancer-api-internal: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 3.647916ms
      message: 'load-balancer-api-internal: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 8.661757ms
      message: 'load-balancer-api-internal: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 4.260412ms
      message: 'load-balancer-api-internal: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 8.988449ms
      message: 'load-balancer-api-internal: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 5.295021ms
      message: 'load-balancer-api-internal: tcp connection to a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 8.124372ms
      message: 'load-balancer-api-internal: resolved host name a77912bd113f44a52b676479c1792e22-89cf602df734e635.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:39:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-ip-10-0-128-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14978"
    uid: ce9092aa-3a0f-4d81-9843-d7139e9160f8
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:44:01Z"
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.288583ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:44:01Z"
    - latency: 2.073856ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 2.180191ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 2.009636ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 2.416209ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 2.13845ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 2.219651ms
      message: 'network-check-target-ip-10-0-128-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:38:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-ip-10-0-131-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14976"
    uid: 494ce2d5-553b-42d3-88d3-b674d998a4d5
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:44:01Z"
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 736.428µs
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:44:01Z"
    - latency: 775.922µs
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 1.312007ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 1.189717ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 1.020623ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 1.321851ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 1.291124ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:38:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-ip-10-0-140-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14977"
    uid: 3c9a3fda-785f-49f3-84dd-fc844d2abb27
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:44:01Z"
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.917206ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:44:01Z"
    - latency: 1.863599ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 1.627757ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 1.742439ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 1.94563ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 1.930881ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 1.881605ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:38:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T12:37:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: 5c2c969a-fdad-4b4d-b0af-b990b4028b9a
    resourceVersion: "14532"
    uid: 32d6f5b1-0a2a-4df3-980e-2a90c768c25f
  spec:
    sourcePod: network-check-source-6f8b768455-lpc8s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T12:43:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 873.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 1.539656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:43:01Z"
    - latency: 919.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 1.586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:42:01Z"
    - latency: 837.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 1.822113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:41:01Z"
    - latency: 853.787µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 1.751783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:40:01Z"
    - latency: 825.764µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:39:01Z"
    - latency: 1.622803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:39:01Z"
kind: List
metadata:
  resourceVersion: ""