apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14436"
    uid: 8362a7c5-d98b-462b-a8bb-252887671e9c
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:30Z"
    - latency: 962.223µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 1.093716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 1.001955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 1.301834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 928.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 1.416102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14073"
    uid: a781c007-1f9f-4f01-b93d-f953e1d709db
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:30Z"
      message: 'load-balancer-api-external: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.95926ms
      message: 'load-balancer-api-external: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 8.589262ms
      message: 'load-balancer-api-external: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 4.063035ms
      message: 'load-balancer-api-external: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 12.506448ms
      message: 'load-balancer-api-external: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 5.445865ms
      message: 'load-balancer-api-external: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 8.790234ms
      message: 'load-balancer-api-external: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 5.426946ms
      message: 'load-balancer-api-external: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 7.930376ms
      message: 'load-balancer-api-external: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 3.572571ms
      message: 'load-balancer-api-external: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 7.830846ms
      message: 'load-balancer-api-external: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:40:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14074"
    uid: 87da50e9-c752-4beb-8c8a-dfae8558b600
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:30Z"
      message: 'load-balancer-api-internal: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.942371ms
      message: 'load-balancer-api-internal: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 8.67969ms
      message: 'load-balancer-api-internal: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 4.737678ms
      message: 'load-balancer-api-internal: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 12.171851ms
      message: 'load-balancer-api-internal: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 5.44662ms
      message: 'load-balancer-api-internal: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 8.86648ms
      message: 'load-balancer-api-internal: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 4.747776ms
      message: 'load-balancer-api-internal: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 8.022699ms
      message: 'load-balancer-api-internal: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 5.322603ms
      message: 'load-balancer-api-internal: tcp connection to acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 7.752229ms
      message: 'load-balancer-api-internal: resolved host name acf01ca3b756149e2bfcc0eaf54a4f10-7bb7f1e278236bf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:40:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-132-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14435"
    uid: 08fb16a6-bc19-41d2-a54d-de79ae1f1d75
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:30Z"
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.940669ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:30Z"
    - latency: 1.915438ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 1.897525ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 1.811789ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 2.096926ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 1.923383ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 2.047835ms
      message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-134-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14433"
    uid: 246c648c-9640-4e30-84ec-6aba856b0575
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:30Z"
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 853.674µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:30Z"
    - latency: 868.471µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 881.454µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 888.391µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 1.469337ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 1.220812ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 1.308362ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-138-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14434"
    uid: b15acd9e-24b4-4872-b2d6-fcb878d76097
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:30Z"
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.347736ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:30Z"
    - latency: 2.349624ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 2.259735ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 2.137926ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 2.143733ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 2.289213ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 2.412444ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: 007cf8b3-a377-402d-84f5-85d9675cb64c
    resourceVersion: "14072"
    uid: 942c369e-3a6c-47cb-a483-af9579b15fda
  spec:
    sourcePod: network-check-source-869dcfcdcd-57xpc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 1.902867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:44:30Z"
    - latency: 893.29µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 2.005144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:43:30Z"
    - latency: 1.098856ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 1.991715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:42:30Z"
    - latency: 911.056µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 2.032722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:41:30Z"
    - latency: 897.008µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:30Z"
    - latency: 1.664918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:40:30Z"
kind: List
metadata:
  resourceVersion: ""