apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "11339"
    uid: 485b73ab-6ff2-452a-9444-d3a396c0bd16
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "15149"
    uid: 6c7f4dbc-279c-4f30-a175-4c40e1e889e9
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T06:29:12Z"
      message: 'load-balancer-api-external: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.078266ms
      message: 'load-balancer-api-external: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:29:12Z"
    - latency: 8.457822ms
      message: 'load-balancer-api-external: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:29:12Z"
    - latency: 4.935175ms
      message: 'load-balancer-api-external: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:28:12Z"
    - latency: 6.957859ms
      message: 'load-balancer-api-external: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:28:12Z"
    - latency: 4.61212ms
      message: 'load-balancer-api-external: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:27:12Z"
    - latency: 8.592725ms
      message: 'load-balancer-api-external: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:27:12Z"
    - latency: 3.429204ms
      message: 'load-balancer-api-external: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:26:12Z"
    - latency: 6.289676ms
      message: 'load-balancer-api-external: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:26:12Z"
    - latency: 4.029054ms
      message: 'load-balancer-api-external: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:25:12Z"
    - latency: 5.849891ms
      message: 'load-balancer-api-external: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:25:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "15148"
    uid: be97e5e4-f833-428a-b7b4-adab2a372bf5
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T06:29:12Z"
      message: 'load-balancer-api-internal: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.097077ms
      message: 'load-balancer-api-internal: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:29:12Z"
    - latency: 8.507548ms
      message: 'load-balancer-api-internal: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:29:12Z"
    - latency: 4.9963ms
      message: 'load-balancer-api-internal: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:28:12Z"
    - latency: 6.899727ms
      message: 'load-balancer-api-internal: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:28:12Z"
    - latency: 4.856739ms
      message: 'load-balancer-api-internal: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:27:12Z"
    - latency: 8.654267ms
      message: 'load-balancer-api-internal: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:27:12Z"
    - latency: 3.489462ms
      message: 'load-balancer-api-internal: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:26:12Z"
    - latency: 6.247728ms
      message: 'load-balancer-api-internal: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:26:12Z"
    - latency: 4.013747ms
      message: 'load-balancer-api-internal: tcp connection to affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:25:12Z"
    - latency: 6.010623ms
      message: 'load-balancer-api-internal: resolved host name affc00ef30f4e490e8fbdc685aa5d770-743a9e00a4435d77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:25:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-network-check-target-ip-10-0-135-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "11335"
    uid: 01d88425-fbd4-4601-8a6b-9781833d70ea
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-network-check-target-ip-10-0-136-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "11338"
    uid: 286f4305-1b13-476c-817f-b03d5e31026c
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-network-check-target-ip-10-0-142-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "11336"
    uid: 5d14c2e3-9768-4fbd-96c6-b221907bd244
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T06:23:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-229-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-229.ec2.internal
      uid: 4d2a5211-37c7-4657-9302-2eee40f1e615
    resourceVersion: "15147"
    uid: 9af87080-e638-4e3b-9151-ea367b32ac77
  spec:
    sourcePod: network-check-source-6f8b768455-lpqh8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T06:29:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:29:12Z"
    - latency: 3.176228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:29:12Z"
    - latency: 1.084195ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:28:12Z"
    - latency: 2.153979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:28:12Z"
    - latency: 1.112803ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:27:12Z"
    - latency: 2.201047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:27:12Z"
    - latency: 997.49µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:26:12Z"
    - latency: 1.810095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:26:12Z"
    - latency: 846.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T06:25:12Z"
    - latency: 1.55757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T06:25:12Z"
kind: List
metadata:
  resourceVersion: ""