apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15457"
    uid: 31b9ec62-e87a-4871-a52e-d71355434723
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.346µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:54:36Z"
    - latency: 922.148µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 1.380977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 1.128596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 918.192µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 1.021712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 940.071µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15120"
    uid: e5efda28-3d88-4a16-902e-f845e1c45dc9
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:36Z"
      message: 'load-balancer-api-external: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.498113ms
      message: 'load-balancer-api-external: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 6.404494ms
      message: 'load-balancer-api-external: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 5.368762ms
      message: 'load-balancer-api-external: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 6.947215ms
      message: 'load-balancer-api-external: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 7.286018ms
      message: 'load-balancer-api-external: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 6.40223ms
      message: 'load-balancer-api-external: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 5.077534ms
      message: 'load-balancer-api-external: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 13.280323ms
      message: 'load-balancer-api-external: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 5.045678ms
      message: 'load-balancer-api-external: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 6.295131ms
      message: 'load-balancer-api-external: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:49:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15121"
    uid: 50ffec06-97a6-404f-9b04-d2213fa08eb3
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:36Z"
      message: 'load-balancer-api-internal: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.732049ms
      message: 'load-balancer-api-internal: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 6.437649ms
      message: 'load-balancer-api-internal: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 5.481646ms
      message: 'load-balancer-api-internal: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 6.87728ms
      message: 'load-balancer-api-internal: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 5.667409ms
      message: 'load-balancer-api-internal: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 6.428981ms
      message: 'load-balancer-api-internal: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 5.076552ms
      message: 'load-balancer-api-internal: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 13.186092ms
      message: 'load-balancer-api-internal: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 3.723051ms
      message: 'load-balancer-api-internal: tcp connection to a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 6.252601ms
      message: 'load-balancer-api-internal: resolved host name a7b6ed7097c41410abebdee0f3f95491-4fe1fb2fcdc3a6b1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:49:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-network-check-target-ip-10-0-129-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15456"
    uid: 0bf7d5da-e138-4307-b9e3-99f18ba745c1
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:36Z"
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.969981ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:54:36Z"
    - latency: 1.894423ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 1.945168ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 1.953769ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 2.082731ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 1.763723ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 2.050787ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-network-check-target-ip-10-0-136-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15455"
    uid: 12ab6100-64ab-4066-b1c0-f63187abfbf6
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:36Z"
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.114145ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:54:36Z"
    - latency: 1.976771ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 2.272274ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 2.029354ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 8.46008ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 2.004649ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 2.236429ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-network-check-target-ip-10-0-138-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15454"
    uid: 995d65ab-6511-4262-9406-cd4166c2fc7e
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:36Z"
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.046µs
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:54:36Z"
    - latency: 764.857µs
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 856.019µs
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 1.483995ms
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 825.918µs
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 904.174µs
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 1.346989ms
      message: 'network-check-target-ip-10-0-138-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-32-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-32.ec2.internal
      uid: a6d5e833-f079-49bd-95b1-01a4b6d13b6c
    resourceVersion: "15119"
    uid: 833293b6-7084-4c45-bf47-c2ae0850d77e
  spec:
    sourcePod: network-check-source-dbd9cf844-vmdzc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.484µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 1.860803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:53:36Z"
    - latency: 850.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 1.767177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:52:36Z"
    - latency: 877.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 1.488669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:51:36Z"
    - latency: 873.921µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 8.701373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:50:36Z"
    - latency: 839.492µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T13:49:36Z"
    - latency: 2.183663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T13:49:36Z"
kind: List
metadata:
  resourceVersion: ""