apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "14337"
    uid: e4d0ae19-e3e4-4f0b-8b10-282832924db4
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:17:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:34Z"
    - latency: 1.048405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 1.048862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 1.05776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 936.907µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 942.229µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 2.545631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:11:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "13850"
    uid: 1096abb3-ceaf-4f86-8bb9-5cb6dfe39d30
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:16:34Z"
      message: 'load-balancer-api-external: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.04198ms
      message: 'load-balancer-api-external: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 7.661047ms
      message: 'load-balancer-api-external: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 5.158057ms
      message: 'load-balancer-api-external: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 8.157392ms
      message: 'load-balancer-api-external: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 5.07786ms
      message: 'load-balancer-api-external: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 6.792925ms
      message: 'load-balancer-api-external: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 4.480916ms
      message: 'load-balancer-api-external: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 7.511986ms
      message: 'load-balancer-api-external: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 4.935227ms
      message: 'load-balancer-api-external: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 7.118845ms
      message: 'load-balancer-api-external: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:12:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "13849"
    uid: 7c4f1205-fe15-4070-9fc7-50d1b94ee1f8
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:16:34Z"
      message: 'load-balancer-api-internal: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.760932ms
      message: 'load-balancer-api-internal: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 7.652997ms
      message: 'load-balancer-api-internal: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 5.176827ms
      message: 'load-balancer-api-internal: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 8.106472ms
      message: 'load-balancer-api-internal: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 5.064945ms
      message: 'load-balancer-api-internal: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 6.771851ms
      message: 'load-balancer-api-internal: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 4.46201ms
      message: 'load-balancer-api-internal: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 7.484371ms
      message: 'load-balancer-api-internal: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 4.32322ms
      message: 'load-balancer-api-internal: tcp connection to a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 7.06959ms
      message: 'load-balancer-api-internal: resolved host name a1dd4a370a4c54f30ace9881a3eb145e-d9078af8670811a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:12:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-network-check-target-ip-10-0-131-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "14334"
    uid: 36996773-07b7-413b-ac58-395d76b11343
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:17:34Z"
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.371µs
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:34Z"
    - latency: 1.014258ms
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 1.481335ms
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 963.022µs
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 1.080732ms
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 826.037µs
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 1.838835ms
      message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:11:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-network-check-target-ip-10-0-135-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "14336"
    uid: 6dffc376-adca-4575-b961-a99cb518f7e5
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:17:34Z"
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.482803ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:34Z"
    - latency: 2.265966ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 2.398358ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 2.078193ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 2.242443ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 2.451077ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 2.546914ms
      message: 'network-check-target-ip-10-0-135-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:11:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-network-check-target-ip-10-0-140-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "14335"
    uid: 5e3e0753-0546-4a36-ba62-9559bc414fcd
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:17:34Z"
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.271862ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:34Z"
    - latency: 2.674806ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 2.775155ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 2.239327ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 2.218063ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 1.960314ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 2.828458ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:11:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:10:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-131-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-131.ec2.internal
      uid: abf10f69-5a37-4261-b84b-687fd836ea23
    resourceVersion: "13845"
    uid: 5310785f-3e21-443e-a5c3-5432492fe63b
  spec:
    sourcePod: network-check-source-685456655f-6r9cs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:16:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.76µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 2.073145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:16:34Z"
    - latency: 902.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 1.760295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:15:34Z"
    - latency: 786.89µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 2.014796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:14:34Z"
    - latency: 949.869µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 1.737153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:13:34Z"
    - latency: 811.273µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:12:34Z"
    - latency: 1.798188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:12:34Z"
kind: List
metadata:
  resourceVersion: ""