apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "23738"
    uid: 27ca8a3c-d950-4c86-ad7e-bcb676c3733c
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:48:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:48:04Z"
    - latency: 1.071595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 1.328907ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 971.938µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 977.741µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 1.441672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 992.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "22399"
    uid: b099a5a4-8dc1-4efb-9aa1-220080fd4f8b
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:47:04Z"
      message: 'load-balancer-api-external: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.693963ms
      message: 'load-balancer-api-external: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 6.641147ms
      message: 'load-balancer-api-external: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 5.69401ms
      message: 'load-balancer-api-external: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 8.576442ms
      message: 'load-balancer-api-external: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 5.779428ms
      message: 'load-balancer-api-external: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 5.854164ms
      message: 'load-balancer-api-external: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 5.137453ms
      message: 'load-balancer-api-external: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 6.595374ms
      message: 'load-balancer-api-external: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 5.33755ms
      message: 'load-balancer-api-external: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 10.467532ms
      message: 'load-balancer-api-external: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:43:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "22398"
    uid: 4d1cac22-3245-49b1-915d-5d779e381bd7
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:47:04Z"
      message: 'load-balancer-api-internal: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.296528ms
      message: 'load-balancer-api-internal: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 6.584334ms
      message: 'load-balancer-api-internal: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 4.532297ms
      message: 'load-balancer-api-internal: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 8.315725ms
      message: 'load-balancer-api-internal: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 5.898672ms
      message: 'load-balancer-api-internal: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 5.815918ms
      message: 'load-balancer-api-internal: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 5.140094ms
      message: 'load-balancer-api-internal: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 6.681701ms
      message: 'load-balancer-api-internal: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 4.697244ms
      message: 'load-balancer-api-internal: tcp connection to a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 10.598ms
      message: 'load-balancer-api-internal: resolved host name a0ec55def9e194d9cbab20b4234a04b0-81965bc7108b2db4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:43:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-network-check-target-ip-10-0-141-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "23736"
    uid: 5c2a23b9-a84b-4d85-ba5d-931c16846e8f
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:48:04Z"
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.299023ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:48:04Z"
    - latency: 2.519716ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 2.797014ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 2.395544ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 2.817543ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 2.306844ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 2.391208ms
      message: 'network-check-target-ip-10-0-141-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-network-check-target-ip-10-0-142-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "23737"
    uid: ca937c2a-9439-4cbb-8d2f-7dce8abbe816
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:48:04Z"
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400855ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:48:04Z"
    - latency: 2.606495ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 2.464406ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 2.587865ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 2.137057ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 2.008955ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 1.898312ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-network-check-target-ip-10-0-142-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "23735"
    uid: 632ee19a-88b4-449a-a133-92c84017f284
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:48:04Z"
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.98µs
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:48:04Z"
    - latency: 1.375121ms
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 1.245585ms
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 1.417315ms
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 1.480113ms
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 1.738525ms
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 1.17001ms
      message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-69-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-69.ec2.internal
      uid: f52ab54b-4918-4e13-8af8-10454884b7e6
    resourceVersion: "22397"
    uid: 7e0ddd9a-bf5e-468e-beb1-59b711fe6187
  spec:
    sourcePod: network-check-source-7f44b6dd87-49hp2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:47:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063429ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 1.713555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:47:04Z"
    - latency: 942.75µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 2.099447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:46:04Z"
    - latency: 1.194766ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 1.746453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:45:04Z"
    - latency: 899.731µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 1.774227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:44:04Z"
    - latency: 789.253µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:43:04Z"
    - latency: 1.916715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:43:04Z"
kind: List
metadata:
  resourceVersion: ""