apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "21246"
    uid: 66f529c7-8885-42b1-809b-a255c04926d6
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:21:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 832.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:21:57Z"
    - latency: 1.094987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:20:57Z"
    - latency: 1.333924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:19:57Z"
    - latency: 1.209262ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:18:57Z"
    - latency: 990.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:17:57Z"
    - latency: 931.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:16:57Z"
    - latency: 1.063306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "26134"
    uid: 6b0eda10-f5e9-4c4c-935a-82fbd171980d
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:20:57Z"
      message: 'load-balancer-api-external: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.482119ms
      message: 'load-balancer-api-external: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:57Z"
    - latency: 6.680355ms
      message: 'load-balancer-api-external: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:26:57Z"
    - latency: 5.703191ms
      message: 'load-balancer-api-external: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:57Z"
    - latency: 7.073008ms
      message: 'load-balancer-api-external: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:25:57Z"
    - latency: 6.965538ms
      message: 'load-balancer-api-external: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:57Z"
    - latency: 9.81546ms
      message: 'load-balancer-api-external: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:24:57Z"
    - latency: 5.142202ms
      message: 'load-balancer-api-external: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:57Z"
    - latency: 7.383082ms
      message: 'load-balancer-api-external: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:23:57Z"
    - latency: 3.727081ms
      message: 'load-balancer-api-external: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:57Z"
    - latency: 6.034385ms
      message: 'load-balancer-api-external: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:22:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "26135"
    uid: 2a406f36-1815-485e-972c-b88cf77aec43
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:20:57Z"
      message: 'load-balancer-api-internal: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.485549ms
      message: 'load-balancer-api-internal: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:57Z"
    - latency: 6.760856ms
      message: 'load-balancer-api-internal: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:26:57Z"
    - latency: 5.587291ms
      message: 'load-balancer-api-internal: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:57Z"
    - latency: 7.04242ms
      message: 'load-balancer-api-internal: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:25:57Z"
    - latency: 6.016209ms
      message: 'load-balancer-api-internal: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:57Z"
    - latency: 9.757317ms
      message: 'load-balancer-api-internal: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:24:57Z"
    - latency: 5.315055ms
      message: 'load-balancer-api-internal: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:57Z"
    - latency: 7.327812ms
      message: 'load-balancer-api-internal: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:23:57Z"
    - latency: 4.875772ms
      message: 'load-balancer-api-internal: tcp connection to aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:57Z"
    - latency: 6.0997ms
      message: 'load-balancer-api-internal: resolved host name aba2519c434a445a493d7a515d00da17-0df22fef57006b71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:22:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-network-check-target-ip-10-0-131-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "21243"
    uid: 818bf906-43af-41dc-a91d-7738ccda6bbb
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:21:57Z"
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02947ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:21:57Z"
    - latency: 1.41097ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:20:57Z"
    - latency: 920.629µs
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:19:57Z"
    - latency: 896.698µs
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:18:57Z"
    - latency: 910.338µs
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:17:57Z"
    - latency: 992.478µs
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:16:57Z"
    - latency: 1.253817ms
      message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-network-check-target-ip-10-0-134-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "21244"
    uid: f4f9fd42-85e0-4c43-8f29-7eac99aa5d7d
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:21:57Z"
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242632ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:21:57Z"
    - latency: 2.536454ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:20:57Z"
    - latency: 2.432583ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:19:57Z"
    - latency: 2.124255ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:18:57Z"
    - latency: 2.180254ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:17:57Z"
    - latency: 1.941789ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:16:57Z"
    - latency: 2.297188ms
      message: 'network-check-target-ip-10-0-134-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-network-check-target-ip-10-0-142-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "21245"
    uid: df0fe719-11f4-442e-aea9-851d755f5bc9
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:21:57Z"
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.970435ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:21:57Z"
    - latency: 1.894373ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:20:57Z"
    - latency: 2.078875ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:19:57Z"
    - latency: 1.686238ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:18:57Z"
    - latency: 1.849354ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:17:57Z"
    - latency: 1.989611ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:16:57Z"
    - latency: 1.896506ms
      message: 'network-check-target-ip-10-0-142-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:14:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-184-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-184.ec2.internal
      uid: c178f5c8-3703-4ca8-8463-00ff1b749083
    resourceVersion: "26133"
    uid: 8b9d59bf-3a03-40b5-b98e-07401f0069ea
  spec:
    sourcePod: network-check-source-56499946bc-wsxkq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:20:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:57Z"
    - latency: 1.989118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:26:57Z"
    - latency: 1.095284ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:57Z"
    - latency: 2.033504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:25:57Z"
    - latency: 822.15µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:57Z"
    - latency: 1.925506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:24:57Z"
    - latency: 774.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:57Z"
    - latency: 2.216021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:23:57Z"
    - latency: 1.080205ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:57Z"
    - latency: 1.734436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:22:57Z"
kind: List
metadata:
  resourceVersion: ""