apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "11183"
    uid: d007c979-20b2-4d8d-8cb9-c6f039ba521b
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "14262"
    uid: 9b52614f-dc33-4d78-bcf1-6609a97e8074
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:36:31Z"
      message: 'load-balancer-api-external: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.014033ms
      message: 'load-balancer-api-external: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:31Z"
    - latency: 9.103013ms
      message: 'load-balancer-api-external: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:36:31Z"
    - latency: 4.880585ms
      message: 'load-balancer-api-external: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:31Z"
    - latency: 7.787431ms
      message: 'load-balancer-api-external: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:35:31Z"
    - latency: 4.070641ms
      message: 'load-balancer-api-external: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:31Z"
    - latency: 8.334527ms
      message: 'load-balancer-api-external: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:34:31Z"
    - latency: 3.725083ms
      message: 'load-balancer-api-external: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:33:31Z"
    - latency: 7.996015ms
      message: 'load-balancer-api-external: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:33:31Z"
    - latency: 3.867043ms
      message: 'load-balancer-api-external: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:32:31Z"
    - latency: 12.235917ms
      message: 'load-balancer-api-external: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:32:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "14263"
    uid: 351aa964-9b17-42cc-ad8a-ece310ec8514
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:36:31Z"
      message: 'load-balancer-api-internal: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.94771ms
      message: 'load-balancer-api-internal: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:31Z"
    - latency: 9.13408ms
      message: 'load-balancer-api-internal: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:36:31Z"
    - latency: 5.373739ms
      message: 'load-balancer-api-internal: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:31Z"
    - latency: 7.774707ms
      message: 'load-balancer-api-internal: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:35:31Z"
    - latency: 4.796796ms
      message: 'load-balancer-api-internal: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:31Z"
    - latency: 8.370288ms
      message: 'load-balancer-api-internal: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:34:31Z"
    - latency: 3.709376ms
      message: 'load-balancer-api-internal: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:33:31Z"
    - latency: 8.050275ms
      message: 'load-balancer-api-internal: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:33:31Z"
    - latency: 3.835709ms
      message: 'load-balancer-api-internal: tcp connection to a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:32:31Z"
    - latency: 12.266366ms
      message: 'load-balancer-api-internal: resolved host name a9bd62e222ea245e5847975f2364a53b-594782334e4d01b5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:32:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-network-check-target-ip-10-0-132-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "11182"
    uid: ab1e4b5e-555c-4490-9c7c-dbbb972c2c6c
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-network-check-target-ip-10-0-133-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "11179"
    uid: 0ef2f558-42fc-47e7-a301-5b05ac849c44
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-network-check-target-ip-10-0-134-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "11181"
    uid: df95f6cb-8c3d-4d14-bc82-248ce91177f8
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:30:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-130-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-130.ec2.internal
      uid: b401c7cf-2535-4ef5-95ae-3cca430adae3
    resourceVersion: "14261"
    uid: 2e47201b-7932-407a-8f85-713d023b972f
  spec:
    sourcePod: network-check-source-dbd9cf844-5fbml
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:36:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.957µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:31Z"
    - latency: 2.32947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:36:31Z"
    - latency: 1.348986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:31Z"
    - latency: 1.776164ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:35:31Z"
    - latency: 889.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:31Z"
    - latency: 1.913497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:34:31Z"
    - latency: 845.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:33:31Z"
    - latency: 2.044535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:33:31Z"
    - latency: 902.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:32:31Z"
    - latency: 1.891697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:32:31Z"
kind: List
metadata:
  resourceVersion: ""