apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14910"
    uid: 3ff346c0-2a35-475f-ba41-297e7ee70928
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:35Z"
    - latency: 956.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 1.2502ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 1.124421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 901.928µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 953.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 974.962µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14554"
    uid: f86c8e0a-1603-4b5e-a353-0320c1a9aa94
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:35Z"
      message: 'load-balancer-api-external: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.808415ms
      message: 'load-balancer-api-external: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 6.861939ms
      message: 'load-balancer-api-external: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 11.300854ms
      message: 'load-balancer-api-external: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 7.586521ms
      message: 'load-balancer-api-external: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 5.192713ms
      message: 'load-balancer-api-external: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 6.673782ms
      message: 'load-balancer-api-external: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 4.557986ms
      message: 'load-balancer-api-external: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 12.485488ms
      message: 'load-balancer-api-external: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 5.040369ms
      message: 'load-balancer-api-external: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 7.961196ms
      message: 'load-balancer-api-external: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14555"
    uid: eb76baad-8417-450b-a2fe-2265faad0831
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:35Z"
      message: 'load-balancer-api-internal: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.935807ms
      message: 'load-balancer-api-internal: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 6.837815ms
      message: 'load-balancer-api-internal: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 4.500758ms
      message: 'load-balancer-api-internal: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 7.676514ms
      message: 'load-balancer-api-internal: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 4.628068ms
      message: 'load-balancer-api-internal: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 6.655802ms
      message: 'load-balancer-api-internal: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 4.624236ms
      message: 'load-balancer-api-internal: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 12.414701ms
      message: 'load-balancer-api-internal: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 4.209265ms
      message: 'load-balancer-api-internal: tcp connection to a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 8.063794ms
      message: 'load-balancer-api-internal: resolved host name a96fa956e95df4880b401d93b8a1ac51-27a348da7292d8c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-133-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14908"
    uid: 295df3aa-4c98-4871-8e27-c16734d21d60
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:35Z"
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.240677ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:35Z"
    - latency: 2.225038ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 2.189609ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 11.956255ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 2.163209ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 2.134027ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 2.553486ms
      message: 'network-check-target-ip-10-0-133-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-138-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14907"
    uid: ba7ae665-4053-43f6-a1d9-a140d6c9a196
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:35Z"
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.643µs
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:35Z"
    - latency: 850.951µs
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 1.172304ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 1.263789ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 7.411259ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 1.467321ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 1.184533ms
      message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-143-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14909"
    uid: 9d7bb28d-d814-4cdc-a18c-0e371d74e65c
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:09:35Z"
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275463ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:09:35Z"
    - latency: 1.903515ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 2.0524ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 2.195254ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 7.135241ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 2.177195ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 1.939368ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-131-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-131.ec2.internal
      uid: c9c07a71-39a0-4322-9fd8-e21958b5094c
    resourceVersion: "14553"
    uid: de0bd1b2-e752-4367-afde-134f427e197e
  spec:
    sourcePod: network-check-source-7d88cb55d8-vlxp9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.26336ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 1.771634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:08:35Z"
    - latency: 951.784µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 1.920347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:35Z"
    - latency: 843.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 1.885319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:35Z"
    - latency: 872.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 7.111971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:35Z"
    - latency: 976.941µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:35Z"
    - latency: 1.828248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:35Z"
kind: List
metadata:
  resourceVersion: ""