apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "13346"
    uid: f97ad976-0bdc-4aa8-915c-75102ba7611d
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:46:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.074949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:46:19Z"
    - latency: 878.244µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 1.121107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 931.948µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 1.308866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 1.067255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 1.075231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "12266"
    uid: f043d8d3-cfa9-476e-91be-b95460c2b56e
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:45:19Z"
      message: 'load-balancer-api-external: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.434689ms
      message: 'load-balancer-api-external: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 5.923702ms
      message: 'load-balancer-api-external: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 17.273898ms
      message: 'load-balancer-api-external: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 6.821686ms
      message: 'load-balancer-api-external: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 17.983285ms
      message: 'load-balancer-api-external: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 6.693064ms
      message: 'load-balancer-api-external: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 18.770539ms
      message: 'load-balancer-api-external: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 6.629074ms
      message: 'load-balancer-api-external: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 17.339482ms
      message: 'load-balancer-api-external: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 6.595645ms
      message: 'load-balancer-api-external: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "12264"
    uid: d22ecdf2-94bb-4860-8388-8be2c929b273
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:45:19Z"
      message: 'load-balancer-api-internal: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.86076ms
      message: 'load-balancer-api-internal: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 5.872991ms
      message: 'load-balancer-api-internal: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 15.640415ms
      message: 'load-balancer-api-internal: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 6.881097ms
      message: 'load-balancer-api-internal: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 18.285246ms
      message: 'load-balancer-api-internal: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 6.657176ms
      message: 'load-balancer-api-internal: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 18.719796ms
      message: 'load-balancer-api-internal: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 6.689021ms
      message: 'load-balancer-api-internal: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 15.610316ms
      message: 'load-balancer-api-internal: tcp connection to ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 6.511486ms
      message: 'load-balancer-api-internal: resolved host name ab8305aae35d54c2e98cca320cc71cea-c5ebbb407277f522.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-network-check-target-ip-10-0-134-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "13345"
    uid: ac364935-4215-4b83-a573-ff7197354de3
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:46:19Z"
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.101604ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:46:19Z"
    - latency: 2.359432ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 2.293055ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 1.96852ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 2.222551ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 2.204176ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 2.287994ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-network-check-target-ip-10-0-136-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "13343"
    uid: 1f7ccce5-e473-4e5a-a5fe-5186638566ef
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:46:19Z"
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.323008ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:46:19Z"
    - latency: 2.304765ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 2.30334ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 2.213918ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 2.691477ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 2.105344ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 2.607503ms
      message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-network-check-target-ip-10-0-138-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "13344"
    uid: 19c56d88-b4f7-4b3e-aaf6-56fb50e20069
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:46:19Z"
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.087µs
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:46:19Z"
    - latency: 819.035µs
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 1.570737ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 907.41µs
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 945.358µs
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 1.301326ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 1.117446ms
      message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T13:39:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-121.ec2.internal
      uid: 02b11429-cd17-4f42-9fa4-093400c4c2e8
    resourceVersion: "12260"
    uid: e9f6e103-5caa-44ca-bfc2-eea968c55700
  spec:
    sourcePod: network-check-source-6f78d59f99-tdqnq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T13:45:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 841.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 1.63502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:45:19Z"
    - latency: 916.493µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 2.354774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:44:19Z"
    - latency: 889.122µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 1.963547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:43:19Z"
    - latency: 1.124064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 1.763605ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:42:19Z"
    - latency: 893.187µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T13:41:19Z"
    - latency: 1.914501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T13:41:19Z"
kind: List
metadata:
  resourceVersion: ""