apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "10262"
    uid: be842047-7edb-4f3b-b6ab-4d4b135c96ec
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "12984"
    uid: 0b8a7cde-35f3-4f61-80c7-4180f280b564
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T09:36:43Z"
      message: 'load-balancer-api-external: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.380311ms
      message: 'load-balancer-api-external: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:36:43Z"
    - latency: 10.218288ms
      message: 'load-balancer-api-external: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:36:43Z"
    - latency: 5.083299ms
      message: 'load-balancer-api-external: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:35:43Z"
    - latency: 9.318609ms
      message: 'load-balancer-api-external: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:35:43Z"
    - latency: 5.252984ms
      message: 'load-balancer-api-external: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:34:43Z"
    - latency: 8.708978ms
      message: 'load-balancer-api-external: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:34:43Z"
    - latency: 4.096864ms
      message: 'load-balancer-api-external: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:33:43Z"
    - latency: 8.542231ms
      message: 'load-balancer-api-external: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:33:43Z"
    - latency: 3.356366ms
      message: 'load-balancer-api-external: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:32:43Z"
    - latency: 14.445243ms
      message: 'load-balancer-api-external: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:32:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "12983"
    uid: b2b44863-15e1-46c0-83a2-ba5d5f6309b4
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T09:36:43Z"
      message: 'load-balancer-api-internal: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.199833ms
      message: 'load-balancer-api-internal: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:36:43Z"
    - latency: 10.069363ms
      message: 'load-balancer-api-internal: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:36:43Z"
    - latency: 4.812124ms
      message: 'load-balancer-api-internal: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:35:43Z"
    - latency: 9.400109ms
      message: 'load-balancer-api-internal: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:35:43Z"
    - latency: 5.267852ms
      message: 'load-balancer-api-internal: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:34:43Z"
    - latency: 8.572122ms
      message: 'load-balancer-api-internal: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:34:43Z"
    - latency: 3.22811ms
      message: 'load-balancer-api-internal: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:33:43Z"
    - latency: 8.510573ms
      message: 'load-balancer-api-internal: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:33:43Z"
    - latency: 5.540025ms
      message: 'load-balancer-api-internal: tcp connection to ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:32:43Z"
    - latency: 14.315985ms
      message: 'load-balancer-api-internal: resolved host name ada4f13427bdc4ca4872cae0778c986b-827f7e147c4bce95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:32:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-network-check-target-ip-10-0-128-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "10259"
    uid: 516f655a-dce2-4fe4-ba02-eea94d489728
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-network-check-target-ip-10-0-128-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "10260"
    uid: f31d5930-ac82-4ecc-a249-0d0bffa995b2
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-network-check-target-ip-10-0-142-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "10258"
    uid: 26229f28-3e1d-476b-9acf-9ab7125ee676
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T09:30:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-82.ec2.internal
      uid: 976b1b87-bc28-4d89-a45e-88a597d14037
    resourceVersion: "12982"
    uid: 5add8736-b5f2-4541-b07d-41b25846b22d
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5gm5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T09:36:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.368095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:36:43Z"
    - latency: 1.727225ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:36:43Z"
    - latency: 840.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:35:43Z"
    - latency: 2.092637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:35:43Z"
    - latency: 983.413µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:34:43Z"
    - latency: 2.080217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:34:43Z"
    - latency: 986.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:33:43Z"
    - latency: 2.008782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:33:43Z"
    - latency: 724.925µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T09:32:43Z"
    - latency: 7.882194ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T09:32:43Z"
kind: List
metadata:
  resourceVersion: ""