apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12465"
    uid: 32eefbf7-418a-4bea-aaa8-18dc59323b1f
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:37:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:37:46Z"
    - latency: 1.053522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 1.21129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 963.78µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 990.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 996.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 1.428684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:31:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12051"
    uid: 5950e381-f773-4028-86ed-dcad8ebd6dc5
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:36:46Z"
      message: 'load-balancer-api-external: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.468117ms
      message: 'load-balancer-api-external: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 11.310628ms
      message: 'load-balancer-api-external: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 4.758612ms
      message: 'load-balancer-api-external: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 8.435099ms
      message: 'load-balancer-api-external: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 4.33963ms
      message: 'load-balancer-api-external: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 6.299497ms
      message: 'load-balancer-api-external: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 5.864407ms
      message: 'load-balancer-api-external: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 12.856767ms
      message: 'load-balancer-api-external: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 4.593478ms
      message: 'load-balancer-api-external: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 12.014426ms
      message: 'load-balancer-api-external: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:32:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12050"
    uid: a5cf86be-219a-49c3-a2f8-6ea5a51f7242
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:36:46Z"
      message: 'load-balancer-api-internal: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.386807ms
      message: 'load-balancer-api-internal: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 11.424173ms
      message: 'load-balancer-api-internal: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 4.739361ms
      message: 'load-balancer-api-internal: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 8.380087ms
      message: 'load-balancer-api-internal: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 4.619342ms
      message: 'load-balancer-api-internal: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 6.354052ms
      message: 'load-balancer-api-internal: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 5.992431ms
      message: 'load-balancer-api-internal: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 12.789259ms
      message: 'load-balancer-api-internal: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 4.816613ms
      message: 'load-balancer-api-internal: tcp connection to a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 11.985383ms
      message: 'load-balancer-api-internal: resolved host name a35e819e3ac5a4e7ea31d8afc0a36f02-717a88277d425e67.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:32:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-ip-10-0-130-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12462"
    uid: fa4de23b-43de-4d98-b88c-2a19b124566a
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:37:46Z"
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.195µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:37:46Z"
    - latency: 993.983µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 1.308202ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 1.05809ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 1.391608ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 1.385185ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 1.471284ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:31:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-ip-10-0-133-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12463"
    uid: da48e078-07e4-4a05-b57b-cc3431c547f4
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:37:46Z"
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.362683ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:37:46Z"
    - latency: 2.442496ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 2.082711ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 2.082288ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 2.055453ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 2.278675ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 2.429187ms
      message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:31:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-ip-10-0-138-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12464"
    uid: e7b05480-e258-43a9-adc0-ba400b7b2ca0
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:37:46Z"
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.174295ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:37:46Z"
    - latency: 2.196724ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 2.391683ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 2.204041ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 2.375549ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 2.543425ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 2.859285ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:31:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:30:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: 918edcf2-586c-4fcd-889c-a0b5f19f27cf
    resourceVersion: "12049"
    uid: d24e58d1-6834-4b4e-b38b-09a198350948
  spec:
    sourcePod: network-check-source-65bdbbff45-qfjlb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:36:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05389ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 1.732896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:36:46Z"
    - latency: 1.166884ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 2.116976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:35:46Z"
    - latency: 723.172µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 1.74254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:34:46Z"
    - latency: 718.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 2.306877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:33:46Z"
    - latency: 1.30569ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T14:32:46Z"
    - latency: 1.833191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T14:32:46Z"
kind: List
metadata:
  resourceVersion: ""