apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "22710"
    uid: 6bf45d15-2afd-483f-8031-4a25c53d15e5
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:34:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.172µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:34:26Z"
    - latency: 1.54007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 889.545µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 1.097862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 726.899µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 963.176µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 1.264786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "21640"
    uid: f27be4a7-25cb-4f07-bcfa-71622c60ef50
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:33:26Z"
      message: 'load-balancer-api-external: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.097139ms
      message: 'load-balancer-api-external: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 16.6244ms
      message: 'load-balancer-api-external: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 4.840201ms
      message: 'load-balancer-api-external: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 8.489629ms
      message: 'load-balancer-api-external: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 5.642718ms
      message: 'load-balancer-api-external: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 8.335455ms
      message: 'load-balancer-api-external: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 4.798925ms
      message: 'load-balancer-api-external: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 14.807885ms
      message: 'load-balancer-api-external: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 3.867583ms
      message: 'load-balancer-api-external: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 9.014185ms
      message: 'load-balancer-api-external: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "21641"
    uid: bdbcadf0-e6c4-4dfd-8044-008810656ff2
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:33:26Z"
      message: 'load-balancer-api-internal: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.064459ms
      message: 'load-balancer-api-internal: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 16.08066ms
      message: 'load-balancer-api-internal: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 5.508934ms
      message: 'load-balancer-api-internal: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 8.510661ms
      message: 'load-balancer-api-internal: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 4.131815ms
      message: 'load-balancer-api-internal: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 8.250154ms
      message: 'load-balancer-api-internal: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 4.806207ms
      message: 'load-balancer-api-internal: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 14.064492ms
      message: 'load-balancer-api-internal: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 3.897952ms
      message: 'load-balancer-api-internal: tcp connection to a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 8.921316ms
      message: 'load-balancer-api-internal: resolved host name a5c3af94c92304f43803c023123a4c99-0c6b9fdf5277f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-130-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "22707"
    uid: d2fbf03c-77d6-43ec-9ae3-7a9eb8d9ae51
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:34:26Z"
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 697.974µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:34:26Z"
    - latency: 1.249346ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 974.035µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 969.186µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 2.291925ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 984.057µs
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 1.513334ms
      message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-132-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "22709"
    uid: e05ccb03-2abf-4e3c-b80a-d8d56ffbc32d
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:34:26Z"
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.898543ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:34:26Z"
    - latency: 3.032676ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 2.067413ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 2.303982ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 2.161873ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 1.975133ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 2.280734ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-133-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "22708"
    uid: a271592b-5ef9-46b4-9ce1-3cb8e5f8e45a
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:34:26Z"
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.860021ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:34:26Z"
    - latency: 2.943985ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 2.138367ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 1.984304ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 1.919964ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 1.723047ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 2.115034ms
      message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T22:27:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-91-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-91.ec2.internal
      uid: 16b0a035-6f4a-47ee-a591-d37048b7e33f
    resourceVersion: "21639"
    uid: 07d832ce-ad5f-45be-983c-7cff21a1f53a
  spec:
    sourcePod: network-check-source-8894fc9bd-g56dv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T22:33:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.286968ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 2.907227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:33:26Z"
    - latency: 917.668µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 1.805564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:32:26Z"
    - latency: 1.105017ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 2.053586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:31:26Z"
    - latency: 839.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 2.150602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:30:26Z"
    - latency: 793.263µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T22:29:26Z"
    - latency: 1.693598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T22:29:26Z"
kind: List
metadata:
  resourceVersion: ""