apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "15307"
    uid: a740fd45-de05-44ea-9a6f-31241b4a2745
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:00:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.747µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:00:05Z"
    - latency: 1.016123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 886.184µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 889.984µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 993.828µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 1.151091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 927.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "14929"
    uid: 621d3998-3de8-4df7-bb0d-fbfd6ed02a1f
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T10:59:05Z"
      message: 'load-balancer-api-external: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.089226ms
      message: 'load-balancer-api-external: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 9.59641ms
      message: 'load-balancer-api-external: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 4.248818ms
      message: 'load-balancer-api-external: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 10.241281ms
      message: 'load-balancer-api-external: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 5.1677ms
      message: 'load-balancer-api-external: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 11.516016ms
      message: 'load-balancer-api-external: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 3.653379ms
      message: 'load-balancer-api-external: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 11.305947ms
      message: 'load-balancer-api-external: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 4.559076ms
      message: 'load-balancer-api-external: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 7.757991ms
      message: 'load-balancer-api-external: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:55:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "14928"
    uid: 9a52ef0e-3b90-4597-a74f-fa709a2e4278
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T10:59:05Z"
      message: 'load-balancer-api-internal: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.27055ms
      message: 'load-balancer-api-internal: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 9.725446ms
      message: 'load-balancer-api-internal: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 4.122ms
      message: 'load-balancer-api-internal: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 10.214383ms
      message: 'load-balancer-api-internal: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 5.151485ms
      message: 'load-balancer-api-internal: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 11.63847ms
      message: 'load-balancer-api-internal: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 5.036869ms
      message: 'load-balancer-api-internal: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 11.394805ms
      message: 'load-balancer-api-internal: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 4.538065ms
      message: 'load-balancer-api-internal: tcp connection to a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 7.681025ms
      message: 'load-balancer-api-internal: resolved host name a67c5191527174b69958ec69ec07ab15-f8cda15f61a4c87d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:55:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-network-check-target-ip-10-0-128-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "15305"
    uid: 40943b8b-3224-4cba-b45a-695affb2ba0b
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:00:05Z"
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376445ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:00:05Z"
    - latency: 2.125093ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 2.403142ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 1.98384ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 4.013192ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 2.397984ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 2.313548ms
      message: 'network-check-target-ip-10-0-128-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-network-check-target-ip-10-0-138-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "15304"
    uid: 23cbba89-89ce-4a47-a397-6f96a70a47cd
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:00:05Z"
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.476548ms
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:00:05Z"
    - latency: 986.515µs
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 791.947µs
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 800.154µs
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 1.302234ms
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 1.477514ms
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 1.106686ms
      message: 'network-check-target-ip-10-0-138-107: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-network-check-target-ip-10-0-140-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "15306"
    uid: 4be863ba-00bd-4bce-ae1b-3dd07dd67d24
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:00:05Z"
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.424232ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:00:05Z"
    - latency: 2.439286ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 2.068068ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 2.137249ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 2.345632ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 1.985247ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 2.210387ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T10:53:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-107-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-107.ec2.internal
      uid: aecb8358-e7bb-4df5-872f-3213561016b8
    resourceVersion: "14927"
    uid: ce000a85-b973-4e20-8d2a-38f303767a46
  spec:
    sourcePod: network-check-source-dbd9cf844-fs92f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T10:59:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 734.002µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 1.70714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:59:05Z"
    - latency: 763.687µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 2.902495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:58:05Z"
    - latency: 766.09µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 1.653499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:57:05Z"
    - latency: 834.309µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 1.578562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:56:05Z"
    - latency: 871.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T10:55:05Z"
    - latency: 1.535185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T10:55:05Z"
kind: List
metadata:
  resourceVersion: ""