apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "21753"
    uid: 1af3d7b8-239b-4fff-9f1e-ba06d6d1840b
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:32:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.419676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:32:38Z"
    - latency: 996.009µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 812.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 1.142513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 930.636µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 1.144402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 895.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "20756"
    uid: c25d2485-0b80-4848-94cf-df7b12264c8c
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:31:38Z"
      message: 'load-balancer-api-external: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.316764ms
      message: 'load-balancer-api-external: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 8.047299ms
      message: 'load-balancer-api-external: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 4.985817ms
      message: 'load-balancer-api-external: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 9.562297ms
      message: 'load-balancer-api-external: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 5.96254ms
      message: 'load-balancer-api-external: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 9.560461ms
      message: 'load-balancer-api-external: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 5.697669ms
      message: 'load-balancer-api-external: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 8.227423ms
      message: 'load-balancer-api-external: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 7.995157ms
      message: 'load-balancer-api-external: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 6.821058ms
      message: 'load-balancer-api-external: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:27:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "20757"
    uid: 877fd306-44e0-49a0-96c6-53a4b207df3c
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:31:38Z"
      message: 'load-balancer-api-internal: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.52846ms
      message: 'load-balancer-api-internal: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 8.085675ms
      message: 'load-balancer-api-internal: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 4.400262ms
      message: 'load-balancer-api-internal: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 9.509475ms
      message: 'load-balancer-api-internal: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 6.059613ms
      message: 'load-balancer-api-internal: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 9.665382ms
      message: 'load-balancer-api-internal: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 5.682627ms
      message: 'load-balancer-api-internal: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 8.157019ms
      message: 'load-balancer-api-internal: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 4.078756ms
      message: 'load-balancer-api-internal: tcp connection to a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 6.699123ms
      message: 'load-balancer-api-internal: resolved host name a5175592df2994387b08d79c3f3ae1f1-94453e17096bd7cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:27:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-network-check-target-ip-10-0-136-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "21752"
    uid: de7052f9-2ab4-401a-96e4-e86e27e7ed7c
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:32:38Z"
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.512274ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:32:38Z"
    - latency: 2.415065ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 2.310712ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 3.638376ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 2.261408ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 2.33325ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 2.383742ms
      message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-network-check-target-ip-10-0-138-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "21750"
    uid: a356bb5b-06ba-4b09-9426-619e4f85dd95
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:32:38Z"
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.308446ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:32:38Z"
    - latency: 1.223928ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 1.360883ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 1.757356ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 1.051247ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 976.087µs
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 1.115406ms
      message: 'network-check-target-ip-10-0-138-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-network-check-target-ip-10-0-142-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "21751"
    uid: 0124c699-6883-4bae-aee2-cb9c39303e83
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:32:38Z"
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.473727ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:32:38Z"
    - latency: 2.184131ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 2.360685ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 2.53525ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 2.172445ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 2.072757ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 2.18719ms
      message: 'network-check-target-ip-10-0-142-239: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-189.ec2.internal
      uid: a3f05e1e-4462-4ea1-a850-2d3722442792
    resourceVersion: "20755"
    uid: ab464a14-9caa-4501-ad32-754a7d1d02c9
  spec:
    sourcePod: network-check-source-989f8b8dc-8dmps
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:31:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 1.67153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:31:38Z"
    - latency: 1.067048ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 1.675889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:30:38Z"
    - latency: 1.558577ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 2.492567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:29:38Z"
    - latency: 898.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 1.672929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:28:38Z"
    - latency: 1.044201ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:27:38Z"
    - latency: 1.719733ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:27:38Z"
kind: List
metadata:
  resourceVersion: ""